My theory is that this is a client side problem and that the list of
dependencies in project.xml is different in the openejb itests and
geronimo and activemq itests. I haven't investigated yet though.
david jencks
On Oct 5, 2004, at 9:33 AM, David Blevins wrote:
On Tue, Oct 05, 2004 at 10:16:16AM -0400, Alan Cabrera wrote:
-----Original Message-----
From: Jeremy Boynes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 05, 2004 10:06 AM
To: [EMAIL PROTECTED]
Subject: Re: RMI startup failure
David Blevins wrote:
Seems we're getting classloading issues from our RMIClassLoaderSpi.
After a clean build, this no workie.
$ cd modules/assembly/target/geronimo-1.0-SNAPSHOT
$ java -
Djava.rmi.server.RMIClassLoaderSpi=org.apache.geronimo.rmi.RMIClassLoa
de
rS
piImpl -jar bin/server.jar
It fails with the attached output.
If I do the same thing in OpenEJB, it's all good.
$ cd openejb/modules/assembly/target/openejb-2.0-SNAPSHOT
$ java -
Djava.rmi.server.RMIClassLoaderSpi=org.apache.geronimo.rmi.RMIClassLoa
de
rS
piImpl -jar bin/server.jar
We got something goofy with our plans?
Looks like a conflict with something in JMXRemoting. But I am
concerned
that something needs special commmand line properties to start and
would
assume due to that the RMIClassLoaderSPIImpl has not been used in
quite
a while.
A gentle reminder, people who have spaces in their home directory will
need to use RMIClassLoaderSPIImpl.
You have any idea on why using this in Geronimo would fail?
What GBean that relies upon the RMIClassLoaderSpi and what classloader
should the RMIClassLoaderSpi be in?
-David
