SAP Knowledge Base Article - Preview

2503363 - 500 Internal Server Error when accessing message ID after an upgrade

Symptom

When trying to access a message ID from the Message Monitor or from Communication Channel Monitor after an upgrade in the PI/PO system, the following error occurs:

500 Internal Server Error
Failed to process request. Please contact your system administrator.
 
In defaultTrace files the following error can be seen:

500 Internal Server Error is returned for HTTP request [http://host:port/webdynpro/resources/sap.com/tc~lm~itsam~ui~mainframe~wd/FloorPlanApp]:
component [forwardServlet],
web module [webdynpro/resources/sap.com/tc~lm~itsam~ui~mainframe~wd],
application [sap.com/tc~lm~itsam~ui~mainframe~wd],
DC name [sap.com/tc~lm~itsam~ui~mainframe~wd],
CSN component[BC-NWA-INC-UIF],
problem categorization [],
internal categorization [-1735455278].

[EXCEPTION]
java.lang.RuntimeException: Attribute MessageData cannot be retrieved.
at com.sap.aii.mdt.itsam.mbeans.compositedata.ProxyCompositeDataSupport.get(ProxyCompositeDataSupport.java:156)
at com.sap.tc.lm.itsam.ui.proxy.JMXGenericModelClassCData.getRelatedModelObjects(JMXGenericModelClassCData.java:291)
at com.sap.tc.lm.itsam.ui.proxy.JMXAbstractModelClass.getRelatedModelObjects(JMXAbstractModelClass.java:101)
at com.sap.tc.lm.itsam.co.ui.xi.msg.wd.model.SAP_ITSAMXIAdapterMessageList.getMessageData(SAP_ITSAMXIAdapterMessageList.java:132)
at com.sap.tc.lm.itsam.co.ui.xi.msg.ximessagedetailed.MessageFilter.retrieveAdaperMessageList(MessageFilter.java:404)
at com.sap.tc.lm.itsam.co.ui.xi.msg.ximessagedetailed.wdp.InternalMessageFilter.retrieveAdaperMessageList(InternalMessageFilter.java:905)
at com.sap.tc.lm.itsam.co.ui.xi.msg.ximessagedetailed.MessageFilterView.fillMessageList(MessageFilterView.java:1420)
...
...
Caused by: java.lang.RuntimeException: No proper getter method exist.
at com.sap.aii.mdt.itsam.mbeans.compositedata.ProxyCompositeDataSupport.loadLocalMethods(ProxyCompositeDataSupport.java:71)
at com.sap.aii.mdt.itsam.mbeans.compositedata.ProxyCompositeDataSupport.<init>(ProxyCompositeDataSupport.java:57)
at com.sap.aii.mdt.itsam.mbeans.compositedata.ProxyCompositeDataSupport.get(ProxyCompositeDataSupport.java:140)
Caused by: java.lang.NoSuchMethodException: com.sap.aii.mdt.itsam.mbeans.compositedata.SAP_ITSAMXIAdapterMessageData.getMessagePriority()
at java.lang.Class.getMethod(Class.java:1654)


Read more...

Environment

  • SAP enhancement package 1 for SAP NetWeaver 7.3
  • SAP NetWeaver 7.4
  • SAP NetWeaver 7.5

Product

SAP NetWeaver 7.0 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP NetWeaver Process Integration 7.1 ; SAP NetWeaver Process Integration, business-to-business add-on 1.0 ; SAP NetWeaver Process Integration, connectivity add-on 1.0 ; SAP NetWeaver Process Integration, secure connectivity add-on 1.0 ; SAP enhancement package 1 for SAP NetWeaver 7.0 ; SAP enhancement package 1 for SAP NetWeaver 7.3 ; SAP enhancement package 1 for SAP NetWeaver Process Integration 7.1 ; SAP enhancement package 2 for SAP NetWeaver 7.0 ; SAP enhancement package 3 for SAP NetWeaver 7.0

Keywords

Process Integration 7.31, PI 7.31, Process Orchestration 7.4, PI 7.4, PO 7.4, Process Orchestration 7.5, PI 7.5, PO 7.5, XI, AEX, message monitor, message monitoring, communication channel monitor, 500 internal server error, upgrade, update, patch, support p ackage, upgradation, message overview , KBA , BC-NWA-XPI , Process Integration Monitoring , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.