You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Kevan Miller (JIRA)" <ji...@apache.org> on 2010/12/13 17:42:01 UTC
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12970886#action_12970886 ]
Kevan Miller commented on GERONIMO-5635:
----------------------------------------
For a scenario as easy to reproduce as this, we should have changed the default configuration for G 2.2.1 to avoid this problem. Apologies for overlooking this when the Jira was updated.
> 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.