[JBoss JIRA] (MODCLUSTER-571) Maven generates an empty distribution tarball on first execution
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-571?page=com.atlassian.jira.pl... ]
Radoslav Husar reassigned MODCLUSTER-571:
-----------------------------------------
Assignee: Radoslav Husar (was: Jean-Frederic Clere)
> Maven generates an empty distribution tarball on first execution
> ----------------------------------------------------------------
>
> Key: MODCLUSTER-571
> URL: https://issues.jboss.org/browse/MODCLUSTER-571
> Project: mod_cluster
> Issue Type: Bug
> Components: Core & Container Integration (Java)
> Affects Versions: 1.3.5.Final
> Environment: Debian 8 (jessie)
> Maven 3.0.5
> Reporter: Antoine Cotten
> Assignee: Radoslav Husar
> Priority: Minor
>
> The Maven {{package}} phase consistently generates an (almost) empty distribution tarball the first time it is executed.
> First execution:
> {code}
> $ tar -tvf /tmp/mod_cluster-1.3.5.Final/target/mod_cluster-parent-1.3.5.Final-bin.tar.gz
> -rw-rw-r-- root/root 7639 2016-10-26 06:40 lgpl.txt
> -rw-rw-r-- root/root 910 2016-10-26 06:40 release.txt
> {code}
> Second execution:
> {code}
> $ tar -tvf /tmp/mod_cluster-1.3.5.Final/target/mod_cluster-parent-1.3.5.Final-bin.tar.gz
> -rw-rw-r-- root/root 7639 2016-10-26 06:40 lgpl.txt
> -rw-rw-r-- root/root 910 2016-10-26 06:40 release.txt
> drwxr-xr-x 0/0 0 2017-02-01 22:26 demo/client/lib/
> -rw-r--r-- root/root 253160 2017-02-01 22:26 demo/client/lib/junit.jar
> -rw-r--r-- root/root 1425742 2017-02-01 22:26 demo/client/lib/jfreechart.jar
> -rw-r--r-- root/root 76643 2017-02-01 22:26 demo/client/lib/hamcrest-core.jar
> -rw-r--r-- root/root 1414161 2017-02-01 22:26 demo/client/lib/mockito-core.jar
> -rw-r--r-- root/root 309293 2017-02-01 22:26 demo/client/lib/jcommon.jar
> -rw-r--r-- root/root 28569 2017-02-01 22:26 demo/client/lib/objenesis.jar
> -rw-r--r-- root/root 36101 2017-02-01 22:26 demo/client/lib/mod_cluster-demo-client-1.3.5.Final.jar
> -rw-r--r-- root/root 589 2017-02-01 22:26 demo/client/run-demo.sh
> -rw-r--r-- root/root 608 2017-02-01 22:26 demo/client/run-demo.bat
> -rw-r--r-- root/root 851271 2017-02-01 22:27 demo/server/mod_cluster-demo-server-1.3.5.Final.war
> -rw-r--r-- root/root 7047 2017-02-01 22:25 JBossWeb-Tomcat/lib/mod_cluster-container-spi-1.3.5.Final.jar
> -rw-r--r-- root/root 119301 2017-02-01 22:25 JBossWeb-Tomcat/lib/mod_cluster-core-1.3.5.Final.jar
> -rw-r--r-- root/root 55248 2017-02-01 22:25 JBossWeb-Tomcat/lib/jboss-logging.jar
> -rw-r--r-- root/root 39049 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-catalina-1.3.5.Final.jar
> -rw-r--r-- root/root 13504 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-catalina-standalone-1.3.5.Final.jar
> -rw-r--r-- root/root 12045 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-tomcat6-1.3.5.Final.jar
> -rw-r--r-- root/root 12512 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-tomcat7-1.3.5.Final.jar
> -rw-r--r-- root/root 14963 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-tomcat8-1.3.5.Final.jar
> drwxr-xr-x 0/0 0 2017-02-01 22:27 mod_cluster.sar/
> drwxr-xr-x root/root 0 2017-02-01 22:27 mod_cluster.sar/META-INF/
> -rw-r--r-- root/root 39049 2017-02-01 22:26 mod_cluster.sar/mod_cluster-container-catalina-1.3.5.Final.jar
> -rw-r--r-- root/root 7047 2017-02-01 22:25 mod_cluster.sar/mod_cluster-container-spi-1.3.5.Final.jar
> -rw-r--r-- root/root 13980 2017-02-01 22:26 mod_cluster.sar/mod_cluster-container-jbossweb-1.3.5.Final.jar
> -rw-r--r-- root/root 12272 2016-10-26 06:40 mod_cluster.sar/META-INF/mod_cluster-jboss-beans.xml
> -rw-r--r-- root/root 119301 2017-02-01 22:25 mod_cluster.sar/mod_cluster-core-1.3.5.Final.jar
> {code}
> ref. http://modcluster.io/documentation/#building-worker-side-components
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (MODCLUSTER-71) Handle multiple versions of the same webapp
by Michal Karm Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-71?page=com.atlassian.jira.plu... ]
Michal Karm Babacek closed MODCLUSTER-71.
-----------------------------------------
Resolution: Out of Date
Unless there is a continuous demand, remains closed...
> Handle multiple versions of the same webapp
> -------------------------------------------
>
> Key: MODCLUSTER-71
> URL: https://issues.jboss.org/browse/MODCLUSTER-71
> Project: mod_cluster
> Issue Type: Feature Request
> Reporter: Brian Stansberry
> Assignee: Jean-Frederic Clere
>
> This is a big picture future roadmap kind of thing.
> Assume the AS develops the ability to host two versions of the same webapp concurrently. Imagine a workflow like this:
> 1) Version 1 is running, handling requests
> 2) Version 2 is deployed, is allowed to receive a low workload to validate that it works properly.
> 3) Version 2 is shifted to allow full workload
> 4) Version 1 is put into disabled mode to drain sessions
> 5) Version 1. is undeployed.
> Obviously making this work requires a lot of currently non-existent stuff in the AS. Point of this JIRA is think about how to deal with it at the mod_cluster level.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (MODCLUSTER-563) MaxAttemps behave
by Michal Karm Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-563?page=com.atlassian.jira.pl... ]
Michal Karm Babacek commented on MODCLUSTER-563:
------------------------------------------------
[~bsikora], updated documentation, http://modcluster.io/documentation/#proxy-configuration-1
WDYT?
> MaxAttemps behave
> -----------------
>
> Key: MODCLUSTER-563
> URL: https://issues.jboss.org/browse/MODCLUSTER-563
> Project: mod_cluster
> Issue Type: Bug
> Reporter: Bogdan Sikora
> Assignee: Michal Karm Babacek
>
> [MaxAttemps Documentation|http://docs.jboss.org/mod_cluster/1.3.0/html_single/#proxy]
> {noformat}
> Number of times an httpd proxy will attempt to send a given request to a worker before giving up. The minimum value is 1, meaning try only once. (Note that mod_proxy default is also 1: no retry)
> {noformat}
> Balancer is not behaving that way. Minimum that one can set is 0 that means "no retry" and overall the number there means how many times balancer should failover that request to another worker not how many (max)times balancer should sent the request to the workers (even the first one counts) as documentation stands.
> *Behave*
> ||MaxAttempts||Undertow||Httpd||Documentation
> | -1| (1) One retry | (1)One retry| Default of 1 should be used and therefore no retry
> | 0| (1) One retry | (0)No retry| Default of 1 should be used and therefore no retry
> | 1| (1) One retry | (1) One retry| No retry
> | 2| (2) Two retries| (2) Two retries | One retry
> \(x\) - x represents amount of retries based on balancer behave
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (MODCLUSTER-376) multiple workers with the same id following a tomcat crash/kill
by Jean-Frederic Clere (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-376?page=com.atlassian.jira.pl... ]
Jean-Frederic Clere updated MODCLUSTER-376:
-------------------------------------------
Labels: missing_upstream (was: )
> multiple workers with the same id following a tomcat crash/kill
> ---------------------------------------------------------------
>
> Key: MODCLUSTER-376
> URL: https://issues.jboss.org/browse/MODCLUSTER-376
> Project: mod_cluster
> Issue Type: Bug
> Components: Native (httpd modules)
> Affects Versions: 1.0.10, 1.2.11.Final
> Environment: -JBoss Enterprise Web Server 1.0.2
> -mod_cluster 1.0.10.GA_CP04
> -Red Hat Enterprise Linux 5
> Reporter: Aaron Ogburn
> Assignee: Michal Karm Babacek
> Labels: missing_upstream
> Fix For: 1.2.13.Final
>
> Attachments: 131122.patch
>
>
> Following a kill or crash of tomcat, multiple workers are seen for a single id when a new tomcat node reconnects and reuses the id from the previously crashed worker.
> The STATUS's ping check sees the old crashed worker first for the id and so pings the wrong destination. Thus the ping fails, and load factor is not applied. The persistent -1 load state leads to 503s.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (MODCLUSTER-571) Maven generates an empty distribution tarball on first execution
by Antoine Cotten (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-571?page=com.atlassian.jira.pl... ]
Antoine Cotten updated MODCLUSTER-571:
--------------------------------------
Description:
The Maven {{package}} phase consistently generates an (almost) empty distribution tarball the first time it is executed.
First execution:
{code}
$ tar -tvf /tmp/mod_cluster-1.3.5.Final/target/mod_cluster-parent-1.3.5.Final-bin.tar.gz
-rw-rw-r-- root/root 7639 2016-10-26 06:40 lgpl.txt
-rw-rw-r-- root/root 910 2016-10-26 06:40 release.txt
{code}
Second execution:
{code}
$ tar -tvf /tmp/mod_cluster-1.3.5.Final/target/mod_cluster-parent-1.3.5.Final-bin.tar.gz
-rw-rw-r-- root/root 7639 2016-10-26 06:40 lgpl.txt
-rw-rw-r-- root/root 910 2016-10-26 06:40 release.txt
drwxr-xr-x 0/0 0 2017-02-01 22:26 demo/client/lib/
-rw-r--r-- root/root 253160 2017-02-01 22:26 demo/client/lib/junit.jar
-rw-r--r-- root/root 1425742 2017-02-01 22:26 demo/client/lib/jfreechart.jar
-rw-r--r-- root/root 76643 2017-02-01 22:26 demo/client/lib/hamcrest-core.jar
-rw-r--r-- root/root 1414161 2017-02-01 22:26 demo/client/lib/mockito-core.jar
-rw-r--r-- root/root 309293 2017-02-01 22:26 demo/client/lib/jcommon.jar
-rw-r--r-- root/root 28569 2017-02-01 22:26 demo/client/lib/objenesis.jar
-rw-r--r-- root/root 36101 2017-02-01 22:26 demo/client/lib/mod_cluster-demo-client-1.3.5.Final.jar
-rw-r--r-- root/root 589 2017-02-01 22:26 demo/client/run-demo.sh
-rw-r--r-- root/root 608 2017-02-01 22:26 demo/client/run-demo.bat
-rw-r--r-- root/root 851271 2017-02-01 22:27 demo/server/mod_cluster-demo-server-1.3.5.Final.war
-rw-r--r-- root/root 7047 2017-02-01 22:25 JBossWeb-Tomcat/lib/mod_cluster-container-spi-1.3.5.Final.jar
-rw-r--r-- root/root 119301 2017-02-01 22:25 JBossWeb-Tomcat/lib/mod_cluster-core-1.3.5.Final.jar
-rw-r--r-- root/root 55248 2017-02-01 22:25 JBossWeb-Tomcat/lib/jboss-logging.jar
-rw-r--r-- root/root 39049 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-catalina-1.3.5.Final.jar
-rw-r--r-- root/root 13504 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-catalina-standalone-1.3.5.Final.jar
-rw-r--r-- root/root 12045 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-tomcat6-1.3.5.Final.jar
-rw-r--r-- root/root 12512 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-tomcat7-1.3.5.Final.jar
-rw-r--r-- root/root 14963 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-tomcat8-1.3.5.Final.jar
drwxr-xr-x 0/0 0 2017-02-01 22:27 mod_cluster.sar/
drwxr-xr-x root/root 0 2017-02-01 22:27 mod_cluster.sar/META-INF/
-rw-r--r-- root/root 39049 2017-02-01 22:26 mod_cluster.sar/mod_cluster-container-catalina-1.3.5.Final.jar
-rw-r--r-- root/root 7047 2017-02-01 22:25 mod_cluster.sar/mod_cluster-container-spi-1.3.5.Final.jar
-rw-r--r-- root/root 13980 2017-02-01 22:26 mod_cluster.sar/mod_cluster-container-jbossweb-1.3.5.Final.jar
-rw-r--r-- root/root 12272 2016-10-26 06:40 mod_cluster.sar/META-INF/mod_cluster-jboss-beans.xml
-rw-r--r-- root/root 119301 2017-02-01 22:25 mod_cluster.sar/mod_cluster-core-1.3.5.Final.jar
{code}
ref. http://modcluster.io/documentation/#building-worker-side-components
was:
The Maven {{package}} goal consistently generates an (almost) empty distribution tarball the first time it is executed.
First execution:
{code}
$ tar -tvf /tmp/mod_cluster-1.3.5.Final/target/mod_cluster-parent-1.3.5.Final-bin.tar.gz
-rw-rw-r-- root/root 7639 2016-10-26 06:40 lgpl.txt
-rw-rw-r-- root/root 910 2016-10-26 06:40 release.txt
{code}
Second execution:
{code}
$ tar -tvf /tmp/mod_cluster-1.3.5.Final/target/mod_cluster-parent-1.3.5.Final-bin.tar.gz
-rw-rw-r-- root/root 7639 2016-10-26 06:40 lgpl.txt
-rw-rw-r-- root/root 910 2016-10-26 06:40 release.txt
drwxr-xr-x 0/0 0 2017-02-01 22:26 demo/client/lib/
-rw-r--r-- root/root 253160 2017-02-01 22:26 demo/client/lib/junit.jar
-rw-r--r-- root/root 1425742 2017-02-01 22:26 demo/client/lib/jfreechart.jar
-rw-r--r-- root/root 76643 2017-02-01 22:26 demo/client/lib/hamcrest-core.jar
-rw-r--r-- root/root 1414161 2017-02-01 22:26 demo/client/lib/mockito-core.jar
-rw-r--r-- root/root 309293 2017-02-01 22:26 demo/client/lib/jcommon.jar
-rw-r--r-- root/root 28569 2017-02-01 22:26 demo/client/lib/objenesis.jar
-rw-r--r-- root/root 36101 2017-02-01 22:26 demo/client/lib/mod_cluster-demo-client-1.3.5.Final.jar
-rw-r--r-- root/root 589 2017-02-01 22:26 demo/client/run-demo.sh
-rw-r--r-- root/root 608 2017-02-01 22:26 demo/client/run-demo.bat
-rw-r--r-- root/root 851271 2017-02-01 22:27 demo/server/mod_cluster-demo-server-1.3.5.Final.war
-rw-r--r-- root/root 7047 2017-02-01 22:25 JBossWeb-Tomcat/lib/mod_cluster-container-spi-1.3.5.Final.jar
-rw-r--r-- root/root 119301 2017-02-01 22:25 JBossWeb-Tomcat/lib/mod_cluster-core-1.3.5.Final.jar
-rw-r--r-- root/root 55248 2017-02-01 22:25 JBossWeb-Tomcat/lib/jboss-logging.jar
-rw-r--r-- root/root 39049 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-catalina-1.3.5.Final.jar
-rw-r--r-- root/root 13504 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-catalina-standalone-1.3.5.Final.jar
-rw-r--r-- root/root 12045 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-tomcat6-1.3.5.Final.jar
-rw-r--r-- root/root 12512 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-tomcat7-1.3.5.Final.jar
-rw-r--r-- root/root 14963 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-tomcat8-1.3.5.Final.jar
drwxr-xr-x 0/0 0 2017-02-01 22:27 mod_cluster.sar/
drwxr-xr-x root/root 0 2017-02-01 22:27 mod_cluster.sar/META-INF/
-rw-r--r-- root/root 39049 2017-02-01 22:26 mod_cluster.sar/mod_cluster-container-catalina-1.3.5.Final.jar
-rw-r--r-- root/root 7047 2017-02-01 22:25 mod_cluster.sar/mod_cluster-container-spi-1.3.5.Final.jar
-rw-r--r-- root/root 13980 2017-02-01 22:26 mod_cluster.sar/mod_cluster-container-jbossweb-1.3.5.Final.jar
-rw-r--r-- root/root 12272 2016-10-26 06:40 mod_cluster.sar/META-INF/mod_cluster-jboss-beans.xml
-rw-r--r-- root/root 119301 2017-02-01 22:25 mod_cluster.sar/mod_cluster-core-1.3.5.Final.jar
{code}
ref. http://modcluster.io/documentation/#building-worker-side-components
> Maven generates an empty distribution tarball on first execution
> ----------------------------------------------------------------
>
> Key: MODCLUSTER-571
> URL: https://issues.jboss.org/browse/MODCLUSTER-571
> Project: mod_cluster
> Issue Type: Bug
> Components: Core & Container Integration (Java)
> Affects Versions: 1.3.5.Final
> Environment: Debian 8 (jessie)
> Maven 3.0.5
> Reporter: Antoine Cotten
> Assignee: Jean-Frederic Clere
> Priority: Minor
>
> The Maven {{package}} phase consistently generates an (almost) empty distribution tarball the first time it is executed.
> First execution:
> {code}
> $ tar -tvf /tmp/mod_cluster-1.3.5.Final/target/mod_cluster-parent-1.3.5.Final-bin.tar.gz
> -rw-rw-r-- root/root 7639 2016-10-26 06:40 lgpl.txt
> -rw-rw-r-- root/root 910 2016-10-26 06:40 release.txt
> {code}
> Second execution:
> {code}
> $ tar -tvf /tmp/mod_cluster-1.3.5.Final/target/mod_cluster-parent-1.3.5.Final-bin.tar.gz
> -rw-rw-r-- root/root 7639 2016-10-26 06:40 lgpl.txt
> -rw-rw-r-- root/root 910 2016-10-26 06:40 release.txt
> drwxr-xr-x 0/0 0 2017-02-01 22:26 demo/client/lib/
> -rw-r--r-- root/root 253160 2017-02-01 22:26 demo/client/lib/junit.jar
> -rw-r--r-- root/root 1425742 2017-02-01 22:26 demo/client/lib/jfreechart.jar
> -rw-r--r-- root/root 76643 2017-02-01 22:26 demo/client/lib/hamcrest-core.jar
> -rw-r--r-- root/root 1414161 2017-02-01 22:26 demo/client/lib/mockito-core.jar
> -rw-r--r-- root/root 309293 2017-02-01 22:26 demo/client/lib/jcommon.jar
> -rw-r--r-- root/root 28569 2017-02-01 22:26 demo/client/lib/objenesis.jar
> -rw-r--r-- root/root 36101 2017-02-01 22:26 demo/client/lib/mod_cluster-demo-client-1.3.5.Final.jar
> -rw-r--r-- root/root 589 2017-02-01 22:26 demo/client/run-demo.sh
> -rw-r--r-- root/root 608 2017-02-01 22:26 demo/client/run-demo.bat
> -rw-r--r-- root/root 851271 2017-02-01 22:27 demo/server/mod_cluster-demo-server-1.3.5.Final.war
> -rw-r--r-- root/root 7047 2017-02-01 22:25 JBossWeb-Tomcat/lib/mod_cluster-container-spi-1.3.5.Final.jar
> -rw-r--r-- root/root 119301 2017-02-01 22:25 JBossWeb-Tomcat/lib/mod_cluster-core-1.3.5.Final.jar
> -rw-r--r-- root/root 55248 2017-02-01 22:25 JBossWeb-Tomcat/lib/jboss-logging.jar
> -rw-r--r-- root/root 39049 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-catalina-1.3.5.Final.jar
> -rw-r--r-- root/root 13504 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-catalina-standalone-1.3.5.Final.jar
> -rw-r--r-- root/root 12045 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-tomcat6-1.3.5.Final.jar
> -rw-r--r-- root/root 12512 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-tomcat7-1.3.5.Final.jar
> -rw-r--r-- root/root 14963 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-tomcat8-1.3.5.Final.jar
> drwxr-xr-x 0/0 0 2017-02-01 22:27 mod_cluster.sar/
> drwxr-xr-x root/root 0 2017-02-01 22:27 mod_cluster.sar/META-INF/
> -rw-r--r-- root/root 39049 2017-02-01 22:26 mod_cluster.sar/mod_cluster-container-catalina-1.3.5.Final.jar
> -rw-r--r-- root/root 7047 2017-02-01 22:25 mod_cluster.sar/mod_cluster-container-spi-1.3.5.Final.jar
> -rw-r--r-- root/root 13980 2017-02-01 22:26 mod_cluster.sar/mod_cluster-container-jbossweb-1.3.5.Final.jar
> -rw-r--r-- root/root 12272 2016-10-26 06:40 mod_cluster.sar/META-INF/mod_cluster-jboss-beans.xml
> -rw-r--r-- root/root 119301 2017-02-01 22:25 mod_cluster.sar/mod_cluster-core-1.3.5.Final.jar
> {code}
> ref. http://modcluster.io/documentation/#building-worker-side-components
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (MODCLUSTER-571) Maven generates an empty distribution tarball on first execution
by Antoine Cotten (JIRA)
Antoine Cotten created MODCLUSTER-571:
-----------------------------------------
Summary: Maven generates an empty distribution tarball on first execution
Key: MODCLUSTER-571
URL: https://issues.jboss.org/browse/MODCLUSTER-571
Project: mod_cluster
Issue Type: Bug
Components: Core & Container Integration (Java)
Affects Versions: 1.3.5.Final
Environment: Debian 8 (jessie)
Maven 3.0.5
Reporter: Antoine Cotten
Assignee: Jean-Frederic Clere
Priority: Minor
The Maven {{package}} goal consistently generates an (almost) empty distribution tarball the first time it is executed.
First execution:
{code}
$ tar -tvf /tmp/mod_cluster-1.3.5.Final/target/mod_cluster-parent-1.3.5.Final-bin.tar.gz
-rw-rw-r-- root/root 7639 2016-10-26 06:40 lgpl.txt
-rw-rw-r-- root/root 910 2016-10-26 06:40 release.txt
{code}
Second execution:
{code}
$ tar -tvf /tmp/mod_cluster-1.3.5.Final/target/mod_cluster-parent-1.3.5.Final-bin.tar.gz
-rw-rw-r-- root/root 7639 2016-10-26 06:40 lgpl.txt
-rw-rw-r-- root/root 910 2016-10-26 06:40 release.txt
drwxr-xr-x 0/0 0 2017-02-01 22:26 demo/client/lib/
-rw-r--r-- root/root 253160 2017-02-01 22:26 demo/client/lib/junit.jar
-rw-r--r-- root/root 1425742 2017-02-01 22:26 demo/client/lib/jfreechart.jar
-rw-r--r-- root/root 76643 2017-02-01 22:26 demo/client/lib/hamcrest-core.jar
-rw-r--r-- root/root 1414161 2017-02-01 22:26 demo/client/lib/mockito-core.jar
-rw-r--r-- root/root 309293 2017-02-01 22:26 demo/client/lib/jcommon.jar
-rw-r--r-- root/root 28569 2017-02-01 22:26 demo/client/lib/objenesis.jar
-rw-r--r-- root/root 36101 2017-02-01 22:26 demo/client/lib/mod_cluster-demo-client-1.3.5.Final.jar
-rw-r--r-- root/root 589 2017-02-01 22:26 demo/client/run-demo.sh
-rw-r--r-- root/root 608 2017-02-01 22:26 demo/client/run-demo.bat
-rw-r--r-- root/root 851271 2017-02-01 22:27 demo/server/mod_cluster-demo-server-1.3.5.Final.war
-rw-r--r-- root/root 7047 2017-02-01 22:25 JBossWeb-Tomcat/lib/mod_cluster-container-spi-1.3.5.Final.jar
-rw-r--r-- root/root 119301 2017-02-01 22:25 JBossWeb-Tomcat/lib/mod_cluster-core-1.3.5.Final.jar
-rw-r--r-- root/root 55248 2017-02-01 22:25 JBossWeb-Tomcat/lib/jboss-logging.jar
-rw-r--r-- root/root 39049 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-catalina-1.3.5.Final.jar
-rw-r--r-- root/root 13504 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-catalina-standalone-1.3.5.Final.jar
-rw-r--r-- root/root 12045 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-tomcat6-1.3.5.Final.jar
-rw-r--r-- root/root 12512 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-tomcat7-1.3.5.Final.jar
-rw-r--r-- root/root 14963 2017-02-01 22:26 JBossWeb-Tomcat/lib/mod_cluster-container-tomcat8-1.3.5.Final.jar
drwxr-xr-x 0/0 0 2017-02-01 22:27 mod_cluster.sar/
drwxr-xr-x root/root 0 2017-02-01 22:27 mod_cluster.sar/META-INF/
-rw-r--r-- root/root 39049 2017-02-01 22:26 mod_cluster.sar/mod_cluster-container-catalina-1.3.5.Final.jar
-rw-r--r-- root/root 7047 2017-02-01 22:25 mod_cluster.sar/mod_cluster-container-spi-1.3.5.Final.jar
-rw-r--r-- root/root 13980 2017-02-01 22:26 mod_cluster.sar/mod_cluster-container-jbossweb-1.3.5.Final.jar
-rw-r--r-- root/root 12272 2016-10-26 06:40 mod_cluster.sar/META-INF/mod_cluster-jboss-beans.xml
-rw-r--r-- root/root 119301 2017-02-01 22:25 mod_cluster.sar/mod_cluster-core-1.3.5.Final.jar
{code}
ref. http://modcluster.io/documentation/#building-worker-side-components
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (MODCLUSTER-570) Multiple invalid nodes created on graceful httpd restart
by Antoine Cotten (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-570?page=com.atlassian.jira.pl... ]
Antoine Cotten updated MODCLUSTER-570:
--------------------------------------
Description:
mod_cluster creates a bunch of invalid nodes after a graceful restart of Apache httpd ({{SIGUSR1}}, {{SIGWINCH}}). The issue happens with or without backend servers in the pool.
httpd logs:
{code}
[mpm_event:notice] [pid 1:tid 140313388616520] AH00493: SIGUSR1 received. Doing graceful restart
[:notice] [pid 1:tid 140313388616520] Advertise initialized for process 1
[mpm_event:notice] [pid 1:tid 140313388616520] AH00489: Apache/2.4.25 (Unix) mod_cluster/1.3.5.Final configured -- resuming normal operations
[core:notice] [pid 1:tid 140313388616520] AH00094: Command line: 'httpd -D FOREGROUND'
[:notice] [pid 116:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
[:notice] [pid 116:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
[:notice] [pid 116:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
# ... trimmed 48 lines ...
[:notice] [pid 145:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
[:notice] [pid 145:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
[:notice] [pid 145:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
[:notice] [pid 145:tid 140313388616520] Created: worker for ://:\x9d\x7f failed: Unable to parse URL
[:notice] [pid 145:tid 140313388616520] add_balancer_node: balancer safe-name (balancer://4:6666\r\nX-Manager-Url: /c8dae916-7642-4deb-b841-2f3435613749\r\nX-Manager-Protocol: http\r\nX-Manager-Host: 172.17.0.4\r\n\r\n) too long
{code}
Application server logs (tomcat8):
{code}
Feb 01, 2017 11:34:25 AM org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler sendRequest
ERROR: MODCLUSTER000042: Error MEM sending STATUS command to 172.17.0.4/172.17.0.4:6666, configuration will be reset: MEM: Can't read node with "java1-depl1-1234" JVMRoute
Feb 01, 2017 11:34:35 AM org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildren
SEVERE: Exception invoking periodic operation:
java.lang.IllegalArgumentException: Node: [1],Name: ,Balancer: ,LBGroup: ,Host: ,Port: ,Type: ,Flushpackets: Off,Flushwait: 0,Ping: 0,Smax: 0,Ttl: 0,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 0
Node: [2],Name: ,Balancer: ,LBGroup: ,Host: ,Port: ,Type: ,Flushpackets: Off,Flushwait: 0,Ping: 0,Smax: 0,Ttl: 0,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 0
Node: [3],Name: ,Balancer: ,LBGroup: ,Host: ,Port: ,Type: ,Flushpackets: Off,Flushwait: 0,Ping: 0,Smax: 0,Ttl: 0,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 0
# ... trimmed lines ...
Node: [18],Name: ,Balancer: ,LBGroup: ,Host: ,Port: ,Type: ,Flushpackets: Off,Flushwait: 0,Ping: 0,Smax: 0,Ttl: 0,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 0
Node: [19],Name: ,Balancer: ,LBGroup: ,Host: ,Port: ,Type: ,Flushpackets: Off,Flushwait: 0,Ping: 0,Smax: 0,Ttl: 0,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 0
Vhost: [0:0:1], Alias:
Vhost: [0:0:2], Alias:
Vhost: [0:0:3], Alias:
# ... trimmed lines ...
Vhost: [0:0:19], Alias:
Vhost: [0:0:20], Alias:
Context: [0:0:1], Context: , Status: REMOVED
Context: [0:0:2], Context: , Status: REMOVED
Context: [0:0:3], Context: , Status: REMOVED
# ... trimmed lines ...
Context: [0:0:97], Context: , Status: REMOVED
Context: [0:0:98], Context: , Status: REMOVED
Context: [0:0:99], Context: , Status: REMOVED
Context: [0:0:1], Context: , Status: REMOVED
at org.jboss.modcluster.mcmp.impl.DefaultMCMPResponseParser.parseInfoResponse(DefaultMCMPResponseParser.java:96)
at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:396)
at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:365)
at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:457)
at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:252)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1374)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1546)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1524)
at java.lang.Thread.run(Thread.java:745)
Feb 01, 2017 11:35:05 AM org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler sendRequest
{code}
was:
mod_cluster creates a bunch of invalid nodes after a graceful restart of Apache httpd (SIGUSR1, SIGWINCH).
httpd logs:
{code}
[mpm_event:notice] [pid 1:tid 140313388616520] AH00493: SIGUSR1 received. Doing graceful restart
[:notice] [pid 1:tid 140313388616520] Advertise initialized for process 1
[mpm_event:notice] [pid 1:tid 140313388616520] AH00489: Apache/2.4.25 (Unix) mod_cluster/1.3.5.Final configured -- resuming normal operations
[core:notice] [pid 1:tid 140313388616520] AH00094: Command line: 'httpd -D FOREGROUND'
[:notice] [pid 116:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
[:notice] [pid 116:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
[:notice] [pid 116:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
# ... trimmed 48 lines ...
[:notice] [pid 145:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
[:notice] [pid 145:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
[:notice] [pid 145:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
[:notice] [pid 145:tid 140313388616520] Created: worker for ://:\x9d\x7f failed: Unable to parse URL
[:notice] [pid 145:tid 140313388616520] add_balancer_node: balancer safe-name (balancer://4:6666\r\nX-Manager-Url: /c8dae916-7642-4deb-b841-2f3435613749\r\nX-Manager-Protocol: http\r\nX-Manager-Host: 172.17.0.4\r\n\r\n) too long
{code}
Application server logs (tomcat8):
{code}
Feb 01, 2017 11:34:25 AM org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler sendRequest
ERROR: MODCLUSTER000042: Error MEM sending STATUS command to 172.17.0.4/172.17.0.4:6666, configuration will be reset: MEM: Can't read node with "java1-depl1-1234" JVMRoute
Feb 01, 2017 11:34:35 AM org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildren
SEVERE: Exception invoking periodic operation:
java.lang.IllegalArgumentException: Node: [1],Name: ,Balancer: ,LBGroup: ,Host: ,Port: ,Type: ,Flushpackets: Off,Flushwait: 0,Ping: 0,Smax: 0,Ttl: 0,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 0
Node: [2],Name: ,Balancer: ,LBGroup: ,Host: ,Port: ,Type: ,Flushpackets: Off,Flushwait: 0,Ping: 0,Smax: 0,Ttl: 0,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 0
Node: [3],Name: ,Balancer: ,LBGroup: ,Host: ,Port: ,Type: ,Flushpackets: Off,Flushwait: 0,Ping: 0,Smax: 0,Ttl: 0,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 0
# ... trimmed lines ...
Node: [18],Name: ,Balancer: ,LBGroup: ,Host: ,Port: ,Type: ,Flushpackets: Off,Flushwait: 0,Ping: 0,Smax: 0,Ttl: 0,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 0
Node: [19],Name: ,Balancer: ,LBGroup: ,Host: ,Port: ,Type: ,Flushpackets: Off,Flushwait: 0,Ping: 0,Smax: 0,Ttl: 0,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 0
Vhost: [0:0:1], Alias:
Vhost: [0:0:2], Alias:
Vhost: [0:0:3], Alias:
# ... trimmed lines ...
Vhost: [0:0:19], Alias:
Vhost: [0:0:20], Alias:
Context: [0:0:1], Context: , Status: REMOVED
Context: [0:0:2], Context: , Status: REMOVED
Context: [0:0:3], Context: , Status: REMOVED
# ... trimmed lines ...
Context: [0:0:97], Context: , Status: REMOVED
Context: [0:0:98], Context: , Status: REMOVED
Context: [0:0:99], Context: , Status: REMOVED
Context: [0:0:1], Context: , Status: REMOVED
at org.jboss.modcluster.mcmp.impl.DefaultMCMPResponseParser.parseInfoResponse(DefaultMCMPResponseParser.java:96)
at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:396)
at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:365)
at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:457)
at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:252)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1374)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1546)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1524)
at java.lang.Thread.run(Thread.java:745)
Feb 01, 2017 11:35:05 AM org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler sendRequest
{code}
> Multiple invalid nodes created on graceful httpd restart
> --------------------------------------------------------
>
> Key: MODCLUSTER-570
> URL: https://issues.jboss.org/browse/MODCLUSTER-570
> Project: mod_cluster
> Issue Type: Bug
> Components: Native (httpd modules)
> Affects Versions: 1.3.5.Final
> Environment: httpd 2.4.25
> Reporter: Antoine Cotten
> Assignee: Jean-Frederic Clere
> Priority: Minor
> Attachments: mod_cluster_after_graceful.png, mod_cluster_before_graceful.png
>
>
> mod_cluster creates a bunch of invalid nodes after a graceful restart of Apache httpd ({{SIGUSR1}}, {{SIGWINCH}}). The issue happens with or without backend servers in the pool.
> httpd logs:
> {code}
> [mpm_event:notice] [pid 1:tid 140313388616520] AH00493: SIGUSR1 received. Doing graceful restart
> [:notice] [pid 1:tid 140313388616520] Advertise initialized for process 1
> [mpm_event:notice] [pid 1:tid 140313388616520] AH00489: Apache/2.4.25 (Unix) mod_cluster/1.3.5.Final configured -- resuming normal operations
> [core:notice] [pid 1:tid 140313388616520] AH00094: Command line: 'httpd -D FOREGROUND'
> [:notice] [pid 116:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
> [:notice] [pid 116:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
> [:notice] [pid 116:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
> # ... trimmed 48 lines ...
> [:notice] [pid 145:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
> [:notice] [pid 145:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
> [:notice] [pid 145:tid 140313388616520] Created: worker for ://: failed: Unable to parse URL
> [:notice] [pid 145:tid 140313388616520] Created: worker for ://:\x9d\x7f failed: Unable to parse URL
> [:notice] [pid 145:tid 140313388616520] add_balancer_node: balancer safe-name (balancer://4:6666\r\nX-Manager-Url: /c8dae916-7642-4deb-b841-2f3435613749\r\nX-Manager-Protocol: http\r\nX-Manager-Host: 172.17.0.4\r\n\r\n) too long
> {code}
> Application server logs (tomcat8):
> {code}
> Feb 01, 2017 11:34:25 AM org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler sendRequest
> ERROR: MODCLUSTER000042: Error MEM sending STATUS command to 172.17.0.4/172.17.0.4:6666, configuration will be reset: MEM: Can't read node with "java1-depl1-1234" JVMRoute
> Feb 01, 2017 11:34:35 AM org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildren
> SEVERE: Exception invoking periodic operation:
> java.lang.IllegalArgumentException: Node: [1],Name: ,Balancer: ,LBGroup: ,Host: ,Port: ,Type: ,Flushpackets: Off,Flushwait: 0,Ping: 0,Smax: 0,Ttl: 0,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 0
> Node: [2],Name: ,Balancer: ,LBGroup: ,Host: ,Port: ,Type: ,Flushpackets: Off,Flushwait: 0,Ping: 0,Smax: 0,Ttl: 0,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 0
> Node: [3],Name: ,Balancer: ,LBGroup: ,Host: ,Port: ,Type: ,Flushpackets: Off,Flushwait: 0,Ping: 0,Smax: 0,Ttl: 0,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 0
> # ... trimmed lines ...
> Node: [18],Name: ,Balancer: ,LBGroup: ,Host: ,Port: ,Type: ,Flushpackets: Off,Flushwait: 0,Ping: 0,Smax: 0,Ttl: 0,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 0
> Node: [19],Name: ,Balancer: ,LBGroup: ,Host: ,Port: ,Type: ,Flushpackets: Off,Flushwait: 0,Ping: 0,Smax: 0,Ttl: 0,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 0
> Vhost: [0:0:1], Alias:
> Vhost: [0:0:2], Alias:
> Vhost: [0:0:3], Alias:
> # ... trimmed lines ...
> Vhost: [0:0:19], Alias:
> Vhost: [0:0:20], Alias:
> Context: [0:0:1], Context: , Status: REMOVED
> Context: [0:0:2], Context: , Status: REMOVED
> Context: [0:0:3], Context: , Status: REMOVED
> # ... trimmed lines ...
> Context: [0:0:97], Context: , Status: REMOVED
> Context: [0:0:98], Context: , Status: REMOVED
> Context: [0:0:99], Context: , Status: REMOVED
> Context: [0:0:1], Context: , Status: REMOVED
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPResponseParser.parseInfoResponse(DefaultMCMPResponseParser.java:96)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:396)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:365)
> at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:457)
> at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:252)
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
> at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
> at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1374)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1546)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1524)
> at java.lang.Thread.run(Thread.java:745)
> Feb 01, 2017 11:35:05 AM org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler sendRequest
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months