[jboss-dev-forums] [Design of EJB 3.0] - Re: EJBTHREE-1607 Update EJB3.0 Tutorials

[jaikiran]

With this change, i was able to move forward to the point where the JBoss-5 GA server was being started from the maven-jboss-as-control-plugin. This maven-jboss-as-control-plugin uses 1.0.0.GA version of the jboss-server-manager:

  | <version.org.jboss.jbossas_jboss-server-manager>1.0.0.GA</version.org.jboss.jbossas_jboss-server-manager>
  |       <!-- JBoss AS Server Manager -->
  |       <dependency>
  |         <groupId>org.jboss.jbossas</groupId>
  |         <artifactId>jboss-server-manager</artifactId>
  |         <version>${version.org.jboss.jbossas_jboss-server-manager}</version>
  |       </dependency>

Unfortunately, the jboss-server-manager fails to start the JBoss-5 GA server. It fails with:

Caused by: java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is: 
  |         java.io.InvalidClassException: org.jboss.security.auth.callback.SecurityAssociationHandler; class invalid for deserialization
  |         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:282)
  |         at sun.rmi.transport.Transport$1.run(Transport.java:153)
  |         at java.security.AccessController.doPrivileged(Native Method)
  |         at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
  |         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
  |         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
  |         at java.lang.Thread.run(Thread.java:595)
  | Caused by: java.io.InvalidClassException: org.jboss.security.auth.callback.SecurityAssociationHandler; class invalid for deserialization
  |         at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:571)
  |         at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552)
  |         at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
  |         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
  |         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 org.jboss.invocation.MarshalledInvocation.readExternal(MarshalledInvocation.java:665)
  |         at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
  |         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717)
  |         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
  |         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
  |         at sun.rmi.server.UnicastRef.unmarshalValue(UnicastRef.java:290)
  |         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:279)
  |         ... 6 more
  | 

Based on this thread, http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146034&postdays=0&postorder=asc&start=20#4193133, the fix is in 2.0.2.SP3 of the org.jboss.security module. The jboss-server-manager in 1.0.0GA version as well as in trunk uses 

    <version.org.jboss.security>2.0.2.CR9</version.org.jboss.security>

I have locally updated the pom for jboss-server-manager and created a 1.0.1-SNAPSHOT to use in the maven-jboss-as-control-plugin. With these changes, i now have the server statup/stop/deploy working through the Maven plugin.


To summarize - The 1.0.0 GA version and trunk of jboss-as-server with JBoss-5.0 GA fails. 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195322#4195322

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4195322