[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-636) When setting PersistSlots to On, EAP node can not rejoin mod_cluster due to java.lang.IllegalArgumentException

[Jean-Frederic Clere (JIRA)]

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

Jean-Frederic Clere commented on MODCLUSTER-636:
------------------------------------------------

1) Yes it does,
2) https://github.com/modcluster/mod_proxy_cluster/blob/master/native/mod_manager/mod_manager.c#L758
    https://github.com/modcluster/mod_proxy_cluster/blob/master/native/mod_manager/mod_manager.c#L829
   basically the smax is stored because of the PersistSlots is On, after a restart and a change in ThreadsPerChild the value of smax is changed and the worker corresponding to the node is marked as not usable (as if the smax would be changed in the mod_cluster configuration aka received in the CONFIG message).
3) I think that is the only one.

> When setting PersistSlots to On, EAP node can not rejoin mod_cluster due to java.lang.IllegalArgumentException
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: MODCLUSTER-636
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-636
>             Project: mod_cluster
>          Issue Type: Bug
>          Components: Native (httpd modules)
>    Affects Versions: 1.3.5.Final
>         Environment: * JBCS httpd 2.4.23 SP2
> * mod_cluster: 1.3.5
> * EAP: 7.0.8
>            Reporter: Alex Cai
>            Assignee: Jean-Frederic Clere
>
> Customer set 'PersistSlots On' and sometimes the jboss eap node could not rejoing into mod_cluster due to java.lang.IllegalArgumentException
> When they got this exception, they have to delete every cache files then restart httpd and jboss for join correctly.
> Customer tried the below actions:
> 1) apache stop -> delet manager.* files in the mod_cluster directory -> apache start 
> - this action could cause http 503 error
> or
> 2) pre-backup the all files(normal files before issue) in the mod_cluster directory. when the issue occure, apache stop -> restore manager.* files from backuped files -> apache start
> - no http 503 error
> Please see the case for more details:
> https://access.redhat.com/support/cases/01986243



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)