7 replies [Last post]
tmackie
Offline
Joined: 2010-06-10

When trying to render a template, the RemoteConverterTerminus logs the following:

INFO | jvm 1 | 2010/05/05 13:26:13 | May 5, 2010 1:26:13 PM com.docmosis.util.logging.JavaLogger log
INFO | jvm 1 | 2010/05/05 13:26:13 | SEVERE: Unexpected error in doProcess
INFO | jvm 1 | 2010/05/05 13:26:13 | com.docmosis.document.converter.ConversionException: The document cannot be converted: could not be loaded (invalid/corrupt?). Setting property "docmosis.converter.file.preserveCorrupted" to "true" will preserve the file for analysis.
INFO | jvm 1 | 2010/05/05 13:26:13 | at com.docmosis.converter.openoffice.LocalOpenOfficeConverter.convertFile(line:263)
INFO | jvm 1 | 2010/05/05 13:26:13 | at com.docmosis.converter.openoffice.LocalOpenOfficeConverter.convert(line:194)
INFO | jvm 1 | 2010/05/05 13:26:13 | at com.docmosis.document.converter.RemoteConverterTerminus$2.run(line:147)
INFO | jvm 1 | 2010/05/05 13:26:13 | at java.lang.Thread.run(Thread.java:619)

Not rendering the template is fine, but the terminus will then fail to provide any converters (it appears to have crashed/hung). I was expecting a LocalOpenOfficeConverter. This is the log from the calling thread:

[#|2010-05-05T13:26:18.188+1000|WARNING|glassfishv3.0|com.docmosis.document.converter.pool.ConverterPoolGroup|_ThreadID=38;_ThreadName=Thread-2;|Waiting longer than configured warning period (5000 ms) to get a converter from group: remoteConverters. You might consider adding more converters to the pool.|#]
com.docmosis.document.converter.ConversionException: Unable to get a converter
Caused by: com.docmosis.document.converter.pool.ConverterPoolException: Took too long to get converter. Max wait is (ms):60000
at com.docmosis.document.converter.pool.ConverterPoolGroup.getConverterFromPool(line:134)
at com.docmosis.document.converter.pool.ConverterPool.getConverter(line:267)
at com.docmosis.document.converter.pool.ConverterPool.getConverter(line:176)

Is this expected behaviour? or have I failed to set some settings?

This is on RedHat Linux.

modman
Offline
Joined: 2010-11-25
Diagnostics

Hello TMackie.

Can you please:
1) say what version of Docmosis you are running
2) say what version of OpenOffice you are running
3) say whether any documents render any attempt fails
4) set "docmosis.converter.file.preserveCorrupted" to true in the script running the remote converter (or in the docmosis.properties file picked up by the script. This is indicated in the initial error logging as a suggestion and will leave any offending documents in the temp area for inspection. If the logs tell you a corrupt file has been preserved, can you get the specified file and email it to support@docmosis.com

Cheers.

tmackie
Offline
Joined: 2010-06-10
We are using docmosis 2.1.0,

We are using docmosis 2.1.0, OpenOffice 3.1.

Rendering documents usually works fine, however, if a user tries to render an invalid/dodgy/incorrect document, then the docmosis process errors and appears to hang. Subsequent rendering requests fail to retrieve a converter. Restarting the RemoteConverterTerminus results in all "normal" documents to render fine.

I've emailed the preserved file, and the originating file.

Thankyou for your help.

modman
Offline
Joined: 2010-11-25
Issues with OpenOffice 3.1 and 3.1.1
Hi tmackie. We are investigating the issue - thanks for the good diagnostics. Could you try (if easy) using OpenOffice 3.2? OpenOffice 3.1 and 3.1.1 have known issues with Docmosis which make them less desirable versions (see the Known Issues in the FAQ). Also, turning off the properties that write errors into the document will prove the failure is caused by bad documents. Set
  docmosis.analyzer.error.fatal=true
  docmosis.populator.error.fatal=true
See section 6.3 of the docmosis developer guide under Properties For Production for details about how and when to set these variables.
tmackie
Offline
Joined: 2010-06-10
Hi, We've upgraded OpenOffice

Hi,

We've upgraded OpenOffice to 3.2, and I set the settings in the docmosis.properties file.

The result is the same. Docmosis still crashes.

Thanks for your help.

admin
Offline
Joined: 2010-09-06
Info from new Properties

Hello TMackie.

Thanks for the diagnostics. These properties change the way Docmosis deals with errors. Did you get any exceptions which describe the failures?

tmackie
Offline
Joined: 2010-06-10
Hi Paul, The error logged

Hi Paul,

The error logged is:

Jun 4, 2010 1:52:32 PM com.docmosis.util.logging.JavaLogger log
WARNING: The document cannot be converted: could not be loaded (invalid/corrupt?). Corrupt file preserved on host:testserver.gbst.net in file /tmp/dmConvert21451138817005558.odt
Jun 4, 2010 1:52:32 PM com.docmosis.util.logging.JavaLogger log
SEVERE: Unexpected error in doProcess
com.docmosis.document.converter.ConversionException: The document cannot be converted: could not be loaded (invalid/corrupt?). Corrupt file preserved on host:testserver.gbst.net in file /tmp/dmConvert21451138817005558.odt
at com.docmosis.converter.openoffice.LocalOpenOfficeConverter.convertFiles(line:261)
at com.docmosis.converter.openoffice.LocalOpenOfficeConverter.convert(line:188)
at com.docmosis.document.converter.RemoteConverterTerminus$2.run(line:206)
at java.lang.Thread.run(Thread.java:619)

Cheers,

Terence

tmackie
Offline
Joined: 2010-06-10
New Release

Thankyou for the patch and release. The change has fixed the problem we were experiencing.

Your help has been much appreciated.