[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-218) CLONE - Make mod_cluster manager tolerant to F5 page refresh when disabled context

[Michal Babacek (JIRA)]

     [ https://issues.jboss.org/browse/MODCLUSTER-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Babacek closed MODCLUSTER-218.
-------------------------------------



Closing. Clean-up.
At least one of the following applies:

  * the issue has been thoroughly tested as a part of one of the current releases
or
  * it hasn't occurred in ~2 years
or
  * it's utterly harmless

> CLONE - Make mod_cluster manager tolerant to F5 page refresh when disabled context
> ----------------------------------------------------------------------------------
>
>                 Key: MODCLUSTER-218
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-218
>             Project: mod_cluster
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.0.2.GA
>            Reporter: Radoslav Husar
>            Assignee: Jean-Frederic Clere
>            Priority: Minor
>             Fix For: 1.0.10
>
>
> I ran into this and found it rather unfriendly, when I wanted to refresh the mod_cluster manager (mcm) server returned Error 500. This happens when the last command was operating with a node which is no longer in the list. For example disabling a context:
> http://jawa11:7777/mod_cluster-manager?nonce=a6302da7-faa0-4338-8d35-9a254f3c1e1c&Cmd=DISABLE-APP&Range=CONTEXT&JVMRoute=node3&Alias=localhost&Context=/invoker
> You can easily run into this since there is no clear way - a link - to get to the page without any parameters (supposingly following the Autorefresh link which is not always desired to turn it off).
> Thanks for considering!



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)