December 2017 - mod_cluster-issues

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

by Anurag Debnath (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-636?page=com.atlassian.jira.pl... ] Anurag Debnath commented on MODCLUSTER-636: ------------------------------------------- Hi [~jfclere] . Can you kindly help answering the above queries from the customer and Ted. Would need to cascade the same to the customer soon. > 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)

7 years

1
0
0 / 0

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

by Ted Won (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-636?page=com.atlassian.jira.pl... ] Ted Won commented on MODCLUSTER-636: ------------------------------------ [~jfclere], We also have another question, the issue also could be related with MPM module in 00-mpm.conf ? It looks reproduced only when using mod_mpm_worker.so, not the default mod_mpm_prefork.so. Is the issue related with only mod_mpm_worker.so ? We will much appreciate on more details. > 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)

7 years

1
0
0 / 0

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

by Alex Cai (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-636?page=com.atlassian.jira.pl... ] Alex Cai edited comment on MODCLUSTER-636 at 12/21/17 10:56 PM: ---------------------------------------------------------------- Thank you so much [~jfclere] Besides Minwoo's question, some further questions from customer: - This Is not a bug? just a constraint? - If changing the smax value arbitrarily, can the same problem occur? according to code you provided. looks it is a yes. - 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? Thanks was (Author: alexcred): Thank you so much [~jfclere] Besides Minwoo's question, some further questions from customer: - This Is not a bug? just a constraint? - If changing the smax value arbitrarily, can the same problem occur? - 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? Thanks > 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)

7 years

1
0
0 / 0

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

by Alex Cai (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-636?page=com.atlassian.jira.pl... ] Alex Cai edited comment on MODCLUSTER-636 at 12/21/17 10:48 PM: ---------------------------------------------------------------- Thank you so much [~jfclere] Besides Minwoo's question, some further questions from customer: - This Is not a bug? just a constraint? - If changing the smax value arbitrarily, can the same problem occur? - 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? Thanks was (Author: alexcred): Thank you so much [~jfclere] Besides Minwoo's question, some further question from customer: - This Is not a bug? just a constraint? - If changing the smax value arbitrarily, can the same problem occur? - 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? Thanks > 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)

7 years

1
0
0 / 0

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

by Alex Cai (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-636?page=com.atlassian.jira.pl... ] Alex Cai commented on MODCLUSTER-636: ------------------------------------- Thank you so much [~jfclere] Besides Minwoo's question, some further question from customer: - This Is not a bug? just a constraint? - If changing the smax value arbitrarily, can the same problem occur? - 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? Thanks > 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)

7 years

1
0
0 / 0

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

by Minwoo Park (JIRA)

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

7 years

1
0
0 / 0

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

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-636?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-636: ------------------------------------------------ 1) Yes it does, 2) https://github.com/modcluster/mod_proxy_cluster/blob/master/native/mod_ma... https://github.com/modcluster/mod_proxy_cluster/blob/master/native/mod_ma... 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)

7 years

1
0
0 / 0

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

by Minwoo Park (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-636?page=com.atlassian.jira.pl... ] Minwoo Park updated MODCLUSTER-636: ----------------------------------- Comment: was deleted (was: [~jfclere] Hi,Jean-Frederic Can you explain the reason for NOT change ThreadsPerChild with 'PersistSlots On'? And is there any other restriction in the case of 'PersistSlots On'? 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)

7 years

1
0
0 / 0

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

by Minwoo Park (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-636?page=com.atlassian.jira.pl... ] Minwoo Park commented on MODCLUSTER-636: ---------------------------------------- [~jfclere] Hi,Jean-Frederic Can you explain the reason for NOT change ThreadsPerChild with 'PersistSlots On'? And is there any other restriction in the case of 'PersistSlots On'? 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)

7 years

1
0
0 / 0

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

by Alex Cai (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-636?page=com.atlassian.jira.pl... ] Alex Cai edited comment on MODCLUSTER-636 at 12/21/17 12:52 AM: ---------------------------------------------------------------- [~jfclere] We got the following feedback from customer regarding ThreadsPerChild: -------- 1. We know that ThreadsPerChild is changed frequently when using apache. - Does it mean that we should not change the ThreadsPerChild value, if we use the PersistSlots On option. - web server administrator said that there was a problem when only restarting the web server, and after tracking what he did, he modified the 00-mpm.conf file and confirmed that he restarted it. - So, to reproduce, 00-mpm.conf was modified and tried to test, and reproduced more than a few times. 2. We modified the ThreadPerChild option to increase the number of threads per apache child process. - It is set to a low value before the load test, and it is set to a high value in the load test. - We also adjusted these options to reduce the number of child processes to find the appropriate values, and to increase the number of threads in each child process. - If you set it to a value greater than or equal to 64, we know that it usually should be set the ThreadLimit and ThreadsPerChild values the same. -------- 1. Does this match your ananlysis? 2. Could you please share more details regarding why changing ThreadsPerChild with PersistSlots On will cause the problem? We will need to let customer understand the reason. 3. Customer also wants to know all the other restrictions besides changing the ThreadsPerChild when having PersistentSlots On. Could you please list these kind of restrictions? Thanks a lot was (Author: alexcred): [~jfclere] We got the following feedback from customer regarding ThreadsPerChild: -------- 1. We know that ThreadsPerChild is changed frequently when using apache. - Does it mean that we should not change the ThreadsPerChild value, if we use the PersistSlots On option. - web server administrator said that there was a problem when only restarting the web server, and after tracking what he did, he modified the 00-mpm.conf file and confirmed that he restarted it. - So, to reproduce, 00-mpm.conf was modified and tried to test, and reproduced more than a few times. 2. We modified the ThreadPerChild option to increase the number of threads per apache child process. - It is set to a low value before the load test, and it is set to a high value in the load test. - We also adjusted these options to reduce the number of child processes to find the appropriate values, and to increase the number of threads in each child process. - If you set it to a value greater than or equal to 64, we know that it usually should be set the ThreadLimit and ThreadsPerChild values the same. -------- Does this match your ananlysis? Could you please share more details regarding why changing ThreadsPerChild with PersistSlots On will cause the problem? We will need to let customer understand the reason. Thanks a lot > 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)

7 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues December 2017