[jboss-dev] testsuite regression

[Scott Stark]

Why isn't there any output from the 
org.jboss.deployers.plugins.deployers.DeployersImpl category in the 
logs? It only shows up in exception traces. We appear to be using a 
jboss-log4j.xml other than what is shipped with the server.

Scott Stark wrote:
> A lot of the failures are due to an existing testTopic that tests are
>
> Caused by: java.lang.IllegalStateException: 
> jboss.mq.destination:name=testTopic,service=Topic is already installed.
>        at 
> org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:716) 
>
>        at 
> org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540) 
>
>        at 
> org.jboss.system.ServiceController.doInstall(ServiceController.java:654)
>        at 
> org.jboss.system.ServiceController.install(ServiceController.java:257)
>        ... 64 more
> 04:26:03,506 WARN  [MainDeployer] Failed to deploy: 
> file:/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/output/resources/messaging/test-destinations-full-service.xml 
>
>
> 04:24:58,860 INFO  [MainDeployer] deploy, 
> url=file:/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/output/lib/jca-txactive-ejb.jar 
>
> 04:24:58,966 INFO  [EjbDeployer] installing bean: 
> ejb/#TxActiveBean,uid11795362
> 04:24:58,966 INFO  [EjbDeployer]   with dependencies:
> 04:24:58,966 INFO  [EjbDeployer]   and supplies:
> 04:24:58,966 INFO  [EjbDeployer]        jndi:test/ejbs/TxActiveBean
> 04:24:59,005 WARN  [AbstractDeploymentContext] Unable to register 
> deployment mbean jboss.mq.destination:name=testTopic,service=Topic
> javax.management.InstanceAlreadyExistsException: 
> jboss.deployment:id="jboss.mq.destination:name=testTopic,service=Topic",type=Component 
> already registered.
>        at 
> org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistry.java:767) 
>
>        at 
> org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:236) 
>
>        at sun.reflect.GeneratedMethodAccessor74.invoke(Unknown Source)
>
> [748][valkyrie: testsuite]$ jar -tf output/lib/jca-txactive-ejb.jar
> META-INF/
> META-INF/MANIFEST.MF
> org/
> org/jboss/
> org/jboss/test/
> org/jboss/test/jca/
> org/jboss/test/jca/interfaces/
> org/jboss/test/jca/interfaces/TransactionActiveHome.class
> org/jboss/test/jca/interfaces/TransactionActiveRemote.class
> org/jboss/test/jca/ejb/
> org/jboss/test/jca/ejb/TransactionActiveBean.class
> META-INF/ejb-jar.xml
> META-INF/jboss.xml
> test-destinations-service.xml
>
> The testTopic was previously installed as part of the 
> output/lib/invokers.jar, but I don't see why it was not undeployed 
> other than this warning from the old MainDeployer:
>
> 04:11:28,440 WARN  [MainDeployer] undeploy 
> 'file:/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/output/lib/invokers.jar' 
> : package not deployed
>
> but this seems to be logged for all deployments.
>
> Dimitris Andreadis wrote:
>> We have a spike of +133 similar failures in the latest run:
>>
>> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun15/1074/testReport/ 
>>
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development