May 2018 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-656) Remove *-javadoc.jar from distribution profiles

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-656?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-656: -------------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/331, https://github.com/modcluster/mod_cluster/pull/332 (was: https://github.com/modcluster/mod_cluster/pull/331) > Remove *-javadoc.jar from distribution profiles > ----------------------------------------------- > > Key: MODCLUSTER-656 > URL: https://issues.jboss.org/browse/MODCLUSTER-656 > Project: mod_cluster > Issue Type: Task > Components: CI & Packaging > Affects Versions: 1.4.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 2.0.0.Alpha1, 1.4.1.Final > > > Looks like unintended consequence of updating the distribution profiles. While this is fine, I think we should drive people to use javadoc from web/IDE/sources rather than providing them in a distribution bundle. > https://www.dropbox.com/s/izhjsmqh7drik72/Screenshot%202018-04-16%2017.54... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-658) Implement mod_cluster worker for Undertow embedded and standalone use case

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-658?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-658: ------------------------------------------- Description: This is a placeholder JIRA for a possible implementation/artifact. It has neither any formal planning nor priority set and it might not happen at all. h2. Workers and balancers Mod_cluster project comprises two kinds of actors: balancers and workers. h3. Balancers Currently there are three balancer implementations: # mod_proxy_cluster module for Apache HTTP Server # Undertow mod_cluster filter that could be used both in Undertow embedded and in Wildfly application server # mod_proxy_cluster Nginx implementation h3. Workers There are these worker implementations: # JBoss AS 5 / mod_cluster.sar worker implementation, {color:red}*Abandoned/Legacy*{color} # JBoss AS7 mod_cluster subsystem, {color:orange}*Legacy*{color} # Wildfly application server, {color:green}*Current*{color} # Tomcat 6.0/7.0/8.0, {color:orange}*Legacy*{color} # Tomcat 8.5/9.0, {color:green}*Current*{color} In addition to those, we would like to see mod_cluster worker login implemented for additional web servers, such as: # Jetty # Go net/http, i.e. Go web servers (mostly for REST APIs) # Undertow embedded # Undertow standalone (UNDERTOW-1356) h3. Undertow worker implementation There should be a mod_cluster worker library that would enable Undertow, both in its embedded and standalone (UNDERTOW-1356) flavour to act as a worker, i.e. to report to another mod_cluster balancer (either httpd, Nginx or another Undertow instance). was: This is a placeholder JIRA for a possible implementation/artifact. It has neither any formal planning nor priority set and it might not happen at all. h2. Workers and balancers Mod_cluster project comprises two kinds of actors: balancers and workers. h3. Balancers Currently there are three balancer implementations: # mod_proxy_cluster module for Apache HTTP Server # Undertow mod_cluster filter that could be used both in Undertow embedded and in Wildfly application server # mod_proxy_cluster Nginx implementation h3. Workers There are these worker implementations: # JBoss AS 5 / mod_cluster.sar worker implementation, {color:red}*Abandoned/Legacy*{color} # JBoss AS7 mod_cluster subsystem, {color:orange}*Legacy*{color} # Wildfly application server, {color:green]*Current*{color} # Tomcat 6.0/7.0/8.0, {color:orange}*Legacy*{color} # Tomcat 8.5/9.0, {color:green]*Current*{color} In addition to those, we would like to see mod_cluster worker login implemented for additional web servers, such as: # Jetty # Go net/http, i.e. Go web servers (mostly for REST APIs) # Undertow embedded # Undertow standalone (UNDERTOW-1356) h3. Undertow worker implementation There should be a mod_cluster worker library that would enable Undertow, both in its embedded and standalone (UNDERTOW-1356) flavour to act as a worker, i.e. to report to another mod_cluster balancer (either httpd, Nginx or another Undertow instance). > Implement mod_cluster worker for Undertow embedded and standalone use case > -------------------------------------------------------------------------- > > Key: MODCLUSTER-658 > URL: https://issues.jboss.org/browse/MODCLUSTER-658 > Project: mod_cluster > Issue Type: Feature Request > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > Priority: Minor > > This is a placeholder JIRA for a possible implementation/artifact. It has neither any formal planning nor priority set and it might not happen at all. > h2. Workers and balancers > Mod_cluster project comprises two kinds of actors: balancers and workers. > h3. Balancers > Currently there are three balancer implementations: > # mod_proxy_cluster module for Apache HTTP Server > # Undertow mod_cluster filter that could be used both in Undertow embedded and in Wildfly application server > # mod_proxy_cluster Nginx implementation > h3. Workers > There are these worker implementations: > # JBoss AS 5 / mod_cluster.sar worker implementation, {color:red}*Abandoned/Legacy*{color} > # JBoss AS7 mod_cluster subsystem, {color:orange}*Legacy*{color} > # Wildfly application server, {color:green}*Current*{color} > # Tomcat 6.0/7.0/8.0, {color:orange}*Legacy*{color} > # Tomcat 8.5/9.0, {color:green}*Current*{color} > In addition to those, we would like to see mod_cluster worker login implemented for additional web servers, such as: > # Jetty > # Go net/http, i.e. Go web servers (mostly for REST APIs) > # Undertow embedded > # Undertow standalone (UNDERTOW-1356) > h3. Undertow worker implementation > There should be a mod_cluster worker library that would enable Undertow, both in its embedded and standalone (UNDERTOW-1356) flavour to act as a worker, i.e. to report to another mod_cluster balancer (either httpd, Nginx or another Undertow instance). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-658) Implement mod_cluster worker for Undertow embedded and standalone use case

by Michal Karm Babacek (JIRA)

Michal Karm Babacek created MODCLUSTER-658: ---------------------------------------------- Summary: Implement mod_cluster worker for Undertow embedded and standalone use case Key: MODCLUSTER-658 URL: https://issues.jboss.org/browse/MODCLUSTER-658 Project: mod_cluster Issue Type: Feature Request Reporter: Michal Karm Babacek Assignee: Michal Karm Babacek Priority: Minor This is a placeholder JIRA for a possible implementation/artifact. It has neither any formal planning nor priority set and it might not happen at all. h2. Workers and balancers Mod_cluster project comprises two kinds of actors: balancers and workers. h3. Balancers Currently there are three balancer implementations: # mod_proxy_cluster module for Apache HTTP Server # Undertow mod_cluster filter that could be used both in Undertow embedded and in Wildfly application server # mod_proxy_cluster Nginx implementation h3. Workers There are these worker implementations: # JBoss AS 5 / mod_cluster.sar worker implementation, {color:red}*Abandoned/Legacy*{color} # JBoss AS7 mod_cluster subsystem, {color:orange}*Legacy*{color} # Wildfly application server, {color:green]*Current*{color} # Tomcat 6.0/7.0/8.0, {color:orange}*Legacy*{color} # Tomcat 8.5/9.0, {color:green]*Current*{color} In addition to those, we would like to see mod_cluster worker login implemented for additional web servers, such as: # Jetty # Go net/http, i.e. Go web servers (mostly for REST APIs) # Undertow embedded # Undertow standalone (UNDERTOW-1356) h3. Undertow worker implementation There should be a mod_cluster worker library that would enable Undertow, both in its embedded and standalone (UNDERTOW-1356) flavour to act as a worker, i.e. to report to another mod_cluster balancer (either httpd, Nginx or another Undertow instance). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-656) Remove *-javadoc.jar from distribution profiles

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-656?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-656: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/331 > Remove *-javadoc.jar from distribution profiles > ----------------------------------------------- > > Key: MODCLUSTER-656 > URL: https://issues.jboss.org/browse/MODCLUSTER-656 > Project: mod_cluster > Issue Type: Task > Components: CI & Packaging > Affects Versions: 1.4.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 2.0.0.Alpha1, 1.4.1.Final > > > Looks like unintended consequence of updating the distribution profiles. While this is fine, I think we should drive people to use javadoc from web/IDE/sources rather than providing them in a distribution bundle. > https://www.dropbox.com/s/izhjsmqh7drik72/Screenshot%202018-04-16%2017.54... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-656) Remove *-javadoc.jar from distribution profiles

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-656?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-656: -------------------------------------- Fix Version/s: 2.0.0.Alpha1 1.4.1.Final > Remove *-javadoc.jar from distribution profiles > ----------------------------------------------- > > Key: MODCLUSTER-656 > URL: https://issues.jboss.org/browse/MODCLUSTER-656 > Project: mod_cluster > Issue Type: Task > Components: CI & Packaging > Affects Versions: 1.4.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 2.0.0.Alpha1, 1.4.1.Final > > > Looks like unintended consequence of updating the distribution profiles. While this is fine, I think we should drive people to use javadoc from web/IDE/sources rather than providing them in a distribution bundle. > https://www.dropbox.com/s/izhjsmqh7drik72/Screenshot%202018-04-16%2017.54... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-479) Add support for Tomcat 9

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-479?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-479: ------------------------------------------- [~prabhat.823] If I remember correctly, this is available in 1.4.0.Final which is a final version. > Add support for Tomcat 9 > ------------------------ > > Key: MODCLUSTER-479 > URL: https://issues.jboss.org/browse/MODCLUSTER-479 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.4.0.Alpha1, 1.4.0.Final, 2.0.0.Alpha1 > > > This won't be binary compatible with Tomcat 8 classes because there are some differences. > Comet support has bee removed, see https://github.com/apache/tomcat/commit/376a308dbb1742f9fc88e693fb8100c44... > Service.getContainer refactored https://github.com/apache/tomcat/commit/2d9d4519cea1879209848952832fe194a... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-479) Add support for Tomcat 9

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-479?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-479: -------------------------------------- Fix Version/s: 1.4.0.Final > Add support for Tomcat 9 > ------------------------ > > Key: MODCLUSTER-479 > URL: https://issues.jboss.org/browse/MODCLUSTER-479 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.4.0.Alpha1, 1.4.0.Final, 2.0.0.Alpha1 > > > This won't be binary compatible with Tomcat 8 classes because there are some differences. > Comet support has bee removed, see https://github.com/apache/tomcat/commit/376a308dbb1742f9fc88e693fb8100c44... > Service.getContainer refactored https://github.com/apache/tomcat/commit/2d9d4519cea1879209848952832fe194a... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-479) Add support for Tomcat 9

by Prabhat Kumar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-479?page=com.atlassian.jira.pl... ] Prabhat Kumar commented on MODCLUSTER-479: ------------------------------------------ Hi, I see the fix is available in alpha version. Can you please let us know when there will be a final version released? Regards, Prabhat > Add support for Tomcat 9 > ------------------------ > > Key: MODCLUSTER-479 > URL: https://issues.jboss.org/browse/MODCLUSTER-479 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.4.0.Alpha1, 2.0.0.Alpha1 > > > This won't be binary compatible with Tomcat 8 classes because there are some differences. > Comet support has bee removed, see https://github.com/apache/tomcat/commit/376a308dbb1742f9fc88e693fb8100c44... > Service.getContainer refactored https://github.com/apache/tomcat/commit/2d9d4519cea1879209848952832fe194a... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-638) Mod_cluster listener doesn't start: misleading docs

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-638?page=com.atlassian.jira.pl... ] Radoslav Husar edited comment on MODCLUSTER-638 at 5/3/18 9:44 AM: ------------------------------------------------------------------- Advertise logic only affects 2.0, since 1.4 still uses the old logic. was (Author: rhusar): This only affects 2.0, since 1.4 still uses the old logic. > Mod_cluster listener doesn't start: misleading docs > --------------------------------------------------- > > Key: MODCLUSTER-638 > URL: https://issues.jboss.org/browse/MODCLUSTER-638 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java), Documentation & Demos > Affects Versions: 1.4.0.Final, 2.0.0.Alpha1 > Environment: Tomcat 9.0.2, Windows, Oracle JDK 8 > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Priority: Blocker > Labels: ux > Fix For: 2.0.0.Alpha1 > > > h3. Old listener conf from docs fails to start, automagic elimination aftermath > h4. server.xml > {code} > <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener" connectorPort="8009"/> > {code} > h4. Fails to start Tomcat server > {code} > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/9.0.2 > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Nov 25 2017 21:08:02 UTC > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 9.0.2.0 > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Windows NT (unknown) > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 10.0 > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64 > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: C:\Program Files\jdk1.8.0_last\jre > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_121-b13 > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: C:\apache-tomcat-9.0.2-windows-x64\apache-tomcat-9.0.2 > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: C:\apache-tomcat-9.0.2-windows-x64\apache-tomcat-9.0.2 > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:\apache-tomcat-9.0.2-windows-x64\apache-tomcat-9.0.2\conf\logging.properties > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048 > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs= > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\apache-tomcat-9.0.2-windows-x64\apache-tomcat-9.0.2 > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\apache-tomcat-9.0.2-windows-x64\apache-tomcat-9.0.2 > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:\apache-tomcat-9.0.2-windows-x64\apache-tomcat-9.0.2\temp > INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR based Apache Tomcat Native library [1.2.16] using APR version [1.6.3]. > INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. > INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true] > INFO [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized [OpenSSL 1.0.2m 2 Nov 2017] > INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"] > INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read > INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-8009"] > INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read > INFO [main] org.jboss.modcluster.ModClusterService.init MODCLUSTER000001: Initializing mod_cluster version 2.0.0.Alpha1-SNAPSHOT > SEVERE [main] org.apache.catalina.startup.Catalina.load Catalina.start > org.apache.catalina.LifecycleException: Failed to initialize component [StandardServer[8005]] > at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:441) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:139) > at org.apache.catalina.startup.Catalina.load(Catalina.java:622) > at org.apache.catalina.startup.Catalina.load(Catalina.java:645) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:309) > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:492) > Caused by: java.lang.RuntimeException: MODCLUSTER000valid advertise interface configured! Disabling multicast advertise mechanism. > at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.initializeDatagramChannel(AdvertiseListenerImpl.java:133) > at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.start(AdvertiseListenerImpl.java:140) > at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.<init>(AdvertiseListenerImpl.java:102) > at org.jboss.modcluster.advertise.impl.AdvertiseListenerFactoryImpl.createListener(AdvertiseListenerFactoryImpl.java:38) > at org.jboss.modcluster.ModClusterService.init(ModClusterService.java:163) > at org.jboss.modcluster.container.tomcat.TomcatEventHandlerAdapter.init(TomcatEventHandlerAdapter.java:249) > at org.jboss.modcluster.container.tomcat.TomcatEventHandlerAdapter.lifecycleEvent(TomcatEventHandlerAdapter.java:187) > at org.jboss.modcluster.container.tomcat.ModClusterListener.lifecycleEvent(ModClusterListener.java:118) > at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) > at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:424) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:137) > ... 8 more > INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1724 ms > SEVERE [main] org.apache.catalina.startup.Catalina.start The required Server component failed to start so Tomcat is unable to start. > org.apache.catalina.LifecycleException: An invalid Lifecycle transition was attempted ([before_stop]) for component [StandardService[Catalina]] in state [INITIALIZED] > at org.apache.catalina.util.LifecycleBase.invalidTransition(LifecycleBase.java:431) > at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:244) > at org.apache.catalina.core.StandardServer.stopInternal(StandardServer.java:791) > at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:257) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:175) > at org.apache.catalina.startup.Catalina.start(Catalina.java:671) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:353) > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:493) > WARNING [main] org.apache.catalina.util.LifecycleBase.destroy Calling stop() on failed component [StandardServer[80trigger clean-up did not complete. > org.apache.catalina.LifecycleException: An invalid Lifecycle transition was attempted ([before_stop]) for component [StandardService[Catalina]] in state [INITIALIZED] > at org.apache.catalina.util.LifecycleBase.invalidTransition(LifecycleBase.java:431) > at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:244) > at org.apache.catalina.core.StandardServer.stopInternal(StandardServer.java:791) > at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:257) > at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:293) > at org.apache.catalina.startup.Catalina.start(Catalina.java:675) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:353) > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:493) > INFO [main] org.jboss.modcluster.ModClusterService.shutdown MODCLUSTER000002: Initiating mod_cluster shutdown > INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-8080"] > INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["ajp-nio-8009"] > {code} > h2. Call to action > Please, fix the docs: > * [README.md|https://github.com/modcluster/mod_cluster/blame/7e7dcbfef3bd357...] > * [Documentation|https://github.com/modcluster/modcluster.io/blame/master/do...] > To save you some attributes lookup and copy pasting, you might want to take a look at this [complete list|https://github.com/Karm/jws-3-tomcat-8-mod_cluster/blob/master/serve...]. > I guess at least this should find its way into the docs, give or take: > {code} > <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener" > advertise="true" > advertiseInterface="172.16.27.10" > advertiseGroupAddress="224.0.1.105" > advertisePort="23364" > connectorPort="8009" > /> > {code} plus the message in the log must be improved. A random user has no chance to understand what the listener wants - it just looks as if it disabled advertising:{code} java.lang.RuntimeException: MODCLUSTER000valid advertise interface configured! Disabling multicast advertise mechanism.{code}, while in fact the whole Tomcat goes down. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-657) Mod_cluster listener doesn't start: misleading docs

by Michal Karm Babacek (JIRA)

Michal Karm Babacek created MODCLUSTER-657: ---------------------------------------------- Summary: Mod_cluster listener doesn't start: misleading docs Key: MODCLUSTER-657 URL: https://issues.jboss.org/browse/MODCLUSTER-657 Project: mod_cluster Issue Type: Bug Components: Core & Container Integration (Java), Documentation & Demos Affects Versions: 1.4.0.Final, 2.0.0.Alpha1 Environment: Tomcat 9.0.2, Windows, Oracle JDK 8 Reporter: Michal Karm Babacek Assignee: Radoslav Husar Priority: Blocker Fix For: 2.0.0.Alpha1 h3. Old listener conf from docs fails to start, automagic elimination aftermath h4. server.xml {code} <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener" connectorPort="8009"/> {code} h4. Fails to start Tomcat server {code} INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/9.0.2 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Nov 25 2017 21:08:02 UTC INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 9.0.2.0 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Windows NT (unknown) INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 10.0 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: C:\Program Files\jdk1.8.0_last\jre INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_121-b13 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: C:\apache-tomcat-9.0.2-windows-x64\apache-tomcat-9.0.2 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: C:\apache-tomcat-9.0.2-windows-x64\apache-tomcat-9.0.2 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:\apache-tomcat-9.0.2-windows-x64\apache-tomcat-9.0.2\conf\logging.properties INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs= INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\apache-tomcat-9.0.2-windows-x64\apache-tomcat-9.0.2 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\apache-tomcat-9.0.2-windows-x64\apache-tomcat-9.0.2 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:\apache-tomcat-9.0.2-windows-x64\apache-tomcat-9.0.2\temp INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR based Apache Tomcat Native library [1.2.16] using APR version [1.6.3]. INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true] INFO [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized [OpenSSL 1.0.2m 2 Nov 2017] INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"] INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-8009"] INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read INFO [main] org.jboss.modcluster.ModClusterService.init MODCLUSTER000001: Initializing mod_cluster version 2.0.0.Alpha1-SNAPSHOT SEVERE [main] org.apache.catalina.startup.Catalina.load Catalina.start org.apache.catalina.LifecycleException: Failed to initialize component [StandardServer[8005]] at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:441) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:139) at org.apache.catalina.startup.Catalina.load(Catalina.java:622) at org.apache.catalina.startup.Catalina.load(Catalina.java:645) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:309) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:492) Caused by: java.lang.RuntimeException: MODCLUSTER000valid advertise interface configured! Disabling multicast advertise mechanism. at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.initializeDatagramChannel(AdvertiseListenerImpl.java:133) at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.start(AdvertiseListenerImpl.java:140) at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.<init>(AdvertiseListenerImpl.java:102) at org.jboss.modcluster.advertise.impl.AdvertiseListenerFactoryImpl.createListener(AdvertiseListenerFactoryImpl.java:38) at org.jboss.modcluster.ModClusterService.init(ModClusterService.java:163) at org.jboss.modcluster.container.tomcat.TomcatEventHandlerAdapter.init(TomcatEventHandlerAdapter.java:249) at org.jboss.modcluster.container.tomcat.TomcatEventHandlerAdapter.lifecycleEvent(TomcatEventHandlerAdapter.java:187) at org.jboss.modcluster.container.tomcat.ModClusterListener.lifecycleEvent(ModClusterListener.java:118) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:424) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:137) ... 8 more INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1724 ms SEVERE [main] org.apache.catalina.startup.Catalina.start The required Server component failed to start so Tomcat is unable to start. org.apache.catalina.LifecycleException: An invalid Lifecycle transition was attempted ([before_stop]) for component [StandardService[Catalina]] in state [INITIALIZED] at org.apache.catalina.util.LifecycleBase.invalidTransition(LifecycleBase.java:431) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:244) at org.apache.catalina.core.StandardServer.stopInternal(StandardServer.java:791) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:257) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:175) at org.apache.catalina.startup.Catalina.start(Catalina.java:671) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:353) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:493) WARNING [main] org.apache.catalina.util.LifecycleBase.destroy Calling stop() on failed component [StandardServer[80trigger clean-up did not complete. org.apache.catalina.LifecycleException: An invalid Lifecycle transition was attempted ([before_stop]) for component [StandardService[Catalina]] in state [INITIALIZED] at org.apache.catalina.util.LifecycleBase.invalidTransition(LifecycleBase.java:431) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:244) at org.apache.catalina.core.StandardServer.stopInternal(StandardServer.java:791) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:257) at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:293) at org.apache.catalina.startup.Catalina.start(Catalina.java:675) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:353) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:493) INFO [main] org.jboss.modcluster.ModClusterService.shutdown MODCLUSTER000002: Initiating mod_cluster shutdown INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-8080"] INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["ajp-nio-8009"] {code} h2. Call to action Please, fix the docs: * [README.md|https://github.com/modcluster/mod_cluster/blame/7e7dcbfef3bd357...] * [Documentation|https://github.com/modcluster/modcluster.io/blame/master/do...] To save you some attributes lookup and copy pasting, you might want to take a look at this [complete list|https://github.com/Karm/jws-3-tomcat-8-mod_cluster/blob/master/serve...]. I guess at least this should find its way into the docs, give or take: {code} <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener" advertise="true" advertiseInterface="172.16.27.10" advertiseGroupAddress="224.0.1.105" advertisePort="23364" connectorPort="8009" /> {code} plus the message in the log must be improved. A random user has no chance to understand what the listener wants - it just looks as if it disabled advertising:{code} java.lang.RuntimeException: MODCLUSTER000valid advertise interface configured! Disabling multicast advertise mechanism.{code}, while in fact the whole Tomcat goes down. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues May 2018