April 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1402) Build timed out while running tests from TestGroup_rawresources02_2

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1402?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1402: ------------------------------------- I'm not sure this really did hang. I thought the job ad hung as it had been running for 1d 19hrs. However, Tom informs me that this job normally takes 2.5d to run! I meant to update the issue, but I forgot :-( Does the test look like it had hung? > Build timed out while running tests from TestGroup_rawresources02_2 > ------------------------------------------------------------------- > > Key: JBTM-1402 > URL: https://issues.jboss.org/browse/JBTM-1402 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 4.17.4 > > > Build failed to execute TestGroup_rawresources02_2 tests and timed out after 1440 minutes. > See: http://172.17.131.2/job/jbossts-narayana-java6/131 -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1634) TX tests failed with "Unable to start a new txn on URI"

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1634?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1634: ---------------------------------------- I tried duplicating the error without success as follows: {noformat} wget -N http://172.17.131.2/job/narayana/lastSuccessfulBuild/artifact/jboss-as/bu... unzip jboss-as-8.0.0.Alpha1-SNAPSHOT.zip cd jboss-as-8.0.0.Alpha1-SNAPSHOT/ export JBOSS_HOME=`pwd` export JBOSSAS_IP_ADDR=localhost $JBOSS_HOME/bin/standalone.sh -c standalone-full.xml -Djboss.bind.address=$JBOSSAS_IP_ADDR -Djboss.bind.address.unsecure=$JBOSSAS_IP_ADDR& curl -X POST -H "Content-Type:application/x-www-form-urlencoded" http://localhost:8080/rest-tx/tx/transaction-manager {noformat} and this worked fine. The error in the desciption is because the path to the coordinator is http://localhosthttp/ etc which is clearly wrong but I could not find this in the logs accompanying the failed job - where did you paste it from? I would have said it looks like something is rewriting that url but, again, I don't see anything untoward in the server log. > TX tests failed with "Unable to start a new txn on URI" > ------------------------------------------------------- > > Key: JBTM-1634 > URL: https://issues.jboss.org/browse/JBTM-1634 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/246/ > http://172.17.131.2/job/blacktie-linux32/915/ > http://172.17.131.2/job/blacktie-linux64/1472/ > {code} > 2013-04-16 06:12:25,324 [0x57fb3f0] DEBUG (HttpClient :114 ) - connected to TM on localhost:8080 URI=http://localhost:8080/rest-tx/tx/transaction-manager > 2013-04-16 06:12:25,484 [0x57fb3f0] DEBUG (HttpClient :74 ) - connect to localhost:8080 ok > 2013-04-16 06:12:25,491 [0x57fb3f0] DEBUG (HttpClient :99 ) - POST http://localhost:8080/rest-tx/tx/transaction-manager HTTP/1.1 > 2013-04-16 06:12:25,495 [0x57fb3f0] DEBUG (HttpClient :99 ) - Host: localhost > 2013-04-16 06:12:25,498 [0x57fb3f0] DEBUG (HttpClient :99 ) - Content-Length: 13 > 2013-04-16 06:12:25,500 [0x57fb3f0] DEBUG (HttpClient :99 ) - Content-Type: application/x-www-form-urlencoded > 2013-04-16 06:12:25,505 [0x57fb3f0] DEBUG (HttpClient :148 ) - timeout=-1000 > 2013-04-16 06:12:25,508 [0x57fb3f0] DEBUG (HttpClient :158 ) - buf size is 4096 > 2013-04-16 06:12:27,023 [0x57fb3f0] DEBUG (HttpClient :162 ) - receive 241 bytes > 2013-04-16 06:12:27,028 [0x57fb3f0] DEBUG (HttpClient :165 ) - HTTP/1.1 404 Not Found > Content-Length: 145 > Connection: keep-alive > Content-Type: text/html > Could not find resource for relative : /rest-tx/tx/transaction-manager of full path: http://localhosthttp/rest-tx/rest-tx/tx/transaction-manager? > 2013-04-16 06:12:27,049 [0x57fb3f0] DEBUG (HttpClient :194 ) - HTTP/1.1 404 Not Found > {code} > It looks like restat-web.war has not regiter as /rest-tx -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1634) TX tests failed with "Unable to start a new txn on URI"

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1634?page=com.atlassian.jira.plugin.... ] Michael Musgrove edited comment on JBTM-1634 at 4/17/13 12:08 PM: ------------------------------------------------------------------ Is BlackTie using the correct media type - maybe undertow is stricter about what is will accept. Try explicitly setting it to: * Content-Type:application/x-www-form-urlencoded Oops I see the trace output is already setting that header so ignore my comment was (Author: mmusgrov): Is BlackTie using the correct media type - maybe undertow is stricter about what is will accept. Try explicitly setting it to: * Content-Type:application/x-www-form-urlencoded > TX tests failed with "Unable to start a new txn on URI" > ------------------------------------------------------- > > Key: JBTM-1634 > URL: https://issues.jboss.org/browse/JBTM-1634 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/246/ > http://172.17.131.2/job/blacktie-linux32/915/ > http://172.17.131.2/job/blacktie-linux64/1472/ > {code} > 2013-04-16 06:12:25,324 [0x57fb3f0] DEBUG (HttpClient :114 ) - connected to TM on localhost:8080 URI=http://localhost:8080/rest-tx/tx/transaction-manager > 2013-04-16 06:12:25,484 [0x57fb3f0] DEBUG (HttpClient :74 ) - connect to localhost:8080 ok > 2013-04-16 06:12:25,491 [0x57fb3f0] DEBUG (HttpClient :99 ) - POST http://localhost:8080/rest-tx/tx/transaction-manager HTTP/1.1 > 2013-04-16 06:12:25,495 [0x57fb3f0] DEBUG (HttpClient :99 ) - Host: localhost > 2013-04-16 06:12:25,498 [0x57fb3f0] DEBUG (HttpClient :99 ) - Content-Length: 13 > 2013-04-16 06:12:25,500 [0x57fb3f0] DEBUG (HttpClient :99 ) - Content-Type: application/x-www-form-urlencoded > 2013-04-16 06:12:25,505 [0x57fb3f0] DEBUG (HttpClient :148 ) - timeout=-1000 > 2013-04-16 06:12:25,508 [0x57fb3f0] DEBUG (HttpClient :158 ) - buf size is 4096 > 2013-04-16 06:12:27,023 [0x57fb3f0] DEBUG (HttpClient :162 ) - receive 241 bytes > 2013-04-16 06:12:27,028 [0x57fb3f0] DEBUG (HttpClient :165 ) - HTTP/1.1 404 Not Found > Content-Length: 145 > Connection: keep-alive > Content-Type: text/html > Could not find resource for relative : /rest-tx/tx/transaction-manager of full path: http://localhosthttp/rest-tx/rest-tx/tx/transaction-manager? > 2013-04-16 06:12:27,049 [0x57fb3f0] DEBUG (HttpClient :194 ) - HTTP/1.1 404 Not Found > {code} > It looks like restat-web.war has not regiter as /rest-tx -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1634) TX tests failed with "Unable to start a new txn on URI"

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1634?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1634: ---------------------------------------- Is BlackTie using the correct media type - maybe undertow is stricter about what is will accept. Try explicitly setting it to: * Content-Type:application/x-www-form-urlencoded > TX tests failed with "Unable to start a new txn on URI" > ------------------------------------------------------- > > Key: JBTM-1634 > URL: https://issues.jboss.org/browse/JBTM-1634 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/246/ > http://172.17.131.2/job/blacktie-linux32/915/ > http://172.17.131.2/job/blacktie-linux64/1472/ > {code} > 2013-04-16 06:12:25,324 [0x57fb3f0] DEBUG (HttpClient :114 ) - connected to TM on localhost:8080 URI=http://localhost:8080/rest-tx/tx/transaction-manager > 2013-04-16 06:12:25,484 [0x57fb3f0] DEBUG (HttpClient :74 ) - connect to localhost:8080 ok > 2013-04-16 06:12:25,491 [0x57fb3f0] DEBUG (HttpClient :99 ) - POST http://localhost:8080/rest-tx/tx/transaction-manager HTTP/1.1 > 2013-04-16 06:12:25,495 [0x57fb3f0] DEBUG (HttpClient :99 ) - Host: localhost > 2013-04-16 06:12:25,498 [0x57fb3f0] DEBUG (HttpClient :99 ) - Content-Length: 13 > 2013-04-16 06:12:25,500 [0x57fb3f0] DEBUG (HttpClient :99 ) - Content-Type: application/x-www-form-urlencoded > 2013-04-16 06:12:25,505 [0x57fb3f0] DEBUG (HttpClient :148 ) - timeout=-1000 > 2013-04-16 06:12:25,508 [0x57fb3f0] DEBUG (HttpClient :158 ) - buf size is 4096 > 2013-04-16 06:12:27,023 [0x57fb3f0] DEBUG (HttpClient :162 ) - receive 241 bytes > 2013-04-16 06:12:27,028 [0x57fb3f0] DEBUG (HttpClient :165 ) - HTTP/1.1 404 Not Found > Content-Length: 145 > Connection: keep-alive > Content-Type: text/html > Could not find resource for relative : /rest-tx/tx/transaction-manager of full path: http://localhosthttp/rest-tx/rest-tx/tx/transaction-manager? > 2013-04-16 06:12:27,049 [0x57fb3f0] DEBUG (HttpClient :194 ) - HTTP/1.1 404 Not Found > {code} > It looks like restat-web.war has not regiter as /rest-tx -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1402) Build timed out while running tests from TestGroup_rawresources02_2

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1402?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1402: ---------------------------------------- The test output shows all of the tests in group TestGroup_rawresources02_2 passing but the timestamp on the final 2 tests are: * drwxr-xr-x. 2 mmusgrov mmusgrov 4096 Apr 17 02:01 RawResources02_2_Test146 * drwxr-xr-x. 2 mmusgrov mmusgrov 4096 Apr 17 15:02 RawResources02_2_Test147 Test 146 should only takes seconds to run so I assume that Test146 is the culprit and that RawResources02_2_Test147 was a old file from a previous run. My recommendation is to split the job into 3 separate jobs to avoid this issue and also so that it is immediately obvious which database test is failing and also to see which database(s) are exceptionally slow (sometimes the job is taking over 4 days to complete). > Build timed out while running tests from TestGroup_rawresources02_2 > ------------------------------------------------------------------- > > Key: JBTM-1402 > URL: https://issues.jboss.org/browse/JBTM-1402 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 4.17.4 > > > Build failed to execute TestGroup_rawresources02_2 tests and timed out after 1440 minutes. > See: http://172.17.131.2/job/jbossts-narayana-java6/131 -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1637) XTS Unit Test Failure: Invalid fault type enumeration: Error reading XMLStreamReader

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1637?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1637: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/undertow-io/undertow/pull/78 > XTS Unit Test Failure: Invalid fault type enumeration: Error reading XMLStreamReader > ------------------------------------------------------------------------------------ > > Key: JBTM-1637 > URL: https://issues.jboss.org/browse/JBTM-1637 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/247 > In particular see: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/247/artifact/XTS/... > Lots of stacktraces, some of which are only warnings. > The First Groovy one is supposed to be benign. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1637) XTS Unit Test Failure: Invalid fault type enumeration: Error reading XMLStreamReader

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1637?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1637: ------------------------------------- Should be fixed in https://github.com/undertow-io/undertow/pull/78 > XTS Unit Test Failure: Invalid fault type enumeration: Error reading XMLStreamReader > ------------------------------------------------------------------------------------ > > Key: JBTM-1637 > URL: https://issues.jboss.org/browse/JBTM-1637 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/247 > In particular see: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/247/artifact/XTS/... > Lots of stacktraces, some of which are only warnings. > The First Groovy one is supposed to be benign. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1522) "no XTS application recovery module found" during XTS Recovery Tests

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1522?page=com.atlassian.jira.plugin.... ] Paul Robinson reassigned JBTM-1522: ----------------------------------- Assignee: Paul Robinson (was: Amos Feng) > "no XTS application recovery module found" during XTS Recovery Tests > -------------------------------------------------------------------- > > Key: JBTM-1522 > URL: https://issues.jboss.org/browse/JBTM-1522 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Critical > Fix For: 4.17.4, 5.0.0.M3 > > Attachments: 2013-04-01_jbtm-1522_outputs.zip, com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit-output.txt, com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-2.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-output-2.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-output.txt, com.arjuna.qa.junit.TestBACrashDuringCommit.txt, com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit-output.txt, com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit.txt > > > See: http://172.17.131.2/view/Narayana+BlackTie/job/narayana/211/artifact/XTS/... > Notice the following log is displayed repeatedly until the test gives up waiting for recovery: > {code} > WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046032: no XTS application recovery module found to help reactivate recovered WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > {code} > This error comes from org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple#recoverParticipants(). In particular: > {code} > if (!found) { > // we failed to find a helper to convert a participant record so log a warning > // but leave it in the table for next time > RecoveryLogger.i18NLogger.warn_participant_at_XTSATRecoveryModule_4(participantRecoveryRecord.getId()); > } > {code} > It looks like the code is unable to restore the participant from the log due to restoreParticipant(XTSATRecoveryModule module) returning false. There is ParticipantRecoveryRecord in the log as you can see it dumped to the console in the above log. Maybe there is a problem with that log, or maybe we are missing another log entry? > This problem is intermittent, so it's unlikely that you will see this happen when you attach a debugger. However, we could attach a debugger to see what happens in the normal case and also to inspect the log to see if anything is missing in the failing case. But I have a cunning plan... > h4.Cunning Plan > We need to get a copy of the failing log, before recovery is attempted. We should then be able to use that log to reproduce the issue on our own machines. Steps to take: > # Update BaseCrashTest to copy the contents of the tx-object-store to a unique folder location (So we can retrieve it later for a failed run). Make sure you create the folder structure under target/surefire-reports so that CI archives it off. Do the copy between controller.kill and controller.start. This way we get the log before the recovery manager has had chance to tamper with it. > # Update the "narayana-JBTM-1522" job in CI to use your branch, containing the change above. > # Configure the job to run @hourly until it fails with this problem. > # Take a copy of the tx-object-store from the failing test and then put it in place on your AS8 build. > # Boot the AS and confirm that the issue is reproduced. > # You can now keep putting the tx-object-store back in place every time you need to reproduce the issue. > # Attach a debugger to find out what the problem is. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1402) Build timed out while running tests from TestGroup_rawresources02_2

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1402?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1402: -------------------------------- Fix Version/s: 4.17.4 > Build timed out while running tests from TestGroup_rawresources02_2 > ------------------------------------------------------------------- > > Key: JBTM-1402 > URL: https://issues.jboss.org/browse/JBTM-1402 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 4.17.4 > > > Build failed to execute TestGroup_rawresources02_2 tests and timed out after 1440 minutes. > See: http://172.17.131.2/job/jbossts-narayana-java6/131 -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1402) Build timed out while running tests from TestGroup_rawresources02_2

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1402?page=com.atlassian.jira.plugin.... ] Paul Robinson reopened JBTM-1402: --------------------------------- > Build timed out while running tests from TestGroup_rawresources02_2 > ------------------------------------------------------------------- > > Key: JBTM-1402 > URL: https://issues.jboss.org/browse/JBTM-1402 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > > Build failed to execute TestGroup_rawresources02_2 tests and timed out after 1440 minutes. > See: http://172.17.131.2/job/jbossts-narayana-java6/131 -- 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

11 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues April 2013