You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Rick Noel <RN...@westwoodone.com.INVALID> on 2024/04/22 14:54:09 UTC
Tomcat 10 skipping state transfer. No members active in cluster group
Hello,
Could someone please explain why I am getting the error............
skipping state transfer. No members active in cluster group
On one sever the reciever is bound to 127.0.0.1:4002
And on the other server the receiver is bound to 127.0.0.1:4001
But both servers report -> no active members in cluster group
22-Apr-2024 10:19:06.726 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Station]
22-Apr-2024 10:19:06.727 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.20]
22-Apr-2024 10:19:06.736 INFO [main] org.apache.catalina.ha.tcp.SimpleTcpCluster.startInternal Cluster is about to start
22-Apr-2024 10:19:06.750 INFO [main] org.apache.catalina.tribes.transport.ReceiverBase.bind Receiver Server Socket bound to:[/127.0.0.1:4002]
22-Apr-2024 10:19:06.762 INFO [main] org.apache.catalina.tribes.membership.McastServiceImpl.setupSocket Setting cluster mcast soTimeout to [500]
22-Apr-2024 10:19:06.771 INFO [main] org.apache.catalina.tribes.membership.McastServiceImpl.waitForMembers Sleeping for [1000] milliseconds to establish cluster membership, start level:[4]
22-Apr-2024 10:19:07.771 INFO [main] org.apache.catalina.tribes.membership.McastServiceImpl.waitForMembers Done sleeping, membership established, start level:[4]
22-Apr-2024 10:19:07.773 INFO [main] org.apache.catalina.tribes.membership.McastServiceImpl.waitForMembers Sleeping for [1000] milliseconds to establish cluster membership, start level:[8]
22-Apr-2024 10:19:08.774 INFO [main] org.apache.catalina.tribes.membership.McastServiceImpl.waitForMembers Done sleeping, membership established, start level:[8]
22-Apr-2024 10:19:08.790 INFO [main] org.apache.catalina.ha.session.JvmRouteBinderValve.startInternal JvmRouteBinderValve started
22-Apr-2024 10:19:08.803 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/home/web/servers/apache-tomcat-10.1.20/station/ROOT##0001.war]
Apr 22, 2024 10:20:01 AM org.apache.catalina.util.SessionIdGeneratorBase createSecureRandom
WARNING: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [51,791] milliseconds.
Apr 22, 2024 10:20:01 AM org.apache.catalina.ha.session.DeltaManager startInternal
INFO: Register manager [##0001] to cluster element [Host] with name [station]
Apr 22, 2024 10:20:01 AM org.apache.catalina.ha.session.DeltaManager startInternal
INFO: Starting clustering manager at [##0001]
Apr 22, 2024 10:20:01 AM org.apache.catalina.ha.session.DeltaManager getAllClusterSessions
INFO: Manager [##0001]: skipping state transfer. No members active in cluster group.
Here is how I have clustering set up on server one............
<Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster" channelSendOptions="8">
<Manager className="org.apache.catalina.ha.session.DeltaManager"
expireSessionsOnShutdown="false"
notifyListenersOnReplication="true"
sessionAttributeNameFilter="uploader_redirect|phone_tree|soundhound.campaigndata|format|employee_id|customer|customer_id|nonidentifier_call_letters|call_letters|caller_id_enabled|ivr_system|ivr_system_id|zip_code|time_zone|is_trial_customer|delete_confirmation|download_settings|clustered_admin|wall_token|employee_first_name|logged_in_user|logged_in"
/>
<Channel className="org.apache.catalina.tribes.group.GroupChannel">
<Membership className="org.apache.catalina.tribes.membership.McastService"
address="228.0.0.4"
port="45565"
frequency="500"
dropTime="3000"/>
<Receiver className="org.apache.catalina.tribes.transport.nio.NioReceiver"
address="auto"
port="4002"
autoBind="100"
selectorTimeout="5000"
maxThreads="6"/>
<Sender className="org.apache.catalina.tribes.transport.ReplicationTransmitter">
<Transport className="org.apache.catalina.tribes.transport.nio.PooledParallelSender"/>
</Sender>
<Interceptor className="org.apache.catalina.tribes.group.interceptors.TcpFailureDetector"/>
<Interceptor className="org.apache.catalina.tribes.group.interceptors.MessageDispatchInterceptor"/>
<Interceptor className="org.apache.catalina.tribes.group.interceptors.ThroughputInterceptor"/>
</Channel>
On the other server I just changed the member ship to a different port port="45564"
And reciver port to a different port also port="4002"
In my application level web.xml on both servers I have included the needed tag
<distributable />
What am I missing here?
Rick Noel
Systems Programmer | Westwood One
RNoel@westwoodone.com
Re: Tomcat 10 skipping state transfer. No members active in cluster group
Posted by Steve Carlsen <st...@besd.net>.
Would you please take me off of this list
On Mon, Apr 22, 2024 at 9:01 AM Rick Noel <RN...@westwoodone.com.invalid>
wrote:
> Hello,
>
> Could someone please explain why I am getting the error............
>
> skipping state transfer. No members active in cluster group
>
> On one sever the reciever is bound to
> 127.0.0.1:4002
> And on the other server the receiver is bound to 127.0.0.1:4001
>
> But both servers report -> no active members in cluster group
>
>
> 22-Apr-2024 10:19:06.726 INFO [main]
> org.apache.catalina.core.StandardService.startInternal Starting service
> [Station]
> 22-Apr-2024 10:19:06.727 INFO [main]
> org.apache.catalina.core.StandardEngine.startInternal Starting Servlet
> engine: [Apache Tomcat/10.1.20]
> 22-Apr-2024 10:19:06.736 INFO [main]
> org.apache.catalina.ha.tcp.SimpleTcpCluster.startInternal Cluster is about
> to start
> 22-Apr-2024 10:19:06.750 INFO [main]
> org.apache.catalina.tribes.transport.ReceiverBase.bind Receiver Server
> Socket bound to:[/127.0.0.1:4002]
> 22-Apr-2024 10:19:06.762 INFO [main]
> org.apache.catalina.tribes.membership.McastServiceImpl.setupSocket Setting
> cluster mcast soTimeout to [500]
> 22-Apr-2024 10:19:06.771 INFO [main]
> org.apache.catalina.tribes.membership.McastServiceImpl.waitForMembers
> Sleeping for [1000] milliseconds to establish cluster membership, start
> level:[4]
> 22-Apr-2024 10:19:07.771 INFO [main]
> org.apache.catalina.tribes.membership.McastServiceImpl.waitForMembers Done
> sleeping, membership established, start level:[4]
> 22-Apr-2024 10:19:07.773 INFO [main]
> org.apache.catalina.tribes.membership.McastServiceImpl.waitForMembers
> Sleeping for [1000] milliseconds to establish cluster membership, start
> level:[8]
> 22-Apr-2024 10:19:08.774 INFO [main]
> org.apache.catalina.tribes.membership.McastServiceImpl.waitForMembers Done
> sleeping, membership established, start level:[8]
> 22-Apr-2024 10:19:08.790 INFO [main]
> org.apache.catalina.ha.session.JvmRouteBinderValve.startInternal
> JvmRouteBinderValve started
> 22-Apr-2024 10:19:08.803 INFO [main]
> org.apache.catalina.startup.HostConfig.deployWAR Deploying web application
> archive [/home/web/servers/apache-tomcat-10.1.20/station/ROOT##0001.war]
> Apr 22, 2024 10:20:01 AM org.apache.catalina.util.SessionIdGeneratorBase
> createSecureRandom
> WARNING: Creation of SecureRandom instance for session ID generation using
> [SHA1PRNG] took [51,791] milliseconds.
> Apr 22, 2024 10:20:01 AM org.apache.catalina.ha.session.DeltaManager
> startInternal
> INFO: Register manager [##0001] to cluster element [Host] with name
> [station]
> Apr 22, 2024 10:20:01 AM org.apache.catalina.ha.session.DeltaManager
> startInternal
> INFO: Starting clustering manager at [##0001]
> Apr 22, 2024 10:20:01 AM org.apache.catalina.ha.session.DeltaManager
> getAllClusterSessions
> INFO: Manager [##0001]: skipping state transfer. No members active in
> cluster group.
>
>
> Here is how I have clustering set up on server one............
>
> <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"
> channelSendOptions="8">
>
> <Manager
> className="org.apache.catalina.ha.session.DeltaManager"
>
> expireSessionsOnShutdown="false"
>
> notifyListenersOnReplication="true"
>
> sessionAttributeNameFilter="uploader_redirect|phone_tree|soundhound.campaigndata|format|employee_id|customer|customer_id|nonidentifier_call_letters|call_letters|caller_id_enabled|ivr_system|ivr_system_id|zip_code|time_zone|is_trial_customer|delete_confirmation|download_settings|clustered_admin|wall_token|employee_first_name|logged_in_user|logged_in"
> />
>
> <Channel
> className="org.apache.catalina.tribes.group.GroupChannel">
>
> <Membership
> className="org.apache.catalina.tribes.membership.McastService"
> address="228.0.0.4"
> port="45565"
> frequency="500"
> dropTime="3000"/>
>
> <Receiver
> className="org.apache.catalina.tribes.transport.nio.NioReceiver"
> address="auto"
> port="4002"
> autoBind="100"
> selectorTimeout="5000"
> maxThreads="6"/>
>
> <Sender
> className="org.apache.catalina.tribes.transport.ReplicationTransmitter">
> <Transport
> className="org.apache.catalina.tribes.transport.nio.PooledParallelSender"/>
> </Sender>
>
> <Interceptor
> className="org.apache.catalina.tribes.group.interceptors.TcpFailureDetector"/>
> <Interceptor
> className="org.apache.catalina.tribes.group.interceptors.MessageDispatchInterceptor"/>
> <Interceptor
> className="org.apache.catalina.tribes.group.interceptors.ThroughputInterceptor"/>
>
> </Channel>
>
>
> On the other server I just changed the member ship to a different port
> port="45564"
> And reciver port to a different port also
> port="4002"
>
>
> In my application level web.xml on both servers I have included the needed
> tag
> <distributable />
>
> What am I missing here?
>
>
> Rick Noel
> Systems Programmer | Westwood One
> RNoel@westwoodone.com
>
>
--
Steven E. Carlsen
Superintendent
Box Elder School District
RE: [EXT]Re: [EXT]Re: [EXT]Re: Tomcat 10 skipping state transfer. No members active in cluster group
Posted by Rick Noel <RN...@westwoodone.com.INVALID>.
Chuck, to get rid of the warnings...........
3-Apr-2024 08:30:22.970 WARNING [Tribes-Task-Receiver[station-Channel]-1] org.apache.catalina.ha.session.ClusterSessionListener.messageReceived Context manager doesn't exist:[##0001]
I moved my Manager element form the server.xml to the context.xml
<Manager className="org.apache.catalina.ha.session.DeltaManager"
expireSessionsOnShutdown="false"
notifyListenersOnReplication="true" sessionAttributeNameFilter="uploader_redirect|phone_tree|soundhound.campaigndata|format|employee_id|customer|customer_id|nonidentifier_call_letters|call_letters|caller_id_enabled|ivr_system|ivr_system_id|zip_code|time_zone|is_trial_customer|delete_confirmation|download_settings|clustered_admin|wall_token|employee_first_name|logged_in_user|logged_in"
/>
That got rid of those warnings
But Now cat log shows these new warnings........
23-Apr-2024 09:19:16.288 WARNING [Tribes-Task-Receiver[station-Channel]-5] org.apache.catalina.ha.session.DeltaManager.deserializeSessions overload existing session [729421EC1DD658816E953C9A0DE4267A]
Do I need to configure something different? Some how allow more deserializeSessions?
23-Apr-2024 09:19:16.243 INFO [main] org.apache.catalina.ha.session.DeltaManager.startInternal Starting clustering manager at [##0001]
23-Apr-2024 09:19:16.246 INFO [main] org.apache.catalina.ha.session.DeltaManager.getAllClusterSessions Manager [##0001], requesting session state from [org.apache.catalina.tribes.membership.MemberImpl[tcp://{192, 168, 47, 157}:4001,{192, 168, 47, 157},4001, alive=3249463, securePort=-1, UDP Port=-1, id={-32 -57 -12 119 64 42 67 56 -69 51 -113 -64 -68 -78 -99 74 }, payload={}, command={}, domain={}]]. This operation will timeout if no session state has been received within [60] seconds.
23-Apr-2024 09:19:16.250 INFO [MessageDispatchInterceptor.MessageDispatchThread[station-Channel]1] org.apache.catalina.tribes.group.interceptors.ThroughputInterceptor.report ThroughputInterceptor Report[
Tx Msg:1 messages
Sent:0.00 MiB (total)
Sent:0.00 MiB (application)
Time:0.00 seconds
Tx Speed:0.15 MiB/s (total)
Tx Speed:0.15 MiB/s (application)
Error Msg:0
Rx Msg:10 messages
Rx Speed:0.00 MiB/s (since 1st msg)
Received:0.01 MiB]
23-Apr-2024 09:19:16.288 WARNING [Tribes-Task-Receiver[station-Channel]-5] org.apache.catalina.ha.session.DeltaManager.deserializeSessions overload existing session [729421EC1DD658816E953C9A0DE4267A]
23-Apr-2024 09:19:16.289 WARNING [Tribes-Task-Receiver[station-Channel]-5] org.apache.catalina.ha.session.DeltaManager.deserializeSessions overload existing session [A2196B2A82F1D0873769053130EA3E7A]
23-Apr-2024 09:19:16.290 WARNING [Tribes-Task-Receiver[station-Channel]-5] org.apache.catalina.ha.session.DeltaManager.deserializeSessions overload existing session [EDC2F576615781AD8CC138E8D8029EB9]
23-Apr-2024 09:19:16.296 WARNING [Tribes-Task-Receiver[station-Channel]-5] org.apache.catalina.ha.session.DeltaManager.deserializeSessions overload existing session [12A38E4D987184560911DC3C43A50410]
23-Apr-2024 09:19:16.354 INFO [main] org.apache.catalina.ha.session.DeltaManager.waitForSendAllSessions Manager [##0001]; session state sent at [4/23/24, 9:19 AM] received in [104] ms.
Rick Noel
Systems Programmer | Westwood One
RNoel@westwoodone.com
-----Original Message-----
From: Rick Noel
Sent: Tuesday, April 23, 2024 8:56 AM
To: Tomcat Users List <us...@tomcat.apache.org>
Cc: Voodoo nmulcahy gmail <nm...@gmail.com>; Rob Kowald <rk...@westwoodone.com>
Subject: RE: [EXT]Re: [EXT]Re: [EXT]Re: Tomcat 10 skipping state transfer. No members active in cluster group
Your suggestion worked Chuck, Thank you!
I now see this in cat log......
23-Apr-2024 08:30:10.969 INFO [Catalina-utility-1] org.apache.catalina.ha.tcp.SimpleTcpCluster.memberAdded Replication member added:[org.apache.catalina.tribes.membership.MemberImpl[tcp://{192, 168, 47, 157}:4001,{192, 168, 47, 157},4001, alive=304632, securePort=-1, UDP Port=-1, id={-32 -57 -12 119 64 42 67 56 -69 51 -113 -64 -68 -78 -99 74 }, payload={}, command={}, domain={}]]
INFO: Starting clustering manager at [##0001] Apr 23, 2024 8:30:46 AM org.apache.catalina.ha.session.DeltaManager getAllClusterSessions
INFO: Manager [##0001], requesting session state from [org.apache.catalina.tribes.membership.MemberImpl[tcp://{192, 168, 47, 157}:4001,{192, 168, 47, 157},4001, alive=340143, securePort=-1, UDP Port=-1, id={-32 -57 -12 119 64 42 67 56 -69 51 -113 -64 -68 -78 -99 74 }, payload={}, command={}, domain={}]]. This operation will timeout if no session state has been received within [60] seconds.
23-Apr-2024 08:30:46.492 INFO [MessageDispatchInterceptor.MessageDispatchThread[station-Channel]1] org.apache.catalina.tribes.group.interceptors.ThroughputInterceptor.report ThroughputInterceptor Report[
Tx Msg:1 messages
Sent:0.00 MiB (total)
Sent:0.00 MiB (application)
Time:0.00 seconds
Tx Speed:0.15 MiB/s (total)
Tx Speed:0.15 MiB/s (application)
Error Msg:0
Rx Msg:10 messages
Rx Speed:0.00 MiB/s (since 1st msg)
Received:0.01 MiB]
Apr 23, 2024 8:30:46 AM org.apache.catalina.ha.session.DeltaManager waitForSendAllSessions
INFO: Manager [##0001]; session state sent at [4/23/24, 8:30 AM] received in [104] ms.
But could you now explain why I get these new warnings........
3-Apr-2024 08:30:22.970 WARNING [Tribes-Task-Receiver[station-Channel]-1] org.apache.catalina.ha.session.ClusterSessionListener.messageReceived Context manager doesn't exist:[##0001]
23-Apr-2024 08:30:22.972 WARNING [Tribes-Task-Receiver[station-Channel]-2] org.apache.catalina.ha.session.ClusterSessionListener.messageReceived Context manager doesn't exist:[##0001]
23-Apr-2024 08:30:32.978 WARNING [Tribes-Task-Receiver[station-Channel]-4] org.apache.catalina.ha.session.ClusterSessionListener.messageReceived Context manager doesn't exist:[##0001]
23-Apr-2024 08:30:32.980 WARNING [Tribes-Task-Receiver[station-Channel]-3] org.apache.catalina.ha.session.ClusterSessionListener.messageReceived Context manager doesn't exist:[##0001]
23-Apr-2024 08:30:42.988 WARNING [Tribes-Task-Receiver[station-Channel]-5] org.apache.catalina.ha.session.ClusterSessionListener.messageReceived Context manager doesn't exist:[##0001]
23-Apr-2024 08:30:42.990 WARNING [Tribes-Task-Receiver[station-Channel]-6] org.apache.catalina.ha.session.ClusterSessionListener.messageReceived Context manager doesn't exist:[##0001] Apr 23, 2024 8:30:46 AM org.apache.catalina.util.SessionIdGeneratorBase createSecureRandom
WARNING: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [32,646] milliseconds.
Rick Noel
Systems Programmer | Westwood One
RNoel@westwoodone.com
-----Original Message-----
From: Chuck Caldarale <n8...@gmail.com>
Sent: Monday, April 22, 2024 10:08 PM
To: Tomcat Users List <us...@tomcat.apache.org>
Subject: [EXT]Re: [EXT]Re: [EXT]Re: Tomcat 10 skipping state transfer. No members active in cluster group
> On Apr 22, 2024, at 18:48, Rick Noel <RN...@westwoodone.com.INVALID> wrote:
>
> So you mean we use the VM's IP as the address value below........
> Instead or using the value of auto ?
>
> <Receiver className="org.apache.catalina.tribes.transport.nio.NioReceiver"
> address="auto"
> port="4001"
> autoBind="100"
> selectorTimeout="5000"
> maxThreads="6"/>
Correct. To quote from the Tomcat doc:
The IP broadcasted is java.net.InetAddress.getLocalHost().getHostAddress() (make sure you don't broadcast 127.0.0.1, this is a common error)
Unless the two JVMs are deployed on the same VM, you cannot use 127.0.0.1 and expect them to be able to communicate with each other.
Here's an old e-mail describing the issue and one way of addressing it:
https://marc.info/?l=tomcat-user&m=118764351104059&w=2
The gist of it is this:
1. check what name the command `hostname` spits out 2. make sure that /etc/hosts contains that hostname and IP address
This must be done on each VM, of course.
Returning localhost is typical for systems that use DHCP to obtain their IP addresses, such as my MacBook:
jshell> java.net.InetAddress.getLocalHost().getHostAddress();
$1 ==> "127.0.0.1"
- Chuck
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you know the sender and you are sure the content is safe. Please report the message using the Report Message feature in your email client if you believe the email is suspicious.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: [EXT]Re: [EXT]Re: [EXT]Re: Tomcat 10 skipping state transfer. No members active in cluster group
Posted by Rick Noel <RN...@westwoodone.com.INVALID>.
Your suggestion worked Chuck, Thank you!
I now see this in cat log......
23-Apr-2024 08:30:10.969 INFO [Catalina-utility-1] org.apache.catalina.ha.tcp.SimpleTcpCluster.memberAdded Replication member added:[org.apache.catalina.tribes.membership.MemberImpl[tcp://{192, 168, 47, 157}:4001,{192, 168, 47, 157},4001, alive=304632, securePort=-1, UDP Port=-1, id={-32 -57 -12 119 64 42 67 56 -69 51 -113 -64 -68 -78 -99 74 }, payload={}, command={}, domain={}]]
INFO: Starting clustering manager at [##0001]
Apr 23, 2024 8:30:46 AM org.apache.catalina.ha.session.DeltaManager getAllClusterSessions
INFO: Manager [##0001], requesting session state from [org.apache.catalina.tribes.membership.MemberImpl[tcp://{192, 168, 47, 157}:4001,{192, 168, 47, 157},4001, alive=340143, securePort=-1, UDP Port=-1, id={-32 -57 -12 119 64 42 67 56 -69 51 -113 -64 -68 -78 -99 74 }, payload={}, command={}, domain={}]]. This operation will timeout if no session state has been received within [60] seconds.
23-Apr-2024 08:30:46.492 INFO [MessageDispatchInterceptor.MessageDispatchThread[station-Channel]1] org.apache.catalina.tribes.group.interceptors.ThroughputInterceptor.report ThroughputInterceptor Report[
Tx Msg:1 messages
Sent:0.00 MiB (total)
Sent:0.00 MiB (application)
Time:0.00 seconds
Tx Speed:0.15 MiB/s (total)
Tx Speed:0.15 MiB/s (application)
Error Msg:0
Rx Msg:10 messages
Rx Speed:0.00 MiB/s (since 1st msg)
Received:0.01 MiB]
Apr 23, 2024 8:30:46 AM org.apache.catalina.ha.session.DeltaManager waitForSendAllSessions
INFO: Manager [##0001]; session state sent at [4/23/24, 8:30 AM] received in [104] ms.
But could you now explain why I get these new warnings........
3-Apr-2024 08:30:22.970 WARNING [Tribes-Task-Receiver[station-Channel]-1] org.apache.catalina.ha.session.ClusterSessionListener.messageReceived Context manager doesn't exist:[##0001]
23-Apr-2024 08:30:22.972 WARNING [Tribes-Task-Receiver[station-Channel]-2] org.apache.catalina.ha.session.ClusterSessionListener.messageReceived Context manager doesn't exist:[##0001]
23-Apr-2024 08:30:32.978 WARNING [Tribes-Task-Receiver[station-Channel]-4] org.apache.catalina.ha.session.ClusterSessionListener.messageReceived Context manager doesn't exist:[##0001]
23-Apr-2024 08:30:32.980 WARNING [Tribes-Task-Receiver[station-Channel]-3] org.apache.catalina.ha.session.ClusterSessionListener.messageReceived Context manager doesn't exist:[##0001]
23-Apr-2024 08:30:42.988 WARNING [Tribes-Task-Receiver[station-Channel]-5] org.apache.catalina.ha.session.ClusterSessionListener.messageReceived Context manager doesn't exist:[##0001]
23-Apr-2024 08:30:42.990 WARNING [Tribes-Task-Receiver[station-Channel]-6] org.apache.catalina.ha.session.ClusterSessionListener.messageReceived Context manager doesn't exist:[##0001]
Apr 23, 2024 8:30:46 AM org.apache.catalina.util.SessionIdGeneratorBase createSecureRandom
WARNING: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [32,646] milliseconds.
Rick Noel
Systems Programmer | Westwood One
RNoel@westwoodone.com
-----Original Message-----
From: Chuck Caldarale <n8...@gmail.com>
Sent: Monday, April 22, 2024 10:08 PM
To: Tomcat Users List <us...@tomcat.apache.org>
Subject: [EXT]Re: [EXT]Re: [EXT]Re: Tomcat 10 skipping state transfer. No members active in cluster group
> On Apr 22, 2024, at 18:48, Rick Noel <RN...@westwoodone.com.INVALID> wrote:
>
> So you mean we use the VM's IP as the address value below........
> Instead or using the value of auto ?
>
> <Receiver className="org.apache.catalina.tribes.transport.nio.NioReceiver"
> address="auto"
> port="4001"
> autoBind="100"
> selectorTimeout="5000"
> maxThreads="6"/>
Correct. To quote from the Tomcat doc:
The IP broadcasted is java.net.InetAddress.getLocalHost().getHostAddress() (make sure you don't broadcast 127.0.0.1, this is a common error)
Unless the two JVMs are deployed on the same VM, you cannot use 127.0.0.1 and expect them to be able to communicate with each other.
Here's an old e-mail describing the issue and one way of addressing it:
https://marc.info/?l=tomcat-user&m=118764351104059&w=2
The gist of it is this:
1. check what name the command `hostname` spits out 2. make sure that /etc/hosts contains that hostname and IP address
This must be done on each VM, of course.
Returning localhost is typical for systems that use DHCP to obtain their IP addresses, such as my MacBook:
jshell> java.net.InetAddress.getLocalHost().getHostAddress();
$1 ==> "127.0.0.1"
- Chuck
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you know the sender and you are sure the content is safe. Please report the message using the Report Message feature in your email client if you believe the email is suspicious.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: [EXT]Re: [EXT]Re: Tomcat 10 skipping state transfer. No members active in cluster group
Posted by Chuck Caldarale <n8...@gmail.com>.
> On Apr 22, 2024, at 18:48, Rick Noel <RN...@westwoodone.com.INVALID> wrote:
>
> So you mean we use the VM's IP as the address value below........
> Instead or using the value of auto ?
>
> <Receiver className="org.apache.catalina.tribes.transport.nio.NioReceiver"
> address="auto"
> port="4001"
> autoBind="100"
> selectorTimeout="5000"
> maxThreads="6"/>
Correct. To quote from the Tomcat doc:
The IP broadcasted is java.net.InetAddress.getLocalHost().getHostAddress() (make sure you don't broadcast 127.0.0.1, this is a common error)
Unless the two JVMs are deployed on the same VM, you cannot use 127.0.0.1 and expect them to be able to communicate with each other.
Here’s an old e-mail describing the issue and one way of addressing it:
https://marc.info/?l=tomcat-user&m=118764351104059&w=2
The gist of it is this:
1. check what name the command `hostname` spits out
2. make sure that /etc/hosts contains that hostname and IP address
This must be done on each VM, of course.
Returning localhost is typical for systems that use DHCP to obtain their IP addresses, such as my MacBook:
jshell> java.net.InetAddress.getLocalHost().getHostAddress();
$1 ==> "127.0.0.1"
- Chuck
RE: [EXT]Re: [EXT]Re: Tomcat 10 skipping state transfer. No members active in cluster group
Posted by Rick Noel <RN...@westwoodone.com.INVALID>.
Chuck,
So you mean we use the VM's IP as the address value below........
Instead or using the value of auto ?
<Receiver className="org.apache.catalina.tribes.transport.nio.NioReceiver"
address="auto"
port="4001"
autoBind="100"
selectorTimeout="5000"
maxThreads="6"/>
Rick Noel
Systems Programmer | Westwood One
RNoel@westwoodone.com
-----Original Message-----
From: Chuck Caldarale <n8...@gmail.com>
Sent: Monday, April 22, 2024 6:20 PM
To: Tomcat Users List <us...@tomcat.apache.org>
Subject: [EXT]Re: [EXT]Re: Tomcat 10 skipping state transfer. No members active in cluster group
> On Apr 22, 2024, at 16:33, Rick Noel <RN...@westwoodone.com.INVALID> wrote:
>
> Tomcats are two different VMs
Which explains why they can’t talk to each other over 127.0.0.1.
> What do you mean each containers published IP
Each VM or container will have an assigned, individual IP address so it can communicate with networks outside of the VM (eg, the host machine or real world). You must use each VM’s assigned IP address - not 127.0.0.1 - in the clustering configuration to allow the two VMs to communicate with each other.
- Chuck
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you know the sender and you are sure the content is safe. Please report the message using the Report Message feature in your email client if you believe the email is suspicious.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: [EXT]Re: Tomcat 10 skipping state transfer. No members active in cluster group
Posted by Chuck Caldarale <n8...@gmail.com>.
> On Apr 22, 2024, at 16:33, Rick Noel <RN...@westwoodone.com.INVALID> wrote:
>
> Tomcats are two different VMs
Which explains why they can’t talk to each other over 127.0.0.1.
> What do you mean each containers published IP
Each VM or container will have an assigned, individual IP address so it can communicate with networks outside of the VM (eg, the host machine or real world). You must use each VM’s assigned IP address - not 127.0.0.1 - in the clustering configuration to allow the two VMs to communicate with each other.
- Chuck
RE: [EXT]Re: Tomcat 10 skipping state transfer. No members active in cluster group
Posted by Rick Noel <RN...@westwoodone.com.INVALID>.
Rick Noel
Systems Programmer | Westwood One
RNoel@westwoodone.com
-----Original Message-----
From: Chuck Caldarale <n8...@gmail.com>
Sent: Monday, April 22, 2024 4:41 PM
To: Tomcat Users List <us...@tomcat.apache.org>
Subject: [EXT]Re: Tomcat 10 skipping state transfer. No members active in cluster group
> On Apr 22, 2024, at 09:54, Rick Noel <RN...@westwoodone.com.INVALID> wrote:
>
> Could someone please explain why I am getting the error............
>
> skipping state transfer. No members active in cluster group
Need a bit more information.
> On one sever the reciever is bound to 127.0.0.1:4002
> And on the other server the receiver is bound to 127.0.0.1:4001
Are both Tomcat instances running on the same system (VM or real)?
Tomcats are two different VMs
> But both servers report -> no active members in cluster group
Indicates they can’t see each other, so they could be on different systems or in separate VMs (containers).
> Apr 22, 2024 10:20:01 AM org.apache.catalina.util.SessionIdGeneratorBase createSecureRandom
> WARNING: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [51,791] milliseconds.
This long random ID generation is typical for a low-entropy VM or container rather than a real system. If the two Tomcats are in separate containers, you’ll have to configure clustering to use each container’s published IP address rather than assuming they can share the same loopback network.
What do you mean each containers published IP
- Chuck
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you know the sender and you are sure the content is safe. Please report the message using the Report Message feature in your email client if you believe the email is suspicious.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 10 skipping state transfer. No members active in cluster group
Posted by Chuck Caldarale <n8...@gmail.com>.
> On Apr 22, 2024, at 09:54, Rick Noel <RN...@westwoodone.com.INVALID> wrote:
>
> Could someone please explain why I am getting the error............
>
> skipping state transfer. No members active in cluster group
Need a bit more information.
> On one sever the reciever is bound to 127.0.0.1:4002
> And on the other server the receiver is bound to 127.0.0.1:4001
Are both Tomcat instances running on the same system (VM or real)?
> But both servers report -> no active members in cluster group
Indicates they can’t see each other, so they could be on different systems or in separate VMs (containers).
> Apr 22, 2024 10:20:01 AM org.apache.catalina.util.SessionIdGeneratorBase createSecureRandom
> WARNING: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [51,791] milliseconds.
This long random ID generation is typical for a low-entropy VM or container rather than a real system. If the two Tomcats are in separate containers, you’ll have to configure clustering to use each container’s published IP address rather than assuming they can share the same loopback network.
- Chuck
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org