January 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2835) NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2835?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2835: ------------------------------------- What does the error look like with your patch? What is the effect of the NPE? > NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start > ----------------------------------------------------------------------------------------- > > Key: JBTM-2835 > URL: https://issues.jboss.org/browse/JBTM-2835 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Common > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Priority: Minor > > 12:49:24,796 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.txn.ArjunaRecoveryManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: WFLYTX0005: Recovery manager create failed > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:126) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NullPointerException > at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:159) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:111) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:68) > at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.<init>(CommitMarkableResourceRecordRecoveryModule.java:156) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClassesWithInit(ClassloadingUtility.java:192) > at com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getRecoveryModules(RecoveryEnvironmentBean.java:465) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.loadModules(PeriodicRecovery.java:883) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.<init>(PeriodicRecovery.java:121) > at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.<init>(RecoveryManagerImple.java:107) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.<init>(RecoveryManager.java:477) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:132) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:112) > at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.create(RecoveryManagerService.java:54) > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:124) > ... 5 more -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2835) NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/JBTM-2835?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Dan Simko created pull request #1117 in GitHub ---------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start > ----------------------------------------------------------------------------------------- > > Key: JBTM-2835 > URL: https://issues.jboss.org/browse/JBTM-2835 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Common > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Priority: Minor > > 12:49:24,796 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.txn.ArjunaRecoveryManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: WFLYTX0005: Recovery manager create failed > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:126) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NullPointerException > at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:159) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:111) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:68) > at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.<init>(CommitMarkableResourceRecordRecoveryModule.java:156) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClassesWithInit(ClassloadingUtility.java:192) > at com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getRecoveryModules(RecoveryEnvironmentBean.java:465) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.loadModules(PeriodicRecovery.java:883) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.<init>(PeriodicRecovery.java:121) > at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.<init>(RecoveryManagerImple.java:107) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.<init>(RecoveryManager.java:477) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:132) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:112) > at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.create(RecoveryManagerService.java:54) > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:124) > ... 5 more -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2835) NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start

by Daniel Simko (JIRA)

Daniel Simko created JBTM-2835: ---------------------------------- Summary: NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start Key: JBTM-2835 URL: https://issues.jboss.org/browse/JBTM-2835 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Common Affects Versions: 5.5.0.Final Reporter: Daniel Simko Priority: Minor 12:49:24,796 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.txn.ArjunaRecoveryManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: WFLYTX0005: Recovery manager create failed at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:126) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NullPointerException at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:159) at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:111) at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:68) at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.<init>(CommitMarkableResourceRecordRecoveryModule.java:156) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442) at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135) at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClassesWithInit(ClassloadingUtility.java:192) at com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getRecoveryModules(RecoveryEnvironmentBean.java:465) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.loadModules(PeriodicRecovery.java:883) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.<init>(PeriodicRecovery.java:121) at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.<init>(RecoveryManagerImple.java:107) at com.arjuna.ats.arjuna.recovery.RecoveryManager.<init>(RecoveryManager.java:477) at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:132) at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:112) at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.create(RecoveryManagerService.java:54) at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:124) ... 5 more -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2822) Add suppressed exceptions for failures during prepare

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2822?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-2822: --------------------------------------- Hi [~tomjenkinson], during the check ups JBEAP issues I got to this issue and when applying the same test as I have for JBTM-2636 I found out that there is a branch in code where deffered exception is not added - that's when heuristic happens. Is it intentional? This kind of update fixes the issue that I refer to: https://github.com/ochaloup/narayana/commit/cb2ab4252a6c2e1106751d28103da... > Add suppressed exceptions for failures during prepare > ----------------------------------------------------- > > Key: JBTM-2822 > URL: https://issues.jboss.org/browse/JBTM-2822 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > JBTM-2636 added support for adding suppressed exceptions for issues reported during commit. It would be useful to do the same for prepare exceptions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2834) Delete a tx participant - XAResource#forget(xid) is not called for JTS

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2834?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka reassigned JBTM-2834: ------------------------------------- Assignee: Michael Musgrove > Delete a tx participant - XAResource#forget(xid) is not called for JTS > ---------------------------------------------------------------------- > > Key: JBTM-2834 > URL: https://issues.jboss.org/browse/JBTM-2834 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Assignee: Michael Musgrove > > Deleting specific participant (introduced by EAP7-594) is not working correctly in DR10. Method forget on a XAResource is not called. It seems to be regression compared to DR9. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2834) Delete a tx participant - XAResource#forget(xid) is not called for JTS

by Daniel Simko (JIRA)

[ https://issues.jboss.org/browse/JBTM-2834?page=com.atlassian.jira.plugin.... ] Daniel Simko updated JBTM-2834: ------------------------------- Affects Version/s: 5.5.0.Final > Delete a tx participant - XAResource#forget(xid) is not called for JTS > ---------------------------------------------------------------------- > > Key: JBTM-2834 > URL: https://issues.jboss.org/browse/JBTM-2834 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > > Deleting specific participant (introduced by EAP7-594) is not working correctly in DR10. Method forget on a XAResource is not called. It seems to be regression compared to DR9. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2834) Delete a tx participant - XAResource#forget(xid) is not called for JTS

by Daniel Simko (JIRA)

Daniel Simko created JBTM-2834: ---------------------------------- Summary: Delete a tx participant - XAResource#forget(xid) is not called for JTS Key: JBTM-2834 URL: https://issues.jboss.org/browse/JBTM-2834 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Daniel Simko Deleting specific participant (introduced by EAP7-594) is not working correctly in DR10. Method forget on a XAResource is not called. It seems to be regression compared to DR9. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2833) Move deprecated tooling classes into an internal package

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2833: -------------------------------------- Summary: Move deprecated tooling classes into an internal package Key: JBTM-2833 URL: https://issues.jboss.org/browse/JBTM-2833 Project: JBoss Transaction Manager Issue Type: Task Components: Tooling Affects Versions: 5.5.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next commit 66a9291f56f (JBTM-2308]) "Mark classes deprecated since we need to rejig package names" marked many/most of the tooling instrumentation classes deprecated - these need to be moved to internal packages and the then marked as not deprecated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2339) MongoDB extension for Compensations

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2339?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2339: --------------------------------------- I've looked into this issue a while back, but it didn't go far because compensations framework update was necessary. It should be possible to get back to the issue now, because now it is possible to register compensation/confirmation handers by instance rather than by class name. It allows having specific database information in the object instance. In addition, a wider conversation on possible API changes might be needed. > MongoDB extension for Compensations > ----------------------------------- > > Key: JBTM-2339 > URL: https://issues.jboss.org/browse/JBTM-2339 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > > Investigate the feasibility of MongoDB compensations patent implementation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2339) MongoDB extension for Compensations

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2339?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2339: ---------------------------------- Description: Investigate the feasibility of MongoDB compensations patent implementation. > MongoDB extension for Compensations > ----------------------------------- > > Key: JBTM-2339 > URL: https://issues.jboss.org/browse/JBTM-2339 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > > Investigate the feasibility of MongoDB compensations patent implementation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues January 2017