[JBoss JIRA] (JBTM-1886) TX tests failed on the windows with 404 when connecting to /rest-tx/tx/transaction-manager
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1886?page=com.atlassian.jira.plugin.... ]
Amos Feng updated JBTM-1886:
----------------------------
Description:
{noformat}
2013-08-16 12:04:48,399 [0x00002104] DEBUG (HttpClient :263 ) - url: /rest-tx/tx/transaction-manager
2013-08-16 12:04:48,400 [0x00002104] DEBUG (HttpClient :114 ) - connected to TM on WIN-5GKPEREVUOO:8080 URI=/rest-tx/tx/transaction-manager
2013-08-16 12:04:48,401 [0x00002104] DEBUG (HttpClient :74 ) - connect to WIN-5GKPEREVUOO:8080 ok
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - POST /rest-tx/tx/transaction-manager HTTP/1.1
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Host: WIN-5GKPEREVUOO:8080
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Content-Length: 13
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Content-Type: application/x-www-form-urlencoded
2013-08-16 12:04:48,407 [0x00002104] DEBUG (HttpClient :148 ) - timeout=-1000
2013-08-16 12:04:48,407 [0x00002104] DEBUG (HttpClient :158 ) - buf size is 4096
2013-08-16 12:04:48,411 [0x00002104] DEBUG (HttpClient :162 ) - receive 169 bytes
2013-08-16 12:04:48,412 [0x00002104] DEBUG (HttpClient :165 ) - HTTP/1.1 404 Not Found
Connection: keep-alive
Content-Length: 74
Content-Type: text/html
<html><head><title>Error</title></head><body>404 - Not Found</body></html>
{noformat}
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
was:
{noformat}
2013-08-16 12:04:48,399 [0x00002104] DEBUG (HttpClient :263 ) - url: /rest-tx/tx/transaction-manager
2013-08-16 12:04:48,400 [0x00002104] DEBUG (HttpClient :114 ) - connected to TM on WIN-5GKPEREVUOO:8080 URI=/rest-tx/tx/transaction-manager
2013-08-16 12:04:48,401 [0x00002104] DEBUG (HttpClient :74 ) - connect to WIN-5GKPEREVUOO:8080 ok
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - POST /rest-tx/tx/transaction-manager HTTP/1.1
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Host: WIN-5GKPEREVUOO:8080
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Content-Length: 13
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Content-Type: application/x-www-form-urlencoded
{noformat}
2013-08-16 12:04:48,407 [0x00002104] DEBUG (HttpClient :148 ) - timeout=-1000
2013-08-16 12:04:48,407 [0x00002104] DEBUG (HttpClient :158 ) - buf size is 4096
2013-08-16 12:04:48,411 [0x00002104] DEBUG (HttpClient :162 ) - receive 169 bytes
2013-08-16 12:04:48,412 [0x00002104] DEBUG (HttpClient :165 ) - HTTP/1.1 404 Not Found
Connection: keep-alive
Content-Length: 74
Content-Type: text/html
<html><head><title>Error</title></head><body>404 - Not Found</body></html>
{noformat}
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
> TX tests failed on the windows with 404 when connecting to /rest-tx/tx/transaction-manager
> ------------------------------------------------------------------------------------------
>
> Key: JBTM-1886
> URL: https://issues.jboss.org/browse/JBTM-1886
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie, REST, Testing
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 5.0.0.M5
>
>
> {noformat}
> 2013-08-16 12:04:48,399 [0x00002104] DEBUG (HttpClient :263 ) - url: /rest-tx/tx/transaction-manager
> 2013-08-16 12:04:48,400 [0x00002104] DEBUG (HttpClient :114 ) - connected to TM on WIN-5GKPEREVUOO:8080 URI=/rest-tx/tx/transaction-manager
> 2013-08-16 12:04:48,401 [0x00002104] DEBUG (HttpClient :74 ) - connect to WIN-5GKPEREVUOO:8080 ok
> 2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - POST /rest-tx/tx/transaction-manager HTTP/1.1
> 2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Host: WIN-5GKPEREVUOO:8080
> 2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Content-Length: 13
> 2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Content-Type: application/x-www-form-urlencoded
> 2013-08-16 12:04:48,407 [0x00002104] DEBUG (HttpClient :148 ) - timeout=-1000
> 2013-08-16 12:04:48,407 [0x00002104] DEBUG (HttpClient :158 ) - buf size is 4096
> 2013-08-16 12:04:48,411 [0x00002104] DEBUG (HttpClient :162 ) - receive 169 bytes
> 2013-08-16 12:04:48,412 [0x00002104] DEBUG (HttpClient :165 ) - HTTP/1.1 404 Not Found
> Connection: keep-alive
> Content-Length: 74
> Content-Type: text/html
> <html><head><title>Error</title></head><body>404 - Not Found</body></html>
> {noformat}
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
--
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
12 years, 7 months
[JBoss JIRA] (JBTM-1886) TX tests failed on the windows with 404 when connecting to /rest-tx/tx/transaction-manager
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1886?page=com.atlassian.jira.plugin.... ]
Amos Feng updated JBTM-1886:
----------------------------
Description:
{noformat}
2013-08-16 12:04:48,399 [0x00002104] DEBUG (HttpClient :263 ) - url: /rest-tx/tx/transaction-manager
2013-08-16 12:04:48,400 [0x00002104] DEBUG (HttpClient :114 ) - connected to TM on WIN-5GKPEREVUOO:8080 URI=/rest-tx/tx/transaction-manager
2013-08-16 12:04:48,401 [0x00002104] DEBUG (HttpClient :74 ) - connect to WIN-5GKPEREVUOO:8080 ok
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - POST /rest-tx/tx/transaction-manager HTTP/1.1
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Host: WIN-5GKPEREVUOO:8080
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Content-Length: 13
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Content-Type: application/x-www-form-urlencoded
{noformat}
2013-08-16 12:04:48,407 [0x00002104] DEBUG (HttpClient :148 ) - timeout=-1000
2013-08-16 12:04:48,407 [0x00002104] DEBUG (HttpClient :158 ) - buf size is 4096
2013-08-16 12:04:48,411 [0x00002104] DEBUG (HttpClient :162 ) - receive 169 bytes
2013-08-16 12:04:48,412 [0x00002104] DEBUG (HttpClient :165 ) - HTTP/1.1 404 Not Found
Connection: keep-alive
Content-Length: 74
Content-Type: text/html
<html><head><title>Error</title></head><body>404 - Not Found</body></html>
{noformat}
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
was:
2013-08-16 12:04:48,399 [0x00002104] DEBUG (HttpClient :263 ) - url: /rest-tx/tx/transaction-manager
2013-08-16 12:04:48,400 [0x00002104] DEBUG (HttpClient :114 ) - connected to TM on WIN-5GKPEREVUOO:8080 URI=/rest-tx/tx/transaction-manager
2013-08-16 12:04:48,401 [0x00002104] DEBUG (HttpClient :74 ) - connect to WIN-5GKPEREVUOO:8080 ok
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - POST /rest-tx/tx/transaction-manager HTTP/1.1
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Host: WIN-5GKPEREVUOO:8080
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Content-Length: 13
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Content-Type: application/x-www-form-urlencoded
{noformat}
2013-08-16 12:04:48,407 [0x00002104] DEBUG (HttpClient :148 ) - timeout=-1000
2013-08-16 12:04:48,407 [0x00002104] DEBUG (HttpClient :158 ) - buf size is 4096
2013-08-16 12:04:48,411 [0x00002104] DEBUG (HttpClient :162 ) - receive 169 bytes
2013-08-16 12:04:48,412 [0x00002104] DEBUG (HttpClient :165 ) - HTTP/1.1 404 Not Found
Connection: keep-alive
Content-Length: 74
Content-Type: text/html
<html><head><title>Error</title></head><body>404 - Not Found</body></html>
{noformat}
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
> TX tests failed on the windows with 404 when connecting to /rest-tx/tx/transaction-manager
> ------------------------------------------------------------------------------------------
>
> Key: JBTM-1886
> URL: https://issues.jboss.org/browse/JBTM-1886
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie, REST, Testing
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 5.0.0.M5
>
>
> {noformat}
> 2013-08-16 12:04:48,399 [0x00002104] DEBUG (HttpClient :263 ) - url: /rest-tx/tx/transaction-manager
> 2013-08-16 12:04:48,400 [0x00002104] DEBUG (HttpClient :114 ) - connected to TM on WIN-5GKPEREVUOO:8080 URI=/rest-tx/tx/transaction-manager
> 2013-08-16 12:04:48,401 [0x00002104] DEBUG (HttpClient :74 ) - connect to WIN-5GKPEREVUOO:8080 ok
> 2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - POST /rest-tx/tx/transaction-manager HTTP/1.1
> 2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Host: WIN-5GKPEREVUOO:8080
> 2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Content-Length: 13
> 2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Content-Type: application/x-www-form-urlencoded
> {noformat}
> 2013-08-16 12:04:48,407 [0x00002104] DEBUG (HttpClient :148 ) - timeout=-1000
> 2013-08-16 12:04:48,407 [0x00002104] DEBUG (HttpClient :158 ) - buf size is 4096
> 2013-08-16 12:04:48,411 [0x00002104] DEBUG (HttpClient :162 ) - receive 169 bytes
> 2013-08-16 12:04:48,412 [0x00002104] DEBUG (HttpClient :165 ) - HTTP/1.1 404 Not Found
> Connection: keep-alive
> Content-Length: 74
> Content-Type: text/html
> <html><head><title>Error</title></head><body>404 - Not Found</body></html>
> {noformat}
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
--
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
12 years, 7 months
[JBoss JIRA] (JBTM-1886) TX tests failed on the windows with 404 when connecting to /rest-tx/tx/transaction-manager
by Amos Feng (JIRA)
Amos Feng created JBTM-1886:
-------------------------------
Summary: TX tests failed on the windows with 404 when connecting to /rest-tx/tx/transaction-manager
Key: JBTM-1886
URL: https://issues.jboss.org/browse/JBTM-1886
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: BlackTie, REST, Testing
Reporter: Amos Feng
Assignee: Amos Feng
Fix For: 5.0.0.M5
2013-08-16 12:04:48,399 [0x00002104] DEBUG (HttpClient :263 ) - url: /rest-tx/tx/transaction-manager
2013-08-16 12:04:48,400 [0x00002104] DEBUG (HttpClient :114 ) - connected to TM on WIN-5GKPEREVUOO:8080 URI=/rest-tx/tx/transaction-manager
2013-08-16 12:04:48,401 [0x00002104] DEBUG (HttpClient :74 ) - connect to WIN-5GKPEREVUOO:8080 ok
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - POST /rest-tx/tx/transaction-manager HTTP/1.1
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Host: WIN-5GKPEREVUOO:8080
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Content-Length: 13
2013-08-16 12:04:48,402 [0x00002104] DEBUG (HttpClient :99 ) - Content-Type: application/x-www-form-urlencoded
{noformat}
2013-08-16 12:04:48,407 [0x00002104] DEBUG (HttpClient :148 ) - timeout=-1000
2013-08-16 12:04:48,407 [0x00002104] DEBUG (HttpClient :158 ) - buf size is 4096
2013-08-16 12:04:48,411 [0x00002104] DEBUG (HttpClient :162 ) - receive 169 bytes
2013-08-16 12:04:48,412 [0x00002104] DEBUG (HttpClient :165 ) - HTTP/1.1 404 Not Found
Connection: keep-alive
Content-Length: 74
Content-Type: text/html
<html><head><title>Error</title></head><body>404 - Not Found</body></html>
{noformat}
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
--
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
12 years, 7 months
[JBoss JIRA] (JBTM-1885) RTS InboundBridgeTestCase failures
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1885?page=com.atlassian.jira.plugin.... ]
Amos Feng updated JBTM-1885:
----------------------------
Description:
{noformat}
Results :
Failed tests: testRollbackWithTwoParticipants(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): expected:<0> but was:<1>
testCommit(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): expected:<0> but was:<1>
testRollback(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): expected:<0> but was:<1>
Tests in error:
testRollbackWithTwoParticipants(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): Unexpected status. Expected 200 got 500
testRollback(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): Unexpected status. Expected 200 got 500
{noformat}
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/233/TESTS=MAIN,jd...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/234/TESTS=BLACKTI...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/235/TESTS=BLACKTI...
was:
{noformat}
Results :
Failed tests: testRollbackWithTwoParticipants(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): expected:<0> but was:<1>
testCommit(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): expected:<0> but was:<1>
testRollback(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): expected:<0> but was:<1>
Tests in error:
testRollbackWithTwoParticipants(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): Unexpected status. Expected 200 got 500
testRollback(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): Unexpected status. Expected 200 got 500
{noformat}
> RTS InboundBridgeTestCase failures
> ----------------------------------
>
> Key: JBTM-1885
> URL: https://issues.jboss.org/browse/JBTM-1885
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: REST, Testing
> Affects Versions: 5.0.0.M4
> Reporter: Amos Feng
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M5
>
>
> {noformat}
> Results :
> Failed tests: testRollbackWithTwoParticipants(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): expected:<0> but was:<1>
> testCommit(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): expected:<0> but was:<1>
> testRollback(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): expected:<0> but was:<1>
> Tests in error:
> testRollbackWithTwoParticipants(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): Unexpected status. Expected 200 got 500
> testRollback(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): Unexpected status. Expected 200 got 500
> {noformat}
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/233/TESTS=MAIN,jd...
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/234/TESTS=BLACKTI...
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/235/TESTS=BLACKTI...
--
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
12 years, 7 months
[JBoss JIRA] (JBTM-1885) RTS InboundBridgeTestCase failures
by Amos Feng (JIRA)
Amos Feng created JBTM-1885:
-------------------------------
Summary: RTS InboundBridgeTestCase failures
Key: JBTM-1885
URL: https://issues.jboss.org/browse/JBTM-1885
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: REST, Testing
Affects Versions: 5.0.0.M4
Reporter: Amos Feng
Assignee: Gytis Trikleris
Fix For: 5.0.0.M5
{noformat}
Results :
Failed tests: testRollbackWithTwoParticipants(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): expected:<0> but was:<1>
testCommit(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): expected:<0> but was:<1>
testRollback(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): expected:<0> but was:<1>
Tests in error:
testRollbackWithTwoParticipants(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): Unexpected status. Expected 200 got 500
testRollback(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): Unexpected status. Expected 200 got 500
{noformat}
--
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
12 years, 7 months
[JBoss JIRA] (JBTM-1674) btadmin.PauseDomainTest failed with command failure
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1674?page=com.atlassian.jira.plugin.... ]
Amos Feng updated JBTM-1674:
----------------------------
Fix Version/s: 5.0.0.M5
(was: 5.0.0.Final)
> btadmin.PauseDomainTest failed with command failure
> ---------------------------------------------------
>
> Key: JBTM-1674
> URL: https://issues.jboss.org/browse/JBTM-1674
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Amos Feng
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.0.M5
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64-el5/1501
> {noformat}
> -------------------------------------------------------------------------------
> Test set: org.jboss.narayana.blacktie.btadmin.PauseDomainTest
> -------------------------------------------------------------------------------
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 83.154 sec <<< FAILURE!
> testPauseDomainWithArg(org.jboss.narayana.blacktie.btadmin.PauseDomainTest) Time elapsed: 53.947 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Command failed
> at junit.framework.Assert.fail(Assert.java:47)
> at org.jboss.narayana.blacktie.btadmin.PauseDomainTest.setUp(PauseDomainTest.java:48)
> at junit.framework.TestCase.runBare(TestCase.java:125)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:98)
> at org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:107)
> at org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:84)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
> at com.sun.proxy.$Proxy0.invoke(Unknown Source)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> {noformat}
--
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
12 years, 7 months
[JBoss JIRA] (JBTM-1674) btadmin.PauseDomainTest failed with command failure
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1674?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1674:
---------------------------------
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/TESTS=BLACKTIE,jd...
> btadmin.PauseDomainTest failed with command failure
> ---------------------------------------------------
>
> Key: JBTM-1674
> URL: https://issues.jboss.org/browse/JBTM-1674
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Amos Feng
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.0.Final
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64-el5/1501
> {noformat}
> -------------------------------------------------------------------------------
> Test set: org.jboss.narayana.blacktie.btadmin.PauseDomainTest
> -------------------------------------------------------------------------------
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 83.154 sec <<< FAILURE!
> testPauseDomainWithArg(org.jboss.narayana.blacktie.btadmin.PauseDomainTest) Time elapsed: 53.947 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Command failed
> at junit.framework.Assert.fail(Assert.java:47)
> at org.jboss.narayana.blacktie.btadmin.PauseDomainTest.setUp(PauseDomainTest.java:48)
> at junit.framework.TestCase.runBare(TestCase.java:125)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:98)
> at org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:107)
> at org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:84)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
> at com.sun.proxy.$Proxy0.invoke(Unknown Source)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> {noformat}
--
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
12 years, 7 months
[JBoss JIRA] (JBTM-1867) Confusing error logged after crash recovery on prepare when hornetq object store used
by Ondřej Chaloupka (JIRA)
[ https://issues.jboss.org/browse/JBTM-1867?page=com.atlassian.jira.plugin.... ]
Ondřej Chaloupka commented on JBTM-1867:
----------------------------------------
Hi Mike,
I'm sorry for longer response time.
I do understand that it's hard (or impossible) to detect the second round of the rollback but it's when the circumstances occur then the log is full of nasty messages. And it's true that is not every day scenario to see such messages but still it's not much kind to user to show him error messages in case that no error occurs.
Maybe at least would be better to log that message by logger than to stderr? But of course I'm not sure whether there is some reason for such behaviour.
Or maybe to reduce the severity to INFO? By default messages from com.arjuna are logged (shown to user) from severity WARN and higher. But probably this is not good solution either as Mark pointed.
I can live with such error messages in this log but I don't like it.
Do you mind to discuss this with Tom next week?
Thank you
Ondra
> Confusing error logged after crash recovery on prepare when hornetq object store used
> -------------------------------------------------------------------------------------
>
> Key: JBTM-1867
> URL: https://issues.jboss.org/browse/JBTM-1867
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTS
> Affects Versions: 4.17.7, 5.0.0.M3
> Reporter: Ondřej Chaloupka
> Assignee: Michael Musgrove
>
> There is logged an confusing error after crash recovery happens when server crashed in prepare phase.
> {code}
> 14:47:59,697 ERROR [stderr] (RequestProcessor-10) com.arjuna.ats.arjuna.exceptions.ObjectStoreException: java.lang.IllegalStateException: Cannot find add info 3
> 14:47:59,698 ERROR [stderr] (RequestProcessor-10) at com.arjuna.ats.internal.arjuna.objectstore.hornetq.HornetqJournalStore.remove_committed(HornetqJournalStore.java:153)
> 14:47:59,698 ERROR [stderr] (RequestProcessor-10) at com.arjuna.ats.internal.arjuna.objectstore.hornetq.HornetqObjectStoreAdaptor.remove_committed(HornetqObjectStoreAdaptor.java:186)
> 14:47:59,698 ERROR [stderr] (RequestProcessor-10) at com.arjuna.ats.internal.jta.resources.jts.orbspecific.XAResourceRecord.destroyState(XAResourceRecord.java:1271)
> 14:47:59,699 INFO [org.jboss.as.test.jbossts.common.TestXAResourceCommon] (Periodic Recovery) TestXAResourceCommon.isSameRM(xaResource=TestXAResourceRecovered(TestXAResourceCommon(0, null)))
> 14:47:59,699 ERROR [stderr] (RequestProcessor-10) at com.arjuna.ats.internal.jta.resources.jts.orbspecific.XAResourceRecord.rollback(XAResourceRecord.java:411)
> 14:47:59,699 ERROR [stderr] (RequestProcessor-10) at com.arjuna.ArjunaOTS.OTSAbstractRecordPOA._invoke(OTSAbstractRecordPOA.java:213)
> 14:47:59,699 ERROR [stderr] (RequestProcessor-10) at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:306)
> 14:47:59,699 ERROR [stderr] (RequestProcessor-10) at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:626)
> 14:47:59,699 ERROR [stderr] (RequestProcessor-10) at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:769)
> 14:47:59,700 ERROR [stderr] (RequestProcessor-10) Caused by: java.lang.IllegalStateException: Cannot find add info 3
> 14:47:59,700 ERROR [stderr] (RequestProcessor-10) at org.hornetq.core.journal.impl.JournalImpl.appendDeleteRecord(JournalImpl.java:904)
> 14:47:59,700 ERROR [stderr] (RequestProcessor-10) at org.hornetq.core.journal.impl.JournalBase.appendDeleteRecord(JournalBase.java:163)
> 14:47:59,700 ERROR [stderr] (RequestProcessor-10) at org.hornetq.core.journal.impl.JournalImpl.appendDeleteRecord(JournalImpl.java:82)
> 14:47:59,701 ERROR [stderr] (RequestProcessor-10) at com.arjuna.ats.internal.arjuna.objectstore.hornetq.HornetqJournalStore.remove_committed(HornetqJournalStore.java:151)
> 14:47:59,701 ERROR [stderr] (RequestProcessor-10) ... 7 more
> {code}
> This happens when hornetq object store is used. This is caused because of the rollback is called on resource two times. This is ok - this matches to OTS spec (https://bugzilla.redhat.com/show_bug.cgi?id=988724).
> But after the second call of rollback the TM tries to remove Xid from object store. But as the xid does not exist anymore the hornetq object store implementation throws exception that is logged directly on stderr:
> XAResourceRecord.destroyState does e.printStackTrace()
> I would propose to put this exception to debug or trace as it does not mean error in fact.
--
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
12 years, 7 months