[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-2177) Fix org.jboss.ejb3.test.asynchronous.unit.AsynchronousTestCase failures

jaikiran pai (JIRA) jira-events at lists.jboss.org
Thu Sep 23 11:57:28 EDT 2010


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

jaikiran pai resolved EJBTHREE-2177.
------------------------------------

    Resolution: Done


> Fix org.jboss.ejb3.test.asynchronous.unit.AsynchronousTestCase failures
> -----------------------------------------------------------------------
>
>                 Key: EJBTHREE-2177
>                 URL: https://jira.jboss.org/browse/EJBTHREE-2177
>             Project: EJB 3.0
>          Issue Type: Task
>          Components: testsuite
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>
> The http://mike.lab.bos.redhat.com:8380/hudson/job/JBoss-AS-6.x-tests-ejb3/717/testReport/org.jboss.ejb3.test.asynchronous.unit/AsynchronousTestCase/testSLRemoteAsynchronous/ tests are failing due to:
> DEPLOYMENTS IN ERROR:
>   Deployment "vfs:///jboss/wc/jbossas/projects/ejb3/trunk/testsuite/target/test-lib/asynchronous-test.jar" is in error due to the following reason(s): java.lang.IllegalStateException: jboss.naming:application=asynchronous-test is already installed.
> 	at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1370) [:2.2.0.Alpha7]
> 	at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1316) [:2.2.0.Alpha7]
> 	at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:968) [:2.2.0.Alpha7]
> 	at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:957) [:2.2.0.Alpha7]
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:373) [:6.0.0-SNAPSHOT]
> 	at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:277) [:6.0.0-SNAPSHOT]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_16]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_16]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_16]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_16]
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.Beta5]
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.Beta5]
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.Beta5]
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.Beta5]
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.Beta5]
> 	at org.jboss.system.server.jmx.MBeanServerWrapper.invoke(MBeanServerWrapper.java:138) [:6.0.0-SNAPSHOT (Build SVNTag:JBoss_6.0.0-SNAPSHOT date: 20100923)]
> 	at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426) [:1.6.0_16]
> 	at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) [:1.6.0_16]
> 	at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264) [:1.6.0_16]
> 	at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1359) [:1.6.0_16]
> 	at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) [:1.6.0_16]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_16]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_16]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_16]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_16]
> 	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) [:1.6.0_16]
> 	at sun.rmi.transport.Transport$1.run(Transport.java:159) [:1.6.0_16]
> 	at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_16]
> 	at sun.rmi.transport.Transport.serviceCall(Transport.java:155) [:1.6.0_16]
> 	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) [:1.6.0_16]
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) [:1.6.0_16]
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) [:1.6.0_16]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_16]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_16]
> 	at java.lang.Thread.run(Thread.java:619) [:1.6.0_16]
> This is because the testcase deploys asynchronous-test.sar and asynchronous-test.jar, which results in the JavaEE naming conflicts.

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

        


More information about the jboss-jira mailing list