To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=66594
Issue #:|66594
Summary:|Problems with Windows File Length Limitation and Last
|Modified Data
Component:|distribution
Version:|OOo 2.0
Platform:|PC
URL:|
OS/Version:|All
Status:|NEW
Status whiteboard:|
Keywords:|
Resolution:|
Issue type:|DEFECT
Priority:|P3
Subcomponent:|www
Assigned to:|[EMAIL PROTECTED]
Reported by:|rkentgibson
------- Additional comments from [EMAIL PROTECTED] Tue Jun 20 07:10:11 -0700
2006 -------
We have had a group of problems which have hindered our ability to deliver an
openoffice application.
Unfortunately many of these are rather hard to reproduce ouside of our
environement and some aspects of the problem are not completely understood,
therefore some of this issues may be hard to reproduce.
These problems relate to a) weaknesses that windows has with file names over 256
characters and b) dependencies that openoffice has on the last modified date of
some of its resources.
Problem 1 - Directory to Deep
We have in a variety of cirumstances encountered problems when we choose to
distribute openoffice on windows when openoffice sits in a directory that is
"too deep". How deep that can be is variable as the location of the soffice.exe
and the user directory both play a role.
Below I will detail how to easily reproduce this problem and you will see that
the path length is reasonable. However I would like to point out that in certain
real world installations (ie sometimes the path is only a fraction of this
length) we get this failure.
Steps to reproduce (on Windows)
a) install openoffice in a directory
C:/OO12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789
of circa 92 characters ( the exes will be in
C:\OO23456789012345678901234567890123456789012345678901234567890123456789012345678901234567890\program)
b) start openoffice and define the user directory for example:
soffice
-env:UserInstallation=C:/OO23456789012345678901234567890123456789012345678901234567890123456789012345678901234567890/workspace/OO
c) you will get immediately this message:
"Configuration data in
file:///C:/OO23456789012345678901234567890123456789012345678901234567890123456789012345678901234567890/workspace/OO/user/uno_packages/cache/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBacken/registry/data/org/openoffice/Office/ProtocolHandler.xcu
is corrupted. Without this data some functions may not operate correctly.
Do you want to continue startup of OpenOffice.org without the corrupted
configuration data?"
What is interesting about this error message is that the length of the file in
the message is circa 256 characters, which is the windows limitation. Ok fair
enough. But this file will never exist (as far as I know). I believe that
OpenOffice has some sort of internal application server logic and that this is
some sort of soft reference to a file. I am just guessing but I reckon somewhere
somehow a condition is firing when the length is greater than 256 and then we
see this error, even though I believe the file will never exist in the file
system.
Problem 2- OpenOffice Date Dependencies
In order to deliver an OpenOffice solution we have checked in OpenOffice into
our CWS system. In the process of a build many things can happen with the last
modified date. For example eclipse just assigns the build date. OpenOffice is
very sensitive about this. It has been hard to isolate this problem, but as a
result we have created our own build script for openoffice which preserves the
last modified date. Furthermore, there is at least one file which is particulary
sensititve :
/share/registry/modules/org/openoffice/TypeDetection/Types/fcfg_xslt_types.xcu
if its last modified date is not accurate to the second and when our the path
length to soffice.exe is greater than about then 85 characters then we get this
error:
com.sun.star.document.CorruptedFilterConfigurationException: The filter
configuration appears to be defective. Please install the office suite again.
at
com.sun.star.lib.uno.environments.remote.Job.remoteUnoRequestRaisedException(Job.java:275)
at com.sun.star.lib.uno.environments.remote.Job.execute(Job.java:141)
at
com.sun.star.lib.uno.environments.remote.JobQueue.enter(JobQueue.java:377)
at
com.sun.star.lib.uno.environments.remote.JobQueue.enter(JobQueue.java:346)
at
com.sun.star.lib.uno.environments.remote.JavaThreadPool.enter(JavaThreadPool.java:106)
at
com.sun.star.lib.uno.bridges.java_remote.java_remote_bridge.sendRequest(java_remote_bridge.java:860)
at
com.sun.star.lib.uno.bridges.java_remote.java_remote_bridge.sendRequest(java_remote_bridge.java:809)
at
com.sun.star.lib.uno.bridges.java_remote.ProxyFactory$Handler.request(ProxyFactory.java:154)
at
com.sun.star.lib.uno.bridges.java_remote.ProxyFactory$Handler.invoke(ProxyFactory.java:140)
at $Proxy6.loadComponentFromURL(Unknown Source)
** IMPORTANT**
If I set the date of this file to a date that can only deduced by trial and
error, then it works.
I would like to understand why this is so in case we get any similiar problems
or we have problems when we upgrade to a new version.
thanks
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
