soffice.bin does not start on x64 Windows when using default install of Tomcat/Java

[GoogleCodeExporter]

What steps will reproduce the problem?
1. On a 64 bit Windows Operating System, install Tomcat in the default location 
(C:\Program Files (x86)\Apache Software 
Foundation\Tomcat 6.0\)
2. Make sure that the java settings in tomcat6w.exe contain the default url for 
java.io.tmpdir: C:\Program Files (x86)\Apache 
Software Foundation\Tomcat 6.0\temp\
3. Deploy a web app that runs the following code:

final DefaultOfficeManagerConfiguration config = new 
DefaultOfficeManagerConfiguration();
config.setPortNumber(34223);
OfficeManager officeManager = config.buildOfficeManager();
officeManager.start();

4. Start tomcat by manually running tomcat.exe.

What is the expected output? What do you see instead?
Instead of starting, the soffice.bin process throws an OpenOffice Fatal 
Exception GUI dialog referencing:

"C:\Program Files (x86)\Apache Software Foundation\Tomcat 
6.0\temp\.jodconverter_socket_host-127.0.0.1_port-
34423\user\uno_packages\cache\registry\com.sun.star.comp.deployment.configuratio
n.PackageRegistryBackend\registry\data\org\openoff
ice\Office\Recovery.xcu"

If you instead run the service using the services control panel, the error is 
squashed and the soffice.bin process starts but does 
not open the sockets so the connection attempt fails.

What version of the product are you using? On what operating system?
Compiled JODConverter from source in Sept.
Windows server x64 both 2003 and 2008.
Tomcat 6.0.20 & 6.0.24.
JRE 1.6.0u16-18 both 32 bit and x64.

Please provide any additional information below.

If you manually change the java.io.tmpdir to c:\tmpdir then it works. There 
must be something with the long file name that fails 
when running on an x64 system

This is a problem because it happens when using all the default install 
parameters for java/tomcat, and therefore has occurred on 
every install we have done on x64.

Original issue reported on code.google.com by sla...@gmail.com on 2 Feb 2010 at 7:39

[GoogleCodeExporter]

See http://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx#maxpath

Your workaround of changing tmpdir looks good to me. It's not an issue in the
JODConverter code and I don't see what we could do about this.

Original comment by mirko.na...@gmail.com on 15 May 2010 at 10:16

• Changed state: WontFix