1 2 Previous Next 18 Replies Latest reply on Aug 26, 2013 5:03 PM by marcodanti

    JBoss errors after moving to Apache 2.4 and mod_cluster 1.2.1.Final

    marcodanti Newbie

      Hi,

      I upgraded my 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), all rebuilt from source.

      Now, 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]

       

      Also, in the apache log, I see repeated lines saying

       

      [Thu Aug 08 14:44:31.181344 2013] [reqtimeout:info] [pid 13299:tid 3037055856] [client 172.16.0.134:45003] AH01382: Request body read timeout

      [Thu Aug 08 14:45:16.696012 2013] [reqtimeout:info] [pid 13300:tid 3028663152] [client 172.16.0.133:39157] AH01382: Request body read timeout

      [Thu Aug 08 14:45:33.076438 2013] [:error] [pid 13300:tid 3020270448] proxy: CLUSTER: (balancer://mycluster). All workers are in error state

       

      Also, the mod_cluster-manager status page is not working properly as before (sometimes it shows some information, sometimes nothing).

       

      None of this was happening with the old apache-2.2 & mod_cluster 1.2.0. Any suggestions?

       

      Thanks,

      Marco

        1 2 Previous Next