Looking up a @Stateful Bean fails cause of AOP Interceptor (

[cwulf]

Got a ClassLoader-Problem with EJB 3's Stateful Session Bean's i don't unterstand.
Have got included all required Client-JAR's (incl. jboss-aop-jdk50-client.jar).

Stateless Session Bean's are working fine, but if i look up for a Stateful i am getting a problem with a ClassLoader, can't find org.jboss.aop.advice.Interceptor.

javax.naming.NamingException: Could not dereference object [Root exception is java.lang.reflect.UndeclaredThrowableException]
 at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1150)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:705)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
 at javax.naming.InitialContext.lookup(InitialContext.java:392)
 at test.Client.main(Client.java:48)
Caused by: java.lang.reflect.UndeclaredThrowableException
 at $Proxy1.createProxy(Unknown Source)
 at org.jboss.ejb3.JndiProxyFactory.getObjectInstance(JndiProxyFactory.java:52)
 at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
 at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1125)
 at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1142)
 ... 4 more
Caused by: java.lang.ClassNotFoundException: [Lorg.jboss.aop.advice.Interceptor;
 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
...

Don't know if this is a client or server side problem, because the class is definitly in the client's classpath (if i drop jboss-aop-jdk50-client.jar the Stateless stop working cause of the Interceptor class).

Any ideas?

[cwulf]

Solved it myself using JDK 1.5 instead of JDK 1.6 for client and JBoss.

Are there known problems with JBoss and Java 6? My remote clients run on the Eclipse Rich Client Platform and i think, i cant hope that no one of my users will upgrade to Java 6...

[nicarran]

"cwulf" wrote:
Solved it myself using JDK 1.5 instead of JDK 1.6 for client and JBoss.

Are there known problems with JBoss and Java 6? My remote clients run on the Eclipse Rich Client Platform and i think, i cant hope that no one of my users will upgrade to Java 6...

Related issue: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=98575

[htran_888]

Hi,

Sounds like it is a JBoss 4.0.4/4.0.5 issue since I have had no problem when using SJASA PE 9.0 with the same Netbeans on the same JDK 6.0.

Anyway, I will try it with JDK 1.5 to see whether it makes any difference.

Cheers,

Henry

[htran_888]

Hi cwulf,

Your recommendation was correct.

By running only the Client program (EJB3ex512) using SDK 1.5 solved this issue.

All session beans and other clients are still using SDK 1.6 without a problem.

Thanks again,

Henry