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

Tomcat 7.0.xx under Java 7?

Ladies and Gentlemen of the Tomcat List: To date, the overwhelming bulk of our own Tomcat experience has been under Java 6 JVMs. And we have a customer who will likely be losing that JVM soon. Are there any "gotchas" running 7.0.47 or later under Java 7? -- James H. H. Lampert Touchtone

Re: Apache Tomcat 7.0.59 - Even if a ws certificate stored in the WSkeystore expires, any webclient request is still accepted by server and not refused

On 07/02/17 19:33, George Stanchev wrote: Mark, Apologies for top posting. We have our own trust manager that is attached to the connector because we want client certificates to be passed in the application for validation and authentication rather than the connector. If we switch to the

RE: Apache Tomcat 7.0.59 - Even if a ws certificate stored in the WSkeystore expires, any webclient request is still accepted by server and not refused

Mark, Apologies for top posting. We have our own trust manager that is attached to the connector because we want client certificates to be passed in the application for validation and authentication rather than the connector. If we switch to the OpenSSL/APR based certificate processing, would

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]

AW: Operation has timed out

Fady, Sorry for top posting. If I remember correctly, the Cluster Element goes into the Container and not the Host. Plus I see in our (working) case, a DeltaManager and a JvmRouteSessionIDBinderListener ... Besides this, only ports, limits and values are different. You may