openmeetings-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Horvat (JIRA)" <j...@apache.org>
Subject [jira] [Created] (OPENMEETINGS-540) Uploading of .odt files
Date Thu, 21 Feb 2013 15:22:13 GMT
Martin Horvat created OPENMEETINGS-540:
------------------------------------------

             Summary: Uploading of .odt files
                 Key: OPENMEETINGS-540
                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-540
             Project: Openmeetings
          Issue Type: Bug
          Components: Import/Export
    Affects Versions: 2.0 Apache Incubator Release
         Environment: Linux OS Debian Wheezy
            Reporter: Martin Horvat
            Assignee: Maxim Solodovnik


In the currect SVN revision 1448588 of Openmeeting 2.0 I have problem uploading libreoffice
files to the rooms. By uploading of an .odt file i get Java errors (from openmeetings.log):

Feb 21, 2013 2:58:11 PM org.artofsolving.jodconverter.office.OfficeProcess start
INFO: starting process with acceptString 'socket,host=127.0.0.1,port=2002,tcpNoDelay=1' and
profileDir '/tmp/.jodconverter_socket_host-127.0.0.1_port-2002'
Feb 21, 2013 2:58:11 PM org.artofsolving.jodconverter.office.OfficeProcess start
INFO: started process; pid = 31250
Exception in thread "main" org.artofsolving.jodconverter.office.OfficeException: failed to
start and connect
        at org.artofsolving.jodconverter.office.ManagedOfficeProcess.startAndWait(ManagedOfficeProcess.java:64)
        at org.artofsolving.jodconverter.office.PooledOfficeManager.start(PooledOfficeManager.java:101)
        at org.artofsolving.jodconverter.office.ProcessPoolOfficeManager.start(ProcessPoolOfficeManager.java:62)
        at org.artofsolving.jodconverter.cli.Convert.main(Convert.java:112)
Caused by: java.util.concurrent.ExecutionException: org.artofsolving.jodconverter.office.OfficeException:
could not establish connection
        at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
        at java.util.concurrent.FutureTask.get(FutureTask.java:83)
        at org.artofsolving.jodconverter.office.ManagedOfficeProcess.startAndWait(ManagedOfficeProcess.java:62)
        ... 3 more
Caused by: org.artofsolving.jodconverter.office.OfficeException: could not establish connection
        at org.artofsolving.jodconverter.office.ManagedOfficeProcess.doStartProcessAndConnect(ManagedOfficeProcess.java:142)
        at org.artofsolving.jodconverter.office.ManagedOfficeProcess.access$000(ManagedOfficeProcess.java:31)
        at org.artofsolving.jodconverter.office.ManagedOfficeProcess$1.run(ManagedOfficeProcess.java:58)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
        at java.lang.Thread.run(Thread.java:662)
Caused by: org.artofsolving.jodconverter.office.OfficeException: office process died with
exit code 134
        at org.artofsolving.jodconverter.office.ManagedOfficeProcess$6.attempt(ManagedOfficeProcess.java:136)
        at org.artofsolving.jodconverter.office.Retryable.execute(Retryable.java:40)
        at org.artofsolving.jodconverter.office.Retryable.execute(Retryable.java:30)
        at org.artofsolving.jodconverter.office.ManagedOfficeProcess.doStartProcessAndConnect(ManagedOfficeProcess.java:120)
        ... 8 more
, command=[java, -Doffice.home=/usr/lib/libreoffice, -cp, /opt/jodconverter-core-3.0-beta-4/lib/commons-cli-1.1.jar,
-cp, /opt/jodconverter-core-3.0-beta-4/lib/jurt-3.2.1.jar, -cp, /opt/jodconverter-core-3.0-beta-4/lib/juh-3.2.1.jar,
-cp, /opt/jodconverter-core-3.0-beta-4/lib/json-20090211.jar, -cp, /opt/jodconverter-core-3.0-beta-4/lib/commons-io-1.4.jar,
-cp, /opt/jodconverter-core-3.0-beta-4/lib/unoil-3.2.1.jar, -cp, /opt/jodconverter-core-3.0-beta-4/lib/ridl-3.2.1.jar,
-cp, /opt/jodconverter-core-3.0-beta-4/lib/jodconverter-core-3.0-beta-4.jar, -jar, /opt/jodconverter-core-3.0-beta-4/lib/jodconverter-core-3.0-beta-4.jar,
/opt/openmeetings/used/dist/red5/webapps/openmeetings/uploadtemp/files/cb523c57833ca95d15a554dedbff141b.doc,
/opt/openmeetings/used/dist/red5/webapps/openmeetings/upload/files/cb523c57833ca95d15a554dedbff141b/cb523c57833ca95d15a554dedbff141b.pdf],
exitValue=1, out=}}, fileName=/opt/openmeetings/used/dist/red5/webapps/openmeetings/uploadtemp/files/cb523c57833ca95d15a554dedbff141b}
DEBUG 02-21 14:58:11.619 WhiteBoardService.java 86775 480 org.openmeetings.app.remote.WhiteBoardService
[NioProcessor-7] - startNewObjectSyncprocess: cb523c57833ca95d15a554dedbff141b.swf1361455091619

Manually this works, e.g:

java -Doffice.home=/usr/lib/libreoffice/ -jar /opt/jodconverter-core-3.0-beta-4/lib/jodconverter-core-3.0-beta-4.jar
t.odt t.pdf

The problems is present also in 2.1 (Revision: 1448638), but there no error dialog appears
and there almost no evidence of an problem in the logs, e.g. only this:

DEBUG 02-21 16:05:47.897 WhiteboardManager.java 2323580 57 org.apache.openmeetings.data.whiteboard.WhiteboardManager
[NioProcessor-13] - actionObject: [swf, http://rheia:5080/openmeetings/DownloadHandler?fileName=1884d5420346c0144532a4d830f1e852%2Eswf&moduleName=videoconf1&parentPath=%2F1884d5420346c0144532a4d830f1e852%2F&room_id=files&sid=d3aa62cebab593268c3a768a017fc2d9,
http://rheia:5080/openmeetings/DownloadHandler?fileName=1884d5420346c0144532a4d830f1e852%2Eswf&moduleName=videoconf1&parentPath=%2F1884d5420346c0144532a4d830f1e852%2F&room_id=files&sid=d3aa62cebab593268c3a768a017fc2d9,
1884d5420346c0144532a4d830f1e852.swf, videoconf1, /1884d5420346c0144532a4d830f1e852, files,
public, 1, 0, 0, 624, 425.3, 20, 624, 425.3, 100, 1884d5420346c0144532a4d830f1e852.swf1361459147772,
t.odt, true, 3, null, 0, 0, 0, 624, 425.3, swfpresentationobject_1361459147772]

The ability to debug decreased in version 2.1.

Could you suggest a solution.

Regards, Martin

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message