LMS 2.6 HTTP Status 500 Error

Answered Question
Jul 6th, 2007
User Badges:

Hello,


I get the HTTP Status 500 - Internal Server Error when trying to access the package map for RME. Common Services > Device Update > Resource Manager Essentials.


The content of the error message is: type Exception report


message Internal Server Error


description The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request.


exception


java.util.NoSuchElementException

at java.util.StringTokenizer.nextToken(StringTokenizer.java:259)

at com.cisco.nm.xms.psu.ui.gui.model.action.DevUpdate.getPackageMap(Unknown Source)

at com.cisco.nm.xms.psu.ui.gui.model.action.DevUpdate.perform(Unknown Source)

at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1786)

at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1585)

at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:491)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)

at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)

at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)

at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)

at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)

at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)

at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)

at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)

at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)

at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)

at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)

at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)

at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)

at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)

at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)

at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)

at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)

at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:457)

at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:576)

at java.lang.Thread.run(Thread.java:534)




Any ideas appreciated.

Correct Answer by Joe Clarke about 9 years 8 months ago

Sorry, typo. New file is attached. Note: you may get a log4j error running this, but that is harmless.



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Joe Clarke Fri, 07/06/2007 - 08:11
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Please post your NMSROOT/lib/classpath/com/cisco/nm/xms/psu/conf/tag.properties file.

Joe Clarke Mon, 07/09/2007 - 12:10
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Please attach NMSROOT/setup/rme.info, cm.info, cmf.info, cdone.info, dfm.info, cvw1.info, nmim.info, and ipm.info.

Joe Clarke Tue, 07/10/2007 - 06:00
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

These look okay. You must have a bad package map. Unfortunately, from this log snippet, I cannot see which map file may be problematic. Therefore, I will need to see them all. Please post all PackageMap.map files under NMSROOT/www/classpath/com/cisco/nm/xms/psu/maps.

Joe Clarke Tue, 07/10/2007 - 08:52
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Your RME device and package maps are corrupt. These files cannot be easily repaired, so they will need to be regenerated. Run the attached CMD file as a local Administrator to regenerate these files (note: you should first delete the originals).


There should be no output, and when it completes, the rmePackageMap.map and rmeDeviceMap.map should be back.



Attachment: 
neonetsup Tue, 07/10/2007 - 09:44
User Badges:

Getting the message "The system cannot find the path specified." when running the .cmd file; is there something I should be tweaking in that file?

Correct Answer
Joe Clarke Tue, 07/10/2007 - 09:48
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Sorry, typo. New file is attached. Note: you may get a log4j error running this, but that is harmless.



Attachment: 

Actions

This Discussion