Skip to Content
author's profile photo Former Member
Former Member

Ping JVM comes and site becomes unavailable

After Every few hours we get following errors:

Pinging the JVM took 34 seconds to respond. Pinging the JVM took 25 seconds to respond. Pinging the JVM took 16 seconds to respond. Pinging the JVM took 7 seconds to respond.

Pinging the JVM took 38 seconds to respond. Pinging the JVM took 29 seconds to respond. Pinging the JVM took 20 seconds to respond. Pinging the JVM took 10 seconds to respond. Pinging the JVM took 1 seconds to respond. site becomes unavailable during 1-2 minutes (no reports at this time isn't written to logs);

then several messages "Pinging JVM ..." appears in the log and site becomes available;

there is "No Data available." message in "Sessions overview" section in hac;

Java takes almost the entire memory.

What could it be? What should we do to solve this problem?

Please find the below memory and cache settings that we have :

regioncache.entityregion.size=500000 regioncache.querycacheregion.size=200000
tomcat.javaoptions=-Xms4G -Xmx12G tomcat.generaloptions=-server -Xms4G -Xmx12G -XX:PermSize=500M -XX:MaxPermSize=500M -Xloggc:../logs/java_gc.log -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+UseParallelGC -XX:+UseParallelOldGC -XX:+UseAdaptiveGCBoundary -XX:+ExplicitGCInvokesConcurrent -Dsun.rmi.dgc.client.gcInteraval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=${tomcat.jmx.port} -Dcom.sun.management.jmxremote.ssl=false -Dorg.tanukisoftware.wrapper.WrapperManager.mbean=true -Dcom.sun.management.jmxremote.authenticate=false

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Aug 22, 2016 at 11:06 AM

    Hello Vinary,

    It looks like there is performance issue going on in your platform.
    But it really depends on the scenario.
    You may need to check if there is any suspicious cronjob running in background?
    Or if any extention running slowly?
    Or any particular customer behaviour caused the issue?
    And you may check the JVM GC logs, to see if there is any unexpected JVM behaviour.
    And how is your CPU usage? is it very high?
    In this case, you'd better provide as much information/detailed logs as possible to investigate further.

    Thanks & Regards,
    Hongxian

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.