RE: InvocationTargetException results OutOfMemory issue ascodecache is full in tomcat 5.5
Hi Chuck, We have increased the codecache for the workaround, found the root casue of this issue is in drool 4.0.7 which we have recenlty integrated in our application. For a permanent fix we will post in jboss drool forum . -- View this message in context: http://www.nabble.com/InvocationTargetException-results-OutOfMemory-issue-as-codecache-is-full-in-tomcat-5.5-tp25745877p25815858.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: InvocationTargetException results OutOfMemory issue as codecache is full in tomcat 5.5
Hi, Thaks for your replies. My server OS is : Windows 2003 server (by mistake above it is given as XP). JVM is 1.6.0 Both are 64 Bit We are not using JSP's . We are using orbeon3.7 (www.orbeon.com) xslt for web forms. In which using oxf:processor where our Java classes are build dynamically. Using probe we observered code cache is reaching it's maximum size. -- View this message in context: http://www.nabble.com/InvocationTargetException-results-OutOfMemory-issue-as-codecache-is-full-in-tomcat-5.5-tp25745877p25764679.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: InvocationTargetException results OutOfMemory issue as codecache is full in tomcat 5.5
Thanks to all for your reply. Today also we have received same issue. After Continuously monitoring probe found that codecache reached 48MB and after that 3 users faced issue. Is there any setting in JAVA_OPTS to refresh the codecache once it reaches to maximum? -- View this message in context: http://www.nabble.com/InvocationTargetException-results-OutOfMemory-issue-as-codecache-is-full-in-tomcat-5.5-tp25745877p25767299.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
InvocationTargetException results OutOfMemory issue as codecache is full in tomcat 5.5
Hi, After tomcat running 3,4 days well with 75 users, suddenly we are facing InvocationTargetException caused by OutOfMemoryError for 3,4 users some times. The JAVA_OPTS options are well configured as observed no heap error issue. Heap utilization is only 60% but Foud that CodeCache is reaching maximum always. But codecache is non heap. Currently everyday out of production time we are restarting server to avoid sudden exception in production. The following is the exception we received as suggestion of finding the root cause. In exception logs there is no permgen space erorr or heap error. Observed by probe after 2/3days codecache is becoming full only results in OutOfMemory as below java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor2049.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.orbeon.oxf.processor.SimpleProcessor$1.readImpl(SimpleProcessor.java:70) at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:995) at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:1178) at org.orbeon.oxf.processor.JavaProcessor$1.readImpl(JavaProcessor.java:66) at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:995) at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:1178) at org.orbeon.oxf.processor.ProcessorImpl.readInputAsSAX(ProcessorImpl.java:350) at org.orbeon.oxf.processor.pipeline.AggregatorProcessor.access$100(AggregatorProcessor.java:38) at org.orbeon.oxf.processor.pipeline.AggregatorProcessor$1.readImpl(AggregatorProcessor.java:93) at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:995) ... at org.orbeon.oxf.processor.ProcessorImpl.readInputAsDOM4J(ProcessorImpl.java:368) at org.orbeon.oxf.processor.ProcessorImpl.readInputAsDOM4J(ProcessorImpl.java:387) at com.expeditor.processors.SingleTaskData.generateData(SingleTaskData.java:85) at sun.reflect.GeneratedMethodAccessor2048.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.orbeon.oxf.processor.SimpleProcessor$1.readImpl(SimpleProcessor.java:70) at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:995) at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:1178) at org.orbeon.oxf.processor.JavaProcessor$1.readImpl(JavaProcessor.java:66) .. at org.orbeon.oxf.pipeline.InitUtils.runProcessor(InitUtils.java:95) at org.orbeon.oxf.webapp.ProcessorService.service(ProcessorService.java:96) at org.orbeon.oxf.portlet.OPSPortletDelegate.forward(OPSPortletDelegate.java:253) at org.orbeon.oxf.externalcontext.PortletToExternalContextRequestDispatcherWrapper.forward(PortletToExternalContextRequestDispatcherWrapper.java:35) at org.orbeon.oxf.xforms.XFormsSubmissionUtils.openOptimizedConnection(XFormsSubmissionUtils.java:108) at org.orbeon.oxf.xforms.XFormsModelSubmission.performDefaultAction(XFormsModelSubmission.java:768) at org.orbeon.oxf.xforms.XFormsContainingDocument.dispatchEvent(XFormsContainingDocument.java:1283) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:684) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:876) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.OutOfMemoryError at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2427) at java.lang.Class.getDeclaredMethods(Class.java:1791) at org.codehaus.janino.ReflectionIClass.getDeclaredIMethods2(ReflectionIClass.java) at org.codehaus.janino.IClass.getDeclaredIMethods(IClass.java) at org.codehaus.janino.IClass.getDeclaredIMethods(IClass.java) at org.codehaus.janino.UnitCompiler.getIMethods(UnitCompiler.java) at org.codehaus.janino.UnitCompiler.findIMethod(UnitCompiler.java) at o -- View this message in context: http://www.nabble.com/InvocationTargetException-results-OutOfMemory-issue-as-codecache-is-full-in-tomcat-5.5-tp25745877p25745877.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: InvocationTargetException results OutOfMemory issue as codecache is full in tomcat 5.5
Hi PidSter, Out of 17 Users 5 users have reported that OutOfMemoryErrorException, Other 12 users working fine at that time also. After clearing the cookies from IE6 browser, 4 users got resolved and 1 user got the same issue again .They have worked continuously for five hours before facing this issue. This issue we are not getting frequently. Every 2/3 days we are facing same issue with above exception, so we are restarting servers daily. We are using Tomcat 5.5 Java Version 1.6 OS : Windows XP System RAM size is 16 GB. We have 3 clustered nodes of each 2 GB as follows set JAVA_OPTS=-server –Xms2048m –Xmx2048m -XX:PermSize=1024m -XX:MaxPermSize=1024m -XX:NewSize=768m -XX:MaxNewSize=768m -XX:SurvivorRatio=4 -Xss256K -XX:+UseParallelGC -XX:-UseGCOverheadLimit -XX:HeapDumpPath=heaperror.log -Djava.net.preferIPv4Stack=true -Dfile.encoding=UTF8 -Duser.timezone=EST -Djava.security.auth.login.config=$CATALINA_HOME/conf/jaas.config -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=8210 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false Our application is combinations of Liferay portlet 4.2.1 + Orbeon 3.7 in which java classes are dynamically called. I am experienced with Heap error result in slowness and outofmemory graduallyl earlier for all users. But this is some what memory is 60% only using. But codechche is showing full in probe which is non-heap. (default is 48MB i think, actually it should released) Thanks Regards Venkata -- View this message in context: http://www.nabble.com/InvocationTargetException-results-OutOfMemory-issue-as-codecache-is-full-in-tomcat-5.5-tp25745877p25750784.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
