Re: Operation has timed out

2017-02-09 18:45 GMT+09:00 Fady Haikal : > i will try that but this required tomcat restart so i will be > scheduling tonight a restart, anyway from where i can enable the > org.apache.catalina.tribes.MESSAGES i didn't found it in the > logging.properties file > The

Re: Operation has timed out

2017-02-09 19:21 GMT+09:00 Fady Haikal : > i already restarted it after changing the parameter to 8 > However, I can not see the log that context has been restarted in the log you showed. You may need to restart Tomcat. > > On Thu, Feb 9, 2017 at 12:16 PM, Keiichi Fujino

Re: Operation has timed out

i already restarted it after changing the parameter to 8 On Thu, Feb 9, 2017 at 12:16 PM, Keiichi Fujino wrote: > It is realy strange. > Have you failed to restart Context? > When starting up the AbstractReplicatedMap, the followings should be logged. > > "Initializing

Re: Operation has timed out

It is realy strange. Have you failed to restart Context? When starting up the AbstractReplicatedMap, the followings should be logged. "Initializing AbstractReplicatedMap with context name:xxx" "AbstractReplicatedMap[xxx] initialization was completed in xxx ms." 2017-02-09 19:09 GMT+09:00 Fady

Re: Operation has timed out

i can only see this error related to AbstractReplicatedMap 09-Feb-2017 12:44:12.676 SEVERE [GroupChannel-Heartbeat-1] org.apache.catalina.tribes.tipis.AbstractReplicatedMap.heartbeat Unable to send AbstractReplicatedMap.ping message java.lang.NullPointerException at

Re: Operation has timed out

Let's not mix issues here. 1) your Host entry is that means that Tomcat will automatically reload any application when it notices that it has been changed. 2) the parameter you changed is in the application's context, so the application has been changed 3) to reload the application,

Re: Operation has timed out

These logs seem to be the tomcat memory leak detections logs during context restart. It is a different issue from this thread's topic. Anyway, Can you see the log likea "AbstractReplicatedMap[xxx] initialization was completed in xxx ms." in your log file? 2017-02-09 18:49 GMT+09:00 Fady Haikal

Re: Operation has timed out

Keiichi, once i changed the mapSendOptions and without restarting the below shown in the tomcat 09-Feb-2017 12:44:12.299 SEVERE [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application

Re: Operation has timed out

i will try that but this required tomcat restart so i will be scheduling tonight a restart, anyway from where i can enable the org.apache.catalina.tribes.MESSAGES i didn't found it in the logging.properties file On Thu, Feb 9, 2017 at 11:40 AM, Keiichi Fujino wrote: > Hi > >

Re: Operation has timed out

Hi Please try mapSendOptions = 8. This means that it does not receive ACK of the messages. Processing is returned immediately after message transmission is completed. As another way, Please try the org.apache.catalina.tribes.MESSAGES. (see previous my response mail.) 2017-02-09 18:23

Re: Operation has timed out

The is set under the context.xml On Thu, Feb 9, 2017 at 11:21 AM, Keiichi Fujino wrote: > 2017-02-09 18:10 GMT+09:00 Fady Haikal : > >> Keiichi, >> mapSendoption is not configured anyway please check my configuration below >> > > > You have not set .

Re: Operation has timed out

2017-02-09 18:10 GMT+09:00 Fady Haikal : > Keiichi, > mapSendoption is not configured anyway please check my configuration below > You have not set . If you do not use Cluster Manager template, DeltaManager is used by default. However, in the logs, it seems to be using

Re: Operation has timed out

Keiichi, mapSendoption is not configured anyway please check my configuration below

Re: Operation has timed out

Hi You seems to be using BackupManager. What is set for mapSendOptions? The Cluster module uses the Tomcat JULI logging FW, so you can enable logging on the org.apache.catalina.tribes.MESSAGES, you can track messages. Note for using the org.apache.catalina.tribes.MESSAGES: The

Re: Operation has timed out

Ashwin, I tried changing the port but unfortunately i'm still facing the same error On Wed, Feb 8, 2017 at 4:44 PM, ashwin rajput wrote: > Hi Fady, > > can you please try changing default Multicast port to something like : > From port="45564" > to port="45562" or

Re: Operation has timed out

Hi Fady, can you please try changing default Multicast port to something like : >From port="45564" to port="45562" or port="45560". let me know the outcome will try to fix it and please make sure if you have firewall enable on system please disable it first and then give a try otherwise you have

Re: Operation has timed out

Hi All, As u know we are using 224.0.0.4 multicast IP for tomcat cluster (Node1: 10.114.43.102 / Node2: 10.114.43.103) i was trying to ping the multicast IP i get reply from 10.114.43.51 IP! Also i have executed the nslookup for 224.0.0.4 i get the DC IP (10.114.43.7) and mcast.net domain:

Re: Operation has timed out

Ashwin, I'm using the below configuration, please let me know how i can check if i'm using a unique multicast address and port On Wed, Feb 8, 2017 at 6:39 AM, ashwin rajput wrote: > I am not sure if anyone has verified below. > > Have

Re: Operation has timed out

I am not sure if anyone has verified below. Have you verifyed clustering is using unique multicast address and port. Cluster multicast address should be unique and not used by any other cluster. Regards, Ashwin On 07-Feb-2017 10:38 pm, "André Warnier (tomcat)" wrote: > On

Re: Operation has timed out

On 07.02.2017 17:20, Fady Haikal wrote: Christopher, For the first time @Christopher : just to make sure you got that bit, buried below : the actual replication seems to work fine. The problem is only these "unsuccesful ping" messages in the log, which fill the log, and which so far nobody

Re: Operation has timed out

Christopher, For the first time On Tue, Feb 7, 2017 at 6:19 PM, Christopher Schultz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Fady, > > On 2/7/17 10:53 AM, Fady Haikal wrote: >> ProcessPID Protocol local address local port >> Remote

Re: Operation has timed out

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Fady, On 2/7/17 10:53 AM, Fady Haikal wrote: > ProcessPID Protocol local address local port > Remote Address State Tomcat8.exe 8160 TCP > imal14-app24000 imal14-app1.albaraka.com.sdESTABLISHED Stupid

Re: Operation has timed out

ProcessPID Protocol local address local port Remote Address State Tomcat8.exe 8160 TCP imal14-app24000 imal14-app1.albaraka.com.sdESTABLISHED On Tue, Feb 7, 2017 at 5:46 PM, Fady Haikal wrote: > Yes there is a

Re: Operation has timed out

Yes there is a ESTABLISHED connection, the replication of sessions is working fine (port 4000 is for tomcat cluster) but we also faced this error on the log file On Tue, Feb 7, 2017 at 5:44 PM, André Warnier (tomcat) wrote: > On 07.02.2017 16:24, Fady Haikal wrote: >> >> Hi, >>

Re: Operation has timed out

On 07.02.2017 16:24, Fady Haikal wrote: Hi, telnet IP 4000 is working fine, i installed a tool for network monitoring at the level of IP and Port and i didnt see any disconnection, but did you see a *connection* ? I mean, on the pinging node, if you use the Windows "netstat" program, for

Re: Operation has timed out

Hi, telnet IP 4000 is working fine, i installed a tool for network monitoring at the level of IP and Port and i didnt see any disconnection, and yes i'm sure that no firewall is enabled. I saw some strange think on the server that I have tried to ping the multicast IP (228.0.0.4) and i get reply

Re: Operation has timed out

Hi. This is for the Tomcat/Tribes experts on the list. I know nothing of Tribes, but the on-line documentation seems to say that the communication happens over TCP and that the protocol used is not encrypted. Fady previously tried a standard "ping" and a "telnet" between the two nodes, and

Re: Operation has timed out

Hi, issue still not fixed. Tomcat session replication is not able to replicate the key from node to node, please find below the error, taking into consideration that there is no network disconnection between 2 nodes 07-Feb-2017 16:36:06.186 SEVERE [http-nio-8080-exec-8]

Re: Operation has timed out

below is the server.xml configuration, as mentioened earlier the issue is related to the cluster configuration, and as per my research i can see that some users are facing the same issue but i didnt found the solution of it

Re: Operation has timed out

On 06.02.2017 17:45, Fady Haikal wrote: Hi, What is the host OS ? Windows Server 2012 What is the Tomcat version ? Apache Tomcat/8.0.30 Is this problem new ? was this working before ? how long ? Since cluster implementation I still don't know tribes, but then my non-educated guess at this

Re: Operation has timed out

Hi, What is the host OS ? Windows Server 2012 What is the Tomcat version ? Apache Tomcat/8.0.30 Is this problem new ? was this working before ? how long ? Since cluster implementation Is there actually something listening on that address/port ? Tomcat cluster the Port 4000 is listening and

Re: Operation has timed out

On 06.02.2017 17:24, Fady Haikal wrote: Plz can i get some help here? This issue is still occurring and it's filling the log file in the Production server Regards, Fady Hi. If you want quick answers, you should provide more information. What is the host OS ? What is the Tomcat version ? Is

Re: Operation has timed out

Plz can i get some help here? This issue is still occurring and it's filling the log file in the Production server Regards, Fady On Mon, Feb 6, 2017 at 8:52 AM, Fady Haikal wrote: > Guys, we are facing the below errors in Tomcat cluster, please advise > > > 06-Feb-2017

Re: Operation has timed out(3000 ms.).;

I have set it as below. However, still it is showing the same error. Please let me know what to do as our all tomcats are going on high load because of this kind of continuous logging. If there is any change required let us know. ERROR logging: *SEVERE: Unable to send message through cluster

Re: Operation has timed out(3000 ms.).;

take a look at the Sender timeout=... .../ attribute http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-sender.html - Original Message - From: Dhaval Jaiswal dhaval.jais...@via.com To: Tomcat Users List users@tomcat.apache.org Sent: Wednesday, March 21, 2012 10:35:14 PM