[jira] Updated: (GERONIMO-5635) corrupt JobSchedulerStore can cause server restart to fail
[
https://issues.apache.org/jira/browse/GERONIMO-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang updated GERONIMO-5635:
--
Affects Version/s: 2.2.2
Fix Version/s: (was: 2.2.1)
3.0
2.2.2
We don't have time to wait for ActiveMQ 5.4.2 to release G2.2.1
corrupt JobSchedulerStore can cause server restart to fail
---
Key: GERONIMO-5635
URL: https://issues.apache.org/jira/browse/GERONIMO-5635
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.2.1, 2.2.2
Reporter: Kevan Miller
Priority: Blocker
Fix For: 2.2.2, 3.0
A hard server stop (e.g. kill -9) will frequently result in a corrupt
JobSchedulerStore. Subsequent restart will fail. See
https://issues.apache.org/activemq/browse/AMQ-2935 for more information.
This should be fixed in an ActiveMQ 5.4.2 release. In meantime, you can avoid
the problem using the following in var/activemq/conf/activemq.xml:
broker xmlns=http://activemq.apache.org/schema/core;
brokerName=${activemq.brokerName}
tmpDataDirectory=${activemq.data}/tmp_storage useShutdownHook=false
start=false schedulerSupport=false
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5635) corrupt JobSchedulerStore can cause server restart to fail
[
https://issues.apache.org/jira/browse/GERONIMO-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevan Miller updated GERONIMO-5635:
---
Priority: Blocker (was: Major)
corrupt JobSchedulerStore can cause server restart to fail
---
Key: GERONIMO-5635
URL: https://issues.apache.org/jira/browse/GERONIMO-5635
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.2.1
Reporter: Kevan Miller
Priority: Blocker
Fix For: 2.2.1
A hard server stop (e.g. kill -9) will frequently result in a corrupt
JobSchedulerStore. Subsequent restart will fail. See
https://issues.apache.org/activemq/browse/AMQ-2935 for more information.
This should be fixed in an ActiveMQ 5.4.2 release. In meantime, you can avoid
the problem using the following in var/activemq/conf/activemq.xml:
broker xmlns=http://activemq.apache.org/schema/core;
brokerName=${activemq.brokerName}
tmpDataDirectory=${activemq.data}/tmp_storage useShutdownHook=false
start=false schedulerSupport=false
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
