Eclipse Community Forums: Equinox » multiple instances, osgi kernel stability issues

Help

Home

Home » Eclipse Projects » Equinox » multiple instances, osgi kernel stability issues

Show: Today's Messages :: Show Polls :: Message Navigator

multiple instances, osgi kernel stability issues [message #66503]

Fri, 12 May 2006 07:54

Erik Vanherck

Messages: 23
Registered: July 2009

Junior Member

Hi,

While testing our new RCP application package we are plagued by
intermittend and hard to reproduce exceptions in classloading,
statereader, statewriter, ... ranging from Nullpointers to
ClassNotFoundExceptions. Now it did not occur to me before but I think we
only get these errors when we have multiple instances running. For
instance our application contains a ui IPlatformRunnable and a server
IPlatformRunnable running in different jvms. So they share the same
configuration area with the same bundledata etc.

Could this present problems ? Especially with plugins that are lazy
started ? How come eclipse itself uses this setup and it keeps on working
then ?

The reason I ask is that some of these errors are quite severe and if this
should work properly then I need to start reporting bugs.

Report message to a moderator

Re: multiple instances, osgi kernel stability issues [message #66523 is a reply to message #66503]

Fri, 12 May 2006 07:55

Erik Vanherck

Messages: 23
Registered: July 2009

Junior Member

For the record, we are working with the RC's of eclipse 3.2

Report message to a moderator

Re: multiple instances, osgi kernel stability issues [message #66542 is a reply to message #66523]

Fri, 12 May 2006 08:24

Erik Vanherck

Messages: 23
Registered: July 2009

Junior Member

Some more information about the issues.

For the record our configuration area is clean and our workspaces are
created on startup so no stale data of old plugins or anything else. We
even have these issues on virtual machines which are restored from a fresh
windows installation each test run.

Most of the problems seem to occur concerning the lazy and state files,
those with the classloader issues I don't seem to find a common ground,
sometimes it seems that the manifests aren't read properly or in some
cases it simply can't open a plugin jar properly. Note that restarting the
application or trying some more sometimes magically solves stuff.

So my concern was looking at the configuration area. I know about the
-initialize option. We weren't doing this so I tried that but still errors
keep popping up. I looked at what data the -initialize option drops in the
configuration area and it does extract stuff in the org.eclipse.ogsi area
but only for the startup bundle.

We have many plugins that are run in the osgi way .. we start lots of
bundles lazy on demand when someone requests a service, we access the
bundles that implement these and start the bundle and then have them
register osgi services in their activators. This deviates a bit from the
eclipse container plugin mechanism so that may be the cause why we are
seeing so much problems.

Anyhow, I was looking in StateReader, StateWriter and such and they acess
files without syncing on a lock file for the multiple jvms .. isn't bound
to cause troubles ?

Report message to a moderator