grehon / wlsagent

Automatically exported from code.google.com/p/wlsagent
GNU General Public License v3.0
0 stars 0 forks source link

Getting service check time out for Weblogic Monitoring after 24 hours #21

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. By killing and staring wlsagent reducing the problem
2.
3.

What is the expected output? What do you see instead?
Server status has to be ok . But showing critical

What version of the product are you using? On what operating system?
Nagios 3.4.4 in Linux

Please provide any additional information below.

We are Getting service check time out for Weblogic Monitoring after 24 hours of 
monitoring . Servers are showing ok for 24 hours and they are becoming critical 
after 24 hours even though they are working fine . At that time by killing and 
staring wlsagent reducing the problem.Please provide correct recommendation for 
this.

Original issue reported on code.google.com by ksantosh...@gmail.com on 12 Aug 2013 at 12:29

GoogleCodeExporter commented 9 years ago
Hello,

I'm afraid there is nothing I can do. There is a memory leak in the plugin 
which is related to the t3 protocol implementation. At the time, I asked some 
help on Oracle forum (see https://forums.oracle.com/thread/2225177), and I also 
created a SR on the support site but the company I was working for only had a 
"server support", and the problem occured on the client side, so I've got 
nothing new.

You will have indeed to schedule a restart of the agent, whatever heap size you 
set.

Original comment by yann.lambret@gmail.com on 12 Aug 2013 at 2:49

GoogleCodeExporter commented 9 years ago
I'm unsure of what level of support we have, but I created an SR. I'll be happy 
to update this thread if that would be useful. 

If it helps, I'm getting an OOM at getNewTla. Some of Oracle's KBs strongly 
advise against tweaking TLAs.  Does this error help you at all? I have a heap 
dump and log file if you'd like to review it. 

java.lang.OutOfMemoryError: getNewTla
    at jrockit/vm/Allocator.getNewTla(JJ)V(Native Method)
    at jrockit/vm/Allocator.allocObjectOrArray(Allocator.java:354)[optimized]
    at java/util/HashMap.newKeyIterator(HashMap.java:1024)[optimized]
    at java/util/HashMap$KeySet.iterator(HashMap.java:1062)[optimized]
    at java/util/HashSet.iterator(HashSet.java:153)
    at sun/nio/ch/SelectorImpl.processDeregisterQueue(SelectorImpl.java:127)
    at sun/nio/ch/EPollSelectorImpl.doSelect(EPollSelectorImpl.java:69)[optimized]
    at sun/nio/ch/SelectorImpl.lockAndDoSelect(SelectorImpl.java:69)[optimized]
    at sun/nio/ch/SelectorImpl.select(SelectorImpl.java:80)[inlined]
    at org/eclipse/jetty/io/nio/SelectorManager$SelectSet.doSelect(SelectorManager.java:564)[optimized]
    at org/eclipse/jetty/io/nio/SelectorManager$1.run(SelectorManager.java:285)
    at org/eclipse/jetty/util/thread/QueuedThreadPool.runJob(QueuedThreadPool.java:599)
    at org/eclipse/jetty/util/thread/QueuedThreadPool$3.run(QueuedThreadPool.java:534)
    at java/lang/Thread.run(Thread.java:662)
    at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
    -- end of trace

Original comment by wayahea...@gmail.com on 23 Feb 2014 at 2:55