Read in the heap dump and check what is keeping the memory. visualvm is one such tool, or you could download a trial for yourkit.
Based on the stack trace it appears that the file you're trying to read does not fit into memory. But that could be caused by other objects that are kept in memory. Martijn On Tue, Feb 22, 2011 at 7:30 PM, maxima_2007 <rajadmi...@gmail.com> wrote: > > Hi, > > We using tomcat 6.0.26 on linux and Sun JDK 1.6.0_05, Db - oralce 11g QA > environment getting below error > > Caused by: java.lang.OutOfMemoryError > at sun.misc.Unsafe.allocateMemory(Native Method) > at java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:99) > at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:288) > at sun.nio.ch.Util.getTemporaryDirectBuffer(Util.java:57) > at sun.nio.ch.IOUtil.read(IOUtil.java:205) > at sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:147) > at > com.pega.pegarules.engine.database.InstancesFile.readFile(InstancesFile.java:257) > at > com.pega.pegarules.engine.database.InstancesFile.<init>(InstancesFile.java:132) > at > com.pega.pegarules.engine.database.InstancesFile.<init>(InstancesFile.java:102) > at > com.pega.pegarules.engine.database.PegaArchiveImpl.<init>(PegaArchiveImpl.java:359) > at > com.pega.pegarules.engine.database.PegaArchiveImpl.<init>(PegaArchiveImpl.java:307) > at > com.pega.pegarules.util.PRRuleMgmtUtils.createArchiveForRead(PRRuleMgmtUtils.java:284) > at > com.pega.pegarules.util.PRRuleMgmtUtils.createArchiveForRead(PRRuleMgmtUtils.java:296) > at > com.pegarules.generated.activity.ra_action_archive_getinventory_36fbbb478a6bb92151b451e0e1207305.step1_circum0(ra_action_archive_getinventory_36fbbb478a6bb92151b451e0e1207305.java:219) > at > com.pegarules.generated.activity.ra_action_archive_getinventory_36fbbb478a6bb92151b451e0e1207305.perform(ra_action_archive_getinventory_36fbbb478a6bb92151b451e0e1207305.java:70) > at > com.pega.pegarules.engine.runtime.Executable.doActivity(Executable.java:3049) > at > com.pega.pegarules.engine.context.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:574) > > > and our jvm setting we are using > > export JAVA_OPTS='-Xms3072M -Xmx3072M -Xss128k -server -Xverify:none > -XX:+HeapDumpOnOutOfMemoryError -Xconcurrentio -XX:+UseConcMark > SweepGC -XX:PermSize=512m -XX:MaxPermSize=512m -XX:+DisableExplicitGC > -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+UsePerfData -XX: > +PrintGCDetails -Xloggc:/opt/prpc/pegalog/GC.log > -Dcom.sun.management.jmxremote.port=19004 > -Dcom.sun.management.jmxremote.authentica > te=false -Dcom.sun.management.jmxremote.ssl=false' > > Any one any suggestions please > > Thanks in Advance > > Max. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Caused-by-java-lang-OutOfMemoryError-at-sun-misc-Unsafe-allocateMemory-Native-Method-tp3319788p3319788.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
