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)