[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-139) Allow override of default clean shutdown behavior

Michal Babacek (JIRA) issues at jboss.org
Fri Aug 8 06:28:55 EDT 2014


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

Michal Babacek closed MODCLUSTER-139.
-------------------------------------



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

> Allow override of default clean shutdown behavior
> -------------------------------------------------
>
>                 Key: MODCLUSTER-139
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-139
>             Project: mod_cluster
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.1.0.CR1
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>            Priority: Minor
>             Fix For: 1.1.0.CR3
>
>
> By default, if a web-app is declared <distributable/>, we will only wait until there are no pending requests and all sessions are safely replicated.  Only if a web-app is not <distributable/>, do we wait until there are no more active sessions, since there is no session replication.  We need the ability to allow the user to override this default  behavior, and use session draining even for <distributable/> apps, to avoid overloading remaining servers with failover requests.



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


More information about the mod_cluster-issues mailing list