on 05-14-2008 12:18 PM
2008-05-14 15:28:51,609 ERROR SAPEngine_Application_Thread[impl:3]_34 org.apache.struts.actions.DispatchAction - Dispatch[/FixAutoDocument] to method update returned an exception
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor1563.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:280)
at org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:216)
at com.pcm.web.pubs.action.AppDispatchAction.execute(AppDispatchAction.java:110)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
at com.pcm.web.pubs.filter.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:128)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.OutOfMemoryError
very thank
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
can i setup frequency of Garbage collection ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You cannot set up Garbage collection frequency. it is internally handled by Java when the Heap size is filled up.
You can always fine tune your server to SAP recommendations.
Note 723909 is a good starting point.
Also other checks include that you use SAP recommended Java versions, OS patches and also that you have enough physical memory.
Thanks & Regards,
Vijith
Hi,
Many JVMs can be configured to write a heap dump (a snapshot of the whole java heap) when an OutOfMemoryError occurs. This data is usually enough to see where the memory is kept. How to get a heap dump you can find [here|https://www.sdn.sap.com/irj/sdn/wiki?path=/pages/viewpage.action&pageid=33456]
We (at SAP) developed a tool for analyzing heap dumps, and recently contributed it to Eclipse as open source. More info where to download the tool from you can find on our Wiki page: https://www.sdn.sap.com/irj/sdn/wiki?path=/display/java/javaMemoryAnalysis.
To start looking for the leak you can see my SDN [blog Finding Memory Leaks with SAP Memory Analyzer|https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/6856] [original link is broken] [original link is broken] [original link is broken];. The buttons have changed from the time when I wrote the blog, but I hope you will find the new ones.
If you need more help, just let me know.
Krum
but this message shows after server run a long time
?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Out of memory error. Either your system does not have enough Physical RAM to run the application or your server is not fine tuned.
Thanks & Regards,
Vijith
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.