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

[Anurag Debnath (JIRA)]

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

Anurag Debnath commented on MODCLUSTER-636:
-------------------------------------------

[~jfclere] , Hello ,

Referring to the queries posted by Alex above, can you provide input on the third point.  

The answers for the first two queries has been provided to the customer as below :

*     This Is not a bug? just a constraint?
          -- [Red Hat] Yes, once setting ThreadsPerChild appropriately and PersistSlots On, user should not change it during operation. 

*     If changing the smax value arbitrarily, can the same problem occur?  according to code you provided. looks it is a yes.
          -- [Red Hat] Yes, it's a constraint and not a bug.

*  If so, does the ThreadsPerChild value have to be correlated with max and smax and should not be arbitrarily changed with max and smax values ?  
       -- [Red Hat]    needs confirmation







> 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)