Restart due to timeout causes next conversion to be cancelled

[GoogleCodeExporter]

If a conversion is submitted just after the previous one has failed due to a 
timeout, it is likely to be cancelled by the PooledOfficeManager:

# PooledOfficeManager.java:52
                logger.warning("connection lost unexpectedly; attempting restart");
                if (currentTask != null) {
                    currentTask.cancel(true);
                }

The attached unit test allows to reproduce the problem.

Original issue reported on code.google.com by mguille...@yahoo.fr on 2 Dec 2011 at 11:12

Attachments:

• testjod.zip

[GoogleCodeExporter]

I'm seeing similar behavior as well.

Original comment by MaryAub...@gmail.com on 19 Apr 2012 at 5:29