July 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2703) When a transaction is committed at the same instance as a resource adapter/remote EJB calls XAT::recover() then you can get an NPE

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2703?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2703: -------------------------------- Description: INFO [com.arjuna.ats.arjuna] ObjectStore record was deleted during restoration, users should not deleted records manually: <SNIP>/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/SubordinateAtomicAction/JCA<SNIP>: java.io.FileNotFoundException: <SNIP>/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/SubordinateAtomicAction/JCA/<SNIP> (No such file or directory) ERROR [stderr] java.io.IOException: java.lang.NullPointerException ERROR [stderr] at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:732) ERROR [stderr] at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.jca.SubordinateAtomicAction.<init>(SubordinateAtomicAction.java:82) ERROR [stderr] at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:393) ERROR [stderr] at org.jboss.as.ejb3.remote.EJBRemoteTransactionsRepository.getXidsToRecoverForParentNode(EJBRemoteTransactionsRepository.java:178) ERROR [stderr] at org.jboss.as.ejb3.remote.protocol.versiontwo.TransactionRecoverMessageHandler$TxRecoveryTask.run(TransactionRecoverMessageHandler.java:96) ERROR [stderr] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) ERROR [stderr] at java.util.concurrent.FutureTask.run(FutureTask.java:262) ERROR [stderr] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) ERROR [stderr] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) ERROR [stderr] at java.lang.Thread.run(Thread.java:745) ERROR [stderr] at org.jboss.threads.JBossThread.run(JBossThread.java:122) ERROR [stderr] Caused by: java.lang.NullPointerException ERROR [stderr] at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:697) ERROR [stderr] ... 10 more > When a transaction is committed at the same instance as a resource adapter/remote EJB calls XAT::recover() then you can get an NPE > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2703 > URL: https://issues.jboss.org/browse/JBTM-2703 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Reporter: Tom Jenkinson > Fix For: 5.next > > > INFO [com.arjuna.ats.arjuna] ObjectStore record was deleted during restoration, users should not deleted records manually: <SNIP>/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/SubordinateAtomicAction/JCA<SNIP>: java.io.FileNotFoundException: <SNIP>/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/SubordinateAtomicAction/JCA/<SNIP> (No such file or directory) > ERROR [stderr] java.io.IOException: java.lang.NullPointerException > ERROR [stderr] at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:732) > ERROR [stderr] at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.jca.SubordinateAtomicAction.<init>(SubordinateAtomicAction.java:82) > ERROR [stderr] at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:393) > ERROR [stderr] at org.jboss.as.ejb3.remote.EJBRemoteTransactionsRepository.getXidsToRecoverForParentNode(EJBRemoteTransactionsRepository.java:178) > ERROR [stderr] at org.jboss.as.ejb3.remote.protocol.versiontwo.TransactionRecoverMessageHandler$TxRecoveryTask.run(TransactionRecoverMessageHandler.java:96) > ERROR [stderr] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > ERROR [stderr] at java.util.concurrent.FutureTask.run(FutureTask.java:262) > ERROR [stderr] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > ERROR [stderr] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > ERROR [stderr] at java.lang.Thread.run(Thread.java:745) > ERROR [stderr] at org.jboss.threads.JBossThread.run(JBossThread.java:122) > ERROR [stderr] Caused by: java.lang.NullPointerException > ERROR [stderr] at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:697) > ERROR [stderr] ... 10 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2703) When a transaction is committed at the same instance as a resource adapter/remote EJB calls XAT::recover() then you can get an NPE

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2703: ----------------------------------- Summary: When a transaction is committed at the same instance as a resource adapter/remote EJB calls XAT::recover() then you can get an NPE Key: JBTM-2703 URL: https://issues.jboss.org/browse/JBTM-2703 Project: JBoss Transaction Manager Issue Type: Bug Components: JCA Reporter: Tom Jenkinson Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2122) Go through JTS code and compare/contrast with capabilities missing in other dist tx code we've got

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2122?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-2122: --------------------------------------- [~tomjenkinson] Not fully sure if our discussion at https://issues.jboss.org/browse/JBEAP-610?focusedCommentId=13147405#comme... is directly connected to this issue but you previous comments seem to me so. What I remember by [~hhovsepy]'s investigation it seemed that JTS works with 2pc for propagated transactions at any time (meaning even with one resource enlisted). Later on that was found that we have (?) some trouble in test and 1pc is used. Your reference of https://c.na7.visual.force.com/apex/Case_View?sbstr=01560781 seems to me not related as it's rather caused by the fact discussing at https://issues.jboss.org/browse/JBEAP-225 and https://issues.jboss.org/browse/WFLY-4608 which is based on issue in container. > Go through JTS code and compare/contrast with capabilities missing in other dist tx code we've got > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2122 > URL: https://issues.jboss.org/browse/JBTM-2122 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Michael Musgrove > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1468) Support pure-JTA client and server for WS-AT and REST-AT

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1468?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1468: ---------------------------------------- Items 3 and 4 have already been implemented. Item 1 needs clarification from [~paul.robinson] > Support pure-JTA client and server for WS-AT and REST-AT > -------------------------------------------------------- > > Key: JBTM-1468 > URL: https://issues.jboss.org/browse/JBTM-1468 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: REST, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 6.later > > Original Estimate: 2 days > Remaining Estimate: 2 days > > This allows the Client and server application to just use the JTA APIs, whilst having the distribution done over WS-AT or REST-AT. > To do this we need to: > # Remove @Transactional annotation. We then need to use some other mechanism to support the (optional) WS-AT participants that want to use annotations. > # Client side JTA->REST-AT bridge. Needs implementing. > # Server side REST-AT->JTA bridge. Needs integrating into code base. > # Update the TXBridge quickstarts to use this and move them out. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1109) JTA -> REST-AT Bridge

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1109?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1109: ---------------------------------------- Changing priority to optional because we have not had any demand from the community for this feature > JTA -> REST-AT Bridge > --------------------- > > Key: JBTM-1109 > URL: https://issues.jboss.org/browse/JBTM-1109 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST, TxBridge > Reporter: Paul Robinson > Fix For: 6.later > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1109) JTA -> REST-AT Bridge

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1109?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1109: ----------------------------------- Priority: Optional (was: Major) > JTA -> REST-AT Bridge > --------------------- > > Key: JBTM-1109 > URL: https://issues.jboss.org/browse/JBTM-1109 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST, TxBridge > Reporter: Paul Robinson > Priority: Optional > Fix For: 6.later > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1575) Test support for Informix

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1575?page=com.atlassian.jira.plugin.... ] Michael Musgrove closed JBTM-1575. ---------------------------------- Resolution: Duplicate > Test support for Informix > ------------------------- > > Key: JBTM-1575 > URL: https://issues.jboss.org/browse/JBTM-1575 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie > Reporter: Michael Musgrove > Priority: Optional > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2221) Remove old TXFramework API

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2221?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2221: ---------------------------------- Component/s: Compensations (was: TXFramework) > Remove old TXFramework API > -------------------------- > > Key: JBTM-2221 > URL: https://issues.jboss.org/browse/JBTM-2221 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 6.later > > > This is now replaced by the CDI based Compensations API. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1052) Support Web services with a webservices.xml present in TXFramework

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1052?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed JBTM-1052. --------------------------------- Fix Version/s: (was: 6.later) Resolution: Rejected > Support Web services with a webservices.xml present in TXFramework > ------------------------------------------------------------------ > > Key: JBTM-1052 > URL: https://issues.jboss.org/browse/JBTM-1052 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: TXFramework > Reporter: Paul Robinson > Priority: Minor > > See: https://community.jboss.org/message/714478#714478 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1006) Review TXFramework test coverage

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1006?page=com.atlassian.jira.plugin.... ] Gytis Trikleris resolved JBTM-1006. ----------------------------------- Resolution: Rejected > Review TXFramework test coverage > -------------------------------- > > Key: JBTM-1006 > URL: https://issues.jboss.org/browse/JBTM-1006 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Affects Versions: 4.17.0.M1/5.0.0.M1 > Reporter: Paul Robinson > Priority: Trivial > > Only the obvious "happy path" cases are tested at the moment. Need to ensure incorrect developer implementation and configuration is handled correctly. > We should also consider taking a copy of the existing XTS tests and modify to use the TXFramework. This could allow us to get some good coverage, relatively quickly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 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 July 2016