April 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1211) Fix qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1211?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1211: ---------------------------------------- The pull request for fixing it (ie disabling the test) on the EAP jobs completed over the holidays and I have just merged it this morning > Fix qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote > ------------------------------------------------------------------------------ > > Key: JBTM-1211 > URL: https://issues.jboss.org/browse/JBTM-1211 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS, Testing, Transaction Core > Affects Versions: 4.16.4 > Reporter: Paul Robinson > Assignee: Michael Musgrove > Fix For: 5.0.0.M3 > > Attachments: jbossts-narayana-java6-ipv6-dualstack.57.tar, jtsremote(1).zip, jtsremote.zip > > Original Estimate: 1 day > Remaining Estimate: 1 day > > See: http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch416-java6/232 > {code} > Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote > [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 169.235 sec > {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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1327) QA Test Suite Failures

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1327?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-1327. ------------------------------------ Resolution: Won't Fix This JIRA aggregates other QA related JIRAs but it's preferable to use labels for this purpose if required. > QA Test Suite Failures > ---------------------- > > Key: JBTM-1327 > URL: https://issues.jboss.org/browse/JBTM-1327 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.0.Final > > > Parent JIRA for QA test failures -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1036) NP: Possible null pointer dereference (NP_NULL_ON_SOME_PATH)

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1036?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1036: ----------------------------------- Many of these are not going to be null when they are used because we will have caught the error earlier in the workflow and reported the problem or thrown an exception. > NP: Possible null pointer dereference (NP_NULL_ON_SOME_PATH) > ------------------------------------------------------------ > > Key: JBTM-1036 > URL: https://issues.jboss.org/browse/JBTM-1036 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA, JTS, Transaction Core > Reporter: Amos Feng > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.Final > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 1.ArjunaJTA/jdbc > Possible null pointer dereference of conn in com.arjuna.ats.internal.jdbc.recovery.BasicXARecovery.getXAResource() Line 169 > 2.ArjunaCore/arjuna > com.arjuna.ats.arjuna.StateManager Line 1234 > Possible null pointer dereference of action in com.arjuna.ats.arjuna.StateManager.forgetAction(BasicAction, boolean, int) > 3.ArjunaCore/arjuna > com.arjuna.ats.internal.arjuna.objectstore.HashedStore Line 131 > Possible null pointer dereference of aUid in com.arjuna.ats.internal.arjuna.objectstore.HashedStore.allObjUids(String, InputObjectState, int) > 4.ArjunaJTS/jtax > com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.coordinator.ServerTransaction Line 108 > Possible null pointer dereference of ServerTransaction._theXid in com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.coordinator.ServerTransaction.save_state(OutputObjectState, int) > 5.ArjunaJTS/jts > com.arjuna.ats.internal.jts.context.ContextManager Line 553 > Possible null pointer dereference of action in com.arjuna.ats.internal.jts.context.ContextManager.pushAction(ControlWrapper) > 6.ArjunaJTS/jts > com.arjuna.ats.jts.extensions.AtomicTransaction Line 617 > Possible null pointer dereference of AtomicTransaction._theAction in com.arjuna.ats.jts.extensions.AtomicTransaction.equals(Object) -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1036) NP: Possible null pointer dereference (NP_NULL_ON_SOME_PATH)

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1036?page=com.atlassian.jira.plugin.... ] Mark Little edited comment on JBTM-1036 at 4/2/13 4:33 AM: ----------------------------------------------------------- Many of these are not going to be null when they are used because we will have caught the error earlier in the state machine and reported the problem or thrown an exception. was (Author: marklittle): Many of these are not going to be null when they are used because we will have caught the error earlier in the workflow and reported the problem or thrown an exception. > NP: Possible null pointer dereference (NP_NULL_ON_SOME_PATH) > ------------------------------------------------------------ > > Key: JBTM-1036 > URL: https://issues.jboss.org/browse/JBTM-1036 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA, JTS, Transaction Core > Reporter: Amos Feng > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.Final > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 1.ArjunaJTA/jdbc > Possible null pointer dereference of conn in com.arjuna.ats.internal.jdbc.recovery.BasicXARecovery.getXAResource() Line 169 > 2.ArjunaCore/arjuna > com.arjuna.ats.arjuna.StateManager Line 1234 > Possible null pointer dereference of action in com.arjuna.ats.arjuna.StateManager.forgetAction(BasicAction, boolean, int) > 3.ArjunaCore/arjuna > com.arjuna.ats.internal.arjuna.objectstore.HashedStore Line 131 > Possible null pointer dereference of aUid in com.arjuna.ats.internal.arjuna.objectstore.HashedStore.allObjUids(String, InputObjectState, int) > 4.ArjunaJTS/jtax > com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.coordinator.ServerTransaction Line 108 > Possible null pointer dereference of ServerTransaction._theXid in com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.coordinator.ServerTransaction.save_state(OutputObjectState, int) > 5.ArjunaJTS/jts > com.arjuna.ats.internal.jts.context.ContextManager Line 553 > Possible null pointer dereference of action in com.arjuna.ats.internal.jts.context.ContextManager.pushAction(ControlWrapper) > 6.ArjunaJTS/jts > com.arjuna.ats.jts.extensions.AtomicTransaction Line 617 > Possible null pointer dereference of AtomicTransaction._theAction in com.arjuna.ats.jts.extensions.AtomicTransaction.equals(Object) -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS subsystem and module

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?focusedWorklogId=12428938&page=... ] Gytis Trikleris logged work on JBTM-1365: ----------------------------------------- Author: Gytis Trikleris Created on: 02/Apr/13 4:27 AM Start Date: 02/Apr/13 4:27 AM Worklog Time Spent: 1 day Issue Time Tracking ------------------- Remaining Estimate: 2 weeks, 3 days, 5 hours (was: 2 weeks, 4 days, 5 hours) Time Spent: 1 day, 3 hours (was: 3 hours) Worklog Id: (was: 12428938) > Deploy REST-AT support as a JBossAS subsystem and module > -------------------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Original Estimate: 3 weeks > Time Spent: 1 day, 3 hours > Remaining Estimate: 2 weeks, 3 days, 5 hours > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. > h3. Open Issues > Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1452) Distribution name of 4.17.x is narayana* rather than jbossts*

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1452?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1452: ---------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes > Distribution name of 4.17.x is narayana* rather than jbossts* > ------------------------------------------------------------- > > Key: JBTM-1452 > URL: https://issues.jboss.org/browse/JBTM-1452 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.3 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 4.17.4 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > See https://www.jboss.org/jbosstm/downloads/4_17_3_Final -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1036) NP: Possible null pointer dereference (NP_NULL_ON_SOME_PATH)

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1036?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1036: ---------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > NP: Possible null pointer dereference (NP_NULL_ON_SOME_PATH) > ------------------------------------------------------------ > > Key: JBTM-1036 > URL: https://issues.jboss.org/browse/JBTM-1036 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA, JTS, Transaction Core > Reporter: Amos Feng > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.Final > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 1.ArjunaJTA/jdbc > Possible null pointer dereference of conn in com.arjuna.ats.internal.jdbc.recovery.BasicXARecovery.getXAResource() Line 169 > 2.ArjunaCore/arjuna > com.arjuna.ats.arjuna.StateManager Line 1234 > Possible null pointer dereference of action in com.arjuna.ats.arjuna.StateManager.forgetAction(BasicAction, boolean, int) > 3.ArjunaCore/arjuna > com.arjuna.ats.internal.arjuna.objectstore.HashedStore Line 131 > Possible null pointer dereference of aUid in com.arjuna.ats.internal.arjuna.objectstore.HashedStore.allObjUids(String, InputObjectState, int) > 4.ArjunaJTS/jtax > com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.coordinator.ServerTransaction Line 108 > Possible null pointer dereference of ServerTransaction._theXid in com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.coordinator.ServerTransaction.save_state(OutputObjectState, int) > 5.ArjunaJTS/jts > com.arjuna.ats.internal.jts.context.ContextManager Line 553 > Possible null pointer dereference of action in com.arjuna.ats.internal.jts.context.ContextManager.pushAction(ControlWrapper) > 6.ArjunaJTS/jts > com.arjuna.ats.jts.extensions.AtomicTransaction Line 617 > Possible null pointer dereference of AtomicTransaction._theAction in com.arjuna.ats.jts.extensions.AtomicTransaction.equals(Object) -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-855) Create an example showing integration with Tomcat and Spring

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.s... ] Gytis Trikleris updated JBTM-855: --------------------------------- Original Estimate: 1 week Remaining Estimate: 1 week > Create an example showing integration with Tomcat and Spring > ------------------------------------------------------------ > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.Final > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Simple example showing TS in use by tomcat and spring -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1249) Update documentation to resolve XA recovery Failed on Oracle (pad-xid=true not propagated to the XARecoveryModule)

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1249?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1249: ---------------------------------- Original Estimate: 20 minutes Remaining Estimate: 20 minutes > Update documentation to resolve XA recovery Failed on Oracle (pad-xid=true not propagated to the XARecoveryModule) > ------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-1249 > URL: https://issues.jboss.org/browse/JBTM-1249 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Application Server Integration, Documentation, JCA, JTS > Affects Versions: 4.16.2 > Environment: JBoss AS 7.1.1 Final, Windows, Oracle > Reporter: Michel PRUNET > Assignee: Gytis Trikleris > Labels: jboss, jts, recovery, xa > Fix For: 5.0.0.Final > > Attachments: TestEJB.zip > > Original Estimate: 20 minutes > Remaining Estimate: 20 minutes > > The XARecoveryManager is unable to recover an Oracle Prepared Transaction. > The reason: > Oracle needs the Xid to be padded (pad-xid set to true in xa-datasource). > When the method XARecoveryModule.getNewXAResource(Xid xid) is called. The value of xid is not padded (retrieved from the tx-object-store). The XID contained in the RecoveryXids are padded (retrieved from oracle). When the method execute xids.remove(xid), it never found the xid. The transaction is never recovered. > In a debug session, if you pad the xid in that method (change the xid.gtrud_length and or bqual_length), the transaction will be recovered successfully. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1485) Change reaper to dump the resources that are stuck and stacks of stuck threads

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1485?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1485: ---------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > Change reaper to dump the resources that are stuck and stacks of stuck threads > ------------------------------------------------------------------------------ > > Key: JBTM-1485 > URL: https://issues.jboss.org/browse/JBTM-1485 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.M3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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, 8 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 April 2013