[jbossts-issues] [JBoss JIRA] (JBTM-2016) Cannot stop WildFly recovery manager when configured with volatile store

Tom Jenkinson (JIRA) jira-events at lists.jboss.org
Mon Nov 11 07:00:06 EST 2013

    [ https://issues.jboss.org/browse/JBTM-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922293#comment-12922293 ] 

Tom Jenkinson commented on JBTM-2016:

The following unhandled exception is raised in the periodic recovery thread, thereby causing the service to hang in stop:

10:57:15,681 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" java.lang.NullPointerException
10:57:15,682 ERROR [stderr] (Periodic Recovery) 	at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.processTransactionsStatus(AtomicActionRecoveryModule.java:241)
10:57:15,682 ERROR [stderr] (Periodic Recovery) 	at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.periodicWorkSecondPass(AtomicActionRecoveryModule.java:109)
10:57:15,683 ERROR [stderr] (Periodic Recovery) 	at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789)
10:57:15,683 ERROR [stderr] (Periodic Recovery) 	at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371)
> Cannot stop WildFly recovery manager when configured with volatile store
> ------------------------------------------------------------------------
>                 Key: JBTM-2016
>                 URL: https://issues.jboss.org/browse/JBTM-2016
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Configuration
>    Affects Versions: 5.0.0.CR1
>            Reporter: gui borland
>            Assignee: Tom Jenkinson
> When using jboss 5, i was able to configure a 'Volatile' action store. I understand it's not the most robust store, but in my case performance is more important than tx consistency.
> I tried to configure the Volatile store in AS 7.1.3 as well (using a custom jbossts-properties.xml file defined via the com.arjuna.ats.arjuna.common.propertiesFile systemsetting ), but doing that breaks the recovery thread. It prints out a warning message (Volatile storage does not support recovery blablabla...). That would be fine, but this recovery issue also prevents jboss from shutting down cleanly. I have to kill it to stop 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

More information about the jbossts-issues mailing list