[jboss-dev] testsuite regression

Dimitris Andreadis dandread at redhat.com
Thu Nov 13 13:41:47 EST 2008 

We have multiple suites running so this one seems to include your last change and also point 
out the same problem (so no need to wait a day :)

http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun15-sun16/332/testReport/

Anil Saldhana wrote:
> Dimitris,  I enabled the sec mgr target yesterday.  But the common/lib 
> move coincided. Hence the sec mgr target has not really started.  We 
> need to wait a day.
> 
> Dimitris Andreadis wrote:
>> The jrockit run that seems to be the most reliable (having the least 
>> transient failures) shows most tests-security-manager tests to be 
>> failing with:
>>
>> javax.naming.CommunicationException: Could not obtain connection to 
>> any of these urls: localhost:1099 and discovery failed with error: 
>> javax.naming.CommunicationException: Receive timed out [Root exception 
>> is java.net.SocketTimeoutException: Receive timed out] [Root exception 
>> is javax.naming.CommunicationException: Failed to connect to server 
>> localhost:1099 [Root exception is 
>> javax.naming.ServiceUnavailableException: Failed to connect to server 
>> localhost:1099 [Root exception is java.net.ConnectException: 
>> Connection refused]]]
>>     at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1727)
>>     at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:680)
>>     at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:673)
>>     at javax.naming.InitialContext.lookup(InitialContext.java:392)
>>     at 
>> org.jboss.test.cts.test.BmpUnitTestCase.getHome(BmpUnitTestCase.java:89)
>>     at 
>> org.jboss.test.cts.test.BmpUnitTestCase.setUp(BmpUnitTestCase.java:770)
>>     at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
>>     at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
>>     at junit.extensions.TestSetup.run(TestSetup.java:25)
>> Caused by: javax.naming.CommunicationException: Failed to connect to 
>> server localhost:1099 [Root exception is 
>> javax.naming.ServiceUnavailableException: Failed to connect to server 
>> localhost:1099 [Root exception is java.net.ConnectException: 
>> Connection refused]]
>>     at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:311)
>>     at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1698)
>> Caused by: javax.naming.ServiceUnavailableException: Failed to connect 
>> to server localhost:1099 [Root exception is java.net.ConnectException: 
>> Connection refused]
>>     at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:281)
>> Caused by: java.net.ConnectException: Connection refused
>>     at java.net.PlainSocketImpl.socketConnect(Native Method)
>>     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>>     at 
>> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>>     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>>     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>>     at java.net.Socket.connect(Socket.java:519)
>>     at 
>> org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97) 
>>
>>     at 
>> org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82) 
>>
>>     at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:277)
>>
>>
>> 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

More information about the jboss-development mailing list