JVM crashes after some time of running the system. Using JbossDrools , ehcache

Bug #744149 reported by kaustubh priye
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openjdk-6 (Ubuntu)
New
Undecided
Unassigned

Bug Description

I am using Jboss Drools for doing some Event processing, It has good amount of data. Plus our application requires to store the data for some time hence we are using ehcache's, LRU model.

Other tools :
1) JBoss Drool
2) ActiveMq
3) ehcache

JVM opts :-d64 -server -Xms2048m -Xmx2048m -XX:MaxPermSize=512m -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:gclogs.txt -Dcom.sun.management.jmxremote -Djava.rmi.server.hostname=192.168.5.33 -Dcom.sun.management.jmxremote.port=14000 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false

I tried running the system by sending 20 events per second. This event was sent to ActiveMQ. Which is another server. (JVM) from ActiveMQ messages are sent to our main server where processing happens. Processing involves heavy usage of JBoss Drools, and each of such Events are stored in ehcache. We are using LRU model of ehcache.

Have set memory to 2GB and have monitored memory through Jconsole and even gc logs. But memory boundaries were never breached.
I changed the number of events to be stored by ehcache from 1000 to 500 to 400 to 300. But as the memory boundaries were never breached, this couldnt be a reason.

Even GC limit reached message was never found, which happens if the crash was due to memory constraint.

Please look into the issue and help.

Thanks in advance.

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability: yes → no
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.