01-14-2011 07:38 AM
Hi,
When I select Job Broser I get the following crash, LMS 3.2, server has been restarted but I continue to get the error :
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.omg.CORBA.NO_MEMORY: Server-side Exception: java.lang.OutOfMemoryError: Java heap space
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
java.lang.reflect.Constructor.newInstance(Constructor.java:494)
org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:223)
org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:321)
org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1074)
org.jacorb.orb.Delegate.invoke(Delegate.java:939)
org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:80)
com.cisco.nm.cmf.jrm._JobIterHistStub.get_job_filter_pattern(_JobIterHistStub.java:82)
com.cisco.nm.cmf.jrm.uii.JrmJobBrowserAction.getJobList(JrmJobBrowserAction.java:545)
com.cisco.nm.cmf.jrm.uii.JrmJobBrowserAction.perform(JrmJobBrowserAction.java:365)
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1786)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1585)
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:491)
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
com.cisco.nm.cmf.util.AccessLogFilter.doFilter(AccessLogFilter.java:128)
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.17 logs.
Any ideas
Thanks
01-15-2011 09:39 PM
You may have so many jobs in the system that Tomcat is running out of memory trying to list them all. Can you launch the RME Job Browser and clean up some of those jobs so that the CS Job Browser will launch?
05-14-2012 12:34 PM
I am getting the same message, but am unable to open RME job browser? How should I proceede?
05-14-2012 06:31 PM
This can be a dangerous step, but it can quickly clear out a lot of JRM jobs. You must have a full LMS backup before trying this.
Shutdown jrm with the command "pdterm jrm".
Login to dbreader and run the following SQL query:
DELETE FROM JRM WHERE run_state != 0 AND run_state != 1 AND run_state != 9 AND (sch_type = 1 OR sch_type = 2)
Restart the Daemon Manager.
If you have any questions, you should contact TAC. And again, make sure you have a full LMS backup before trying this.
01-10-2013 07:39 AM
Hi,
I have the same problem, but with LMS 4.2.2.
My question is: why is this a dangerous step? What can occur in the worst case?
Thanks
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide