Changing path for OSGi configuration [message #203973] |
Thu, 30 November 2006 06:06  |
Eclipse User |
|
|
|
Originally posted by: oliver.zein.email.de
I need to change the location of the OSGi configuration files which is by
default /WEB-INF/platform/confguration.
This is necessary, because it runs in a Tomcat clustered environment and
the files in the webapps directory are not replicated. Right now I get an
error message that the file
WEB-INF\platform\configuration\org.eclipse.osgi\.manager\.fi leTableLock
can not be read.
I'm using the birt web-viewer under Tomcat 5.
Is this possible?
|
|
|
|
|
|
|
|
|
|
|
Re: Changing path for OSGi configuration [message #208605 is a reply to message #208183] |
Tue, 02 January 2007 04:08   |
Eclipse User |
|
|
|
Originally posted by: arne.degenring.com
Update: In the meantime, I did some more testing. Adding
"osgi.configuration.area.readOnly=true" to the
platform/configuration/config.ini did not have an effect. After setting it
as a JVM system parameter, only a log file and
org.eclipse.update/platform.xml still were written to the
platform/configuration dir. But, when I tried to execute reports, I
experienced a class loading error:
java.lang.ClassCastException: java.lang.NoClassDefFoundError
at
org.eclipse.birt.report.soapengine.processor.AbstractBaseCom ponentProcessor.process(AbstractBaseComponentProcessor.java: 115)
at
org.eclipse.birt.report.soapengine.endpoint.BirtSoapBindingI mpl.getUpdatedObjects(BirtSoapBindingImpl.java:66)
....
Maybe "osgi.configuration.area" could be used to move the whole
configuration directory away instead of setting it read-only, but I
haven't tried it yet.
Regards,
--Arne
Arne Degenring wrote:
> Oliver Zein wrote:
>> I think the most important question is:
>> Does the web viewer need to write to any of the files under
>> WEB-INFplatformconfigurationorg.eclipse.osgi?
>>
>> If yes, that would be the problem. Because any change made
>> by one node is not visible to any of the other nodes in the
>> tomcat cluster.
> Oliver,
> the fact that the web viewer does by default write to the
> WEB-INF/platform/configuration directory is something I don't like either.
> I believe the written files are only some kind of cached OSGi plugin
> metadata, so I assume it wouldn't be a problem that the changes wouldn't
> be visible to other nodes.
> But anyway, in some production environments write access to the deployment
> directories might be disabled which would lead to problems. I started to
> experiment with the following setting that I added to the
> platform/configuration/config.ini file:
> osgi.configuration.area.readOnly=true
> Afterwards, nothing seems to be written to the configuration directory any
> more. Could anyone with deeper OSGi knowledge confirm, that adding this
> setting won't lead to problems?
> Thanks
> -- Arne
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05224 seconds