[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:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> 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, REST
> Reporter: Gytis Trikleris
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.0.0.Final
>
>
> 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
10 years, 9 months
[JBoss JIRA] (JBTM-1965) Add support for XADisk
by Mark Little (JIRA)
Mark Little created JBTM-1965:
---------------------------------
Summary: Add support for XADisk
Key: JBTM-1965
URL: https://issues.jboss.org/browse/JBTM-1965
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Student project
Affects Versions: 5.0.0.M5
Reporter: Mark Little
Assignee: Paul Robinson
We're unlikely to maintain fileio but there may be a need for supporting some transactional file interactions. XADisk (https://xadisk.java.net/) seems to have a vibrant user community, so we should take a look at this.
--
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
10 years, 9 months
[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:
-----------------------------------
Git Pull Request: https://github.com/jbosstm/narayana/pull/485 (was: https://github.com/jbosstm/narayana/pull/436)
> 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, REST
> Reporter: Gytis Trikleris
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.0.0.Final
>
>
> 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
10 years, 9 months
[JBoss JIRA] (JBTM-1964) Create a separate student/incubator repo
by Mark Little (JIRA)
Mark Little created JBTM-1964:
---------------------------------
Summary: Create a separate student/incubator repo
Key: JBTM-1964
URL: https://issues.jboss.org/browse/JBTM-1964
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Student project
Affects Versions: 5.0.0.M5
Reporter: Mark Little
Assignee: Paul Robinson
Some student projects, such as fileio, are unlikely to every be supported or maintained. Having them in the main repo causes confusion. We should have a separate student project repo where they can live until we decide to move them into the main repo. Maybe have this as a generic incubator for more than student projects?
--
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
10 years, 9 months
[JBoss JIRA] (JBTM-1963) Automatically added TXBridge handler should be optional
by Gytis Trikleris (JIRA)
Gytis Trikleris created JBTM-1963:
-------------------------------------
Summary: Automatically added TXBridge handler should be optional
Key: JBTM-1963
URL: https://issues.jboss.org/browse/JBTM-1963
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Application Server Integration, TxBridge
Reporter: Gytis Trikleris
Assignee: Paul Robinson
Fix For: 5.0.0.Final
XTS subsystem automatically adds XTS and TXBridge handlers if the deployment has a class annotated with @WebService and @Transactional. However, TXBridge handler required the WS-AT transaction to be available for every request. If the transaction is not present, it fails to handle the message with com.arjuna.wst.UnknownTransactionException.
The problem arises when @Transactional annotation has a type such as SUPPORTED, in which case WS-AT transaction should not be mandatory.
--
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
10 years, 9 months
[JBoss JIRA] (JBTM-1963) Automatically added TXBridge handler should be optional
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1963?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-1963:
----------------------------------
Description:
XTS subsystem automatically adds XTS and TXBridge handlers if the deployment has a class annotated with @WebService and @Transactional. However, TXBridge handler required the WS-AT transaction to be available for every request. If the transaction is not present, it fails to handle the message with com.arjuna.wst.UnknownTransactionException.
The problem arises when @Transactional annotation has a type such as SUPPORTED, in which case WS-AT transaction should not be mandatory.
We could write a wrapper for the current handler, which will delegate the call only if the transaction is available.
was:
XTS subsystem automatically adds XTS and TXBridge handlers if the deployment has a class annotated with @WebService and @Transactional. However, TXBridge handler required the WS-AT transaction to be available for every request. If the transaction is not present, it fails to handle the message with com.arjuna.wst.UnknownTransactionException.
The problem arises when @Transactional annotation has a type such as SUPPORTED, in which case WS-AT transaction should not be mandatory.
> Automatically added TXBridge handler should be optional
> -------------------------------------------------------
>
> Key: JBTM-1963
> URL: https://issues.jboss.org/browse/JBTM-1963
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Application Server Integration, TxBridge
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> Fix For: 5.0.0.Final
>
>
> XTS subsystem automatically adds XTS and TXBridge handlers if the deployment has a class annotated with @WebService and @Transactional. However, TXBridge handler required the WS-AT transaction to be available for every request. If the transaction is not present, it fails to handle the message with com.arjuna.wst.UnknownTransactionException.
> The problem arises when @Transactional annotation has a type such as SUPPORTED, in which case WS-AT transaction should not be mandatory.
> We could write a wrapper for the current handler, which will delegate the call only if the transaction is available.
--
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
10 years, 9 months
[JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server"
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.... ]
Amos Feng updated JBTM-1683:
----------------------------
Fix Version/s: 5.0.0.Final
(was: 6.0.0.Final)
> btadmin tests on windows failed with "Could not start the server"
> -----------------------------------------------------------------
>
> Key: JBTM-1683
> URL: https://issues.jboss.org/browse/JBTM-1683
> 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.Final
>
>
> http://172.17.131.2/job/blacktie-windows2008-taconic/272
> {code}
> Failed tests:
> testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful
> testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server
> testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful
> testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> {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
10 years, 9 months
[JBoss JIRA] (JBTM-1674) btadmin.PauseDomainTest failed with ArrayIndexOutOfBoundsException
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.Final
(was: 5.0.0.M6)
> btadmin.PauseDomainTest failed with ArrayIndexOutOfBoundsException
> ------------------------------------------------------------------
>
> 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
> 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
10 years, 9 months