]
Amos Feng updated JBTM-1634:
----------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request:
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: