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
rn...@westwoodone.com

-----Original Message-----
From: Chuck Caldarale <n82...@gmail.com>
Sent: Monday, April 22, 2024 10:08 PM
To: Tomcat Users List <users@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-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to