Re: Operation has timed out

[ashwin rajput]

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 to change firewall configuration to allow
multicast traffic.

Regards,
Ashwin

On Wed, Feb 8, 2017 at 12:56 PM, Fady Haikal <fadyhai...@gmail.com> wrote:

> 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:
>
> C:\Users\Administrator>nslookup 224.0.0.4
> Server:  hq-dc02.albaraka.com.sd
> Address:  10.114.43.7
>
> Name:dvmrp.mcast.net
> Address:  224.0.0.4
>
> On Wed, Feb 8, 2017 at 8:59 AM, Fady Haikal <fadyhai...@gmail.com> wrote:
> > 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
> >
> >
> > 
> >  > className="org.apache.catalina.tribes.membership.McastService"
> > address="228.0.0.4"
> > port="45564"
> > frequency="500"
> > dropTime="9000"/>
> >  > className="org.apache.catalina.tribes.transport.nio.NioReceiver"
> >       address="auto"
> >   port="4000"
> >   autoBind="100"
> >   selectorTimeout="5000"
> >   maxThreads="6"/>
> >
> > On Wed, Feb 8, 2017 at 6:39 AM, ashwin rajput <ash271...@gmail.com>
> wrote:
> >> 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)" <a...@ice-sa.com>
> wrote:
> >>
> >>> 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 has managed to find an explanation for.
> >>>
> >>>
> >>>> On Tue, Feb 7, 2017 at 6:19 PM, Christopher Schultz
> >>>> <ch...@christopherschultz.net> 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 Address  State Tomcat8.exe 8160 TCP
> >>>>>> imal14-app24000 imal14-app1.albaraka.com.sdESTABLISHED
> >>>>>>
> >>>>>
> >>>>> Stupid question: was this working in the past, and it stopped
> working?
> >>>>> Or are you trying to get this working for the first time?
> >>>>>
> >>>>> - -chris
> >>>>>
> >>>>> On Tue, Feb 7, 2017 at 5:46 PM, Fady Haikal <fadyhai...@gmail.com>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> 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)
> >>>>>>> <a...@ice-sa.com> wrote:
> >>>>>>>
> >>>>>>>> On 07.02.2017 16:24, Fady Haikal wrote:
> >>>>>>>>
> >>&g

Re: Operation has timed out

[ashwin rajput]

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 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 has managed to find an explanation for.
>
>
>> 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 Address  State Tomcat8.exe 8160 TCP
 imal14-app24000 imal14-app1.albaraka.com.sdESTABLISHED

>>>
>>> Stupid question: was this working in the past, and it stopped working?
>>> Or are you trying to get this working for the first time?
>>>
>>> - -chris
>>>
>>> On Tue, Feb 7, 2017 at 5:46 PM, Fady Haikal 
 wrote:

> 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, 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 example as
>> netstat -aon -p TCP you should see a list of connections in the
>> ESTABLISHED state, of which one of the IP/ports should be your
>> target IP:4000 (in the "remote" column). And on the pinged
>> node, this port :4000 should be in the "local" column, in
>> LISTEN mode (and also probably one in the ESTABLISHED state, if
>> they agree.)
>>
>> Is that the case ?
>>
>>
>>
>> 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 from
>>> different IPs in the network, i don't know why and how i get
>>> those IPs, after checking with the network team they told me
>>> that those IPs are related to the SAN storage taking into
>>> consideration that the Tomcat servers are not connected in
>>> anyway to that SUN storage.
>>>
>>>
>>> On Tue, Feb 7, 2017 at 4:51 PM, André Warnier (tomcat)
>>>  wrote:
>>>

 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 that is the base for him mentioning that "there
 is no network disconnection" between the nodes.
 Nevertheless, the calling pinging node seems to say that it
 times out without getting a response fom the target node.
 There is evidently a contradiction there. So this could
 still be some kind of network issue.

 Considering that the protocol command for this "ping"
 should be known by someone here, would it not be possible
 to imagine a little program in some scripting language (or
 even java, God forbid), which would open a TCP channel with
 the target node IP/port, send such a "ping" message, wait
 for a response and report the result ? That would at least
 confirm/deny that the problem is with the network.

 The log below does not for example say if the error happens
 when opening the TCP communication channel, or after
 sending the ping message on it, (Of course, testing the TCP
 open could be done with "telnet IP 4000", but I don't know
 if Fady tried this). Maybe tribes also already contains
 some löw-level debugging options ? wireshark maybe another
 option, but it has quite a learning curve. And this is on
 Windows.

 By the way Fady, are you sure that your "Windows Firewall
 with Enhanced Security" is not just dropping TCP packets
 to/from port 40xx (or from "java.exe") ? There are some
 "network policies" there which can have 

Re: Error in Tomcat 6.0.32

[ashwin rajput]

Shailesh,

increase heap size of your JVM instance and try again.

Regards,
Ashwin

On Tue, May 31, 2016 at 7:25 PM, André Warnier (tomcat) 
wrote:

> Now really ?
> What do you not understand in
>
> > java.lang.OutOfMemoryError: Java heap space
>
> ?
>
>
>
> On 31.05.2016 15:35, Shailesh Jain wrote:
>
>> Hello All,
>> Below is the error coming in tomcat6, can you pleaes advise what can be
>> done to resolve the issue.
>> SEVERE: Servlet.service() for servlet ComponentDispatcher threw exception
>> java.lang.OutOfMemoryError: Java heap space
>> May 27, 2016 11:27:58 AM org.apache.catalina.core.StandardWrapperValve
>> invoke
>> SEVERE: Servlet.service() for servlet jsp threw exception
>> java.lang.OutOfMemoryError: Java heap space
>> May 27, 2016 11:33:36 AM org.apache.catalina.core.StandardWrapperValve
>> invoke
>> SEVERE: Servlet.service() for servlet Redirect threw exception
>> java.lang.IllegalStateException
>>  at
>> org.apache.catalina.connector.ResponseFacade.sendError(ResponseFacade.java:407)
>>  at com.suncor.redirect.Redirect.doGet(Redirect.java:175)
>>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>>  at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>>  at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>>  at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>>  at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>>  at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>>  at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>>  at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>>  at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>>  at
>> org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:864)
>>  at
>> org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:579)
>>  at org.apache.tomcat.util.net
>> .AprEndpoint$Worker.run(AprEndpoint.java:1665)
>>  at java.lang.Thread.run(Thread.java:662)  Thanks Shailesh jain
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>