[jbossts-issues] [JBoss JIRA] (JBTM-2065) TestExternManageDestination::test_stored_message_schedule() hangs on Windows
Tom Jenkinson (JIRA)
issues at jboss.org
Mon Jan 27 04:31:28 EST 2014
[ https://issues.jboss.org/browse/JBTM-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12938870#comment-12938870 ]
Tom Jenkinson commented on JBTM-2065:
-------------------------------------
Hi Clebert,
Here are the CI instructions to get a full build on Windows:
call "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcvarsall.bat"
set ANT_HOME=C:\hudson\tools\apache-ant-1.8.2
set PATH=%ANT_HOME%\bin;%PATH%
rmdir /Q /S \Users\hudson\.m2\repository\org\jboss\narayana\
call scripts\hudson\narayana.bat "-DskipTests"
Once you have a full build the test that fails is disabled in commit:
68c980ba085117eabf38b27bee6330b5d06975fa
Now that could take a few hours to get running.
What I think best is if Amos can look at our TestExternManageDestination::test_stored_message_schedule and see what stomp connect methods are called then try to create a simple Java program that replicates the issue. This is the test that hangs: https://github.com/jbosstm/narayana/blob/master/blacktie/queue/src/test/cpp/TestExternManageDestination.cxx#L188
The output:
{code}
[exec] .2013-12-23 14:30:51,179 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - TestExternManageDestination::setUp
14:30:53,452 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 82) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1
14:30:53,454 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 82) JBAS011601: Bound messaging object to jndi name /queue/BTR_.testsui1
[exec] 2013-12-23 14:30:53,505 [0x0000af78] INFO (AtmiBrokerServer :938 ) - advertised service .testsui1
[exec] 2013-12-23 14:30:53,506 [0x0000af78] INFO (AtmiBrokerServer :243 ) - Server 1 Running
[exec] 2013-12-23 14:30:53,507 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - test_stored_message_schedule
[exec] 2013-12-23 14:30:53,588 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - Sent 28 0 1387809099000
[exec] 2013-12-23 14:30:53,623 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - Sent 26 0 1387809095000
[exec] 2013-12-23 14:30:53,656 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - Sent 24 0 1387809091000
[exec] 2013-12-23 14:30:53,689 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - Sent 22 0 1387809087000
[exec] 2013-12-23 14:30:53,729 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - Sent 20 0 0
[exec] 2013-12-23 14:30:53,764 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - Sent 29 0 1387809101000
[exec] 2013-12-23 14:30:53,806 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - Sent 27 0 1387809097000
[exec] 2013-12-23 14:30:53,849 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - Sent 25 0 1387809093000
[exec] 2013-12-23 14:30:53,893 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - Sent 23 0 1387809089000
[exec] 2013-12-23 14:30:53,932 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - Sent 21 0 1387809085000
[exec] 2013-12-23 14:30:53,971 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - qservice iteration: 0 expected: 20 received: 20
[exec] 2013-12-23 14:31:27,010 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - qservice iteration: 1 expected: 21 received: 21
[exec] 2013-12-23 14:31:29,358 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - qservice iteration: 2 expected: 22 received: 22
[exec] 2013-12-23 14:31:29,614 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - qservice iteration: 3 expected: 23 received: 23
[exec] 2013-12-23 14:31:33,014 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - qservice iteration: 4 expected: 24 received: 24
14:31:33,650 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a1%3a729492/terminate
14:31:33,659 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a2%3a401367/terminate
14:31:33,663 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a7%3a463867/terminate
14:31:33,666 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a8%3a120117/terminate
[exec] 2013-12-23 14:31:35,018 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - qservice iteration: 5 expected: 25 received: 25
[exec] 2013-12-23 14:31:37,011 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - qservice iteration: 6 expected: 26 received: 26
[exec] 2013-12-23 14:31:39,018 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - qservice iteration: 7 expected: 27 received: 27
[exec] 2013-12-23 14:31:41,021 [0x0000af78] INFO (AtmiBrokerLogc :60 ) - qservice iteration: 8 expected: 28 received: 28
{code}
We expect a qservice iteration: 9 expected 29 received: 29
Amos, please can you provide more background on the issue, what you have tried and observed. For example, you said you couldn't replicate it on your machine. If you increase the number of sends/receives can you replicate it on your machine? You also thought it only ever happened in the morning? Also, there isn't a repeating job set up for this, please can you add it to Jenkins?
Tom
> TestExternManageDestination::test_stored_message_schedule() hangs on Windows
> ----------------------------------------------------------------------------
>
> Key: JBTM-2065
> URL: https://issues.jboss.org/browse/JBTM-2065
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 6.0.0.Alpha1
>
>
> http://172.17.131.2/job/btny-pulls-narayana-windows2008/523/consoleText
> http://172.17.131.2/job/btny-pulls-narayana-windows2008/524/consoleText
--
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