[jbossts-issues] [JBoss JIRA] (JBTM-1344) org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests Timeout (900mins)

Paul Robinson (JIRA) jira-events at lists.jboss.org
Mon Jan 21 03:41:22 EST 2013


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

Paul Robinson edited comment on JBTM-1344 at 1/21/13 3:41 AM:
--------------------------------------------------------------

Notice that it's 'basic test' that is hanging. This test does not cause a crash, which makes it simpler to figure out what's going on.

The thread dump doesn't seem to show any of the TXBridge tests or code in the stack traces, so it's not clear what the test is waiting for.

It's possible that we could be missing some output from the console due to Hudson not flushing the log before it was killed. Assuming we are not, the next line of output you would expect (captured from a successful run) is:

{code}
installing: RULE org.jboss.byteman.contrib.dtest.Instrumentor_org.jboss.jbossts.txbridge.tests.outbound.utility.TestVolatileParticipant_error_remotetrace_entry
{code}

This line of output would be produced when the test calls:

{code}
instrumentedTestVolatileParticipant = instrumentor.instrumentClass(TestVolatileParticipant.class);
{code}

And in particular when the method 'error' is instrumented by 'org.jboss.byteman.contrib.dtest.Instrumentor#instrumentClass'. There is no refrence to 'dtest' in the stack dump.

Also, the only Byteman thread in the stack dump is as follows: 

{code}
"Thread-0" daemon prio=10 tid=0x54943000 nid=0x7686 runnable [0x548fe000]
   java.lang.Thread.State: RUNNABLE
	at java.net.PlainSocketImpl.socketAccept(Native Method)
	at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398)
	at java.net.ServerSocket.implAccept(ServerSocket.java:522)
	at java.net.ServerSocket.accept(ServerSocket.java:490)
	at org.jboss.byteman.agent.TransformListener.run(TransformListener.java:133)
{code}



                
      was (Author: paul.robinson):
    Notice that it's 'basic test' that is hanging. This test does not cause a crash, which makes it simpler to figure out what's going on.

The thread dump doesn't seem to show any of the TXBridge tests or code in the stack traces, so it's not clear what the test is waiting for.

It's possible that we could be missing some output from the console due to Hudson not flushing the log before it was killed. Assuming we are not, the next line of output you would expect (captured from a successful run) is:

{code}
installing: RULE org.jboss.byteman.contrib.dtest.Instrumentor_org.jboss.jbossts.txbridge.tests.outbound.utility.TestVolatileParticipant_error_remotetrace_entry
{code}

The only Byteman thread in the stack dump is as follows: 

{code}
"Thread-0" daemon prio=10 tid=0x54943000 nid=0x7686 runnable [0x548fe000]
   java.lang.Thread.State: RUNNABLE
	at java.net.PlainSocketImpl.socketAccept(Native Method)
	at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398)
	at java.net.ServerSocket.implAccept(ServerSocket.java:522)
	at java.net.ServerSocket.accept(ServerSocket.java:490)
	at org.jboss.byteman.agent.TransformListener.run(TransformListener.java:133)
{code}



                  
> org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests Timeout (900mins)
> ------------------------------------------------------------------------------------
>
>                 Key: JBTM-1344
>                 URL: https://issues.jboss.org/browse/JBTM-1344
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: TxBridge
>            Reporter: Paul Robinson
>            Assignee: Paul Robinson
>            Priority: Minor
>             Fix For: 4.17.3, 5.0.0.M2
>
>
> See: http://172.17.131.2/job/jbossts-narayana-java6/81/

--
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