[jbossts-issues] [JBoss JIRA] (JBTM-1386) ATBridgeTest hangs during Deployment

Paul Robinson (JIRA) jira-events at lists.jboss.org
Fri Dec 14 06:44:17 EST 2012

    [ https://issues.jboss.org/browse/JBTM-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741435#comment-12741435 ] 

Paul Robinson commented on JBTM-1386:

It seems strange that this only happens for the TXFramework tests, where our usage of Arquillian is pretty similar to elsewhere. I suspect it could be because txframework/pom.xml still specifies version numbers from the days when it was a standalone project.

This problem might be 'fixed' for us by JBTM-1375 as one task was to remove version numbers. We should wait for this failing again after JBTM-1375 is merged before spending any more time on it.
> ATBridgeTest hangs during Deployment
> ------------------------------------
>                 Key: JBTM-1386
>                 URL: https://issues.jboss.org/browse/JBTM-1386
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Testing, TXFramework
>         Environment: Job 124:
> Linux tenafly.buildnet.ncl.jboss.com 2.6.32-279.14.1.el6.i686 #1 SMP Tue Nov 6 21:05:14 UTC 2012 i686 i686 i386 GNU/Linux
> CentOS release 6.3 (Final)
> java version "1.6.0_37"
> Java(TM) SE Runtime Environment (build 1.6.0_37-b06)
> Java HotSpot(TM) Client VM (build 20.12-b01, mixed mode, sharing)
> AS7 master on 10/12/2012
>            Reporter: Paul Robinson
>            Assignee: Paul Robinson
>             Fix For: 5.0.0.M2
>         Attachments: jboss.stacktrace, org.jboss.narayana.txframework.functional.ATBridgeTest-output.txt
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
> Notice the following in the stack dump which looks very similar to [AS7-5946]:
> {code}
> "management-handler-thread - 3" prio=10 tid=0xa0661800 nid=0x282b in Object.wait() [0x9c669000]
>    java.lang.Thread.State: WAITING (on object monitor)
> 	at java.lang.Object.wait(Native Method)
> 	- waiting on <0xa626ae88> (a org.jboss.as.controller.ContainerStateMonitor)
> 	at java.lang.Object.wait(Object.java:485)
> 	at org.jboss.as.controller.ContainerStateMonitor.awaitContainerStateChangeReport(ContainerStateMonitor.java:158)
> 	- locked <0xa626ae88> (a org.jboss.as.controller.ContainerStateMonitor)
> 	at org.jboss.as.controller.ModelControllerImpl.awaitContainerStateChangeReport(ModelControllerImpl.java:452)
> 	at org.jboss.as.controller.OperationContextImpl.awaitModelControllerContainerMonitor(OperationContextImpl.java:147)
> {code}
> Also, notice the last line of the server log:
> {code}
> 16:08:52,111 INFO  [org.jboss.as.arquillian] (MSC service thread 1-1) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."test.jar",unit=test.jar,tests=[org.jboss.narayana.txframework.functional.ATStatefullTest, org.jboss.narayana.txframework.functional.ATBridgeTest, org.jboss.narayana.txframework.functional.rest.at.simpleEJB
> {code}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the jbossts-issues mailing list