[JBoss JIRA] (MODCLUSTER-339) "proxy: DNS lookup failure" with IPv6 on Solaris
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-339?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on MODCLUSTER-339:
----------------------------------------------------
Michal Babacek <mbabacek(a)redhat.com> changed the Status of [bug 963723|https://bugzilla.redhat.com/show_bug.cgi?id=963723] from ASSIGNED to ON_QA
> "proxy: DNS lookup failure" with IPv6 on Solaris
> ------------------------------------------------
>
> Key: MODCLUSTER-339
> URL: https://issues.jboss.org/browse/MODCLUSTER-339
> Project: mod_cluster
> Issue Type: Bug
> Affects Versions: 1.2.3.Final, 1.2.4.Final
> Environment: Solaris 10 x86, Solaris 11 x86, Solaris 11 SPARC
> Reporter: Michal Babacek
> Assignee: Jean-Frederic Clere
> Priority: Critical
> Labels: ipv6
> Fix For: 1.2.5.Final
>
> Attachments: access_log-mod_cluster, error_log-mod_cluster, error_log-mod_cluster-RHEL, error_log-proxypass, error_log_pull20, http.conf, mod_manager.so, sockaddr.lo_fedora18_x86_64, sockaddr.lo_solaris11_sparc64
>
>
> h2. Failure with mod_cluster
> Having the following setting:
> {code:title=mod_cluster.conf|borderStyle=solid|borderColor=#ccc| titleBGColor=#F7D6C1}
> LoadModule slotmem_module modules/mod_slotmem.so
> LoadModule manager_module modules/mod_manager.so
> LoadModule proxy_cluster_module modules/mod_proxy_cluster.so
> LoadModule advertise_module modules/mod_advertise.so
> MemManagerFile "/tmp/mod_cluster-eap6/jboss-ews-2.0/var/cache/mod_cluster"
> ServerName [2620:52:0:105f::ffff:50]:2080
> <IfModule manager_module>
> Listen [2620:52:0:105f::ffff:50]:6666
> LogLevel debug
> <VirtualHost [2620:52:0:105f::ffff:50]:6666>
> ServerName [2620:52:0:105f::ffff:50]:6666
> <Directory />
> Order deny,allow
> Deny from all
> Allow from all
> </Directory>
> KeepAliveTimeout 60
> MaxKeepAliveRequests 0
> ServerAdvertise on
> AdvertiseFrequency 5
> ManagerBalancerName qacluster
> AdvertiseGroup [ff01::7]:23964
> EnableMCPMReceive
> <Location /mcm>
> SetHandler mod_cluster-manager
> Order deny,allow
> Deny from all
> Allow from all
> </Location>
> </VirtualHost>
> </IfModule>
> {code}
> I get a weird {{proxy: DNS lookup failure}} as soon as worker sends {{CONFIGURE}}}:
> {code:title=access_log|borderStyle=solid|borderColor=#ccc| titleBGColor=#F7D6C1}
> 2620:52:0:105f::ffff:50 - - [16/May/2013:08:37:24 -0400] "INFO / HTTP/1.1" 200 - "-" "ClusterListener/1.0"
> 2620:52:0:105f::ffff:50 - - [16/May/2013:08:37:24 -0400] "CONFIG / HTTP/1.1" 200 - "-" "ClusterListener/1.0"
> 2620:52:0:105f::ffff:50 - - [16/May/2013:08:37:24 -0400] "STATUS / HTTP/1.1" 200 64 "-" "ClusterListener/1.0"
> ...
> {code}
> {code:title=error_log|borderStyle=solid|borderColor=#ccc| titleBGColor=#F7D6C1}
> ...
> [Thu May 16 08:37:24 2013] [debug] mod_manager.c(1923): manager_trans INFO (/)
> [Thu May 16 08:37:24 2013] [debug] mod_manager.c(2598): manager_handler INFO (/) processing: ""
> [Thu May 16 08:37:24 2013] [debug] mod_manager.c(2647): manager_handler INFO OK
> [Thu May 16 08:37:24 2013] [debug] mod_manager.c(1923): manager_trans CONFIG (/)
> [Thu May 16 08:37:24 2013] [debug] mod_manager.c(2598): manager_handler CONFIG (/) processing: "JVMRoute=jboss-eap-6.1&Host=%5B2620%3A52%3A0%3A105f%3A0%3A0%3Affff%3A50%252%5D&Maxattempts=1&Port=8009&StickySessionForce=No&Type=ajp&ping=10"
> [Thu May 16 08:37:24 2013] [debug] mod_manager.c(2647): manager_handler CONFIG OK
> [Thu May 16 08:37:24 2013] [debug] mod_manager.c(1923): manager_trans STATUS (/)
> [Thu May 16 08:37:24 2013] [debug] mod_manager.c(2598): manager_handler STATUS (/) processing: "JVMRoute=jboss-eap-6.1&Load=100"
> [Thu May 16 08:37:24 2013] [debug] mod_manager.c(1638): Processing STATUS
> [Thu May 16 08:37:24 2013] [debug] mod_proxy_cluster.c(655): add_balancer_node: Create balancer balancer://qacluster
> [Thu May 16 08:37:24 2013] [debug] mod_proxy_cluster.c(426): Created: worker for ajp://[2620:52:0:105f:0:0:ffff:50%2]:8009
> [Thu May 16 08:37:24 2013] [debug] mod_proxy_cluster.c(532): proxy: initialized worker 1 in child 16847 for (2620:52:0:105f:0:0:ffff:50%2) min=0 max=25 smax=25
> [Thu May 16 08:37:24 2013] [debug] mod_proxy_cluster.c(601): Created: worker for ajp://[2620:52:0:105f:0:0:ffff:50%2]:8009 1 (status): 1
> [Thu May 16 08:37:24 2013] [debug] proxy_util.c(2011): proxy: ajp: has acquired connection for (2620:52:0:105f:0:0:ffff:50%2)
> [Thu May 16 08:37:24 2013] [debug] proxy_util.c(2067): proxy: connecting ajp://[2620:52:0:105f:0:0:ffff:50%2]:8009/ to 2620:52:0:105f:0:0:ffff:50%2:8009
> [Thu May 16 08:37:24 2013] [error] [client 2620:52:0:105f::ffff:50] proxy: DNS lookup failure for: 2620:52:0:105f:0:0:ffff:50%2 returned by /
> [Thu May 16 08:37:24 2013] [debug] proxy_util.c(2029): proxy: ajp: has released connection for (2620:52:0:105f:0:0:ffff:50%2)
> ...
> {code}
> An attempt to access the mod_cluster manager console yields an unpleasant {{NOTOK}} (obviously, we have All workers are in error state...):
> {code}
> curl -g [2620:52:0:105f::ffff:50]:6666/mcm
> ...
> <h1> Node jboss-eap-6.1 (ajp://[2620:52:0:105f:0:0:ffff:50%2]:8009): </h1>
> <a href="/mcm?nonce=1bddeeea-f9d5-eeea-ee5b-e3a5e3c0a965&Cmd=ENABLE-APP&Range=NODE&JVMRoute=jboss-eap-6.1">Enable Contexts</a> <a href="/mcm?nonce=1bddeeea-f9d5-eeea-ee5b-e3a5e3c0a965&Cmd=DISABLE-APP&Range=NODE&JVMRoute=jboss-eap-6.1">Disable Contexts</a><br/>
> Balancer: qacluster,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 26,Ttl: 60000000,Status: NOTOK,Elected: 0,Read: 0,Transferred: 0,Connected: 0,Load: -1
> {code}
> You might take a look at the logs: [^error_log-mod_cluster], [^access_log-mod_cluster].
> h2. ProxyPass itself works just fine
> On the other hand, when I had tried this:
> {code:title=proxypass.conf|borderStyle=solid|borderColor=#ccc| titleBGColor=#F7D6C1}
> LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
> ServerName [2620:52:0:105f::ffff:50]:2080
> Listen [2620:52:0:105f::ffff:50]:6666
> LogLevel debug
> <VirtualHost [2620:52:0:105f::ffff:50]:6666>
> ServerName [2620:52:0:105f::ffff:50]:6666
> ProxyPass / ajp://[2620:52:0:105f:0:0:ffff:50]:8009/
> ProxyPassReverse / ajp://[2620:52:0:105f:0:0:ffff:50]:8009/
> <Directory />
> Order deny,allow
> Deny from all
> Allow from all
> </Directory>
> </VirtualHost>
> {code}
> I received:
> {code:title=error_log|borderStyle=solid|borderColor=#ccc| titleBGColor=#F7D6C1}
> ...
> [Thu May 16 08:29:00 2013] [debug] mod_proxy_ajp.c(45): proxy: AJP: canonicalising URL //[2620:52:0:105f:0:0:ffff:50]:8009/
> [Thu May 16 08:29:00 2013] [debug] proxy_util.c(1506): [client 2620:52:0:105f::ffff:50] proxy: ajp: found worker ajp://[2620:52:0:105f:0:0:ffff:50]:8009/ for ajp://[2620:52:0:105f:0:0:ffff:50]:8009/
> [Thu May 16 08:29:00 2013] [debug] mod_proxy.c(1020): Running scheme ajp handler (attempt 0)
> [Thu May 16 08:29:00 2013] [debug] mod_proxy_http.c(1963): proxy: HTTP: declining URL ajp://[2620:52:0:105f:0:0:ffff:50]:8009/
> [Thu May 16 08:29:00 2013] [debug] mod_proxy_ajp.c(681): proxy: AJP: serving URL ajp://[2620:52:0:105f:0:0:ffff:50]:8009/
> [Thu May 16 08:29:00 2013] [debug] proxy_util.c(2011): proxy: AJP: has acquired connection for (2620:52:0:105f:0:0:ffff:50)
> [Thu May 16 08:29:00 2013] [debug] proxy_util.c(2067): proxy: connecting ajp://[2620:52:0:105f:0:0:ffff:50]:8009/ to 2620:52:0:105f:0:0:ffff:50:8009
> [Thu May 16 08:29:00 2013] [debug] proxy_util.c(2193): proxy: connected / to 2620:52:0:105f:0:0:ffff:50:8009
> [Thu May 16 08:29:00 2013] [debug] proxy_util.c(2444): proxy: AJP: fam 26 socket created to connect to 2620:52:0:105f:0:0:ffff:50
> ...
> {code}
> And from the client's side, it worked:
> {{curl -g [2620:52:0:105f::ffff:50]:6666/}} brought me the worker's home page (EAP's welcome in this case).
> Take a look at the whole log [^error_log-proxypass].
> *Note:* The [^http.conf] was the same both for mod_cluster and for proxypass test.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[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:
----------------------------------------------------
Michal Babacek <mbabacek(a)redhat.com> changed the Status of [bug 960246|https://bugzilla.redhat.com/show_bug.cgi?id=960246] from ON_QA to VERIFIED
> 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.6#6264)
9 years, 10 months
[JBoss JIRA] (MODCLUSTER-178) Domains: non sticky requests should be contained within a given domain
by Roman Jurkov (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-178?page=com.atlassian.jira.pl... ]
Roman Jurkov commented on MODCLUSTER-178:
-----------------------------------------
never mind, just noticed that force was set to yes in my test, so i see what you've described. so do we want to just add new configuration value or extend StickySession not to just have yes/no but to make it node/domain/no and for backwards compatibility to keep yes, which would be same as "node"?
> Domains: non sticky requests should be contained within a given domain
> ----------------------------------------------------------------------
>
> Key: MODCLUSTER-178
> URL: https://issues.jboss.org/browse/MODCLUSTER-178
> Project: mod_cluster
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Jean-Frederic Clere
> Attachments: cluster-small.png, cluster.jpg
>
>
> If we have a couple of domains, then non-sticky requests can go to *any* server in *any* domain.
> It would be nice if we could at least make the domain sticky, so e.g. non-sticky requests always pick the same domain, as long as there are servers in that domain.
> Maybe this should be a new flag, e.g. stickyDomain. If stickySession is false, then we'd check stickyDomain.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 10 months
[JBoss JIRA] (MODCLUSTER-178) Domains: non sticky requests should be contained within a given domain
by Roman Jurkov (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-178?page=com.atlassian.jira.pl... ]
Roman Jurkov commented on MODCLUSTER-178:
-----------------------------------------
Rado,
is there a special configuration that i should do to achieve case 3? i've tested it with sticky session true and force to false, and i am getting 503 if node goes down, here is my info:
balancer: [1] Name: mycluster Sticky: 1 [JSESSIONID]/[jsessionid] remove: 0 force: 1 Timeout: 0 maxAttempts: 1
node: [2:2],Balancer: mycluster,JVMRoute: MyClusterE1,LBGroup: [MyDomain2],Host: 127.0.0.1,Port: 4453,Type: http,flushpackets: 0,flushwait: 1,ping: 10,smax: 0,ttl: 60,timeout: 0
host: 1 [myClusterAlias2] vhost: 1 node: 2
host: 2 [mycluterAlias1] vhost: 1 node: 2
context: 1 [/cluster] vhost: 1 node: 2 status: 1
my session cookie:
id: 6a1f20eda1ec119e7fa168f766f2309bb5f42692.MyClusterD route: MyClusterD
as you see node is MyClusterD and route is MyClusterD which died, however there is MyClusterE that serves /cluster context, however mod_cluster doesn't elect that node
> Domains: non sticky requests should be contained within a given domain
> ----------------------------------------------------------------------
>
> Key: MODCLUSTER-178
> URL: https://issues.jboss.org/browse/MODCLUSTER-178
> Project: mod_cluster
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Jean-Frederic Clere
> Attachments: cluster-small.png, cluster.jpg
>
>
> If we have a couple of domains, then non-sticky requests can go to *any* server in *any* domain.
> It would be nice if we could at least make the domain sticky, so e.g. non-sticky requests always pick the same domain, as long as there are servers in that domain.
> Maybe this should be a new flag, e.g. stickyDomain. If stickySession is false, then we'd check stickyDomain.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 10 months
[JBoss JIRA] (MODCLUSTER-411) java.lang.NoSuchFieldError: SESSION_COOKIE_NAME, Tomcat7
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-411?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on MODCLUSTER-411:
----------------------------------------------------
Michal Babacek <mbabacek(a)redhat.com> changed the Status of [bug 1101977|https://bugzilla.redhat.com/show_bug.cgi?id=1101977] from ON_QA to VERIFIED
> 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)
9 years, 10 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 commented on MODCLUSTER-412:
----------------------------------------------------
Michal Babacek <mbabacek(a)redhat.com> changed the Status of [bug 1102012|https://bugzilla.redhat.com/show_bug.cgi?id=1102012] from ON_QA to VERIFIED
> 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)
9 years, 10 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 closed MODCLUSTER-412.
-------------------------------------
Closing.
> 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)
9 years, 10 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 resolved MODCLUSTER-412.
---------------------------------------
Resolution: Rejected
Packaging issue.
> 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)
9 years, 10 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 closed MODCLUSTER-411.
-------------------------------------
Closing.
> 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)
9 years, 10 months