JBoss 4.0.1 on IBM Power5 with JDK 1.5 MDB classloader probl

[frintrop]

Hi, we are trying to deploy our app ( well runing under linux/i586/sun jdk15 ) on IBM Power5 with IBM JDK 1.5 and got following error while deploying the MDB´s in our ear / jar :

2006-04-05 09:22:30,519 49717 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] (main:jboss.j2ee:service=EJB,plugin=invoker,binding=message-driven-bean,jndiName=local/PrintingMDB JMSContainerInvoker DLQHandler) Creating DLQHandler
2006-04-05 09:22:30,544 49742 WARN [org.jboss.system.ServiceController] (main:) Problem starting service jboss.j2ee:service=EJB,plugin=invoker,binding=message-driven-bean,jndiName=local/PrintingMDB
java.lang.NoClassDefFoundError: $Proxy737
 at sun.reflect.GeneratedSerializationConstructorAccessor345.newInstance(Unknown Source)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:521)
 at java.io.ObjectStreamClass.newInstance(ObjectStreamClass.java:951)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:354)
 at java.rmi.MarshalledObject.get(MarshalledObject.java:163)
 at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:195)
 at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1185)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:515)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:508)
 at javax.naming.InitialContext.lookup(InitialContext.java:363)
 at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:147)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)
 at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:164)
 at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:545)
 at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:767)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:615)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
 at $Proxy356.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:416)
 at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)

we can not figure out, what the problem is ? we think a class loader problem with ibm´s jdk ?