[
https://issues.jboss.org/browse/MODCLUSTER-636?page=com.atlassian.jira.pl...
]
Minwoo Park commented on MODCLUSTER-636:
----------------------------------------
Hi Jean-Frederic,
I could see below statement in the KCS [1]
https://access.redhat.com/solutions/72803,
~~~~~
"Please note if PersistSlots is set to on in apache httpd.conf then the manager.*
files must be deleted before restarting apache since changing MaxHost, or MaxNode, or
MaxContext can corrupt the persist slots data. These files are stored under the apache
logs folder by default."
~~~~~
If we should change the ThreadPerShild on production, then I MUST delete the manager.*
files before restarting apache to avoid this issue?
Thanks,
Minwoo
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)