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/10/08 17:01:35 UTC

[jira] Created: (GERONIMO-5635) corrupt JobSchedulerStore can cause server restart to fail

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
             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.

[jira] Updated: (GERONIMO-5635) corrupt JobSchedulerStore can cause server restart to fail

Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.

     [ 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.