JBoss-4.0.0DR2 remote client JNDI connection problem

[sradford]

Anyone know what's changed from JBoss-3 (and an earlier CVS build of JBoss 4) to JBoss-4.0.0DR2 that now causes my JUnit tests to fall over.

Basically, I'm trying to do a JNDI lookup to a SessionBean...

With jboss-all-client.jar in the classpath I get:
java.lang.NoClassDefFoundError: org/jboss/system/ServiceMBeanSupport

So I add jboss-system.jar (not a client jar!) and get:
java.lang.NoClassDefFoundError: javax/management/NotificationBroadcasterSupport

So I add jbossjmx-ant.jar and get:
java.lang.NoClassDefFoundError: Lorg/jboss/remoting/ClientInterceptor;

So I add jboss-remoting.jar (not a client jar!) and get:
Caused by: java.io.InvalidClassException: org.jboss.invocation.remoting.RemotingAdapter; unable to create instance
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1633)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
at java.util.HashMap.readObject(HashMap.java:1006)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:838)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1746)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
at org.jboss.proxy.ClientContainer.readExternal(ClientContainer.java:113)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1686)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1644)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
at java.rmi.MarshalledObject.get(MarshalledObject.java:135)
at org.jnp.interfaces.MarshalledValuePair.get(MarshalledValuePair.java:30)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:522)
... 46 more

Any ideas, as I NEED help - spend all day on this :-( (and I don't want this project to have to use JBoss-3.xx)

Thanks in advance,

Sean

[sradford]

Ok, I've sorted it..

Instead of jbossjmx-ant.jar I include jboss-jmx.jar (not a client jar).

And then include dom4j.jar.

Hey presto!

[mortena]

That's a good question. I've spent an entire week rewriting my application, to get rid of that error.
And now you say that I could have solved it by including jar files from other places than /client....

This is an annoying issue, and does not exactly add value to my JBoss goodwill.

Thanks

Morten Andersen

[andyhardy]

Cheers budy

That helped a lot!!!

[steven_anto]

It was very helpful while running my sample application in JBoss 4.0.

But b4 "HelloWorld" gets printed I got the following messages.

No property editor for type: class javax.management.ObjectName, setting value to null rather than jboss.tm:service=TransactionManagerService
No property editor for type: class javax.management.ObjectName, setting value to null rather than jboss.remoting:service=InterceptorAdapter
No property editor for type: class javax.management.ObjectName, setting value to null rather than jboss.tm:service=TxLogger
No property editor for type: class javax.management.ObjectName, setting value to null rather than jboss.tm:service=XidFactory
No property editor for type: class javax.management.ObjectName, setting value to null rather than jboss.tm:service=TxLogger
No property editor for type: class javax.management.ObjectName, setting value to null rather than jboss.tm:service=TransactionManagerService
No property editor for type: class javax.management.ObjectName, setting value to null rather than jboss.jca:service=CachedConnectionManager
Hello World!