Fwd: Failed to stop component [StandardEngine[Catalina].StandardHost[localhost]
We can see the below error on the log file please advise: OS: windows Tomcat Version: 8.0.30 Cluster Tomcat 30-Nov-2016 08:32:21.197 SEVERE [Catalina-startStop-2] org.apache.catalina.core.ContainerBase.stopInternal A child container failed during stop java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to stop component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]] at java.util.concurrent.FutureTask.report(Unknown Source) at java.util.concurrent.FutureTask.get(Unknown Source) at org.apache.catalina.core.ContainerBase.stopInternal(ContainerBase.java:972) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) at org.apache.catalina.core.ContainerBase$StopChild.call( ContainerBase.java:1424) at org.apache.catalina.core.ContainerBase$StopChild.call( ContainerBase.java:1413) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.apache.catalina.LifecycleException: Failed to stop component [StandardEngine[Catalina].StandardHost[localhost]. StandardContext[]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) ... 6 more Caused by: org.apache.catalina.LifecycleException: Failed to stop component [WebappLoader[]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.core.StandardContext.stopInternal( StandardContext.java:5517) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 6 more Caused by: java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(Unknown Source) at java.util.HashMap$ValueIterator.next(Unknown Source) at org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesRmiTargets( WebappClassLoaderBase.java:2275) at org.apache.catalina.loader.WebappClassLoaderBase.clearReferences( WebappClassLoaderBase.java:1578) at org.apache.catalina.loader.WebappClassLoaderBase.stop( WebappClassLoaderBase.java:1521) at org.apache.catalina.loader.WebappLoader.stopInternal(WebappLoader.java:447) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 8 more 30-Nov-2016 08:32:21.354 SEVERE [Catalina-startStop-2] org.apache.catalina.core.ContainerBase.stopInternal A child container failed during stop java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to stop component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/docs]] at java.util.concurrent.FutureTask.report(Unknown Source) at java.util.concurrent.FutureTask.get(Unknown Source) at org.apache.catalina.core.ContainerBase.stopInternal( ContainerBase.java:972) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) at org.apache.catalina.core.ContainerBase$StopChild.call( ContainerBase.java:1424) at org.apache.catalina.core.ContainerBase$StopChild.call( ContainerBase.java:1413) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.apache.catalina.LifecycleException: Failed to stop component [StandardEngine[Catalina].StandardHost[localhost]. StandardContext[/docs]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) ... 6 more Caused by: org.apache.catalina.LifecycleException: Failed to stop component [WebappLoader[/docs]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.core.StandardContext.stopInternal( StandardContext.java:5517) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 6 more Caused by: java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(Unknown Source) at java.util.HashMap$ValueIterator.next(Unknown Source) at org.apache.catalina.loader.WebappClassLoaderBase. clearReferencesRmiTargets(WebappClassLoaderBase.java:2275) at org.apache.catalina.loader.WebappClassLoaderBase.clearReferences( WebappClassLoaderBase.java:1578) at org.apache.catalina.loader.WebappClassLoaderBase.stop( WebappClassLoaderBase.java:1521) at org.apache.catalina.loader.WebappLoader.stopInternal( WebappLoader.java:447) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 8 more Regards, Fady
Re: Fwd: Failed to stop component [StandardEngine[Catalina].StandardHost[localhost]
Dear Mark, is this bug is fixed in any version? Regards, Fady On Thu, Dec 22, 2016 at 10:22 PM, Mark Thomas wrote: > On 22/12/2016 15:46, Fady Haikal wrote: >> We can see the below error on the log file please advise: > > You are using multiple start/start threads and the RMI reference > cleaning isn't thread safe. Arguably that is a bug in Tomcat but if you > fix the RMI memory leaks in your application you won't hit the Tomcat bug. > > Mark > > >> >> OS: windows >> Tomcat Version: 8.0.30 >> Cluster Tomcat >> >> 30-Nov-2016 08:32:21.197 SEVERE [Catalina-startStop-2] >> org.apache.catalina.core.ContainerBase.stopInternal A child container >> failed during stop >> >> java.util.concurrent.ExecutionException: >> org.apache.catalina.LifecycleException: Failed to stop component >> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]] >> >> at java.util.concurrent.FutureTask.report(Unknown Source) >> >> at java.util.concurrent.FutureTask.get(Unknown Source) >> >> at >> org.apache.catalina.core.ContainerBase.stopInternal(ContainerBase.java:972) >> >> at >> org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) >> >> at >> org.apache.catalina.core.ContainerBase$StopChild.call( >> ContainerBase.java:1424) >> >> at >> org.apache.catalina.core.ContainerBase$StopChild.call( >> ContainerBase.java:1413) >> >> at java.util.concurrent.FutureTask.run(Unknown Source) >> >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) >> >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) >> >> at java.lang.Thread.run(Unknown Source) >> >> Caused by: org.apache.catalina.LifecycleException: Failed to stop >> component [StandardEngine[Catalina].StandardHost[localhost]. >> StandardContext[]] >> >> at >> org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) >> >> ... 6 more >> >> Caused by: org.apache.catalina.LifecycleException: Failed to stop >> component [WebappLoader[]] >> >> at >> org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) >> >> at >> org.apache.catalina.core.StandardContext.stopInternal( >> StandardContext.java:5517) >> >> at >> org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) >> >> ... 6 more >> >> Caused by: java.util.ConcurrentModificationException >> >> at java.util.HashMap$HashIterator.nextEntry(Unknown Source) >> >> at java.util.HashMap$ValueIterator.next(Unknown Source) >> >> at >> org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesRmiTargets( >> WebappClassLoaderBase.java:2275) >> >> at >> org.apache.catalina.loader.WebappClassLoaderBase.clearReferences( >> WebappClassLoaderBase.java:1578) >> >> at >> org.apache.catalina.loader.WebappClassLoaderBase.stop( >> WebappClassLoaderBase.java:1521) >> >> at >> org.apache.catalina.loader.WebappLoader.stopInternal(WebappLoader.java:447) >> >> at >> org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) >> >> ... 8 more >> >> >> >> >> 30-Nov-2016 08:32:21.354 SEVERE [Catalina-startStop-2] >> org.apache.catalina.core.ContainerBase.stopInternal A child container >> failed during stop >> java.util.concurrent.ExecutionException: >> org.apache.catalina.LifecycleException: Failed to stop component >> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/docs]] >> at java.util.concurrent.FutureTask.report(Unknown Source) >> at java.util.concurrent.FutureTask.get(Unknown Source) >> at org.apache.catalina.core.ContainerBase.stopInternal( >> ContainerBase.java:972) >> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) >> at org.apache.catalina.core.ContainerBase$StopChild.call( >> ContainerBase.java:1424) >> at org.apache.catalina.core.ContainerBase$StopChild.call( >> ContainerBase.java:1413) >> at java.util.concurrent.FutureTask.run(Unknown Source) >> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) >> at
User session is not replicated to second node
Dear Team, In case of cluster, user session was not replicated to the second node in case of failover until we have moved the below configuration from server.xml to context.xml, please advise if this is the solution or we have any other solution Regards, Fady - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Fwd: User session is not replicated to second node
Dear Team, In case of cluster, user session was not replicated to the second node in case of failover until we have moved the below configuration from server.xml to context.xml, please advise if this is the solution or we have any other solution Regards, Fady - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Cannot Allocate Memory errno=12
Guys, We are facing the below error (attached also) while trying to shutdown tomcat server Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0xd555, 715849728, 0) failed; error='Cannot allocate memory' (errno=12) # # There is insufficient memory for the Java Runtime Environment to continue. # Native memory allocation (mmap) failed to map 715849728 bytes for committing reserved memory. # An error report file with more information is saved as: # /home/Jakob/Apps/Botlanegg/hs_err_pid40075.log Server Memory is 14 GB Tomcat allocate 10 GB Attached setenv.sh Please advise Regards, Fady setenv.sh Description: Bourne shell script - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Cannot Allocate Memory errno=12
Yes log already sent, anw attached On Wed, Jan 18, 2017 at 3:07 PM, André Warnier (tomcat) wrote: > On 18.01.2017 13:49, Fady Haikal wrote: >> >> Guys, We are facing the below error (attached also) while trying to >> shutdown tomcat server >> >> Java HotSpot(TM) 64-Bit Server VM warning: INFO: >> os::commit_memory(0xd555, 715849728, 0) failed; >> error='Cannot allocate memory' (errno=12) >> # >> # There is insufficient memory for the Java Runtime Environment to >> continue. >> # Native memory allocation (mmap) failed to map 715849728 bytes for >> committing reserved memory. >> # An error report file with more information is saved as: >> # /home/Jakob/Apps/Botlanegg/hs_err_pid40075.log >> >> Server Memory is 14 GB >> Tomcat allocate 10 GB >> Attached setenv.sh >> >> Please advise >> >> Regards, >> Fady >> > > And does the above-mentioned error report file contain more information, as > it seems to promise ? > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Cannot Allocate Memory errno=12
plz find it on the below link https://drive.google.com/file/d/0By0Z6xkBVBFHVGJKVkRqM2hwUVE/view?usp=sharing On Wed, Jan 18, 2017 at 3:16 PM, André Warnier (tomcat) wrote: > On 18.01.2017 14:08, Fady Haikal wrote: >> >> Yes log already sent, anw attached > > > Well no. Only the "setenv.sh" was attached. > This list server strips many attachments. Maybe you need to paste the > content directly into your message (if not too long), or post it somewhere > where we can look at it. > > > >> >> On Wed, Jan 18, 2017 at 3:07 PM, André Warnier (tomcat) >> wrote: >>> >>> On 18.01.2017 13:49, Fady Haikal wrote: >>>> >>>> >>>> Guys, We are facing the below error (attached also) while trying to >>>> shutdown tomcat server >>>> >>>> Java HotSpot(TM) 64-Bit Server VM warning: INFO: >>>> os::commit_memory(0xd555, 715849728, 0) failed; >>>> error='Cannot allocate memory' (errno=12) >>>> # >>>> # There is insufficient memory for the Java Runtime Environment to >>>> continue. >>>> # Native memory allocation (mmap) failed to map 715849728 bytes for >>>> committing reserved memory. >>>> # An error report file with more information is saved as: >>>> # /home/Jakob/Apps/Botlanegg/hs_err_pid40075.log >>>> >>>> Server Memory is 14 GB >>>> Tomcat allocate 10 GB >>>> Attached setenv.sh >>>> >>>> Please advise >>>> >>>> Regards, >>>> Fady >>>> >>> >>> And does the above-mentioned error report file contain more information, >>> as >>> it seems to promise ? >>> >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: users-h...@tomcat.apache.org >>> >> >> >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Cannot Allocate Memory errno=12
Thank You Andre so much will check the below now On Wed, Jan 18, 2017 at 4:10 PM, André Warnier (tomcat) wrote: > On 18.01.2017 14:51, André Warnier (tomcat) wrote: >> >> Actually, I think that you need to look closer at the tomcat shutdown >> scripts on your >> system, and their settings. >> If I remember correctly, when you call the tomcat shutdown script, it >> actually starts >> another java JVM instance, just to send a shutdown message to the running >> tomcat's JVM. >> And with your current JAVA_OPTS, it looks like this shutdown JVM is also >> requesting a Java >> heap with an initial size of 8 GB. And that is what may trigger this OOM. >> There is something in that area about the difference between JAVA_OPTS and >> CATALINA_OPTS. >> > > Additional information : > (I have now found it again) > > Somewhere in your tomcat software directory (which may be anywhere, > depending on where you got this tomcat from), there is a file named > "RUNNING.txt". > In this file is a section which I copy below here, in case you are having > trouble finding it. It explains what happens with these JAVA_OPTS and > CATALINA_OPTS environment variables. In particular the last paragraph. > > > quote > ... > > (3.3) Other variables (optional) > > Other environment variables exist, besides the four described above. > See the comments at the top of catalina.bat or catalina.sh scripts for > the list and a description of each of them. > > One frequently used variable is CATALINA_OPTS. It allows specification of > additional options for the java command that starts Tomcat. > > See the Java documentation for the options that affect the Java Runtime > Environment. > > See the "System Properties" page in the Tomcat Configuration Reference for > the system properties that are specific to Tomcat. > > A similar variable is JAVA_OPTS. It is used less frequently. It allows > specification of options that are used both to start and to stop Tomcat as > well > as for other commands. > > Note: Do not use JAVA_OPTS to specify memory limits. You do not need much > memory for a small process that is used to stop Tomcat. Those settings > belong to CATALINA_OPTS. > > > unquote > > > > >> >> On 18.01.2017 14:31, André Warnier (tomcat) wrote: >>> >>> On 18.01.2017 14:20, Fady Haikal wrote: >>>> >>>> plz find it on the below link >>>> >>>> >>>> https://drive.google.com/file/d/0By0Z6xkBVBFHVGJKVkRqM2hwUVE/view?usp=sharing >>> >>> >>> Hmm, that's a nice logfile. >>> It also starts with a number of hints and recommendations, did you see ? >>> >>> Very generically : >>> When tomcat is shutting down, it does need some extra memory for a while, >>> to run the >>> shutdown processes (in addition to the other processes which are >>> running). >>> So it asks the Java JVM for more memory. >>> And then the java JVM asks the OS for that extra memory. >>> And in your case, it does not get it, because the OS is telling it that >>> there is no more >>> available memory. So the JVM crashes. >>> Now why there is no more memory available at that time, is mostly for you >>> to find out. >>> There are certainly other processes running on that server, in addition >>> to tomcat's java >>> JVM. They use memory too. >>> >>> And otherwise, either you need a bigger system, or you need smaller >>> applications. >>> >>>> >>>> On Wed, Jan 18, 2017 at 3:16 PM, André Warnier (tomcat) >>>> wrote: >>>>> >>>>> On 18.01.2017 14:08, Fady Haikal wrote: >>>>>> >>>>>> >>>>>> Yes log already sent, anw attached >>>>> >>>>> >>>>> >>>>> Well no. Only the "setenv.sh" was attached. >>>>> This list server strips many attachments. Maybe you need to paste the >>>>> content directly into your message (if not too long), or post it >>>>> somewhere >>>>> where we can look at it. >>>>> >>>>> >>>>> >>>>>> >>>>>> On Wed, Jan 18, 2017 at 3:07 PM, André Warnier (tomcat) >>>>>> >>>>>> wrote: >>>>>>> >>>>>>> >>>>>>> On 18.01.2017 13:49, Fady Haikal
Operation has timed out
Guys, we are facing the below errors in Tomcat cluster, please advise
06-Feb-2017 01:14:20.718 SEVERE [GroupChannel-Heartbeat-1]
org.apache.catalina.tribes.tipis.AbstractReplicatedMap.heartbeat
Unable to send AbstractReplicatedMap.ping message
org.apache.catalina.tribes.ChannelException: Operation has timed
out(3000 ms.).; Faulty members:tcp://{10, 114, 43, 103}:4000;
at
org.apache.catalina.tribes.transport.nio.ParallelNioSender.sendMessage(ParallelNioSender.java:108)
at
org.apache.catalina.tribes.transport.nio.PooledParallelSender.sendMessage(PooledParallelSender.java:48)
at
org.apache.catalina.tribes.transport.ReplicationTransmitter.sendMessage(ReplicationTransmitter.java:54)
at
org.apache.catalina.tribes.group.ChannelCoordinator.sendMessage(ChannelCoordinator.java:82)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
at
org.apache.catalina.tribes.group.interceptors.MessageDispatchInterceptor.sendMessage(MessageDispatchInterceptor.java:81)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
at
org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.sendMessage(TcpFailureDetector.java:93)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
at org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:233)
at org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:186)
at org.apache.catalina.tribes.group.RpcChannel.send(RpcChannel.java:99)
at
org.apache.catalina.tribes.tipis.AbstractReplicatedMap.ping(AbstractReplicatedMap.java:267)
at
org.apache.catalina.tribes.tipis.AbstractReplicatedMap.heartbeat(AbstractReplicatedMap.java:885)
at
org.apache.catalina.tribes.group.GroupChannel.heartbeat(GroupChannel.java:161)
at
org.apache.catalina.tribes.group.GroupChannel$HeartbeatThread.run(GroupChannel.java:697)
06-Feb-2017 01:20:51.437 SEVERE [NioReceiver]
org.apache.catalina.tribes.transport.nio.NioReceiver.listen Unable to
process request in NioReceiver
java.io.IOException: A non-blocking socket operation could not be
completed immediately
at sun.nio.ch.SocketDispatcher.close0(Native Method)
at sun.nio.ch.SocketDispatcher.close(Unknown Source)
at sun.nio.ch.SocketChannelImpl.kill(Unknown Source)
at sun.nio.ch.WindowsSelectorImpl.implDereg(Unknown Source)
at sun.nio.ch.SelectorImpl.processDeregisterQueue(Unknown Source)
at sun.nio.ch.WindowsSelectorImpl.doSelect(Unknown Source)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(Unknown Source)
at sun.nio.ch.SelectorImpl.select(Unknown Source)
at
org.apache.catalina.tribes.transport.nio.NioReceiver.listen(NioReceiver.java:272)
at
org.apache.catalina.tribes.transport.nio.NioReceiver.run(NioReceiver.java:425)
at java.lang.Thread.run(Unknown Source)
Regards,
Fady
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
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 01:14:20.718 SEVERE [GroupChannel-Heartbeat-1]
> org.apache.catalina.tribes.tipis.AbstractReplicatedMap.heartbeat
> Unable to send AbstractReplicatedMap.ping message
> org.apache.catalina.tribes.ChannelException: Operation has timed
> out(3000 ms.).; Faulty members:tcp://{10, 114, 43, 103}:4000;
> at
> org.apache.catalina.tribes.transport.nio.ParallelNioSender.sendMessage(ParallelNioSender.java:108)
> at
> org.apache.catalina.tribes.transport.nio.PooledParallelSender.sendMessage(PooledParallelSender.java:48)
> at
> org.apache.catalina.tribes.transport.ReplicationTransmitter.sendMessage(ReplicationTransmitter.java:54)
> at
> org.apache.catalina.tribes.group.ChannelCoordinator.sendMessage(ChannelCoordinator.java:82)
> at
> org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
> at
> org.apache.catalina.tribes.group.interceptors.MessageDispatchInterceptor.sendMessage(MessageDispatchInterceptor.java:81)
> at
> org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
> at
> org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.sendMessage(TcpFailureDetector.java:93)
> at
> org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
> at org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:233)
> at org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:186)
> at org.apache.catalina.tribes.group.RpcChannel.send(RpcChannel.java:99)
> at
> org.apache.catalina.tribes.tipis.AbstractReplicatedMap.ping(AbstractReplicatedMap.java:267)
> at
> org.apache.catalina.tribes.tipis.AbstractReplicatedMap.heartbeat(AbstractReplicatedMap.java:885)
> at
> org.apache.catalina.tribes.group.GroupChannel.heartbeat(GroupChannel.java:161)
> at
> org.apache.catalina.tribes.group.GroupChannel$HeartbeatThread.run(GroupChannel.java:697)
>
>
> 06-Feb-2017 01:20:51.437 SEVERE [NioReceiver]
> org.apache.catalina.tribes.transport.nio.NioReceiver.listen Unable to
> process request in NioReceiver
> java.io.IOException: A non-blocking socket operation could not be
> completed immediately
> at sun.nio.ch.SocketDispatcher.close0(Native Method)
> at sun.nio.ch.SocketDispatcher.close(Unknown Source)
> at sun.nio.ch.SocketChannelImpl.kill(Unknown Source)
> at sun.nio.ch.WindowsSelectorImpl.implDereg(Unknown Source)
> at sun.nio.ch.SelectorImpl.processDeregisterQueue(Unknown Source)
> at sun.nio.ch.WindowsSelectorImpl.doSelect(Unknown Source)
> at sun.nio.ch.SelectorImpl.lockAndDoSelect(Unknown Source)
> at sun.nio.ch.SelectorImpl.select(Unknown Source)
> at
> org.apache.catalina.tribes.transport.nio.NioReceiver.listen(NioReceiver.java:272)
> at
> org.apache.catalina.tribes.transport.nio.NioReceiver.run(NioReceiver.java:425)
> at java.lang.Thread.run(Unknown Source)
>
> Regards,
> Fady
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
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 there is no disconnection between 2
nodes ping and telnet are OK
On Mon, Feb 6, 2017 at 6:42 PM, André Warnier (tomcat) wrote:
> 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 this problem new ? was this working before ? how long ?
>
> I do not know tribes at all, but according to the logfile below, it seems
> that something is trying to "ping" the address 10.114.43.103, port 4000, and
> never getting a response (or at least not within 3000ms).
> Is there actually something listening on that address/port ?
> The "netstat" command (available both on Linux and Windows) can tell you.
> If there is something listening there, can it respond to whatever is
> ping-ing it ?
> (routing, firewall, ..)
>
>>
>> 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 01:14:20.718 SEVERE [GroupChannel-Heartbeat-1]
>>> org.apache.catalina.tribes.tipis.AbstractReplicatedMap.heartbeat
>>> Unable to send AbstractReplicatedMap.ping message
>>> org.apache.catalina.tribes.ChannelException: Operation has timed
>>> out(3000 ms.).; Faulty members:tcp://{10, 114, 43, 103}:4000;
>>> at
>>> org.apache.catalina.tribes.transport.nio.ParallelNioSender.sendMessage(ParallelNioSender.java:108)
>>> at
>>> org.apache.catalina.tribes.transport.nio.PooledParallelSender.sendMessage(PooledParallelSender.java:48)
>>> at
>>> org.apache.catalina.tribes.transport.ReplicationTransmitter.sendMessage(ReplicationTransmitter.java:54)
>>> at
>>> org.apache.catalina.tribes.group.ChannelCoordinator.sendMessage(ChannelCoordinator.java:82)
>>> at
>>> org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
>>> at
>>> org.apache.catalina.tribes.group.interceptors.MessageDispatchInterceptor.sendMessage(MessageDispatchInterceptor.java:81)
>>> at
>>> org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
>>> at
>>> org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.sendMessage(TcpFailureDetector.java:93)
>>> at
>>> org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
>>> at
>>> org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:233)
>>> at
>>> org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:186)
>>> at org.apache.catalina.tribes.group.RpcChannel.send(RpcChannel.java:99)
>>> at
>>> org.apache.catalina.tribes.tipis.AbstractReplicatedMap.ping(AbstractReplicatedMap.java:267)
>>> at
>>> org.apache.catalina.tribes.tipis.AbstractReplicatedMap.heartbeat(AbstractReplicatedMap.java:885)
>>> at
>>> org.apache.catalina.tribes.group.GroupChannel.heartbeat(GroupChannel.java:161)
>>> at
>>> org.apache.catalina.tribes.group.GroupChannel$HeartbeatThread.run(GroupChannel.java:697)
>>>
>>>
>>> 06-Feb-2017 01:20:51.437 SEVERE [NioReceiver]
>>> org.apache.catalina.tribes.transport.nio.NioReceiver.listen Unable to
>>> process request in NioReceiver
>>> java.io.IOException: A non-blocking socket operation could not be
>>> completed immediately
>>> at sun.nio.ch.SocketDispatcher.close0(Native Method)
>>> at sun.nio.ch.SocketDispatcher.close(Unknown Source)
>>> at sun.nio.ch.SocketChannelImpl.kill(Unknown Source)
>>> at sun.nio.ch.WindowsSelectorImpl.implDereg(Unknown Source)
>>> at sun.nio.ch.SelectorImpl.processDeregisterQueue(Unknown Source)
>>> at sun.nio.ch.WindowsSelectorImpl.doSelect(Unknown Source)
>>> at sun.nio.ch.SelectorImpl.lockAndDoSelect(Unknown Source)
>>> at sun.nio.ch.SelectorImpl.select(Unknown Source)
>>> at
>>> org.apache.catalina.tribes.transport.nio.NioReceiver.listen(NioReceiver.java:272)
>>> at
>>> org.apache.catalina.tribes.transport.nio.NioReceiver.run(NioR
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
On Mon, Feb 6, 2017 at 6:51 PM, André Warnier (tomcat) wrote:
> 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 point
> would be that there is something wrong in your configuration.
> Can you copy/paste it here ? (remove sensible things like passwords, public
> IP addresses etc..)(but not to the point of making it uncheckable).
>
> Then maybe some tribes-specialist can take over ?
>
>
>>
>> Is there actually something listening on that address/port ? Tomcat
>> cluster
>>
>> the Port 4000 is listening and there is no disconnection between 2
>> nodes ping and telnet are OK
>>
>> On Mon, Feb 6, 2017 at 6:42 PM, André Warnier (tomcat)
>> wrote:
>>>
>>> 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 this problem new ? was this working before ? how long ?
>>>
>>> I do not know tribes at all, but according to the logfile below, it seems
>>> that something is trying to "ping" the address 10.114.43.103, port 4000,
>>> and
>>> never getting a response (or at least not within 3000ms).
>>> Is there actually something listening on that address/port ?
>>> The "netstat" command (available both on Linux and Windows) can tell you.
>>> If there is something listening there, can it respond to whatever is
>>> ping-ing it ?
>>> (routing, firewall, ..)
>>>
>>>>
>>>> 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 01:14:20.718 SEVERE [GroupChannel-Heartbeat-1]
>>>>> org.apache.catalina.tribes.tipis.AbstractReplicatedMap.heartbeat
>>>>> Unable to send AbstractReplicatedMap.ping message
>>>>>org.apache.catalina.tribes.ChannelException: Operation has timed
>>>>> out(3000 ms.).; Faulty members:tcp://{10, 114, 43, 103}:4000;
>>>>> at
>>>>>
>>>>> org.apache.catalina.tribes.transport.nio.ParallelNioSender.sendMessage(ParallelNioSender.java:108)
>>>>> at
>>>>>
>>>>> org.apache.catalina.tribes.transport.nio.PooledParallelSender.sendMessage(PooledParallelSender.java:48)
>>>>> at
>>>>>
>>>>> org.apache.catalina.tribes.transport.ReplicationTransmitter.sendMessage(ReplicationTransmitter.java:54)
>>>>> at
>>>>>
>>>>> org.apache.catalina.tribes.group.ChannelCoordinator.sendMessage(ChannelCoordinator.java:82)
>>>>> at
>>>>>
>>>>> org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
>>>>> at
>>>>>
>>>>> org.apache.catalina.tribes.group.interceptors.MessageDispatchInterceptor.sendMessage(MessageDispatchInterceptor.java:81)
>>>>> at
>>>>>
>>>>> org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
>>>>> at
>>>>>
>>>>> org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.sendMessage(TcpFailureDetector.java:93)
>>>&
Re: Operation has timed out
e.catalina.tribes.group.interceptors.TcpFailureDetector"/>
>> > className="org.apache.catalina.tribes.group.interceptors.MessageDispatch15Interceptor"/>
>>
>>
>> > filter=""/>
>> > className="org.apache.catalina.ha.session.JvmRouteBinderValve"/>
>>
>> > tempDir="D:/imaljava/TomcatNode1/tmp/war-temp/"
>> deployDir="D:/imaljava/TomcatNode1/tmp/war-deploy/"
>> watchDir="D:/imaljava/TomcatNode1/tmp/war-listen/"
>> watchEnabled="false"/>
>>
>> > className="org.apache.catalina.ha.session.ClusterSessionListener"/>
>>
>>
>>
>>
>>
>> > directory="logs"
>>prefix="localhost_access_log" suffix=".txt"
>>pattern="%h %l %u %t "%r" %s %b" />
>> > threshold="900" />
>>
>>
>>
>>
>>
>>
>> On Mon, Feb 6, 2017 at 6:51 PM, André Warnier (tomcat)
>> wrote:
>> > 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 point
>> > would be that there is something wrong in your configuration.
>> > Can you copy/paste it here ? (remove sensible things like passwords, public
>> > IP addresses etc..)(but not to the point of making it uncheckable).
>> >
>> > Then maybe some tribes-specialist can take over ?
>> >
>> >
>> >>
>> >> Is there actually something listening on that address/port ? Tomcat
>> >> cluster
>> >>
>> >> the Port 4000 is listening and there is no disconnection between 2
>> >> nodes ping and telnet are OK
>> >>
>> >> On Mon, Feb 6, 2017 at 6:42 PM, André Warnier (tomcat)
>> >> wrote:
>> >>>
>> >>> 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 this problem new ? was this working before ? how long ?
>> >>>
>> >>> I do not know tribes at all, but according to the logfile below, it seems
>> >>> that something is trying to "ping" the address 10.114.43.103, port 4000,
>> >>> and
>> >>> never getting a response (or at least not within 3000ms).
>> >>> Is there actually something listening on that address/port ?
>> >>> The "netstat" command (available both on Linux and Windows) can tell you.
>> >>> If there is something listening there, can it respond to whatever is
>> >>> ping-ing it ?
>> >>> (routing, firewall, ..)
>> >>>
>> >>>>
>> >>>> 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 01:14:20.718 SEVERE [GroupChannel-Heartbeat-1]
>> >>>>> org.apache.catalina.tribes.tipis.AbstractReplicatedMap.heartbeat
>> >>>>> Unable to send AbstractReplicatedMap.ping message
>> >>>>>org.apache.catalina.tribes.ChannelException: Operation has timed
>> >>>>> out(3000 ms.).; Faulty members:tcp://{10, 114, 43, 103}:4000;
>> >>>>> at
>> >>>>>
>>
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 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
> wide-ranging side-effects.
>
>
>
>
> On 07.02.2017 14:42, Fady Haikal wrote:
>>
>> 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]
>> org.apache.catalina.tribes.tipis.LazyReplicatedMap.publishEntryInfo
>> Unable to replicate backup
>> key:58291D242C742A8A4B1657BA42C831A4.TomcatNode2 to
>> backup:org.apache.catalina.tribes.membership.MemberImpl[tcp://{10,
>> 114, 43, 102}:4000,{10, 114, 43, 102},4000, alive=68841350,
>> securePort=-1, UDP Port=-1, id={85 5 -62 -66 106 -12 64 12 -102 -14
>> -85 -87 15 9 -51 -112 }, payload={}, command={}, domain={}, ].
>> Reason:Operation has timed out(3000 ms.).; Faulty members:tcp://{10,
>> 114, 43, 102}:4000;
>> org.apache.catalina.tribes.ChannelException: Operation has timed
>> out(3000 ms.).; Faulty members:tcp://{10, 114, 43, 102}:4000;
>> at
>> org.apache.catalina.tribes.transport.nio.ParallelNioSender.sendMessage(ParallelNioSender.java:108)
>> at
>> org.apache.catalina.tribes.transport.nio.PooledParallelSender.sendMessage(PooledParallelSender.java:48)
>> at
>> org.apache.catalina.tribes.transport.ReplicationTransmitter.sendMessage(ReplicationTransmitter.java:54)
>> at
>> org.apache.catalina.tribes.group.ChannelCoordinator.sendMessage(ChannelCoordinator.java:82)
>> at
>> org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
>> at
>> org.apache.catalina.tribes.group.interceptors.MessageDispatchInterceptor.sendMessage(MessageDispatchInterceptor.java:81)
>> at
>> org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
>> at
>> org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.sendMessage(TcpFailureDetector.java:93)
>> at
>> org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
>> at
>> org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:233)
>> at
>> org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:186)
&
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,
>> 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
>>> wide-ranging side-effects.
>>>
>>>
>>>
>>>
>>> On 07.02.2017 14:42, Fady Haikal wrote:
>>>>
>>>>
>>>> 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]
>>>> org.apache.catalina.tribes.tipis.LazyReplicatedMap.publishEntryInfo
>>>> Unable to replicate backup
>>>> key:58291D242C742A8A4B1657BA42C831A4.TomcatNode2 to
>>>> backup:org.apache.catalina.tribes.membership.MemberImpl[tcp://{10,
>>>> 114, 43, 102}:4000,{10, 114, 43, 102},4000, alive=68841350,
>>>> securePort=-1, UDP Port=-1, id={85 5 -62 -66 106 -12 64 12 -102 -14
>>>> -85 -87 15 9 -51 -112 }, payload={}, command={}, domain={}, ].
>>>> Reason:Operation has timed out(300
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 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 >>>> wide-ranging side-effects. >>>> >>>> >>>> >>>> >>>> On 07.02.2017 14:42, Fady Haikal wrote: >>>>> >>>>> >>>>> 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 >>>>>
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 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 ha
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 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 kno
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: 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 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.group.GroupChannel"> > 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 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)" 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 ESTABLISH
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 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 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 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 >> 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)" >> 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 >> >>>>>
Change Severe to Info
Hi Can we change a severe exception in catalina that can be ignored to info? Tomcat logging is SEVERE and we are facing an error in catalina that can bi ignored, can we change the type of this error to INFO or Warning? Regards - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Change Severe to Info
this error
09-Feb-2017 11:21:09.851 SEVERE [GroupChannel-Heartbeat-1]
org.apache.catalina.tribes.tipis.AbstractReplicatedMap.heartbeat
Unable to send AbstractReplicatedMap.ping message
org.apache.catalina.tribes.ChannelException: Operation has timed
out(3000 ms.).; Faulty members:tcp://{10, 114, 43, 103}:4000;
at
org.apache.catalina.tribes.transport.nio.ParallelNioSender.sendMessage(ParallelNioSender.java:108)
at
org.apache.catalina.tribes.transport.nio.PooledParallelSender.sendMessage(PooledParallelSender.java:48)
at
org.apache.catalina.tribes.transport.ReplicationTransmitter.sendMessage(ReplicationTransmitter.java:54)
at
org.apache.catalina.tribes.group.ChannelCoordinator.sendMessage(ChannelCoordinator.java:82)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
at
org.apache.catalina.tribes.group.interceptors.MessageDispatchInterceptor.sendMessage(MessageDispatchInterceptor.java:81)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
at
org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.sendMessage(TcpFailureDetector.java:93)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:76)
at org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:233)
at org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:186)
at org.apache.catalina.tribes.group.RpcChannel.send(RpcChannel.java:99)
at
org.apache.catalina.tribes.tipis.AbstractReplicatedMap.ping(AbstractReplicatedMap.java:267)
at
org.apache.catalina.tribes.tipis.AbstractReplicatedMap.heartbeat(AbstractReplicatedMap.java:885)
at
org.apache.catalina.tribes.group.GroupChannel.heartbeat(GroupChannel.java:161)
at
org.apache.catalina.tribes.group.GroupChannel$HeartbeatThread.run(GroupChannel.java:697)
On Thu, Feb 9, 2017 at 10:49 AM, Mark Thomas wrote:
> On 09/02/17 07:53, Fady Haikal wrote:
>>
>> Hi Can we change a severe exception in catalina that can be ignored to
>> info?
>
>
> Not without patching the source code, no.
>
>> Tomcat logging is SEVERE and we are facing an error in catalina that
>> can bi ignored, can we change the type of this error to INFO or
>> Warning?
>
>
> What error? SEVERE typically means bad things have happened or or going to
> happen that you need to deal with.
>
> Mark
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Operation has timed out
Keiichi,
mapSendoption is not configured anyway please check my configuration below
On Thu, Feb 9, 2017 at 10:32 AM, Keiichi Fujino wrote:
> 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 org.apache.catalina.tribes.MESSAGES outputs a lot of trace level logs.
> So It should get logs in a short period of time.
>
>
> 2017-02-06 15:52 GMT+09:00 Fady Haikal :
>
>> Guys, we are facing the below errors in Tomcat cluster, please advise
>>
>>
>> 06-Feb-2017 01:14:20.718 SEVERE [GroupChannel-Heartbeat-1]
>> org.apache.catalina.tribes.tipis.AbstractReplicatedMap.heartbeat
>> Unable to send AbstractReplicatedMap.ping message
>> org.apache.catalina.tribes.ChannelException: Operation has timed
>> out(3000 ms.).; Faulty members:tcp://{10, 114, 43, 103}:4000;
>> at org.apache.catalina.tribes.transport.nio.ParallelNioSender.sendMessage(
>> ParallelNioSender.java:108)
>> at org.apache.catalina.tribes.transport.nio.PooledParallelSender.
>> sendMessage(PooledParallelSender.java:48)
>> at org.apache.catalina.tribes.transport.ReplicationTransmitter.
>> sendMessage(ReplicationTransmitter.java:54)
>> at org.apache.catalina.tribes.group.ChannelCoordinator.sendMessage(
>> ChannelCoordinator.java:82)
>> at org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(
>> ChannelInterceptorBase.java:76)
>> at org.apache.catalina.tribes.group.interceptors.
>> MessageDispatchInterceptor.sendMessage(MessageDispatchInterceptor.java:81)
>> at org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(
>> ChannelInterceptorBase.java:76)
>> at org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.
>> sendMessage(TcpFailureDetector.java:93)
>> at org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(
>> ChannelInterceptorBase.java:76)
>> at org.apache.catalina.tribes.group.GroupChannel.send(
>> GroupChannel.java:233)
>> at org.apache.catalina.tribes.group.GroupChannel.send(
>> GroupChannel.java:186)
>> at org.apache.catalina.tribes.group.RpcChannel.send(RpcChannel.java:99)
>> at org.apache.catalina.tribes.tipis.AbstractReplicatedMap.
>> ping(AbstractReplicatedMap.java:267)
>> at org.apache.catalina.tribes.tipis.AbstractReplicatedMap.heartbeat(
>> AbstractReplicatedMap.java:885)
>> at org.apache.catalina.tribes.group.GroupChannel.heartbeat(
>> GroupChannel.java:161)
>> at org.apache.catalina.tribes.group.GroupChannel$HeartbeatThread.run(
>> GroupChannel.java:697)
>>
>>
>> 06-Feb-2017 01:20:51.437 SEVERE [NioReceiver]
>> org.apache.catalina.tribes.transport.nio.NioReceiver.listen Unable to
>> process request in NioReceiver
>> java.io.IOException: A non-blocking socket operation could not be
>> completed immediately
>> at sun.nio.ch.SocketDispatcher.close0(Native Method)
>> at sun.nio.ch.SocketDispatcher.close(Unknown Source)
>> at sun.nio.ch.SocketChannelImpl.kill(Unknown Source)
>> at sun.nio.ch.WindowsSelectorImpl.implDereg(Unknown Source)
>> at sun.nio.ch.SelectorImpl.processDeregisterQueue(Unknown Source)
>> at sun.nio.ch.WindowsSelectorImpl.doSelect(Unknown Source)
>> at sun.nio.ch.SelectorImpl.lockAndDoSelect(Unknown Source)
>> at sun.nio.ch.SelectorImpl.select(Unknown Source)
>> at org.apache.catalina.tribes.transport.nio.NioReceiver.
>> listen(NioReceiver.java:272)
>> at org.apache.catalina.tribes.transport.nio.NioReceiver.run(
>> NioReceiver.java:425)
>> at java.lang.Thread.run(Unknown Source)
>>
>> Regards,
>> Fady
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
>
>
> --
> Keiichi.Fujino
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
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 .
> If you do not use Cluster Manager template, DeltaManager is used by default.
> However, in the logs, it seems to be using BackupManager.
> Have you set in webapps/{your app} /META-INF/context.xml
> or conf/{Engine}/{Host}/{your app}.xml?
>
>
>
>>
>>
>>
>>
>> > />
>>
>>
>> > SSLEngine="on" />
>>
>> > />
>> > />
>> > />
>>
>>
>>
>>
>> > type="org.apache.catalina.UserDatabase"
>> description="User database that can be updated and saved"
>> factory="org.apache.catalina.users.
>> MemoryUserDatabaseFactory"
>> pathname="conf/tomcat-users.xml" />
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> >connectionTimeout="6" maxThreads="500"
>> minSpareThreads="25" maxSpareThreads="75" enableLookups="false"
>> disableUploadTimeout="true" acceptCount="100" redirectPort="8443" />
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> > jvmRoute="TomcatNode1">
>>
>>
>>
>> >resourceName="UserDatabase"/>
>>
>>
>> > unpackWARs="true" autoDeploy="true" startStopThreads="0">
>>
>>
>>
>> > channelSendOptions="4">
>>
>> > className="org.apache.catalina.tribes.membership.McastService"
>> address="228.0.0.4"
>> port="45560"
>> frequency="500"
>> dropTime="9000"/>
>> > className="org.apache.catalina.tribes.transport.nio.NioReceiver"
>> address="auto"
>> port="4000"
>> autoBind="100"
>> selectorTimeout="5000"
>> maxThreads="6"/>
>>
>> > className="org.apache.catalina.tribes.transport.ReplicationTransmitter">
>> > className="org.apache.catalina.tribes.transport.nio.
>> PooledParallelSender"/>
>>
>> > className="org.apache.catalina.tribes.group.interceptors.
>> TcpFailureDetector"/>
>> > className="org.apache.catalina.tribes.group.interceptors.
>> MessageDispatch15Interceptor"/>
>>
>>
>> >
>> filter=".*\.gif|.*\.js|.*\.jpeg|.*\.jpg|.*\.png|.*\.htm|.
>> *\.html|.*\.css|.*\.txt"/>
>> > className="org.apache.catalina.ha.session.JvmRouteBinderValve"/>
>>
>> > tempDir="D:/imaljava/TomcatNode1/tmp/war-temp/"
>> deployDir="D:/imaljava/TomcatNode1/tmp/war-deploy/"
>> watchDir="D:/imaljava/TomcatNode1/tmp/war-listen/"
>> watchEnabled="false"/>
>>
>> > className="org.apache.catalina.ha.session.ClusterSessionListener"/>
>>
>>
>>
>>
>>
>> > directory="logs"
>>prefix="localhost_access_log" suffix=".txt"
>>pattern="%h %l %u %t "%r" %s %b" />
>> > threshold="900" />
>>
>>
>>
>>
>>
>>
>>
>> On Thu, Feb 9, 2017 at 10:32 AM, Keiichi Fujino
>> wrote:
>> > 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.a
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
>
> 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 GMT+09:00 Fady Haikal :
>
>> The is set under the context.xml
>>
>> >notifyListenersOnReplication="true"
>>mapSendOptions="6"/>
>>
>> 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 .
>> > If you do not use Cluster Manager template, DeltaManager is used by
>> default.
>> > However, in the logs, it seems to be using BackupManager.
>> > Have you set in webapps/{your app}
>> /META-INF/context.xml
>> > or conf/{Engine}/{Host}/{your app}.xml?
>> >
>> >
>> >
>> >>
>> >>
>> >>
>> >>
>> >> > >> />
>> >>
>> >>
>> >> > >> SSLEngine="on" />
>> >>
>> >> > >> />
>> >> > >> />
>> >> > >> />
>> >>
>> >>
>> >>
>> >>
>> >> > >> type="org.apache.catalina.UserDatabase"
>> >> description="User database that can be updated and saved"
>> >> factory="org.apache.catalina.users.
>> >> MemoryUserDatabaseFactory"
>> >> pathname="conf/tomcat-users.xml" />
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> > >>connectionTimeout="6" maxThreads="500"
>> >> minSpareThreads="25" maxSpareThreads="75" enableLookups="false"
>> >> disableUploadTimeout="true" acceptCount="100" redirectPort="8443" />
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> > >> jvmRoute="TomcatNode1">
>> >>
>> >>
>> >>
>> >> > >>resourceName="UserDatabase"/>
>> >>
>> >>
>> >> > >> unpackWARs="true" autoDeploy="true" startStopThreads="0">
>> >>
>> >>
>> >>
>> >> > >> channelSendOptions="4">
>> >>
>> >> > >> className="org.apache.catalina.tribes.membership.McastService"
>> >> address="228.0.0.4"
>> >> port="45560"
>> >> frequency="500"
>> >> dropTime="9000"/>
>> >> > >> className="org.apache.catalina.tribes.transport.nio.NioReceiver"
>> >> address="auto"
>> >> port="4000"
>> >> autoBind="100"
>> >> selectorTimeout="5000"
>> >> maxThreads="6"/>
>> >>
>> >> > >> className="org.apache.catalina.tribes.transport.
>> ReplicationTransmitter">
>> >> > >> className="org.apache.catalina.tribes.transport.nio.
>> >> PooledParallelSender"/>
>> &g
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 [imal_services] created a ThreadLocal with key of
type [com.path.lib.common.util.ThreadAttributes$1] (value
[com.path.lib.common.util.ThreadAttributes$1@6ca9b927]) and a value of
type [java.util.HashMap] (value [{PATH_INFO=IBIS M.HANAFI
UNKNOWN_PROG_REF}]) but failed to remove it when the web application
was stopped. Threads are going to be renewed over time to try and
avoid a probable memory leak.
09-Feb-2017 12:44:12.300 SEVERE
[ContainerBackgroundProcessor[StandardEngine[Catalina]]]
org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks
The web application [imal_services] created a ThreadLocal with key of
type [com.path.lib.common.util.ThreadAttributes$1] (value
[com.path.lib.common.util.ThreadAttributes$1@6ca9b927]) and a value of
type [java.util.HashMap] (value [{PATH_INFO=IBIS A.ALMANA
UNKNOWN_PROG_REF}]) but failed to remove it when the web application
was stopped. Threads are going to be renewed over time to try and
avoid a probable memory leak.
09-Feb-2017 12:44:12.300 SEVERE
[ContainerBackgroundProcessor[StandardEngine[Catalina]]]
org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks
The web application [imal_services] created a ThreadLocal with key of
type [com.path.lib.common.util.ThreadAttributes$1] (value
[com.path.lib.common.util.ThreadAttributes$1@6ca9b927]) and a value of
type [java.util.HashMap] (value [{PATH_INFO=IBIS M.HANAFI
UNKNOWN_PROG_REF}]) but failed to remove it when the web application
was stopped. Threads are going to be renewed over time to try and
avoid a probable memory leak.
09-Feb-2017 12:44:12.301 SEVERE
[ContainerBackgroundProcessor[StandardEngine[Catalina]]]
org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks
The web application [imal_services] created a ThreadLocal with key of
type [com.path.lib.common.util.ThreadAttributes$1] (value
[com.path.lib.common.util.ThreadAttributes$1@6ca9b927]) and a value of
type [java.util.HashMap] (value [{PATH_INFO=IBIS M.SHAIKH LOGOUT
Process}]) but failed to remove it when the web application was
stopped. Threads are going to be renewed over time to try and avoid a
probable memory leak.
09-Feb-2017 12:44:12.301 SEVERE
[ContainerBackgroundProcessor[StandardEngine[Catalina]]]
org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks
The web application [imal_services] created a ThreadLocal with key of
type [com.path.lib.common.util.ThreadAttributes$1] (value
[com.path.lib.common.util.ThreadAttributes$1@6ca9b927]) and a value of
type [java.util.HashMap] (value [{PATH_INFO=IBIS M.HANAFI
UNKNOWN_PROG_REF}]) but failed to remove it when the web application
was stopped. Threads are going to be renewed over time to try and
avoid a probable memory leak.
09-Feb-2017 12:44:12.302 SEVERE
[ContainerBackgroundProcessor[StandardEngine[Catalina]]]
org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks
The web application [imal_services] created a ThreadLocal with key of
type [com.path.lib.common.util.ThreadAttributes$1] (value
[com.path.lib.common.util.ThreadAttributes$1@6ca9b927]) and a value of
type [java.util.HashMap] (value [{PATH_INFO=IBIS M.HANAFI
UNKNOWN_PROG_REF}]) but failed to remove it when the web application
was stopped. Threads are going to be renewed over time to try and
avoid a probable memory leak.
09-Feb-2017 12:44:12.303 SEVERE
[ContainerBackgroundProcessor[StandardEngine[Catalina]]]
org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks
The web application [imal_services] created a ThreadLocal with key of
type [com.path.lib.common.util.ThreadAttributes$1] (value
[com.path.lib.common.util.ThreadAttributes$1@6ca9b927]) and a value of
type [java.util.HashMap] (value [{PATH_INFO=IBIS M.HANAFI
UNKNOWN_PROG_REF}]) but failed to remove it when the web application
was stopped. Threads are going to be renewed over time to try and
avoid a probable memory leak.
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
org.apache.catalina.tribes.tipis.AbstractReplicatedMap.ping(AbstractReplicatedMap.java:256)
at
org.apache.catalina.tribes.tipis.AbstractReplicatedMap.heartbeat(AbstractReplicatedMap.java:885)
at
org.apache.catalina.tribes.group.GroupChannel.heartbeat(GroupChannel.java:166)
at
org.apache.catalina.tribes.group.GroupChannel$HeartbeatThread.run(GroupChannel.java:697)
09-Feb-2017 12:44:14.834 SEVERE
[ContainerBackgroundProcessor[StandardEngine[Catalina]]]
org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks
The web application [imal_tfa_ser
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
org.apache.catalina.tribes.tipis.AbstractReplicatedMap.ping(AbstractReplicatedMap.java:256)
at
org.apache.catalina.tribes.tipis.AbstractReplicatedMap.heartbeat(AbstractReplicatedMap.java:885)
at
org.apache.catalina.tribes.group.GroupChannel.heartbeat(GroupChannel.java:166)
at
org.apache.catalina.tribes.group.GroupChannel$HeartbeatThread.run(GroupChannel.java:697)
On Thu, Feb 9, 2017 at 12:04 PM, Keiichi Fujino wrote:
> 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 :
>
>> 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 [imal_services] created a ThreadLocal with key of
>> type [com.path.lib.common.util.ThreadAttributes$1] (value
>> [com.path.lib.common.util.ThreadAttributes$1@6ca9b927]) and a value of
>> type [java.util.HashMap] (value [{PATH_INFO=IBIS M.HANAFI
>> UNKNOWN_PROG_REF}]) but failed to remove it when the web application
>> was stopped. Threads are going to be renewed over time to try and
>> avoid a probable memory leak.
>> 09-Feb-2017 12:44:12.300 SEVERE
>> [ContainerBackgroundProcessor[StandardEngine[Catalina]]]
>> org.apache.catalina.loader.WebappClassLoaderBase.
>> checkThreadLocalMapForLeaks
>> The web application [imal_services] created a ThreadLocal with key of
>> type [com.path.lib.common.util.ThreadAttributes$1] (value
>> [com.path.lib.common.util.ThreadAttributes$1@6ca9b927]) and a value of
>> type [java.util.HashMap] (value [{PATH_INFO=IBIS A.ALMANA
>> UNKNOWN_PROG_REF}]) but failed to remove it when the web application
>> was stopped. Threads are going to be renewed over time to try and
>> avoid a probable memory leak.
>> 09-Feb-2017 12:44:12.300 SEVERE
>> [ContainerBackgroundProcessor[StandardEngine[Catalina]]]
>> org.apache.catalina.loader.WebappClassLoaderBase.
>> checkThreadLocalMapForLeaks
>> The web application [imal_services] created a ThreadLocal with key of
>> type [com.path.lib.common.util.ThreadAttributes$1] (value
>> [com.path.lib.common.util.ThreadAttributes$1@6ca9b927]) and a value of
>> type [java.util.HashMap] (value [{PATH_INFO=IBIS M.HANAFI
>> UNKNOWN_PROG_REF}]) but failed to remove it when the web application
>> was stopped. Threads are going to be renewed over time to try and
>> avoid a probable memory leak.
>> 09-Feb-2017 12:44:12.301 SEVERE
>> [ContainerBackgroundProcessor[StandardEngine[Catalina]]]
>> org.apache.catalina.loader.WebappClassLoaderBase.
>> checkThreadLocalMapForLeaks
>> The web application [imal_services] created a ThreadLocal with key of
>> type [com.path.lib.common.util.ThreadAttributes$1] (value
>> [com.path.lib.common.util.ThreadAttributes$1@6ca9b927]) and a value of
>> type [java.util.HashMap] (value [{PATH_INFO=IBIS M.SHAIKH LOGOUT
>> Process}]) but failed to remove it when the web application was
>> stopped. Threads are going to be renewed over time to try and avoid a
>> probable memory leak.
>> 09-Feb-2017 12:44:12.301 SEVERE
>> [ContainerBackgroundProcessor[StandardEngine[Catalina]]]
>> org.apache.catalina.loader.WebappClassLoaderBase.
>> checkThreadLocalMapForLeaks
>> The web application [imal_services] created a ThreadLocal with key of
>> type [com.path.lib.common.util.ThreadAttributes$1] (value
>> [com.path.lib.common.util.ThreadAttributes$1@6ca9b927]) and a value of
>> type [java.util.HashMap] (value [{PATH_INFO=IBIS M.HANAFI
>> UNKNOWN_PROG_REF}]) but failed to remove it when the web application
>> was stopped. Threads are going to be renewed over time to try and
>> avoid a probable memory leak.
>> 09-Feb-2017 12:44:12.302 SEVERE
>> [ContainerBackgroundProcessor[StandardEngine[Catalina]]]
>> org.apache.catalina.loader.WebappClassLoaderBase.
>> checkThreadLocalMapForLeaks
>> The web application [imal_services] created a ThreadLocal with key of
>> type [com.path.lib.co
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 AbstractReplicatedMap with context name:xxx"
> "AbstractReplicatedMap[xxx] initialization was completed in xxx ms."
>
>
> 2017-02-09 19:09 GMT+09:00 Fady Haikal :
>
>> 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 org.apache.catalina.tribes.tipis.AbstractReplicatedMap.
>> ping(AbstractReplicatedMap.java:256)
>> at org.apache.catalina.tribes.tipis.AbstractReplicatedMap.heartbeat(
>> AbstractReplicatedMap.java:885)
>> at org.apache.catalina.tribes.group.GroupChannel.heartbeat(
>> GroupChannel.java:166)
>> at org.apache.catalina.tribes.group.GroupChannel$HeartbeatThread.run(
>> GroupChannel.java:697)
>>
>> On Thu, Feb 9, 2017 at 12:04 PM, Keiichi Fujino
>> wrote:
>> > 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 :
>> >
>> >> 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 [imal_services] created a ThreadLocal with key of
>> >> type [com.path.lib.common.util.ThreadAttributes$1] (value
>> >> [com.path.lib.common.util.ThreadAttributes$1@6ca9b927]) and a value of
>> >> type [java.util.HashMap] (value [{PATH_INFO=IBIS M.HANAFI
>> >> UNKNOWN_PROG_REF}]) but failed to remove it when the web application
>> >> was stopped. Threads are going to be renewed over time to try and
>> >> avoid a probable memory leak.
>> >> 09-Feb-2017 12:44:12.300 SEVERE
>> >> [ContainerBackgroundProcessor[StandardEngine[Catalina]]]
>> >> org.apache.catalina.loader.WebappClassLoaderBase.
>> >> checkThreadLocalMapForLeaks
>> >> The web application [imal_services] created a ThreadLocal with key of
>> >> type [com.path.lib.common.util.ThreadAttributes$1] (value
>> >> [com.path.lib.common.util.ThreadAttributes$1@6ca9b927]) and a value of
>> >> type [java.util.HashMap] (value [{PATH_INFO=IBIS A.ALMANA
>> >> UNKNOWN_PROG_REF}]) but failed to remove it when the web application
>> >> was stopped. Threads are going to be renewed over time to try and
>> >> avoid a probable memory leak.
>> >> 09-Feb-2017 12:44:12.300 SEVERE
>> >> [ContainerBackgroundProcessor[StandardEngine[Catalina]]]
>> >> org.apache.catalina.loader.WebappClassLoaderBase.
>> >> checkThreadLocalMapForLeaks
>> >> The web application [imal_services] created a ThreadLocal with key of
>> >> type [com.path.lib.common.util.ThreadAttributes$1] (value
>> >> [com.path.lib.common.util.ThreadAttributes$1@6ca9b927]) and a value of
>> >> type [java.util.HashMap] (value [{PATH_INFO=IBIS M.HANAFI
>> >> UNKNOWN_PROG_REF}]) but failed to remove it when the web application
>> >> was stopped. Threads are going to be renewed over time to try and
>> >> avoid a probable memory leak.
>> >> 09-Feb-2017 12:44:12.301 SEVERE
>> >> [ContainerBackgroundProcessor[StandardEngine[Catalina]]]
>> >> org.apache.catalina.loader.WebappClassLoaderBase.
>> >> checkThreadLocalMapForLeaks
>> >> The web application [imal_services] created a ThreadLocal with key of
>> >> type [com.path.lib.common.util.ThreadAttributes$1] (value
>> >> [com.path.lib.common.util.ThreadAttributes$1@6ca9b927]) and a value of
>> >> type [java.util.HashMap] (value [{PATH_INFO=IBIS M.SHAIKH LOGOUT
>> >> Process}]) but failed to remove it wh
Simultaneous Users / Transactions
Hi Team, I need to know if Tomcat can handle around 2000 concurent user, 17000 number of simultaneouse transactions peak per 10 minutes, assuming the application can handle them, in additional i need to know what is the recommended configuration for Tomcat in order to handle this number of requests. Regards, Fady
Re: Simultaneous Users / Transactions
- Concurrent active connections: 3000 - Concurent passive connections: 1000 - concurrent active connections (i.e. actively processing a request): 1000 - new requests made per second: 28 - average time taken to process a request: 2 - 3 seconds On Mon, Jun 19, 2017 at 12:46 PM, Mark Thomas wrote: > On 19/06/17 10:06, Fady Haikal wrote: > > Hi Team, > > I need to know if Tomcat can handle around 2000 concurent user, 17000 > > number of simultaneouse transactions peak per 10 minutes, assuming the > > application can handle them, in additional i need to know what is the > > recommended configuration for Tomcat in order to handle this number of > > requests. > > Tomcat will easily handle this. The limiting factor will be the > application and/or the hardware you are running on. > > How can 2000 concurrent users generate 17000 simultaneous transactions? > > Regarding configuration, the factors you need to consider are: > - concurrent connections (active and inactive) > - concurrent active connections (i.e. actively processing a request) > - new requests made per second > - average time taken to process a request > > Depending on the answers, the default configuration may be sufficient. > > The alert reader may have noticed that at least one of the factors above > can be derived from the others. This is deliberate. I want to see if the > answers provide are internally consistent. > > Mark > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: Simultaneous Users / Transactions
@Mark, we have 3rd parties and applications that are connecting to the Tomcat server (not only the users) that will made these transactions On Mon, Jun 19, 2017 at 12:58 PM, Mark Thomas wrote: > On 19/06/17 10:53, Fady Haikal wrote: > > - Concurrent active connections: 3000 > > - Concurent passive connections: 1000 > > - concurrent active connections (i.e. actively processing a request): > 1000 > > - new requests made per second: 28 > > - average time taken to process a request: 2 - 3 seconds > > Those numbers don't add up. > > 28 new requests per second with an average processing time of 2-3 > seconds gives a figure for concurrent active connections of 56-84. > > The default Tomcat configuration will easily handle 3000 concurrent > connections with ~100 active at any one time. > > Mark > > > > > > On Mon, Jun 19, 2017 at 12:46 PM, Mark Thomas wrote: > > > >> On 19/06/17 10:06, Fady Haikal wrote: > >>> Hi Team, > >>> I need to know if Tomcat can handle around 2000 concurent user, 17000 > >>> number of simultaneouse transactions peak per 10 minutes, assuming the > >>> application can handle them, in additional i need to know what is the > >>> recommended configuration for Tomcat in order to handle this number of > >>> requests. > >> > >> Tomcat will easily handle this. The limiting factor will be the > >> application and/or the hardware you are running on. > >> > >> How can 2000 concurrent users generate 17000 simultaneous transactions? > >> > >> Regarding configuration, the factors you need to consider are: > >> - concurrent connections (active and inactive) > >> - concurrent active connections (i.e. actively processing a request) > >> - new requests made per second > >> - average time taken to process a request > >> > >> Depending on the answers, the default configuration may be sufficient. > >> > >> The alert reader may have noticed that at least one of the factors above > >> can be derived from the others. This is deliberate. I want to see if the > >> answers provide are internally consistent. > >> > >> Mark > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > >> For additional commands, e-mail: users-h...@tomcat.apache.org > >> > >> > > > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Tomcat memory
Dear Team, I'm facing an issue that tomcat from task manager is consuming around 60 GB of memory while from Oracle Java Mission Control is showing maximum 10 GB (Attached screenshots), and from time to time the server hang due to insufficent memory. can you please advise why the above is showing like that? and why the memory of the server is not reducing? Tomcat Version: 8.0.30 JDK: 1.7.0_67 Regards, Fady - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat memory
@Suvendu, I took a heap dump from Java VisualVM but honestly i didnt know how i should analyse it, please some help here also please find below the java configuration i used: -XX:PermSize=10240m -XX:MaxPermSize=10240m -XX:ReservedCodeCacheSize=512m -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:TargetSurvivorRatio=90 Initial and Max Memory Pool: 10MB Regards, Fady On Wed, Aug 16, 2017 at 5:46 PM, Suvendu Sekhar Mondal wrote: > Hi Fady, > > On Aug 16, 2017 7:04 PM, "Fady Haikal" wrote: > > Dear Team, > I'm facing an issue that tomcat from task manager is consuming around 60 GB > of memory while from Oracle Java Mission Control is showing maximum 10 GB > (Attached screenshots), and from time to time the server hang due to > insufficent memory. > can you please advise why the above is showing like that? and why the > memory of the server is not reducing? > > Tomcat Version: 8.0.30 > JDK: 1.7.0_67 > > > I couldn't find the screenshot. Anyway, the issue you mentioned is very > interesting. Usually I saw some difference(in MB) between task manager data > and JMC data...but not like this. Can you please let us know about the > Java Heap, Permgen and thread stack size configuration? > > For starter, I will suggest to take a heap dump and look into it. It will > show you which objects are live and holding the memory. Also it will be > awesome if you can enable Native Memory Tracking for your TC instance. > > Thanks! > Suvendu >
Re: Tomcat memory
Team, Please i need some help her Regards, On Thu, Aug 17, 2017 at 9:46 AM, Fady Haikal wrote: > @Suvendu, > I took a heap dump from Java VisualVM but honestly i didnt know how i > should analyse it, please some help here > > also please find below the java configuration i used: > -XX:PermSize=10240m > -XX:MaxPermSize=10240m > -XX:ReservedCodeCacheSize=512m > -XX:+UseParNewGC > -XX:+UseConcMarkSweepGC > -XX:+CMSParallelRemarkEnabled > -XX:TargetSurvivorRatio=90 > > Initial and Max Memory Pool: 10MB > > Regards, > Fady > > > On Wed, Aug 16, 2017 at 5:46 PM, Suvendu Sekhar Mondal > wrote: > >> Hi Fady, >> >> On Aug 16, 2017 7:04 PM, "Fady Haikal" wrote: >> >> Dear Team, >> I'm facing an issue that tomcat from task manager is consuming around 60 >> GB >> of memory while from Oracle Java Mission Control is showing maximum 10 GB >> (Attached screenshots), and from time to time the server hang due to >> insufficent memory. >> can you please advise why the above is showing like that? and why the >> memory of the server is not reducing? >> >> Tomcat Version: 8.0.30 >> JDK: 1.7.0_67 >> >> >> I couldn't find the screenshot. Anyway, the issue you mentioned is very >> interesting. Usually I saw some difference(in MB) between task manager >> data >> and JMC data...but not like this. Can you please let us know about the >> Java Heap, Permgen and thread stack size configuration? >> >> For starter, I will suggest to take a heap dump and look into it. It will >> show you which objects are live and holding the memory. Also it will be >> awesome if you can enable Native Memory Tracking for your TC instance. >> >> Thanks! >> Suvendu >> > >
