[
https://issues.apache.org/jira/browse/GERONIMO-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755394#action_12755394
]
Shawn Jiang commented on GERONIMO-4850:
---------------------------------------
When node-A (main node) is shutdown.
BasicClusterConfigurationController.doStop() get executed, it will stop the
cviewer configuration on each node in clustering.
When configuration cviewer in node-B is getting stopped by
LocalAttributeManager.stopConfiguration(Artifact){
.....
configuration.setLoad(false);
....
}
The cviewer configuration is set to "load=false". To fix it is not hard, but
I'm wondering if it's working as design case.
> WADI clustering: the application no node B will not start up when start up
> the node B.
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-4850
> URL: https://issues.apache.org/jira/browse/GERONIMO-4850
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Clustering
> Affects Versions: 2.2
> Environment: windows sp2
> jdk1.6
> Reporter: liangkun
> Assignee: Shawn Jiang
>
> 1.I configuration two nodes A and B following the WADI clustering and deploy
> the cviewer.war on the node A the no the node B there is cviewer.war also and
> they work well on 2 nodes.
> 2.shutdown A node first and then shutdown B node, I find that the cviewer.war
> load is set false in the config.xml of node B.
> 3 .start A and B, the cviewer.war on the node B can not start automatically.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
