[mod_cluster-issues] [JBoss JIRA] Updated: (MODCLUSTER-220) Extra ENABLE-APP/REMOVE-APP event after failover

[Radoslav Husar (JIRA)]

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

Radoslav Husar updated MODCLUSTER-220:
--------------------------------------

              Summary: Extra ENABLE-APP/REMOVE-APP event after failover  (was: Extra REMOVE-APP event after failover)
    Affects Version/s: 1.0.8
          Environment: Deployment on Tomcat6
             Priority: Major  (was: Trivial)


This is a Tomcat deplyment, so its non-HA (which is not supported on Tomcat). I updated the Jira accordingly. I cant judge the severity of the issue but a race condition might trigger 404. Do the apps have also a state which is propagated in ENABLE-APP event? I don't think that's the case meaning its useless to remove and add back from the server.

> Extra ENABLE-APP/REMOVE-APP event after failover
> ------------------------------------------------
>
>                 Key: MODCLUSTER-220
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-220
>             Project: mod_cluster
>          Issue Type: Enhancement
>    Affects Versions: 1.0.8
>         Environment: Deployment on Tomcat6
>            Reporter: Radoslav Husar
>            Assignee: Jean-Frederic Clere
>
> Trivial thing: I think there is an extra REMOVE-APP event happening after fail-over. The test scenario is simple - start a node with 6 context, kill the node and reconnect. The apps are unchanged but 5 are remembered as were and one is removed and added back? Since they happen at the same time it looks like it happens uselessly and can cause race condition.
> {code}
> 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "INFO / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
> 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "CONFIG / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
> 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
> 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
> 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
> 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
> 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
> 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
> 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "STATUS / HTTP/1.0" 200 58 "-" "ClusterListener/1.0"
> ...
> 127.0.0.1 - - [04/Apr/2011:19:19:03 +0200] "GET /SessionTest/SessionTestServlet? HTTP/1.1" 200 1 "-" "Jakarta Commons-HttpClient/3.1"
> ...
> 127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "INFO / HTTP/1.0" 200 575 "-" "ClusterListener/1.0"
> 127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "CONFIG / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
> 127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
> 127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "REMOVE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
> 127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "STATUS / HTTP/1.0" 200 58 "-" "ClusterListener/1.0"
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira