JBoss & Java 1.6 class loading issue?

[mousersvk]

Hello, I am using JBoss AS 4.0.4 / JBoss AS 4.0.5 and this problem occures on both while using JRE/JDK 1.6 on the client side.

I've got simple EJB3 and invoking its method like this:

// get the initial context
 Context ctx = new InitialContext();
 // find context of our interface
 Locator test = (Locator) ctx.lookup("LocatorBean/remote");

 // perform 'invoke()' method on bean itself
 GetCitiesRequest req = new GetCitiesRequest("Slovakia", "Bratislava");
 System.out.println(test.invoke(req));

Object that has 'String' class inside is returned. Logic of bean is performed successfully, but while the result is being returned back to client, following exception is thrown (there is only cause, real:

java.lang.reflect.UndeclaredThrowableException
 at $Proxy0.invoke(Unknown Source)
 ..
Caused by: java.lang.ClassNotFoundException: [Ljava.lang.String;
 at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
 at org.jboss.remoting.loading.RemotingClassLoader.loadClass(RemotingClassLoader.java:50)
 at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.resolveClass(ObjectInputStreamWithClassLoader.java:139)
 at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
 at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
 at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1624)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1323)
 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
 at org.jboss.aop.joinpoint.InvocationResponse.readExternal(InvocationResponse.java:107)
 at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
 at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128)
 at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66)
 at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279)
 at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
 at org.jboss.remoting.Client.invoke(Client.java:525)
 at org.jboss.remoting.Client.invoke(Client.java:488)
 at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:41)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88)
 at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:46)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88)
 at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:40)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88)
 at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88)
 at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
 ... 2 more

Everything is fine when using Java 1.5 on client side. I've tried running the server both on Java 1.5 and 1.6. Results were the same.
Maybe there is problem in loading of class because of Java 1.6 runtime regression, as it is described here ?:

http://forums.java.net/jive/thread.jspa?threadID=15823
https://glassfish.dev.java.net/issues/show_bug.cgi?id=714

Similar problem is described here (I think it is the same one):
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988513[/url]

Anyone else experiencing this? Or can someone tell if this is bug in JBoss?

Thanks,
Mouser.

[alexg79]

This is a known bug in JBoss Remoting v1.4.x. For some reason, the fix has not been backported to the 1.4 branch. This is especially odd since the 2.x versions can't replace v1.4.x directly, and thus JBoss 4 users are left "hanging" or being told to fix the problem by building from CVS (this involved grabbing some code from the 2.0 branch and inserting it to the v1.4 branch and then recompiling).
I can't find the exact post any more because of some bug in the forum software that leaves out some of my posts from the search.
JBoss folks: could you _please_ release v1.4.5 with the deserialization bug fixed so posts like these would end?

[starksm64]

http://jira.jboss.com/jira/browse/JBREM-651

[alexg79]

So is this a JDK6 bug? I know the behavior was changed, but is it broken in JDK6, or do the other software just have catching up to do?

[starksm64]

I view it as a bug and it appears to have been accepted as such.

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6434149

[alexg79]

Damn...I guess we can only wait for 6.0 update 1 :(
EJB3 remote interfaces are totally unusuable atm, since this happens with collections too.

[alexg79]

I took a second look at the related bugs, and found this:

I am the submitter of the bug. After analysing the related bugs, it seems that this change is an intended change (and not a regression). See the evaluation of bug #6446627 and bug #4872868. It seems that some products have not been updated to take this into account. I saw this while using toplink-essentials for example. I will now file a bug there (with a suggested patch).

If this is true, it means that JBoss Remoting needs to be patched. What say you?

[aron-smith]

I say it needs to be fixed, it is still not fixed in 5.0 beta so no sign of a change...

...anyone know how to hack it?

[fcorneli]

Hello,

Is there a patched jboss-remoting.jar for JBoss AS 4.0.5.GA that has a fix for this issue? Apparently according to:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6446627
jboss-remoting should be patched to use Class.forName instead of ClassLoader.loadClass for loading array classes.

This issue with jboss-remoting in JBoss AS 4.0.5.GA is really blocking my integration tests, and I need Java6 because of the improved security API and smart card support.

Frank.

[alexg79]

Is there a patched jboss-remoting.jar for JBoss AS 4.0.5.GA that has a fix for this issue?

I have compiled a patched version of jboss-remoting.jar, and it seems to work with JDK6. I'm looking for someone to host the fixed version.
See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=98575

[tom.elrod]

(Per http://jira.jboss.com/jira/browse/JBREM-659)

Have update all the places where ClassLoader.loadClass() was being called and either replaced with Class.forName() call or changed to use the ClassLoaderUtility class. These changes have been made to HEAD, remoting_2_x and remoting_1_4 branches.

Have also created a 1.4.6.GA release for these changes (with tag of remoting_1_4_6_GA) and have published to jboss repository (see Jhttp://repository.jboss.com/jboss/remoting/1.4.6.GA/lib/)

Although was able to manually test some of the remoting tests within the testsuite using jdk 1.6, could not run the automated testsuite run with jdk 1.6. The reason for this is that distributed test framework used (JBoss JRunit) uses JGroups for its communication transport, which itself uses ClassLoader.loadClass() and therefore can't run under jdk 1.6 (see http://javagroups.cvs.sourceforge.net/javagroups/JGroups/src/org/jgroups/util/Util.java?revision=1.113&view=markup).

Therefore, although 1.4.6.GA, 2.2.0.Beta1 and any 3.x releases *should* work with jdk 1.6, I can't say they will with certainty since can't run the full testsuite.