[jboss-jira] [JBoss JIRA] Updated: (JBASM-26) JBoss AS Server Manager fails to deploy applications and even stop the server against JBossAS-5.0 GA

jaikiran pai (JIRA) jira-events at lists.jboss.org
Sat Dec 13 05:31:47 EST 2008


     [ https://jira.jboss.org/jira/browse/JBASM-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jaikiran pai updated JBASM-26:
------------------------------

    Attachment: JBASM-26.patch


> JBoss AS Server Manager fails to deploy applications and even stop the server against JBossAS-5.0 GA
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JBASM-26
>                 URL: https://jira.jboss.org/jira/browse/JBASM-26
>             Project: JBoss AS Server Manager
>          Issue Type: Bug
>    Affects Versions: 1.0.0.GA
>         Environment: jbossas-server-manager 1.0.0 GA (and even trunk), JBossAS5.0 GA, Sun JDK 1.5, RHEL 5 operating system
>            Reporter: jaikiran pai
>            Assignee: Shelly McGowan
>         Attachments: JBASM-26.patch
>
>
> The jbossas-server-manager version 1.0.0 GA and even the trunk fails to stop a server or even deploy applications against JBoss-5.0 GA. The unit tests in the trunk show the reason for failure. Most of the unit tests are failing with :
> 	at org.jboss.jbossas.servermanager.ServerController.stopServer(ServerController.java:333)
> 	at org.jboss.jbossas.servermanager.test.common.AsLifecycleDelegate.stopJbossAs(AsLifecycleDelegate.java:112)
> 	at org.jboss.jbossas.servermanager.test.jmxinvocation.unit.JmxInvocationTest.afterClass(JmxInvocationTest.java:169)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.junit.internal.runners.ClassRoadie.runAfters(ClassRoadie.java:65)
> 	at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:40)
> 	at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42)
> 	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
> 	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338)
> 	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997)
> 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
> The fix is to upgrade the org.jboss.security version to 2.0.2.SP3 (from its current 2.0.2.CR9). Please see the referenced forum thread for details. 
> Also find attached a patch for this issue (just a change in pom.xml). With this patch all the unit tests passed locally.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list