You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gabriele Garuglieri (JIRA)" <ji...@apache.org> on 2007/03/22 08:47:35 UTC
[jira] Created: (AMQ-1213) Deploying a shared filesystem slave rar
configuration will completely hang Jboss
Deploying a shared filesystem slave rar configuration will completely hang Jboss
--------------------------------------------------------------------------------
Key: AMQ-1213
URL: https://issues.apache.org/activemq/browse/AMQ-1213
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 4.1.0
Environment: Java 1.5.0
ActiveMQ 4.1.0 and 4.1-SNAPSHOT
Jboss 4.0.5-GA
Reporter: Gabriele Garuglieri
Priority: Blocker
When starting a shared filesystem slave the journaledJDBC persistence adapter initialization won't return until it has acquired the journal lock, but this behaviour has devastating effects in Jboss.
Infact this means that the deploy won't complete, hanging the Jboss deployer so that applications cannot any longer be deployed or undeployed.
Even worse if you try to restart Jboss with AMQ still deployed the application server startup phase won't complete and you won't be able to interact with Jboss. No console, no applications, not even able to orderly shutdown it.
The only thing you can do to recover is to kill the process and manually remove the AMQ from deploy directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (AMQ-1213) Deploying a shared filesystem slave rar
configuration will completely hang Jboss
Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Snyder closed AMQ-1213.
-----------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: AGING_TO_DIE)
> Deploying a shared filesystem slave rar configuration will completely hang Jboss
> --------------------------------------------------------------------------------
>
> Key: AMQ-1213
> URL: https://issues.apache.org/activemq/browse/AMQ-1213
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.1.0
> Environment: Java 1.5.0
> ActiveMQ 4.1.0 and 4.1-SNAPSHOT
> Jboss 4.0.5-GA
> Reporter: Gabriele Garuglieri
>
> When starting a shared filesystem slave the journaledJDBC persistence adapter initialization won't return until it has acquired the journal lock, but this behaviour has devastating effects in Jboss.
> Infact this means that the deploy won't complete, hanging the Jboss deployer so that applications cannot any longer be deployed or undeployed.
> Even worse if you try to restart Jboss with AMQ still deployed the application server startup phase won't complete and you won't be able to interact with Jboss. No console, no applications, not even able to orderly shutdown it.
> The only thing you can do to recover is to kill the process and manually remove the AMQ from deploy directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-1213) Deploying a shared filesystem slave rar
configuration will completely hang Jboss
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully updated AMQ-1213:
----------------------------
Fix Version/s: 5.3.0
(was: 5.2.0)
> Deploying a shared filesystem slave rar configuration will completely hang Jboss
> --------------------------------------------------------------------------------
>
> Key: AMQ-1213
> URL: https://issues.apache.org/activemq/browse/AMQ-1213
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.1.0
> Environment: Java 1.5.0
> ActiveMQ 4.1.0 and 4.1-SNAPSHOT
> Jboss 4.0.5-GA
> Reporter: Gabriele Garuglieri
> Fix For: 5.3.0
>
>
> When starting a shared filesystem slave the journaledJDBC persistence adapter initialization won't return until it has acquired the journal lock, but this behaviour has devastating effects in Jboss.
> Infact this means that the deploy won't complete, hanging the Jboss deployer so that applications cannot any longer be deployed or undeployed.
> Even worse if you try to restart Jboss with AMQ still deployed the application server startup phase won't complete and you won't be able to interact with Jboss. No console, no applications, not even able to orderly shutdown it.
> The only thing you can do to recover is to kill the process and manually remove the AMQ from deploy directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-1213) Deploying a shared filesystem slave rar
configuration will completely hang Jboss
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies updated AMQ-1213:
----------------------------
Priority: Major (was: Blocker)
> Deploying a shared filesystem slave rar configuration will completely hang Jboss
> --------------------------------------------------------------------------------
>
> Key: AMQ-1213
> URL: https://issues.apache.org/activemq/browse/AMQ-1213
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.1.0
> Environment: Java 1.5.0
> ActiveMQ 4.1.0 and 4.1-SNAPSHOT
> Jboss 4.0.5-GA
> Reporter: Gabriele Garuglieri
>
> When starting a shared filesystem slave the journaledJDBC persistence adapter initialization won't return until it has acquired the journal lock, but this behaviour has devastating effects in Jboss.
> Infact this means that the deploy won't complete, hanging the Jboss deployer so that applications cannot any longer be deployed or undeployed.
> Even worse if you try to restart Jboss with AMQ still deployed the application server startup phase won't complete and you won't be able to interact with Jboss. No console, no applications, not even able to orderly shutdown it.
> The only thing you can do to recover is to kill the process and manually remove the AMQ from deploy directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.