CommunicationException when looking up EJB (SLSB 3.0)

[shreyasshinde]

Hello,

When looking up an SLSB (EJB 3.0) I am getting a CommunicationException in JBoss 5.0

javax.naming.CommunicationException: Failed to connect to server 10.14.51.52:1100 [Root exception is java.lang.ClassCastException: java.util.Collections$UnmodifiableRandomAccessList]

The properties used in the InitialContext are:

java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
jnp.discoveryGroup=230.0.0.4
jnp.discoveryPort=1102
jnp.discoveryTimeout=5000
jnp.disableDiscovery=false
jnp.partitionName=ClusterOne

Can you tell me what could I be missing? Any pointers would be appreciated..

Thanks,

Shreyas


Platform: RHEL4
JBoss AS 5.0


The entire stack trace is here:

javax.naming.CommunicationException: Failed to connect to server 10.14.51.52:1100 [Root exception is java.lang.ClassCastException: java.util.Collections$UnmodifiableRandomAccessList]
 at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:274)
 at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1457)
 at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1582)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:634)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)

Caused by: java.lang.ClassCastException: java.util.Collections$UnmodifiableRandomAccessList
 at org.jboss.ha.framework.interfaces.HARMIClient.readObject(HARMIClient.java:342)
 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.lang.reflect.Method.invoke(Method.java:585)
 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
 at java.rmi.MarshalledObject.get(MarshalledObject.java:135)
 at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:257)
 ... 33 more

[peterj]

What JDK are you using? Look in the console log, near the beginning, there should be lines like:

19:22:08,508 INFO [ServerInfo] Java version: 1.5.0_16,Sun Microsystems Inc.
19:22:08,509 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 1.5.0_16-b02,Sun Microsystems Inc.

Please post those lines from your log.

[shreyasshinde]

I am using JDL 1.5.0 update 10.

Here is the trace from the startup logs:

17:54:52,037 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_10-b03,Sun Microsystems Inc.
17:54:52,037 INFO [ServerInfo] OS-System: Linux 2.6.9-55.ELsmp,i386

Are there known issues with any of the JDKs?

Thanks,

Shreyas

[shreyasshinde]

I tried running with JDK 1.6 but with the same result.

13:10:24,286 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc.
13:10:24,286 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0-b105,Sun Microsystems Inc.
13:10:24,286 INFO [ServerInfo] OS-System: Linux 2.6.9-55.ELsmp,i386

I continue to get the ClassCastException (listed in the original post). The AutoDiscovery feature is kicking in and I can see the client trying to connect to the right server.

Thanks,

Shreyas

[brian.stansberry]

https://jira.jboss.org/jira/browse/JBAS-6345 is almost certainly the cause.

Where is your client? Running inside an AS 4.x or 3.x server? If not, just make sure the jbossall-client.jar *from AS 5* is on the classpath and this problem should go away. If so this is a problem unless your app configures an isolated classloader and includes the the AS 5 jbossall-client.jar in its classpath.

[shreyasshinde]

Thanks Brain.

I installed JBoss 5.0.0 CR2 and updated the client JARS with everything in the jbossall-client.jar MANIFEST and don't see any of the exceptions any more.

Are all the JARs listed in the jbossall-client.jar's MANIFEST required on the client side?

Thanks,

Shreyas

[shreyasshinde]

I apologize for the typo. Thanks Brian.

[brian.stansberry]

No need to apologize, result isn't so bad and I occasionally do that myself. :-)

You likely don't need all the jars, but I can't say exactly what you do need; depends on what all your app does. The clustering related ones that you do need are jboss-ha-client.jar and jboss-ha-legacy-client.jar.