From: Tom E. <to...@jb...> - 2006-04-28 15:47:26
|
The problem stems from NamingService using MarshalledInvocation, which now requires org.jboss.remoting.serialization.IMarshalledValue and org.jboss.remoting.serialization.SerializationStreamFactory (which is found within jboss-remoting.jar). However, jboss-remoting.jar is not included within server/minimal/lib nor within jboss-minimal.jar. Easiest thing to do would be to include jboss-remoting.jar in the minimal/lib directory (which is 586K). This what you think should be done Dimitris? Dimitris Andreadis wrote: > Did something change recently in serialization/remoting? > > run -c minimal > ... > 15:15:32,609 INFO [NamingService] JNDI bootstrap JNP=/0.0.0.0:1099, > RMI=/0.0.0.0:1098, backlog=50, no client SocketFactory, Server > SocketFactory=class org.jboss.net.sockets.DefaultSocketFactory > 15:15:32,629 WARN [ServiceController] Problem starting service > jboss:service=Naming > java.lang.NoClassDefFoundError: > org/jboss/remoting/serialization/impl/java/JavaSerializationManager > at java.lang.ClassLoader.defineClass0(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:539) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123) > ... > --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- > ObjectName: jboss:service=Naming > State: FAILED > Reason: java.lang.NoClassDefFoundError: > org/jboss/remoting/serialization/impl/ > java/JavaSerializationManager > I Depend On: > jboss.system:service=ThreadPool > > |