[
https://issues.jboss.org/browse/JBTM-1762?page=com.atlassian.jira.plugin....
]
Michael Musgrove commented on JBTM-1762:
----------------------------------------
I have noticed that the BlackTie transaction completion code performs an HTTP HEAD request
followed by an HTTP PUT. This is going to seriously degrade transaction throughput. Can we
discuss why the HEAD request is needed and try and figure out an alternative.
TX TestTransactions::test_rollback failed with un-expect TX_FAIL
----------------------------------------------------------------
Key: JBTM-1762
URL:
https://issues.jboss.org/browse/JBTM-1762
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: BlackTie
Reporter: Amos Feng
Assignee: Amos Feng
Fix For: 5.0.0.M4
Original Estimate: 2 days
Remaining Estimate: 2 days
{noformat}
[exec] 1) test: TestTransactions::test_rollback (F) line: 288
/home/hudson/workspace/blacktie-linux32/tx/src/test/cpp/TestTransactions.cxx
[exec] equality assertion failed
[exec] - Expected: -2
[exec] - Actual : -7
{noformat}
It looks like the TM server returns code 412 and no content. so tx_commit() returns
TX_FAIL but expects TX_ROLLBACK.
{code}
2013-06-07 08:34:08,732 [0x57fd3f0] DEBUG (HttpClient :162 ) - receive 79
bytes
2013-06-07 08:34:08,734 [0x57fd3f0] DEBUG (HttpClient :165 ) - HTTP/1.1 412
Precondition Failed
Connection: keep-alive
Content-Length: 0
2013-06-07 08:34:08,736 [0x57fd3f0] DEBUG (HttpClient :194 ) - HTTP/1.1 412
Precondition Failed
2013-06-07 08:34:08,738 [0x57fd3f0] DEBUG (HttpClient :194 ) - Connection:
keep-alive
2013-06-07 08:34:08,739 [0x57fd3f0] DEBUG (HttpClient :194 ) -
Content-Length: 0
2013-06-07 08:34:08,741 [0x57fd3f0] DEBUG (HttpClient :220 ) -
status_code:412
2013-06-07 08:34:08,743 [0x57fd3f0] DEBUG (TxHttpControl :299 ) - do_end: HTTP
status: 412 resp:
2013-06-07 08:34:08,745 [0x57fd3f0] DEBUG (TxControl :66 ) - end:
outcome: -7
{code}
--
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