June 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1782) Add cersei, janei and lancel to blacktie test config files

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1782?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1782. --------------------------------- Resolution: Done > Add cersei, janei and lancel to blacktie test config files > ---------------------------------------------------------- > > Key: JBTM-1782 > URL: https://issues.jboss.org/browse/JBTM-1782 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BlackTie, Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M4 > > > Found using grep of another node > [tom@dhcppc1 blacktie](master) $ find . -name \*.java -o -name \*.xml | xargs grep -l haverstraw | grep -v target > ./btadmin/src/test/resources/btconfig.xml > ./jatmibroker-xatmi/src/test/resources/btconfigERROR.xml > ./jatmibroker-xatmi/src/test/resources/btconfig.xml > ./jatmibroker-nbf/src/test/resources/btconfig.xml -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1782) Add cersei, janei and lancel to blacktie test config files

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1782: ----------------------------------- Summary: Add cersei, janei and lancel to blacktie test config files Key: JBTM-1782 URL: https://issues.jboss.org/browse/JBTM-1782 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: BlackTie, Testing Reporter: Tom Jenkinson Assignee: Amos Feng Fix For: 5.0.0.M4 Found using grep of another node [tom@dhcppc1 blacktie](master) $ find . -name \*.java -o -name \*.xml | xargs grep -l haverstraw | grep -v target ./btadmin/src/test/resources/btconfig.xml ./jatmibroker-xatmi/src/test/resources/btconfigERROR.xml ./jatmibroker-xatmi/src/test/resources/btconfig.xml ./jatmibroker-nbf/src/test/resources/btconfig.xml -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1781) Cannot enlist volatile or durable RESTAT participants if txn has status TransactionRollbackOnly

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1781?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1781: ---------------------------------------- That applies to the JTA spec however I am referring to the RESTAT specification which currently says (in the section about Enlisting a two-phase aware participant): {quote} 385If the transaction is not TransactionActive when registration is attempted, then the implementation 386MUST return a 412 status code. {quote} > Cannot enlist volatile or durable RESTAT participants if txn has status TransactionRollbackOnly > ----------------------------------------------------------------------------------------------- > > Key: JBTM-1781 > URL: https://issues.jboss.org/browse/JBTM-1781 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M4 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The implementation (and spec) doesn't allow this at the moment and should be changed to more closely match the JTA behavior. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1778) JBossTS qa testsuite fails on HP-UX

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-1778?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka updated JBTM-1778: ----------------------------------- Attachment: jstack-3091 Output from jstack for qa-currenttests01 and test number 20 > JBossTS qa testsuite fails on HP-UX > ----------------------------------- > > Key: JBTM-1778 > URL: https://issues.jboss.org/browse/JBTM-1778 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.6.1.CP13 > Reporter: Ondřej Chaloupka > Assignee: Michael Musgrove > Attachments: jstack-3091 > > > Hi Michael, > as part of the EAP5.2.0 certification tests running on HP-UX 11v3 machines. > I've hit problems with several testcases in the ts testsuite. > We are testing on machines under this tag: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/hpux11v3/ > As I think that you know the testsuite the most I'm assigning this issue to you. If I've mistaken, please, reassign it. > Those are: > - jbossts-qa-currenttests01 number 20 stays stuck forever. It stays on current.resume call. I'm adding the jstack output, that I've got from the call, as attachment here. > - jbossts-qa-jtatests01 number 005 fails with error message: > java.lang.Exception: Test failed! JTATests01_Test005 got 1 fewer task passes than expected > - jbossts-qa-otsserver number 010, 011, 012 and 017 fail with the error > got 1 fewer task passes than expected > I've tried to get some closer knowledge about the problem but I wasn't able much. > Others tests from testsuite pass fine without error. Just their run time is longer in comparison with testsuite running on RHEL. > We are running tests on jdk6 and jdk7 on 32bits and 64bits. These particular results belong to jdk6 and 32b. > The jenkins run could be found at: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap5-jbossts-testsui... > Would you have some suggestion about 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1781) Cannot enlist volatile or durable RESTAT participants if txn has status TransactionRollbackOnly

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1781?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1781: ----------------------------------- Throws: RollbackException Thrown to indicate that the transaction has been marked for rollback only. > Cannot enlist volatile or durable RESTAT participants if txn has status TransactionRollbackOnly > ----------------------------------------------------------------------------------------------- > > Key: JBTM-1781 > URL: https://issues.jboss.org/browse/JBTM-1781 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M4 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The implementation (and spec) doesn't allow this at the moment and should be changed to more closely match the JTA behavior. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1781) Cannot enlist volatile or durable RESTAT participants if txn has status TransactionRollbackOnly

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1781: -------------------------------------- Summary: Cannot enlist volatile or durable RESTAT participants if txn has status TransactionRollbackOnly Key: JBTM-1781 URL: https://issues.jboss.org/browse/JBTM-1781 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: REST Affects Versions: 5.0.0.M3 Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Minor Fix For: 5.0.0.M4 The implementation (and spec) doesn't allow this at the moment and should be changed to more closely match the JTA behavior. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1762) TX TestTransactions::test_rollback failed with un-expect TX_FAIL

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1762?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-1762. ------------------------------------ Resolution: Done I manually set off build number [http://172.17.131.2/job/blacktie-linux/8/jdk=jdk7.latest,label_exp=linux3...] and all the tx tests passed (including TestTransactions::test_rollback) > 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1780) Missing test for failures during the REST-AT volatile prepare phase

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1780: -------------------------------------- Summary: Missing test for failures during the REST-AT volatile prepare phase Key: JBTM-1780 URL: https://issues.jboss.org/browse/JBTM-1780 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: REST Affects Versions: 5.0.0.M3 Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Minor Fix For: 5.0.0.M4 There is code in the test participant (org.jboss.jbossts.star.test.BaseTest TransactionalResource#synchronizations) to fail the volatile prepare phase but org.jboss.jbossts.star.test.OptionalSpecTest does not exercise it). -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1767) restat-api failures with emma: Tests run: 30, Failures: 11, Errors: 2

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1767?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1767: ---------------------------------------- Note that the fix suggested in the first comment failed on one of the wildfly RTS integration tests. The suggested fix inserted two / characters between the base URI and path component which resulted, when running under Arquillian, in a 404 Not Found error. Anyway, I ended up beefing up the code that extracts the URI from instances of UriInfo. > restat-api failures with emma: Tests run: 30, Failures: 11, Errors: 2 > --------------------------------------------------------------------- > > Key: JBTM-1767 > URL: https://issues.jboss.org/browse/JBTM-1767 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST, Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M4 > > > Failed tests: test1PCAbort(org.jboss.jbossts.star.test.CoordinatorTest): expected:<v[2]> but was:<v[1]> > test2PC(org.jboss.jbossts.star.test.CoordinatorTest): expected:<v[2]> but was:<v[1]> > testEnlistVolatileParticipant(org.jboss.jbossts.star.test.OptionalSpecTest): null expected:<[0]> but was:<[4]> > testRecoveryURLTwoPhaseAwareWithoutNotification(org.jboss.jbossts.star.test.SpecTest): null expected:<Transaction[RolledBack]> but was:<Transaction[Active]> > testRecoveryURLTwoPhaseAwareWithNotification(org.jboss.jbossts.star.test.SpecTest): null expected:<Transaction[Committed]> but was:<Transaction[Active]> > testRecoveryURLTwoPhaseUnawareWithoutNotification(org.jboss.jbossts.star.test.SpecTest): null expected:<Transaction[RolledBack]> but was:<Transaction[Active]> > testRecoveryURLTwoPhaseUnawareWithNotification(org.jboss.jbossts.star.test.SpecTest): null expected:<Transaction[Committed]> but was:<Transaction[Active]> > testHeuristic(org.jboss.jbossts.star.test.SpecTest): null expected:<txstatus=Transaction[HeuristicMixed]> but was:<txstatus=Transaction[RolledBack]> > testHeuristicWithForget(org.jboss.jbossts.star.test.SpecTest): null expected:<txstatus=Transaction[HeuristicRollb]ack> but was:<txstatus=Transaction[RolledB]ack> > testSpec6(org.jboss.jbossts.star.test.SpecTest): null expected:<txstatus=Transaction[RolledBack]> but was:<txstatus=Transaction[Committed]> > testCannotEnlistDuring2PC(org.jboss.jbossts.star.test.SpecTest): expected:<500> but was:<412> > Tests in error: > testTransactionStatistics(org.jboss.jbossts.star.test.OptionalSpecTest): org.jboss.jbossts.star.util.media.txstatusext.TransactionManagerElement cannot be cast to org.jboss.jbossts.star.util.media.txstatusext.TransactionStatisticsElement > testParticipantStatus(org.jboss.jbossts.star.test.SpecTest): Unexpected status. Expected 200 got 404 -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1779) txframework DataManagementTest does not work under emma

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1779: ----------------------------------- Summary: txframework DataManagementTest does not work under emma Key: JBTM-1779 URL: https://issues.jboss.org/browse/JBTM-1779 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing, TXFramework Reporter: Tom Jenkinson Assignee: Paul Robinson Fix For: 5.0.0.M4 There is a single txf test that does not run correctly under emma. It complains about not being able to find vladium. The problem appears to be that this test creates an arq deployment containing its own copy of the TXDataMap rather than trying to use the one that is deployed already in the AS and is therefore in a different classloader so can't see the shaded emma classes from the real module. When I modify the test to remove that class and use the txf module directly, the same as all the other tests in the txf module, it can't load the TXDM class from the module. The difference is that the TXDM is injected into test beans that are injected into the tests, rather than directly injected. I think this could be a limitation of Emma. -- 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

11 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2013