September 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1924) Build does not stop on Windows if there is a build failure on the AS and it is not a pull request

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1924: ----------------------------------- Summary: Build does not stop on Windows if there is a build failure on the AS and it is not a pull request Key: JBTM-1924 URL: https://issues.jboss.org/browse/JBTM-1924 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Paul Robinson You can see the AS failed to build: http://172.17.131.2/job/narayana-windows2008-taconic/415/console I suspect it is something to do with: call build.bat clean install "-DskipTests" "-Drelease=true" || (call:comment_on_pull "AS Failed %BUILD_URL%" && exit -1) Maybe commit on pull is returning false because nothing is done? -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1923) JTA quick start guide link on website incorrect

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1923: ----------------------------------- Summary: JTA quick start guide link on website incorrect Key: JBTM-1923 URL: https://issues.jboss.org/browse/JBTM-1923 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Reporter: Tom Jenkinson Assignee: Tom Jenkinson on http://www.jboss.org/jbosstm/documentation/5_0_0_M4 for jta quick start guide the link, instead of quick_start_guide is only quick_start -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1923) JTA quick start guide link on website incorrect

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1923?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1923: -------------------------------- Reporter: Ondřej Chaloupka (was: Tom Jenkinson) > JTA quick start guide link on website incorrect > ----------------------------------------------- > > Key: JBTM-1923 > URL: https://issues.jboss.org/browse/JBTM-1923 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Ondřej Chaloupka > Assignee: Tom Jenkinson > > on http://www.jboss.org/jbosstm/documentation/5_0_0_M4 > for jta quick start guide the link, instead of quick_start_guide is only quick_start -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1920) Blacktie TestTransactions test failed: REST-AT stricter?

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1920?page=com.atlassian.jira.plugin.... ] Michael Musgrove edited comment on JBTM-1920 at 9/15/13 9:43 PM: ----------------------------------------------------------------- I've reduce the priority since I have committed a work around - blacktie passes the enlistment urls in the http request body (instead of the Link header). Someone needs to run the RTS quickstarts against the latest wildfly asap. Note that the problem is somewhere between undertow and the resteasy interceptors since I tried manually enlisting using the Link header via the command line (cURL) and got the same problem (namely the JAX-RS @HeaderParam("Link") annotation is coming through as a null value): {code} [hudson@tenafly blacktie]$ curl -d "timeout=10" -X POST http://localhost:8080/rest-tx/tx/transaction-manager # this line creates a new transaction [hudson@tenafly blacktie]$ curl http://localhost:8080/rest-tx/tx/transaction-manager # get the resource url for the new transaction http://localhost:8080/rest-tx/tx/transaction-manager/0_ffffac118314_-2cc3... # now enlist a participant using a Link header [hudson@tenafly blacktie]$ curl -X POST --header "Link: <http://127.0.0.1:8888/xid/131077%3a100%3a0%3a1%3a1379280076%3a834173/term...>;rel="terminator",<http://127.0.0.1:8888/xid/131077%3a100%3a0%3a1%3a1379280076%3a834173/status>;rel="participant"" http://localhost:8080/rest-tx/tx/transaction-manager/0_ffffac118314_-2cc3... Missing Enlistment Link Header[hudson@tenafly blacktie]$ {code} was (Author: mmusgrov): I've reduce the priority since I have committed a work around - blacktie passes the enlistment urls in the http request body (instead of the Link header). Note that the problem is somewhere between undertow and the resteasy interceptors since I tried manually enlisting using the Link header via the command line (cURL) and got the same problem (namely the JAX-RS @HeaderParam("Link") annotation is coming through as a null value): {code} [hudson@tenafly blacktie]$ curl -d "timeout=10" -X POST http://localhost:8080/rest-tx/tx/transaction-manager # this line creates a new transaction [hudson@tenafly blacktie]$ curl http://localhost:8080/rest-tx/tx/transaction-manager # get the resource url for the new transaction http://localhost:8080/rest-tx/tx/transaction-manager/0_ffffac118314_-2cc3... # now enlist a participant using a Link header [hudson@tenafly blacktie]$ curl -X POST --header "Link: <http://127.0.0.1:8888/xid/131077%3a100%3a0%3a1%3a1379280076%3a834173/term...>;rel="terminator",<http://127.0.0.1:8888/xid/131077%3a100%3a0%3a1%3a1379280076%3a834173/status>;rel="participant"" http://localhost:8080/rest-tx/tx/transaction-manager/0_ffffac118314_-2cc3... Missing Enlistment Link Header[hudson@tenafly blacktie]$ {code} > Blacktie TestTransactions test failed: REST-AT stricter? > -------------------------------------------------------- > > Key: JBTM-1920 > URL: https://issues.jboss.org/browse/JBTM-1920 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.0.0.M5 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI... > {code} > Test Results: > [exec] Run: 14 Failures: 10 Errors: 0 > [exec] > [exec] > [exec] 1) test: TestTransactions::test_basic (F) line: 90 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTxAvoid.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 2) test: TestTransactions::test_transactions (F) line: 94 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 3) test: TestTransactions::test_protocol (F) line: 125 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 4) test: TestTransactions::test_info (F) line: 165 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 5) test: TestTransactions::test_timeout1 (F) line: 217 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 6) test: TestTransactions::test_timeout2 (F) line: 261 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 7) test: TestTransactions::test_rollback (F) line: 285 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 8) test: TestTransactions::test_hhazard (F) line: 317 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 9) test: TestTransactions::test_RM (F) line: 345 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 10) test: TestTransactions::test_recovery (F) line: 486 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1920) Blacktie TestTransactions test failed: REST-AT stricter?

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1920?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1920: ---------------------------------------- I've reduce the priority since I have committed a work around - blacktie passes the enlistment urls in the http request body (instead of the Link header). Note that the problem is somewhere between undertow and the resteasy interceptors since I tried manually enlisting using the Link header via the command line (cURL) and got the same problem (namely the JAX-RS @HeaderParam("Link") annotation is coming through as a null value): {code} [hudson@tenafly blacktie]$ curl -d "timeout=10" -X POST http://localhost:8080/rest-tx/tx/transaction-manager # this line creates a new transaction [hudson@tenafly blacktie]$ curl http://localhost:8080/rest-tx/tx/transaction-manager # get the resource url for the new transaction http://localhost:8080/rest-tx/tx/transaction-manager/0_ffffac118314_-2cc3... # now enlist a participant using a Link header [hudson@tenafly blacktie]$ curl -X POST --header "Link: <http://127.0.0.1:8888/xid/131077%3a100%3a0%3a1%3a1379280076%3a834173/term...>;rel="terminator",<http://127.0.0.1:8888/xid/131077%3a100%3a0%3a1%3a1379280076%3a834173/status>;rel="participant"" http://localhost:8080/rest-tx/tx/transaction-manager/0_ffffac118314_-2cc3... Missing Enlistment Link Header[hudson@tenafly blacktie]$ {code} > Blacktie TestTransactions test failed: REST-AT stricter? > -------------------------------------------------------- > > Key: JBTM-1920 > URL: https://issues.jboss.org/browse/JBTM-1920 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.0.0.M5 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI... > {code} > Test Results: > [exec] Run: 14 Failures: 10 Errors: 0 > [exec] > [exec] > [exec] 1) test: TestTransactions::test_basic (F) line: 90 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTxAvoid.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 2) test: TestTransactions::test_transactions (F) line: 94 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 3) test: TestTransactions::test_protocol (F) line: 125 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 4) test: TestTransactions::test_info (F) line: 165 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 5) test: TestTransactions::test_timeout1 (F) line: 217 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 6) test: TestTransactions::test_timeout2 (F) line: 261 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 7) test: TestTransactions::test_rollback (F) line: 285 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 8) test: TestTransactions::test_hhazard (F) line: 317 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 9) test: TestTransactions::test_RM (F) line: 345 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 10) test: TestTransactions::test_recovery (F) line: 486 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1920) Blacktie TestTransactions test failed: REST-AT stricter?

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1920?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1920: ----------------------------------- Priority: Major (was: Critical) > Blacktie TestTransactions test failed: REST-AT stricter? > -------------------------------------------------------- > > Key: JBTM-1920 > URL: https://issues.jboss.org/browse/JBTM-1920 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.0.0.M5 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI... > {code} > Test Results: > [exec] Run: 14 Failures: 10 Errors: 0 > [exec] > [exec] > [exec] 1) test: TestTransactions::test_basic (F) line: 90 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTxAvoid.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 2) test: TestTransactions::test_transactions (F) line: 94 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 3) test: TestTransactions::test_protocol (F) line: 125 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 4) test: TestTransactions::test_info (F) line: 165 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 5) test: TestTransactions::test_timeout1 (F) line: 217 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 6) test: TestTransactions::test_timeout2 (F) line: 261 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 7) test: TestTransactions::test_rollback (F) line: 285 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 8) test: TestTransactions::test_hhazard (F) line: 317 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 9) test: TestTransactions::test_RM (F) line: 345 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 10) test: TestTransactions::test_recovery (F) line: 486 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1920) Blacktie TestTransactions test failed: REST-AT stricter?

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1920?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1920: ---------------------------------------- I have raised a PR containing a temporary fix. The most relevant wildfly commit is https://github.com/wildfly/wildfly/commit/8feb7d7d86e2a9619dbf7997b22d163... which upgraded undertow (https://github.com/undertow-io/undertow) to Beta13 > Blacktie TestTransactions test failed: REST-AT stricter? > -------------------------------------------------------- > > Key: JBTM-1920 > URL: https://issues.jboss.org/browse/JBTM-1920 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.0.0.M5 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI... > {code} > Test Results: > [exec] Run: 14 Failures: 10 Errors: 0 > [exec] > [exec] > [exec] 1) test: TestTransactions::test_basic (F) line: 90 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTxAvoid.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 2) test: TestTransactions::test_transactions (F) line: 94 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 3) test: TestTransactions::test_protocol (F) line: 125 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 4) test: TestTransactions::test_info (F) line: 165 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 5) test: TestTransactions::test_timeout1 (F) line: 217 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 6) test: TestTransactions::test_timeout2 (F) line: 261 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 7) test: TestTransactions::test_rollback (F) line: 285 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 8) test: TestTransactions::test_hhazard (F) line: 317 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 9) test: TestTransactions::test_RM (F) line: 345 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > [exec] > [exec] > [exec] 10) test: TestTransactions::test_recovery (F) line: 486 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx > [exec] equality assertion failed > [exec] - Expected: 0 > [exec] - Actual : -6 > {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1922) RTS error and warning messages do have unique codes for identification purposes

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1922?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1922: ----------------------------------- Fix Version/s: 6.0.0.Final > RTS error and warning messages do have unique codes for identification purposes > ------------------------------------------------------------------------------- > > Key: JBTM-1922 > URL: https://issues.jboss.org/browse/JBTM-1922 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: REST > Affects Versions: 5.0.0.M4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.0.0.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > > ANDIAMO-7 says that all error and warning messages should have a unique code that can be used to identify them. RTS does not conform with this requirement. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1922) RTS error and warning messages do have unique codes for identification purposes

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1922?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1922: ----------------------------------- Affects Version/s: 5.0.0.M4 > RTS error and warning messages do have unique codes for identification purposes > ------------------------------------------------------------------------------- > > Key: JBTM-1922 > URL: https://issues.jboss.org/browse/JBTM-1922 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: REST > Affects Versions: 5.0.0.M4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Original Estimate: 2 days > Remaining Estimate: 2 days > > ANDIAMO-7 says that all error and warning messages should have a unique code that can be used to identify them. RTS does not conform with this requirement. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1922) RTS error and warning messages do have unique codes for identification purposes

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1922: -------------------------------------- Summary: RTS error and warning messages do have unique codes for identification purposes Key: JBTM-1922 URL: https://issues.jboss.org/browse/JBTM-1922 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: REST Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Minor ANDIAMO-7 says that all error and warning messages should have a unique code that can be used to identify them. RTS does not conform with this requirement. -- 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, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2013