one my server instances has started to go haywire in a multi-instance setup running adobe coldfusion 8.1 enterprise. the built in cf server monitor is throwing these alert snapshots constantly, however, this same box is running Fusion Reactor {http://www.fusion-reactor.com/fr/} and I can not figure out where they are coming from. anyone have any pointers or a good tool to decode these files?
full link: http://pastebin.com/42M2Nzpj
"CM Configuration Updater" prio=5 tid=82 WAITING
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:76)
at java.lang.Thread.run(Thread.java:662)
"AWT-Windows" prio=6 tid=299 RUNNABLE
at sun.awt.windows.WToolkit.eventLoop(Native Method)
at sun.awt.windows.WToolkit.run(WToolkit.java:293)
at java.lang.Thread.run(Thread.java:662)
"Signal Dispatcher" prio=9 tid=5 RUNNABLE
"Timer-3" prio=5 tid=67 TIMED_WAITING
at java.lang.Object.wait(Native Method)
at java.util.TimerThread.mainLoop(Timer.java:509)
at java.util.TimerThread.run(Timer.java:462)
"scheduler-4" prio=5 tid=36 TIMED_WAITING
at java.lang.Object.wait(Native Method)
at jrunx.scheduler.SchedulerService.createRunnable(SchedulerService.java:188)
at jrunx.scheduler.ThreadPool$ThreadThrottle.createRunnable(ThreadPool.java:349)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:62)
"jrpp-145" prio=5 tid=11622 RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
at jrun.servlet.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:581)
at jrun.servlet.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:573)
at jrun.servlet.jrpp.ProxyEndpoint.readInt(ProxyEndpoint.java:591)
at jrun.servlet.jrpp.ProxyEndpoint.readRequest(ProxyEndpoint.java:231)
at jrun.servlet.jrpp.JRunProxyService.swapRunnable(JRunProxyService.java:143)
at jrunx.scheduler.ThreadPool$ThreadThrottle.swapRunnable(ThreadPool.java:410)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:76)
I suspect you have an snapshot/alert set to collect a snapshot file when your JVM allocates more than 1000 megabytes of memory. This is probably not a great idea since under normal circumstances your Jvm might indeed allocate that much and recover with a GC. I would look at your alert/snapshot settings and adjust them.