[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-365) Reset MCMPs are sent to all available proxies

[Aaron Ogburn (JIRA)]

    [ https://issues.jboss.org/browse/MODCLUSTER-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12822946#comment-12822946 ] 

Aaron Ogburn commented on MODCLUSTER-365:
-----------------------------------------

I was able to correct this by adding an additional private method to be used on the status call to send the reset requests just to the designated proxy.  This corrects the noted auto-enable-context=false scenario since the resets DISABLE-APP is only sent to the restarted httpd.  The other non-restarted httpd remains with its context ENABLED as desired, no t impacted by the other httpd's restart any longer.
                
> Reset MCMPs are sent to all available proxies
> ---------------------------------------------
>
>                 Key: MODCLUSTER-365
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-365
>             Project: mod_cluster
>          Issue Type: Bug
>    Affects Versions: 1.2.6.Final
>         Environment: -JBoss Enterprise Application Platform (EAP) 6.1.1
>            Reporter: Aaron Ogburn
>            Assignee: Jean-Frederic Clere
>
> Consider a JBoss server with multiple httpd servers defined in its proxy-list.  If one of those httpd servers goes down and then comes back up, then reset MCMPs (CONFIG, ENABLE-APP) would be sent to the restarted httpd proxy but needlessly to all other proxies as well.  This is because DefaultMCMPHandler.status just calls sendRequests, which will send to all proxies by design.
> This has negative implications if auto-enable-contexts is set to false and can break desired behavior.  Reproducer steps detail the issue introduced in that scenario.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira