January 2016 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-353) SocketTimeoutException in DefaultMCMPHandler when using httpd 2.4.x

by Micheal Delson Nadar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-353?page=com.atlassian.jira.pl... ] Micheal Delson Nadar commented on MODCLUSTER-353: ------------------------------------------------- We too have the same issue configuring Jboss 7.1.1 and Apache httpd 2.4.12 with mod_cluster/1.3.1.Final (mod so files build from source) error seen in Jboss server log ============ 18:29:08,415 INFO [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) IO error sending command CONFIG to proxy server01/1.1.1.1:6666: java.net.SocketTimeoutException: Read timed out ============ The code fix provided in below link is already merged in mod_cluster/1.3.1.Final, but still issue remains https://developer.jboss.org/thread/231375?start=15&tstart=0 > SocketTimeoutException in DefaultMCMPHandler when using httpd 2.4.x > ------------------------------------------------------------------- > > Key: MODCLUSTER-353 > URL: https://issues.jboss.org/browse/MODCLUSTER-353 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.1.Final > Environment: httpd-2.4.6 and mod_cluster-1.2.1.Final and above > Reporter: Marco Danti > Assignee: Jean-Frederic Clere > Attachments: screenshot-1.png > > > After upgrading a web server from Apache 2.2.x (with mod_cluster 1.2.0) to Apache 2.4.6 (with mod_cluster 1.2.1.Final), when I bring up JBoss (7.2.0.Final) I start seeing repeated errors like the following: > > 14:45:36,777 INFO [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) IO error sending command CONFIG to proxy stw-1.priv.softeco.it/172.16.0.133:6666: java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) [rt.jar:1.7.0_21] > at java.net.SocketInputStream.read(SocketInputStream.java:150) [rt.jar:1.7.0_21] > at java.net.SocketInputStream.read(SocketInputStream.java:121) [rt.jar:1.7.0_21] > at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283) [rt.jar:1.7.0_21] > at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325) [rt.jar:1.7.0_21] > at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177) [rt.jar:1.7.0_21] > at java.io.InputStreamReader.read(InputStreamReader.java:184) [rt.jar:1.7.0_21] > at java.io.BufferedReader.fill(BufferedReader.java:154) [rt.jar:1.7.0_21] > at java.io.BufferedReader.readLine(BufferedReader.java:317) [rt.jar:1.7.0_21] > at java.io.BufferedReader.readLine(BufferedReader.java:382) [rt.jar:1.7.0_21] > at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.sendRequest(DefaultMCMPHandler.java:670) > at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.sendRequests(DefaultMCMPHandler.java:437) > at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:385) > at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:349) > at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:468) > at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:244) > at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.2.0.Final.jar:7.2.0.Final] > at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1323) [jbossweb-7.2.0.Final.jar:7.2.0.Final] > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1588) [jbossweb-7.2.0.Final.jar:7.2.0.Final] > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1574) [jbossweb-7.2.0.Final.jar:7.2.0.Final] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-318) Make connector address user configurable

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-318?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-318: -------------------------------------- Component/s: Core & Container Integration (Java) > Make connector address user configurable > ---------------------------------------- > > Key: MODCLUSTER-318 > URL: https://issues.jboss.org/browse/MODCLUSTER-318 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Affects Versions: 1.2.1.Final > Reporter: Aleksandar Kostadinov > Assignee: Radoslav Husar > > MODCLUSTER-168 introduced a change that broke some existing working configurations relying on using IP instead of a hostname. Also it is likely to be the cause of MODCLUSTER-91. > To have everybody happy, this needs to be made configurable, perhaps a system property that user can set to force a particular IP or hostname. It would also be very useful if there is a special value that makes the behavior same as before the changes in MODCLUSTER-168. For example setting the value to -1 would return the original behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-318) Make connector address user configurable

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-318?page=com.atlassian.jira.pl... ] Work on MODCLUSTER-318 started by Radoslav Husar. ------------------------------------------------- > Make connector address user configurable > ---------------------------------------- > > Key: MODCLUSTER-318 > URL: https://issues.jboss.org/browse/MODCLUSTER-318 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.1.Final > Reporter: Aleksandar Kostadinov > Assignee: Radoslav Husar > > MODCLUSTER-168 introduced a change that broke some existing working configurations relying on using IP instead of a hostname. Also it is likely to be the cause of MODCLUSTER-91. > To have everybody happy, this needs to be made configurable, perhaps a system property that user can set to force a particular IP or hostname. It would also be very useful if there is a special value that makes the behavior same as before the changes in MODCLUSTER-168. For example setting the value to -1 would return the original behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-318) Make connector address user configurable

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-318?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-318: ------------------------------------------- {quote}Also it is likely to be the cause of MODCLUSTER-91.{quote} I don' think so, MODCLUSTER-91 is about adding extra logic to infer the actual address if any local address was used for binding, also the issue is 1 year older than the other fix. {quote}It would also be very useful if there is a special value that makes the behavior same as before the changes in MODCLUSTER-168. For example setting the value to -1 would return the original behavior.{quote} If I am understanding the user request correctly and we do need to add support for overriding the address behind NAT/port-forward/container/etc, we shouldn't need to add the support to fiddle with the host resolution. > Make connector address user configurable > ---------------------------------------- > > Key: MODCLUSTER-318 > URL: https://issues.jboss.org/browse/MODCLUSTER-318 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.1.Final > Reporter: Aleksandar Kostadinov > Assignee: Radoslav Husar > > MODCLUSTER-168 introduced a change that broke some existing working configurations relying on using IP instead of a hostname. Also it is likely to be the cause of MODCLUSTER-91. > To have everybody happy, this needs to be made configurable, perhaps a system property that user can set to force a particular IP or hostname. It would also be very useful if there is a special value that makes the behavior same as before the changes in MODCLUSTER-168. For example setting the value to -1 would return the original behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-318) Make connector address user configurable

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-318?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-318: ------------------------------------------- {quote}perhaps.. if httpd and jboss are separate machines {quote} Well, in that case -- when they are on the same machine -- you wouldn't need workarounds since they would be able to connect virtually on any address. > Make connector address user configurable > ---------------------------------------- > > Key: MODCLUSTER-318 > URL: https://issues.jboss.org/browse/MODCLUSTER-318 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.1.Final > Reporter: Aleksandar Kostadinov > Assignee: Radoslav Husar > > MODCLUSTER-168 introduced a change that broke some existing working configurations relying on using IP instead of a hostname. Also it is likely to be the cause of MODCLUSTER-91. > To have everybody happy, this needs to be made configurable, perhaps a system property that user can set to force a particular IP or hostname. It would also be very useful if there is a special value that makes the behavior same as before the changes in MODCLUSTER-168. For example setting the value to -1 would return the original behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-318) Make connector address user configurable

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-318?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-318: ------------------------------------------- The change that added the {{org.jboss.modcluster.USE_HOST_NAME}} property (b162059a03342464e04c7baed67ff997900b525b) is only in the 1.0 CP stream. Bringing that back could resolve the 2nd concern in the issue, but doesn't solve the "NAT problem" without workarounds. > Make connector address user configurable > ---------------------------------------- > > Key: MODCLUSTER-318 > URL: https://issues.jboss.org/browse/MODCLUSTER-318 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.1.Final > Reporter: Aleksandar Kostadinov > Assignee: Radoslav Husar > > MODCLUSTER-168 introduced a change that broke some existing working configurations relying on using IP instead of a hostname. Also it is likely to be the cause of MODCLUSTER-91. > To have everybody happy, this needs to be made configurable, perhaps a system property that user can set to force a particular IP or hostname. It would also be very useful if there is a special value that makes the behavior same as before the changes in MODCLUSTER-168. For example setting the value to -1 would return the original behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl... ] Radoslav Husar closed MODCLUSTER-168. ------------------------------------- Resolution: Done > mod_cluster should use hostname provided in address instead a IP address > ------------------------------------------------------------------------ > > Key: MODCLUSTER-168 > URL: https://issues.jboss.org/browse/MODCLUSTER-168 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.1.0.CR3 > Environment: any > Reporter: Jean-Frederic Clere > Assignee: Paul Ferraro > Fix For: 1.3.2.Alpha1, 1.2.12.Final, 1.1.0.Final > > > The CONFIG message contains something like: > JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp > Even if the Connector is defined like: > <Connector port="8009" address= "jfcpc" protocol="AJP/1.3" redirectPort="8443" /> > There are 2 ways to fix: > - Use the String (Change the Connector.java in mod_cluster). > - Use parameters.put("Host", connector.getAddress().getHostName()); when building the CONFIG message. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl... ] Radoslav Husar reassigned MODCLUSTER-168: ----------------------------------------- Assignee: Paul Ferraro (was: Radoslav Husar) The commit for this is 947f42165f575c048855468b7a40ba28921ee174 and its in all branches. The change that added the {{org.jboss.modcluster.USE_HOST_NAME}} with hash b162059a03342464e04c7baed67ff997900b525b is only in the 1.0 CP stream, issue for bringing this back is MODCLUSTER-318. > mod_cluster should use hostname provided in address instead a IP address > ------------------------------------------------------------------------ > > Key: MODCLUSTER-168 > URL: https://issues.jboss.org/browse/MODCLUSTER-168 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.1.0.CR3 > Environment: any > Reporter: Jean-Frederic Clere > Assignee: Paul Ferraro > Fix For: 1.1.0.Final, 1.3.2.Alpha1, 1.2.12.Final > > > The CONFIG message contains something like: > JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp > Even if the Connector is defined like: > <Connector port="8009" address= "jfcpc" protocol="AJP/1.3" redirectPort="8443" /> > There are 2 ways to fix: > - Use the String (Change the Connector.java in mod_cluster). > - Use parameters.put("Host", connector.getAddress().getHostName()); when building the CONFIG message. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-168: -------------------------------------- Fix Version/s: 1.1.0.Final > mod_cluster should use hostname provided in address instead a IP address > ------------------------------------------------------------------------ > > Key: MODCLUSTER-168 > URL: https://issues.jboss.org/browse/MODCLUSTER-168 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.1.0.CR3 > Environment: any > Reporter: Jean-Frederic Clere > Assignee: Radoslav Husar > Fix For: 1.1.0.Final, 1.3.2.Alpha1, 1.2.12.Final > > > The CONFIG message contains something like: > JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp > Even if the Connector is defined like: > <Connector port="8009" address= "jfcpc" protocol="AJP/1.3" redirectPort="8443" /> > There are 2 ways to fix: > - Use the String (Change the Connector.java in mod_cluster). > - Use parameters.put("Host", connector.getAddress().getHostName()); when building the CONFIG message. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-318) Make connector address user configurable

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-318?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-318: -------------------------------------- Summary: Make connector address user configurable (was: make connector address user configurable) > Make connector address user configurable > ---------------------------------------- > > Key: MODCLUSTER-318 > URL: https://issues.jboss.org/browse/MODCLUSTER-318 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.1.Final > Reporter: Aleksandar Kostadinov > Assignee: Radoslav Husar > > MODCLUSTER-168 introduced a change that broke some existing working configurations relying on using IP instead of a hostname. Also it is likely to be the cause of MODCLUSTER-91. > To have everybody happy, this needs to be made configurable, perhaps a system property that user can set to force a particular IP or hostname. It would also be very useful if there is a special value that makes the behavior same as before the changes in MODCLUSTER-168. For example setting the value to -1 would return the original behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues January 2016