[JBoss JIRA] (MODCLUSTER-335) Regression in ProxyPass integration
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-335?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on MODCLUSTER-335:
----------------------------------------------------
Weinan Li <weli(a)redhat.com> changed the Status of [bug 960246|https://bugzilla.redhat.com/show_bug.cgi?id=960246] from NEW to ON_QA
> Regression in ProxyPass integration
> -----------------------------------
>
> Key: MODCLUSTER-335
> URL: https://issues.jboss.org/browse/MODCLUSTER-335
> Project: mod_cluster
> Issue Type: Feature Request
> Affects Versions: 1.2.4.Final
> Environment: RHEL6 x86_64, the rest is to be confirmed...
> Reporter: Michal Babacek
> Assignee: Jean-Frederic Clere
> Fix For: 1.2.5.Final
>
> Attachments: logs-and-configs-m_c-1.2.3.zip, logs-and-configs-m_c-1.2.4.zip, test-run-modProxyOnlyPartOfUrlSpaceTest-mod_cluster-1.2.3.log, test-run-modProxyOnlyPartOfUrlSpaceTest-mod_cluster-1.2.4.log
>
>
> This configuration & test worked just fine with 1.2.3.Final and it is broken in 1.2.4.Final, so we have a *regression* here, I guess.
> {code}
> ProxyPassMatch ^/app/static/ !
> ProxyPass /app balancer://qacluster stickysession=JSESSIONID|jsessionid nofailover=on
> ProxyPass / !
> ProxyPassReverse /app balancer://qacluster
> ProxyPassReverseCookieDomain / /app/
> ProxyPassReverseCookiePath / /app/
> ProxyPreserveHost on
> {code}
> Accessing e.g. {{/app/clusterbench/requestinfo/}} returns HTTP 503. *requestinfo* comes from the famous [CommonRequestInfoServlet.java|https://github.com/Karm/clusterbench/blob/s...].
> h3. mod_cluster 1.2.3 ProxyPass test:
> *Failed tests*
> * modProxyOnlyPartOfUrlSpaceTest: Known fail: [JBQA-7899] Assert #10 Session ID must always be the same.
> * modProxyWithoutSessionId: Assert #1, fail, known as [MODCLUSTER-334], http://10.16.45.160:2080/clusterbench/requestinfo/ should have been available...
> h3. mod_cluster 1.2.4 ProxyPass test:
> *Failed tests*
> * modProxyOnlyPartOfUrlSpaceTest: Assert #1, fail, http://10.16.45.160:2080/app/clusterbench/requestinfo/ should have been available...
> * modProxyWithoutSessionId: Assert #1, fail, known as [MODCLUSTER-334], http://10.16.45.160:2080/clusterbench/requestinfo/ should have been available...
> What the test does is it accesses various URLs, getting either static content from httpd or a dynamic one from application server.
> Browse the attached files for complete configs, debug logs and test results. Ping me, if the zipped file structure does not make sense to you...
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (MODCLUSTER-407) worker-timeout can cause httpd thread stalls
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-407?page=com.atlassian.jira.pl... ]
Michal Babacek commented on MODCLUSTER-407:
-------------------------------------------
This is awesome :) THX.
> worker-timeout can cause httpd thread stalls
> --------------------------------------------
>
> Key: MODCLUSTER-407
> URL: https://issues.jboss.org/browse/MODCLUSTER-407
> Project: mod_cluster
> Issue Type: Bug
> Affects Versions: 1.2.8.Final
> Reporter: Aaron Ogburn
> Assignee: Jean-Frederic Clere
> Fix For: 1.3.1.Final, 1.2.9.Final
>
>
> Setting a modcluster worker-timeout can stall requests and threads on the httpd side when the requests are received with workers in a down state. A stack of the problem thread looks like the following (recursive loops through mod_proxy_cluster from #160 to #2):
> #0 0x00007ff8eb547533 in select () from /lib64/libc.so.6
> #1 0x00007ff8eba39185 in apr_sleep () from /usr/lib64/libapr-1.so.0
> #2 0x00007ff8e84be0d1 in ?? () from /etc/httpd/modules/mod_proxy_cluster.so
> ...
> #160 0x00007ff8e84beb9f in ?? () from /etc/httpd/modules/mod_proxy_cluster.so
> #161 0x00007ff8e88d2116 in proxy_run_pre_request () from /etc/httpd/modules/mod_proxy.so
> #162 0x00007ff8e88d9186 in ap_proxy_pre_request () from /etc/httpd/modules/mod_proxy.so
> #163 0x00007ff8e88d63c2 in ?? () from /etc/httpd/modules/mod_proxy.so
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (MODCLUSTER-411) java.lang.NoSuchFieldError: SESSION_COOKIE_NAME, Tomcat7
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-411?page=com.atlassian.jira.pl... ]
Michal Babacek commented on MODCLUSTER-411:
-------------------------------------------
Hmm, it's actually most likely Tomcat6/7 mod_cluster libraries mismatch, see: [BZ 1102012|https://bugzilla.redhat.com/show_bug.cgi?id=1102014].
> java.lang.NoSuchFieldError: SESSION_COOKIE_NAME, Tomcat7
> --------------------------------------------------------
>
> Key: MODCLUSTER-411
> URL: https://issues.jboss.org/browse/MODCLUSTER-411
> Project: mod_cluster
> Issue Type: Bug
> Affects Versions: 1.2.8.Final
> Environment: oracle JDK 1.7, Tomcat 7, Windows, Apache Tomcat Native library 1.1.30 using APR version 1.4.8
> Reporter: Michal Babacek
> Assignee: Jean-Frederic Clere
> Fix For: 1.2.9.Final
>
>
> mod_cluster in Tomcat 7 on Windows fails to register with Apache HTTP Server:
> {code}
> May 28, 2014 10:52:03 AM org.apache.catalina.core.AprLifecycleListener init
> INFO: Loaded APR based Apache Tomcat Native library 1.1.30 using APR version 1.4.8.
> May 28, 2014 10:52:03 AM org.apache.catalina.core.AprLifecycleListener init
> INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
> May 28, 2014 10:52:03 AM org.apache.catalina.core.AprLifecycleListener initializeSSL
> INFO: OpenSSL successfully initialized (OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008)
> May 28, 2014 10:52:04 AM org.apache.coyote.AbstractProtocol init
> INFO: Initializing ProtocolHandler ["http-apr-192.168.122.24-8080"]
> May 28, 2014 10:52:04 AM org.apache.coyote.AbstractProtocol init
> INFO: Initializing ProtocolHandler ["ajp-apr-192.168.122.24-8009"]
> May 28, 2014 10:52:04 AM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 1892 ms
> May 28, 2014 10:52:04 AM org.jboss.modcluster.ModClusterService init
> INFO: MODCLUSTER000001: Initializing mod_cluster version ${project.version}
> May 28, 2014 10:52:04 AM org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl start
> INFO: MODCLUSTER000032: Listening to proxy advertisements on /224.0.7.222:43294
> May 28, 2014 10:52:04 AM org.apache.catalina.core.StandardService startInternal
> INFO: Starting service Catalina
> May 28, 2014 10:52:04 AM org.apache.catalina.core.StandardEngine startInternal
> INFO: Starting Servlet Engine: Apache Tomcat/7.0.52
> May 28, 2014 10:52:04 AM org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive C:\Program Files\jboss-ews-2.1\share\tomcat7\webapps\clusterbench.war
> May 28, 2014 10:52:06 AM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory C:\Program Files\jboss-ews-2.1\share\tomcat7\webapps\docs
> May 28, 2014 10:52:06 AM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory C:\Program Files\jboss-ews-2.1\share\tomcat7\webapps\examples
> May 28, 2014 10:52:06 AM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory C:\Program Files\jboss-ews-2.1\share\tomcat7\webapps\host-manager
> May 28, 2014 10:52:07 AM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory C:\Program Files\jboss-ews-2.1\share\tomcat7\webapps\manager
> May 28, 2014 10:52:07 AM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory C:\Program Files\jboss-ews-2.1\share\tomcat7\webapps\ROOT
> May 28, 2014 10:52:07 AM org.apache.coyote.AbstractProtocol start
> INFO: Starting ProtocolHandler ["http-apr-192.168.122.24-8080"]
> May 28, 2014 10:52:08 AM org.apache.coyote.AbstractProtocol start
> INFO: Starting ProtocolHandler ["ajp-apr-192.168.122.24-8009"]
> May 28, 2014 10:52:08 AM org.apache.catalina.startup.Catalina start
> INFO: Server startup in 3876 ms
> May 28, 2014 10:52:18 AM org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildren
> SEVERE: Exception invoking periodic operation:
> java.lang.NoSuchFieldError: SESSION_COOKIE_NAME
> at org.jboss.modcluster.container.jbossweb.JBossWebEngine.getSessionCookieName(JBossWebEngine.java:43)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPRequestFactory.createConfigRequest(DefaultMCMPRequestFactory.java:127)
> at org.jboss.modcluster.mcmp.impl.ResetRequestSourceImpl.getResetRequests(ResetRequestSourceImpl.java:89)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:384)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:350)
> at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:458)
> at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:249)
> 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:1530)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1519)
> at java.lang.Thread.run(Thread.java:745)
> May 28, 2014 10:52:28 AM org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildren
> SEVERE: Exception invoking periodic operation:
> java.lang.NoSuchMethodError: org.apache.catalina.connector.Connector.isAvailable()Z
> at org.jboss.modcluster.container.jbossweb.JBossWebConnector.isAvailable(JBossWebConnector.java:39)
> at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:464)
> at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:249)
> 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:1530)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1519)
> at java.lang.Thread.run(Thread.java:745)
> +++
> repeats...
> {code}
> On the Apache HTTP Server side, it looks very weird, because there is an INFO message from Tomcat 7, but no CONFIG...
> {code}
> [notice] Apache/2.2.26 (Win64) DAV/2 mod_cluster/1.2.8.Final configured -- resuming normal operations
> [notice] Server built: May 13 2014 08:51:33
> [notice] Parent: Created child process 3432
> [debug] mpm_winnt.c(477): Parent: Sent the scoreboard to the child
> [debug] util_ldap.c(1990): LDAP merging Shared Cache conf: shm=0x6833e0 rmm=0x683438 for VHOST: WIN-NKI15SIE9RC
> [info] APR LDAP: Built with Microsoft Corporation. LDAP SDK
> [info] LDAP: SSL support unavailable: LDAP: CA certificates cannot be set using this method, as they are stored in the registry instead.
> [notice] Digest: generating secret for digest authentication ...
> [notice] Digest: done
> [debug] mod_advertise.c(589): [3432 - 3460] in child post config hook
> [notice] Child 3432: Child process is running
> [debug] mpm_winnt.c(398): Child 3432: Retrieved our scoreboard from the parent.
> [info] Parent: Duplicating socket 268 and sending it to child process 3432
> [info] Parent: Duplicating socket 260 and sending it to child process 3432
> [debug] mpm_winnt.c(595): Parent: Sent 2 listeners to child 3432
> [debug] mpm_winnt.c(554): Child 3432: retrieved 2 listeners from parent
> [debug] proxy_util.c(1825): proxy: grabbed scoreboard slot 0 in child 3432 for worker proxy:reverse
> [debug] proxy_util.c(1921): proxy: initialized worker 0 in child 3432 for (*) min=0 max=150 smax=150
> [notice] Child 3432: Acquired the start mutex.
> [notice] Child 3432: Starting 150 worker threads.
> [notice] Child 3432: Starting thread to listen on port 2181.
> [notice] Child 3432: Starting thread to listen on port 8847.
> [debug] mod_manager.c(1901): manager_trans INFO (/)
> [debug] mod_manager.c(2617): manager_handler INFO (C:/) processing: ""
> [debug] mod_manager.c(2666): manager_handler INFO OK
> [debug] mod_manager.c(1901): manager_trans INFO (/)
> [debug] mod_manager.c(2617): manager_handler INFO (C:/) processing: ""
> [debug] mod_manager.c(2666): manager_handler INFO OK
> --end of the log, no more relevant messages--
> {code}
> Tomcat 7 configuration:
> {code}
> <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener"
> loadMetricClass="org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric"
> loadMetricCapacity="1"
> loadHistory="9"
> loadDecayFactor="2"
> stickySession="true"
> stickySessionForce="false"
> stickySessionRemove="true"
> advertise="true"
> advertiseGroupAddress="224.0.7.222"
> advertisePort="43294" />
> {code}
> Nothing suspicious in the Apache HTTP Server mod_cluster config:
> {code}
> MemManagerFile "C:\Program Files\jboss-ews-2.1\var\cache\mod_cluster"
> ServerName WIN-NKI15SIE9RC:2181
> <IfModule manager_module>
> Listen 192.168.122.24:8847
> LogLevel debug
> <VirtualHost 192.168.122.24:8847>
> ServerName WIN-NKI15SIE9RC:8847
> <Directory />
> Order deny,allow
> Deny from all
> Allow from all
> </Directory>
> KeepAliveTimeout 60
> MaxKeepAliveRequests 0
> ServerAdvertise on
> AdvertiseFrequency 5
> ManagerBalancerName qacluster
> AdvertiseGroup 224.0.7.222:43294
> EnableMCPMReceive
> <Location /mcm>
> SetHandler mod_cluster-manager
> Order deny,allow
> Deny from all
> Allow from all
> </Location>
> </VirtualHost>
> </IfModule>
> {code}
> I'm unable to hit it on RHEL.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (MODCLUSTER-412) java.lang.NoSuchMethodError: org.apache.catalina.Context.isStarted()Z, Tomcat6, Windows
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-412?page=com.atlassian.jira.pl... ]
Michal Babacek commented on MODCLUSTER-412:
-------------------------------------------
Hmm, it's actually most likely Tomcat6/7 mod_cluster libraries mismatch, see: [BZ 1102012|https://bugzilla.redhat.com/show_bug.cgi?id=1102014].
> java.lang.NoSuchMethodError: org.apache.catalina.Context.isStarted()Z, Tomcat6, Windows
> ---------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-412
> URL: https://issues.jboss.org/browse/MODCLUSTER-412
> Project: mod_cluster
> Issue Type: Bug
> Affects Versions: 1.2.8.Final
> Environment: Oracle JDK 1.7, Windows, Tomcat6, Apache Tomcat Native library 1.1.30 using APR version 1.4.8.
> Reporter: Michal Babacek
> Assignee: Jean-Frederic Clere
> Fix For: 1.2.9.Final
>
>
> mod_cluster with Tomcat 6 on Windows fails on initialization in this weird fashion:
> {code}
> INFO: Loaded APR based Apache Tomcat Native library 1.1.30 using APR version 1.4.8.
> May 28, 2014 12:12:40 PM org.apache.catalina.core.AprLifecycleListener init
> INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
> May 28, 2014 12:12:41 PM org.apache.catalina.core.AprLifecycleListener initializeSSL
> INFO: OpenSSL successfully initialized with version OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
> May 28, 2014 12:12:41 PM org.jboss.modcluster.ModClusterService init
> INFO: MODCLUSTER000001: Initializing mod_cluster version ${project.version}
> May 28, 2014 12:12:41 PM org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl start
> INFO: MODCLUSTER000032: Listening to proxy advertisements on /224.0.7.222:43294
> May 28, 2014 12:12:41 PM org.apache.coyote.http11.Http11AprProtocol init
> INFO: Initializing Coyote HTTP/1.1 on http-192.168.122.24-8080
> May 28, 2014 12:12:41 PM org.apache.coyote.ajp.AjpAprProtocol init
> INFO: Initializing Coyote AJP/1.3 on ajp-192.168.122.24-8009
> May 28, 2014 12:12:41 PM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 1928 ms
> May 28, 2014 12:12:41 PM org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> May 28, 2014 12:12:41 PM org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/6.0.39
> May 28, 2014 12:12:41 PM org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive clusterbench.war
> May 28, 2014 12:12:42 PM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory docs
> May 28, 2014 12:12:43 PM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory examples
> May 28, 2014 12:12:43 PM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory host-manager
> May 28, 2014 12:12:43 PM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory manager
> May 28, 2014 12:12:43 PM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory ROOT
> May 28, 2014 12:12:43 PM org.apache.coyote.http11.Http11AprProtocol start
> INFO: Starting Coyote HTTP/1.1 on http-192.168.122.24-8080
> May 28, 2014 12:12:44 PM org.apache.coyote.ajp.AjpAprProtocol start
> INFO: Starting Coyote AJP/1.3 on ajp-192.168.122.24-8009
> May 28, 2014 12:12:44 PM org.apache.catalina.startup.Catalina start
> INFO: Server startup in 2395 ms
> May 28, 2014 12:12:54 PM org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildren
> SEVERE: Exception invoking periodic operation:
> java.lang.NoSuchMethodError: org.apache.catalina.Context.isStarted()Z
> at org.jboss.modcluster.container.jbossweb.JBossWebContext.isStarted(JBossWebContext.java:60)
> at org.jboss.modcluster.mcmp.impl.ResetRequestSourceImpl.getResetRequests(ResetRequestSourceImpl.java:135)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:384)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:350)
> at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:458)
> at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:249)
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
> at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1389)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1653)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1642)
> at java.lang.Thread.run(Thread.java:745)
> May 28, 2014 12:13:04 PM org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler sendRequest
> ERROR: MODCLUSTER000042: Error MEM sending STATUS command to WIN-NKI15SIE9RC/192.168.122.24:8847, configuration will be reset: MEM: Can't read node
> May 28, 2014 12:13:14 PM org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildren
> SEVERE: Exception invoking periodic operation:
> java.lang.NoSuchMethodError: org.apache.catalina.Context.isStarted()Z
> at org.jboss.modcluster.container.jbossweb.JBossWebContext.isStarted(JBossWebContext.java:60)
> at org.jboss.modcluster.mcmp.impl.ResetRequestSourceImpl.getResetRequests(ResetRequestSourceImpl.java:135)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:384)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:350)
> at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:458)
> at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:249)
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
> at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1389)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1653)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1642)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> with the configuration being:
> {code}
> <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener" loadMetricClass="org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric"
> loadMetricCapacity="1" loadHistory="9" loadDecayFactor="2" stickySession="true" stickySessionForce="false"
> stickySessionRemove="true" advertise="true"
> advertiseGroupAddress="224.0.7.222" advertisePort="43294" />
> {code}
> According to Apache HTTP Server log, the Tomcat is trying to register itself, but it does not offer any contexts:
> {code}
> [notice] Apache/2.2.26 (Win64) DAV/2 mod_cluster/1.2.8.Final configured -- resuming normal operations
> [notice] Server built: May 13 2014 08:51:33
> [notice] Parent: Created child process 2140
> [debug] mpm_winnt.c(477): Parent: Sent the scoreboard to the child
> [debug] util_ldap.c(1990): LDAP merging Shared Cache conf: shm=0x6733e0 rmm=0x673438 for VHOST: WIN-NKI15SIE9RC
> [info] APR LDAP: Built with Microsoft Corporation. LDAP SDK
> [info] LDAP: SSL support unavailable: LDAP: CA certificates cannot be set using this method, as they are stored in the registry instead.
> [notice] Digest: generating secret for digest authentication ...
> [notice] Digest: done
> [debug] mod_advertise.c(589): [2140 - 3024] in child post config hook
> [notice] Child 2140: Child process is running
> [debug] mpm_winnt.c(398): Child 2140: Retrieved our scoreboard from the parent.
> [info] Parent: Duplicating socket 268 and sending it to child process 2140
> [info] Parent: Duplicating socket 260 and sending it to child process 2140
> [debug] mpm_winnt.c(595): Parent: Sent 2 listeners to child 2140
> [debug] mpm_winnt.c(554): Child 2140: retrieved 2 listeners from parent
> [debug] proxy_util.c(1825): proxy: grabbed scoreboard slot 0 in child 2140 for worker proxy:reverse
> [debug] proxy_util.c(1921): proxy: initialized worker 0 in child 2140 for (*) min=0 max=150 smax=150
> [notice] Child 2140: Acquired the start mutex.
> [notice] Child 2140: Starting 150 worker threads.
> [notice] Child 2140: Starting thread to listen on port 8847.
> [notice] Child 2140: Starting thread to listen on port 2181.
> [debug] mod_manager.c(1901): manager_trans INFO (/)
> [debug] mod_manager.c(2617): manager_handler INFO (C:/) processing: ""
> [debug] mod_manager.c(2666): manager_handler INFO OK
> [debug] mod_manager.c(1901): manager_trans INFO (/)
> [debug] mod_manager.c(2617): manager_handler INFO (C:/) processing: ""
> [debug] mod_manager.c(2666): manager_handler INFO OK
> [debug] mod_manager.c(1901): manager_trans STATUS (/)
> [debug] mod_manager.c(2617): manager_handler STATUS (C:/) processing: "JVMRoute=tomcat-6-1&Load=100"
> [debug] mod_manager.c(1616): Processing STATUS
> [warn] manager_handler STATUS error: MEM: Can't read node
> [debug] mod_manager.c(1901): manager_trans STATUS (/)
> [debug] mod_manager.c(2617): manager_handler STATUS (C:/) processing: "JVMRoute=tomcat-6-2&Load=100"
> [debug] mod_manager.c(1616): Processing STATUS
> [warn] manager_handler STATUS error: MEM: Can't read node
> [debug] mod_manager.c(1901): manager_trans INFO (/)
> [debug] mod_manager.c(2617): manager_handler INFO (C:/) processing: ""
> [debug] mod_manager.c(2666): manager_handler INFO OK
> [debug] mod_manager.c(1901): manager_trans INFO (/)
> [debug] mod_manager.c(2617): manager_handler INFO (C:/) processing: ""
> [debug] mod_manager.c(2666): manager_handler INFO OK
> [debug] mod_manager.c(1901): manager_trans STATUS (/)
> [debug] mod_manager.c(2617): manager_handler STATUS (C:/) processing: "JVMRoute=tomcat-6-1&Load=100"
> [debug] mod_manager.c(1616): Processing STATUS
> [warn] manager_handler STATUS error: MEM: Can't read node
> --repeats--
> {code}
> I can't hit this on RHEL.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (MODCLUSTER-412) java.lang.NoSuchMethodError: org.apache.catalina.Context.isStarted()Z, Tomcat6, Windows
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-412?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration updated MODCLUSTER-412:
-----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1102012
> java.lang.NoSuchMethodError: org.apache.catalina.Context.isStarted()Z, Tomcat6, Windows
> ---------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-412
> URL: https://issues.jboss.org/browse/MODCLUSTER-412
> Project: mod_cluster
> Issue Type: Bug
> Affects Versions: 1.2.8.Final
> Environment: Oracle JDK 1.7, Windows, Tomcat6, Apache Tomcat Native library 1.1.30 using APR version 1.4.8.
> Reporter: Michal Babacek
> Assignee: Jean-Frederic Clere
> Fix For: 1.2.9.Final
>
>
> mod_cluster with Tomcat 6 on Windows fails on initialization in this weird fashion:
> {code}
> INFO: Loaded APR based Apache Tomcat Native library 1.1.30 using APR version 1.4.8.
> May 28, 2014 12:12:40 PM org.apache.catalina.core.AprLifecycleListener init
> INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
> May 28, 2014 12:12:41 PM org.apache.catalina.core.AprLifecycleListener initializeSSL
> INFO: OpenSSL successfully initialized with version OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
> May 28, 2014 12:12:41 PM org.jboss.modcluster.ModClusterService init
> INFO: MODCLUSTER000001: Initializing mod_cluster version ${project.version}
> May 28, 2014 12:12:41 PM org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl start
> INFO: MODCLUSTER000032: Listening to proxy advertisements on /224.0.7.222:43294
> May 28, 2014 12:12:41 PM org.apache.coyote.http11.Http11AprProtocol init
> INFO: Initializing Coyote HTTP/1.1 on http-192.168.122.24-8080
> May 28, 2014 12:12:41 PM org.apache.coyote.ajp.AjpAprProtocol init
> INFO: Initializing Coyote AJP/1.3 on ajp-192.168.122.24-8009
> May 28, 2014 12:12:41 PM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 1928 ms
> May 28, 2014 12:12:41 PM org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> May 28, 2014 12:12:41 PM org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/6.0.39
> May 28, 2014 12:12:41 PM org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive clusterbench.war
> May 28, 2014 12:12:42 PM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory docs
> May 28, 2014 12:12:43 PM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory examples
> May 28, 2014 12:12:43 PM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory host-manager
> May 28, 2014 12:12:43 PM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory manager
> May 28, 2014 12:12:43 PM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory ROOT
> May 28, 2014 12:12:43 PM org.apache.coyote.http11.Http11AprProtocol start
> INFO: Starting Coyote HTTP/1.1 on http-192.168.122.24-8080
> May 28, 2014 12:12:44 PM org.apache.coyote.ajp.AjpAprProtocol start
> INFO: Starting Coyote AJP/1.3 on ajp-192.168.122.24-8009
> May 28, 2014 12:12:44 PM org.apache.catalina.startup.Catalina start
> INFO: Server startup in 2395 ms
> May 28, 2014 12:12:54 PM org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildren
> SEVERE: Exception invoking periodic operation:
> java.lang.NoSuchMethodError: org.apache.catalina.Context.isStarted()Z
> at org.jboss.modcluster.container.jbossweb.JBossWebContext.isStarted(JBossWebContext.java:60)
> at org.jboss.modcluster.mcmp.impl.ResetRequestSourceImpl.getResetRequests(ResetRequestSourceImpl.java:135)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:384)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:350)
> at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:458)
> at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:249)
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
> at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1389)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1653)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1642)
> at java.lang.Thread.run(Thread.java:745)
> May 28, 2014 12:13:04 PM org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler sendRequest
> ERROR: MODCLUSTER000042: Error MEM sending STATUS command to WIN-NKI15SIE9RC/192.168.122.24:8847, configuration will be reset: MEM: Can't read node
> May 28, 2014 12:13:14 PM org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildren
> SEVERE: Exception invoking periodic operation:
> java.lang.NoSuchMethodError: org.apache.catalina.Context.isStarted()Z
> at org.jboss.modcluster.container.jbossweb.JBossWebContext.isStarted(JBossWebContext.java:60)
> at org.jboss.modcluster.mcmp.impl.ResetRequestSourceImpl.getResetRequests(ResetRequestSourceImpl.java:135)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:384)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:350)
> at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:458)
> at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:249)
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
> at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1389)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1653)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1642)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> with the configuration being:
> {code}
> <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener" loadMetricClass="org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric"
> loadMetricCapacity="1" loadHistory="9" loadDecayFactor="2" stickySession="true" stickySessionForce="false"
> stickySessionRemove="true" advertise="true"
> advertiseGroupAddress="224.0.7.222" advertisePort="43294" />
> {code}
> According to Apache HTTP Server log, the Tomcat is trying to register itself, but it does not offer any contexts:
> {code}
> [notice] Apache/2.2.26 (Win64) DAV/2 mod_cluster/1.2.8.Final configured -- resuming normal operations
> [notice] Server built: May 13 2014 08:51:33
> [notice] Parent: Created child process 2140
> [debug] mpm_winnt.c(477): Parent: Sent the scoreboard to the child
> [debug] util_ldap.c(1990): LDAP merging Shared Cache conf: shm=0x6733e0 rmm=0x673438 for VHOST: WIN-NKI15SIE9RC
> [info] APR LDAP: Built with Microsoft Corporation. LDAP SDK
> [info] LDAP: SSL support unavailable: LDAP: CA certificates cannot be set using this method, as they are stored in the registry instead.
> [notice] Digest: generating secret for digest authentication ...
> [notice] Digest: done
> [debug] mod_advertise.c(589): [2140 - 3024] in child post config hook
> [notice] Child 2140: Child process is running
> [debug] mpm_winnt.c(398): Child 2140: Retrieved our scoreboard from the parent.
> [info] Parent: Duplicating socket 268 and sending it to child process 2140
> [info] Parent: Duplicating socket 260 and sending it to child process 2140
> [debug] mpm_winnt.c(595): Parent: Sent 2 listeners to child 2140
> [debug] mpm_winnt.c(554): Child 2140: retrieved 2 listeners from parent
> [debug] proxy_util.c(1825): proxy: grabbed scoreboard slot 0 in child 2140 for worker proxy:reverse
> [debug] proxy_util.c(1921): proxy: initialized worker 0 in child 2140 for (*) min=0 max=150 smax=150
> [notice] Child 2140: Acquired the start mutex.
> [notice] Child 2140: Starting 150 worker threads.
> [notice] Child 2140: Starting thread to listen on port 8847.
> [notice] Child 2140: Starting thread to listen on port 2181.
> [debug] mod_manager.c(1901): manager_trans INFO (/)
> [debug] mod_manager.c(2617): manager_handler INFO (C:/) processing: ""
> [debug] mod_manager.c(2666): manager_handler INFO OK
> [debug] mod_manager.c(1901): manager_trans INFO (/)
> [debug] mod_manager.c(2617): manager_handler INFO (C:/) processing: ""
> [debug] mod_manager.c(2666): manager_handler INFO OK
> [debug] mod_manager.c(1901): manager_trans STATUS (/)
> [debug] mod_manager.c(2617): manager_handler STATUS (C:/) processing: "JVMRoute=tomcat-6-1&Load=100"
> [debug] mod_manager.c(1616): Processing STATUS
> [warn] manager_handler STATUS error: MEM: Can't read node
> [debug] mod_manager.c(1901): manager_trans STATUS (/)
> [debug] mod_manager.c(2617): manager_handler STATUS (C:/) processing: "JVMRoute=tomcat-6-2&Load=100"
> [debug] mod_manager.c(1616): Processing STATUS
> [warn] manager_handler STATUS error: MEM: Can't read node
> [debug] mod_manager.c(1901): manager_trans INFO (/)
> [debug] mod_manager.c(2617): manager_handler INFO (C:/) processing: ""
> [debug] mod_manager.c(2666): manager_handler INFO OK
> [debug] mod_manager.c(1901): manager_trans INFO (/)
> [debug] mod_manager.c(2617): manager_handler INFO (C:/) processing: ""
> [debug] mod_manager.c(2666): manager_handler INFO OK
> [debug] mod_manager.c(1901): manager_trans STATUS (/)
> [debug] mod_manager.c(2617): manager_handler STATUS (C:/) processing: "JVMRoute=tomcat-6-1&Load=100"
> [debug] mod_manager.c(1616): Processing STATUS
> [warn] manager_handler STATUS error: MEM: Can't read node
> --repeats--
> {code}
> I can't hit this on RHEL.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (MODCLUSTER-412) java.lang.NoSuchMethodError: org.apache.catalina.Context.isStarted()Z, Tomcat6, Windows
by Michal Babacek (JIRA)
Michal Babacek created MODCLUSTER-412:
-----------------------------------------
Summary: java.lang.NoSuchMethodError: org.apache.catalina.Context.isStarted()Z, Tomcat6, Windows
Key: MODCLUSTER-412
URL: https://issues.jboss.org/browse/MODCLUSTER-412
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.2.8.Final
Environment: Oracle JDK 1.7, Windows, Tomcat6, Apache Tomcat Native library 1.1.30 using APR version 1.4.8.
Reporter: Michal Babacek
Assignee: Jean-Frederic Clere
Fix For: 1.2.9.Final
mod_cluster with Tomcat 6 on Windows fails on initialization in this weird fashion:
{code}
INFO: Loaded APR based Apache Tomcat Native library 1.1.30 using APR version 1.4.8.
May 28, 2014 12:12:40 PM org.apache.catalina.core.AprLifecycleListener init
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
May 28, 2014 12:12:41 PM org.apache.catalina.core.AprLifecycleListener initializeSSL
INFO: OpenSSL successfully initialized with version OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
May 28, 2014 12:12:41 PM org.jboss.modcluster.ModClusterService init
INFO: MODCLUSTER000001: Initializing mod_cluster version ${project.version}
May 28, 2014 12:12:41 PM org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl start
INFO: MODCLUSTER000032: Listening to proxy advertisements on /224.0.7.222:43294
May 28, 2014 12:12:41 PM org.apache.coyote.http11.Http11AprProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-192.168.122.24-8080
May 28, 2014 12:12:41 PM org.apache.coyote.ajp.AjpAprProtocol init
INFO: Initializing Coyote AJP/1.3 on ajp-192.168.122.24-8009
May 28, 2014 12:12:41 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1928 ms
May 28, 2014 12:12:41 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
May 28, 2014 12:12:41 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.39
May 28, 2014 12:12:41 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive clusterbench.war
May 28, 2014 12:12:42 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory docs
May 28, 2014 12:12:43 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory examples
May 28, 2014 12:12:43 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory host-manager
May 28, 2014 12:12:43 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory manager
May 28, 2014 12:12:43 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory ROOT
May 28, 2014 12:12:43 PM org.apache.coyote.http11.Http11AprProtocol start
INFO: Starting Coyote HTTP/1.1 on http-192.168.122.24-8080
May 28, 2014 12:12:44 PM org.apache.coyote.ajp.AjpAprProtocol start
INFO: Starting Coyote AJP/1.3 on ajp-192.168.122.24-8009
May 28, 2014 12:12:44 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 2395 ms
May 28, 2014 12:12:54 PM org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildren
SEVERE: Exception invoking periodic operation:
java.lang.NoSuchMethodError: org.apache.catalina.Context.isStarted()Z
at org.jboss.modcluster.container.jbossweb.JBossWebContext.isStarted(JBossWebContext.java:60)
at org.jboss.modcluster.mcmp.impl.ResetRequestSourceImpl.getResetRequests(ResetRequestSourceImpl.java:135)
at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:384)
at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:350)
at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:458)
at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:249)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1389)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1653)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1642)
at java.lang.Thread.run(Thread.java:745)
May 28, 2014 12:13:04 PM org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler sendRequest
ERROR: MODCLUSTER000042: Error MEM sending STATUS command to WIN-NKI15SIE9RC/192.168.122.24:8847, configuration will be reset: MEM: Can't read node
May 28, 2014 12:13:14 PM org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildren
SEVERE: Exception invoking periodic operation:
java.lang.NoSuchMethodError: org.apache.catalina.Context.isStarted()Z
at org.jboss.modcluster.container.jbossweb.JBossWebContext.isStarted(JBossWebContext.java:60)
at org.jboss.modcluster.mcmp.impl.ResetRequestSourceImpl.getResetRequests(ResetRequestSourceImpl.java:135)
at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:384)
at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:350)
at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:458)
at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:249)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1389)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1653)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1642)
at java.lang.Thread.run(Thread.java:745)
{code}
with the configuration being:
{code}
<Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener" loadMetricClass="org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric"
loadMetricCapacity="1" loadHistory="9" loadDecayFactor="2" stickySession="true" stickySessionForce="false"
stickySessionRemove="true" advertise="true"
advertiseGroupAddress="224.0.7.222" advertisePort="43294" />
{code}
According to Apache HTTP Server log, the Tomcat is trying to register itself, but it does not offer any contexts:
{code}
[notice] Apache/2.2.26 (Win64) DAV/2 mod_cluster/1.2.8.Final configured -- resuming normal operations
[notice] Server built: May 13 2014 08:51:33
[notice] Parent: Created child process 2140
[debug] mpm_winnt.c(477): Parent: Sent the scoreboard to the child
[debug] util_ldap.c(1990): LDAP merging Shared Cache conf: shm=0x6733e0 rmm=0x673438 for VHOST: WIN-NKI15SIE9RC
[info] APR LDAP: Built with Microsoft Corporation. LDAP SDK
[info] LDAP: SSL support unavailable: LDAP: CA certificates cannot be set using this method, as they are stored in the registry instead.
[notice] Digest: generating secret for digest authentication ...
[notice] Digest: done
[debug] mod_advertise.c(589): [2140 - 3024] in child post config hook
[notice] Child 2140: Child process is running
[debug] mpm_winnt.c(398): Child 2140: Retrieved our scoreboard from the parent.
[info] Parent: Duplicating socket 268 and sending it to child process 2140
[info] Parent: Duplicating socket 260 and sending it to child process 2140
[debug] mpm_winnt.c(595): Parent: Sent 2 listeners to child 2140
[debug] mpm_winnt.c(554): Child 2140: retrieved 2 listeners from parent
[debug] proxy_util.c(1825): proxy: grabbed scoreboard slot 0 in child 2140 for worker proxy:reverse
[debug] proxy_util.c(1921): proxy: initialized worker 0 in child 2140 for (*) min=0 max=150 smax=150
[notice] Child 2140: Acquired the start mutex.
[notice] Child 2140: Starting 150 worker threads.
[notice] Child 2140: Starting thread to listen on port 8847.
[notice] Child 2140: Starting thread to listen on port 2181.
[debug] mod_manager.c(1901): manager_trans INFO (/)
[debug] mod_manager.c(2617): manager_handler INFO (C:/) processing: ""
[debug] mod_manager.c(2666): manager_handler INFO OK
[debug] mod_manager.c(1901): manager_trans INFO (/)
[debug] mod_manager.c(2617): manager_handler INFO (C:/) processing: ""
[debug] mod_manager.c(2666): manager_handler INFO OK
[debug] mod_manager.c(1901): manager_trans STATUS (/)
[debug] mod_manager.c(2617): manager_handler STATUS (C:/) processing: "JVMRoute=tomcat-6-1&Load=100"
[debug] mod_manager.c(1616): Processing STATUS
[warn] manager_handler STATUS error: MEM: Can't read node
[debug] mod_manager.c(1901): manager_trans STATUS (/)
[debug] mod_manager.c(2617): manager_handler STATUS (C:/) processing: "JVMRoute=tomcat-6-2&Load=100"
[debug] mod_manager.c(1616): Processing STATUS
[warn] manager_handler STATUS error: MEM: Can't read node
[debug] mod_manager.c(1901): manager_trans INFO (/)
[debug] mod_manager.c(2617): manager_handler INFO (C:/) processing: ""
[debug] mod_manager.c(2666): manager_handler INFO OK
[debug] mod_manager.c(1901): manager_trans INFO (/)
[debug] mod_manager.c(2617): manager_handler INFO (C:/) processing: ""
[debug] mod_manager.c(2666): manager_handler INFO OK
[debug] mod_manager.c(1901): manager_trans STATUS (/)
[debug] mod_manager.c(2617): manager_handler STATUS (C:/) processing: "JVMRoute=tomcat-6-1&Load=100"
[debug] mod_manager.c(1616): Processing STATUS
[warn] manager_handler STATUS error: MEM: Can't read node
--repeats--
{code}
I can't hit this on RHEL.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (MODCLUSTER-411) java.lang.NoSuchFieldError: SESSION_COOKIE_NAME, Tomcat7
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-411?page=com.atlassian.jira.pl... ]
Michal Babacek updated MODCLUSTER-411:
--------------------------------------
Environment: oracle JDK 1.7, Tomcat 7, Windows, Apache Tomcat Native library 1.1.30 using APR version 1.4.8 (was: Tomcat 7, Windows, Apache Tomcat Native library 1.1.30 using APR version 1.4.8)
> java.lang.NoSuchFieldError: SESSION_COOKIE_NAME, Tomcat7
> --------------------------------------------------------
>
> Key: MODCLUSTER-411
> URL: https://issues.jboss.org/browse/MODCLUSTER-411
> Project: mod_cluster
> Issue Type: Bug
> Affects Versions: 1.2.8.Final
> Environment: oracle JDK 1.7, Tomcat 7, Windows, Apache Tomcat Native library 1.1.30 using APR version 1.4.8
> Reporter: Michal Babacek
> Assignee: Jean-Frederic Clere
> Fix For: 1.2.9.Final
>
>
> mod_cluster in Tomcat 7 on Windows fails to register with Apache HTTP Server:
> {code}
> May 28, 2014 10:52:03 AM org.apache.catalina.core.AprLifecycleListener init
> INFO: Loaded APR based Apache Tomcat Native library 1.1.30 using APR version 1.4.8.
> May 28, 2014 10:52:03 AM org.apache.catalina.core.AprLifecycleListener init
> INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
> May 28, 2014 10:52:03 AM org.apache.catalina.core.AprLifecycleListener initializeSSL
> INFO: OpenSSL successfully initialized (OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008)
> May 28, 2014 10:52:04 AM org.apache.coyote.AbstractProtocol init
> INFO: Initializing ProtocolHandler ["http-apr-192.168.122.24-8080"]
> May 28, 2014 10:52:04 AM org.apache.coyote.AbstractProtocol init
> INFO: Initializing ProtocolHandler ["ajp-apr-192.168.122.24-8009"]
> May 28, 2014 10:52:04 AM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 1892 ms
> May 28, 2014 10:52:04 AM org.jboss.modcluster.ModClusterService init
> INFO: MODCLUSTER000001: Initializing mod_cluster version ${project.version}
> May 28, 2014 10:52:04 AM org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl start
> INFO: MODCLUSTER000032: Listening to proxy advertisements on /224.0.7.222:43294
> May 28, 2014 10:52:04 AM org.apache.catalina.core.StandardService startInternal
> INFO: Starting service Catalina
> May 28, 2014 10:52:04 AM org.apache.catalina.core.StandardEngine startInternal
> INFO: Starting Servlet Engine: Apache Tomcat/7.0.52
> May 28, 2014 10:52:04 AM org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive C:\Program Files\jboss-ews-2.1\share\tomcat7\webapps\clusterbench.war
> May 28, 2014 10:52:06 AM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory C:\Program Files\jboss-ews-2.1\share\tomcat7\webapps\docs
> May 28, 2014 10:52:06 AM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory C:\Program Files\jboss-ews-2.1\share\tomcat7\webapps\examples
> May 28, 2014 10:52:06 AM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory C:\Program Files\jboss-ews-2.1\share\tomcat7\webapps\host-manager
> May 28, 2014 10:52:07 AM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory C:\Program Files\jboss-ews-2.1\share\tomcat7\webapps\manager
> May 28, 2014 10:52:07 AM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory C:\Program Files\jboss-ews-2.1\share\tomcat7\webapps\ROOT
> May 28, 2014 10:52:07 AM org.apache.coyote.AbstractProtocol start
> INFO: Starting ProtocolHandler ["http-apr-192.168.122.24-8080"]
> May 28, 2014 10:52:08 AM org.apache.coyote.AbstractProtocol start
> INFO: Starting ProtocolHandler ["ajp-apr-192.168.122.24-8009"]
> May 28, 2014 10:52:08 AM org.apache.catalina.startup.Catalina start
> INFO: Server startup in 3876 ms
> May 28, 2014 10:52:18 AM org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildren
> SEVERE: Exception invoking periodic operation:
> java.lang.NoSuchFieldError: SESSION_COOKIE_NAME
> at org.jboss.modcluster.container.jbossweb.JBossWebEngine.getSessionCookieName(JBossWebEngine.java:43)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPRequestFactory.createConfigRequest(DefaultMCMPRequestFactory.java:127)
> at org.jboss.modcluster.mcmp.impl.ResetRequestSourceImpl.getResetRequests(ResetRequestSourceImpl.java:89)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:384)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:350)
> at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:458)
> at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:249)
> 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:1530)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1519)
> at java.lang.Thread.run(Thread.java:745)
> May 28, 2014 10:52:28 AM org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildren
> SEVERE: Exception invoking periodic operation:
> java.lang.NoSuchMethodError: org.apache.catalina.connector.Connector.isAvailable()Z
> at org.jboss.modcluster.container.jbossweb.JBossWebConnector.isAvailable(JBossWebConnector.java:39)
> at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:464)
> at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:249)
> 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:1530)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1519)
> at java.lang.Thread.run(Thread.java:745)
> +++
> repeats...
> {code}
> On the Apache HTTP Server side, it looks very weird, because there is an INFO message from Tomcat 7, but no CONFIG...
> {code}
> [notice] Apache/2.2.26 (Win64) DAV/2 mod_cluster/1.2.8.Final configured -- resuming normal operations
> [notice] Server built: May 13 2014 08:51:33
> [notice] Parent: Created child process 3432
> [debug] mpm_winnt.c(477): Parent: Sent the scoreboard to the child
> [debug] util_ldap.c(1990): LDAP merging Shared Cache conf: shm=0x6833e0 rmm=0x683438 for VHOST: WIN-NKI15SIE9RC
> [info] APR LDAP: Built with Microsoft Corporation. LDAP SDK
> [info] LDAP: SSL support unavailable: LDAP: CA certificates cannot be set using this method, as they are stored in the registry instead.
> [notice] Digest: generating secret for digest authentication ...
> [notice] Digest: done
> [debug] mod_advertise.c(589): [3432 - 3460] in child post config hook
> [notice] Child 3432: Child process is running
> [debug] mpm_winnt.c(398): Child 3432: Retrieved our scoreboard from the parent.
> [info] Parent: Duplicating socket 268 and sending it to child process 3432
> [info] Parent: Duplicating socket 260 and sending it to child process 3432
> [debug] mpm_winnt.c(595): Parent: Sent 2 listeners to child 3432
> [debug] mpm_winnt.c(554): Child 3432: retrieved 2 listeners from parent
> [debug] proxy_util.c(1825): proxy: grabbed scoreboard slot 0 in child 3432 for worker proxy:reverse
> [debug] proxy_util.c(1921): proxy: initialized worker 0 in child 3432 for (*) min=0 max=150 smax=150
> [notice] Child 3432: Acquired the start mutex.
> [notice] Child 3432: Starting 150 worker threads.
> [notice] Child 3432: Starting thread to listen on port 2181.
> [notice] Child 3432: Starting thread to listen on port 8847.
> [debug] mod_manager.c(1901): manager_trans INFO (/)
> [debug] mod_manager.c(2617): manager_handler INFO (C:/) processing: ""
> [debug] mod_manager.c(2666): manager_handler INFO OK
> [debug] mod_manager.c(1901): manager_trans INFO (/)
> [debug] mod_manager.c(2617): manager_handler INFO (C:/) processing: ""
> [debug] mod_manager.c(2666): manager_handler INFO OK
> --end of the log, no more relevant messages--
> {code}
> Tomcat 7 configuration:
> {code}
> <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener"
> loadMetricClass="org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric"
> loadMetricCapacity="1"
> loadHistory="9"
> loadDecayFactor="2"
> stickySession="true"
> stickySessionForce="false"
> stickySessionRemove="true"
> advertise="true"
> advertiseGroupAddress="224.0.7.222"
> advertisePort="43294" />
> {code}
> Nothing suspicious in the Apache HTTP Server mod_cluster config:
> {code}
> MemManagerFile "C:\Program Files\jboss-ews-2.1\var\cache\mod_cluster"
> ServerName WIN-NKI15SIE9RC:2181
> <IfModule manager_module>
> Listen 192.168.122.24:8847
> LogLevel debug
> <VirtualHost 192.168.122.24:8847>
> ServerName WIN-NKI15SIE9RC:8847
> <Directory />
> Order deny,allow
> Deny from all
> Allow from all
> </Directory>
> KeepAliveTimeout 60
> MaxKeepAliveRequests 0
> ServerAdvertise on
> AdvertiseFrequency 5
> ManagerBalancerName qacluster
> AdvertiseGroup 224.0.7.222:43294
> EnableMCPMReceive
> <Location /mcm>
> SetHandler mod_cluster-manager
> Order deny,allow
> Deny from all
> Allow from all
> </Location>
> </VirtualHost>
> </IfModule>
> {code}
> I'm unable to hit it on RHEL.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (MODCLUSTER-391) mod_cluster and mod_proxy integration
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-391?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on MODCLUSTER-391:
----------------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 987259|https://bugzilla.redhat.com/show_bug.cgi?id=987259] from ASSIGNED to MODIFIED
> mod_cluster and mod_proxy integration
> -------------------------------------
>
> Key: MODCLUSTER-391
> URL: https://issues.jboss.org/browse/MODCLUSTER-391
> Project: mod_cluster
> Issue Type: Bug
> Affects Versions: 1.2.6.Final
> Environment: All platforms we build mod_cluster for.
> Reporter: Michal Babacek
> Assignee: Jean-Frederic Clere
> Labels: native_libraries
> Fix For: 1.3.1.Final, 1.2.10.Final
>
> Attachments: error_log, mod_cluster.conf, mod_proxy.conf, standalone-ha.xml
>
>
> This Jira encapsulates all concerns regarding mod_cluster - mod_proxy integration. For instance, while basic {{ProxyPass}} settings work just fine, e.g. serving some files on {{/static}} from the Apache HTTP itself:
> {code}
> ProxyPassMatch ^/static/ !
> ProxyPass / balancer://qacluster stickysession=JSESSIONID|jsessionid nofailover=on
> ProxyPassReverse / balancer://qacluster
> ProxyPreserveHost on
> {code}
> there are more complex setups, involving {{BalancerMember}} configurations, that do not work as expected. In the following example, one wanted to have {{/clusterbench}} application managed by mod_cluster, dynamically, while at the same time, in a different VirtualHost, having {{/tses}} application handled by manually created mod_proxy balancer settings.
> Attached [^mod_cluster.conf], [^mod_proxy.conf], [^standalone-ha.xml](modcluster subsystem element only) and [^error_log].
> The aforementioned setup resulted in:
> |HTTP 200|(From worker)|http://10.16.88.19:8847/clusterbench/requestinfo/|OK|(/)|
> |HTTP 404|(From httpd)|http://10.16.88.19:8847/tses/session.jsp|Expected fail|(/)|
> |HTTP 503|(From httpd)|http://10.16.88.19:2182/tses/session.jsp|Unexpected fail|(x)|
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months