cancel
Showing results for 
Search instead for 
Did you mean: 

Error in single stack Message monitoring tool

Muniyappan
Active Contributor
0 Kudos

Hi,

I am getting this error in Pimon database tab.

Error retrieving data: javax.management.openmbean.InvalidKeyException: Argument key="SenderPartnerName" is not an existing item name for this CompositeData instance.; check trace files or contact support for further assistance

But message over works fine.

this is java single stack 7.4 and sp08.

if i use nwds to monitor iflow, and click on message id, i am getting below error.

java.lang.NoSuchMethodError: com.sap.aii.mdt.util.message.MessageFacade.getCommonMessage(Ljava/lang/String;Ljava/lang/String;Z)Lcom/sap/aii/mdt/util/message/CommonMessage;

  at com.sap.tc.lm.itsam.co.ui.xi.msg.ximessagedetailed.MsgDetailedView.onPlugDetailedMessage(MsgDetailedView.java:514)

  at com.sap.tc.lm.itsam.co.ui.xi.msg.ximessagedetailed.wdp.InternalMsgDetailedView.wdInvokeEventHandler(InternalMsgDetailedView.java:394)

  at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)

  at com.sap.tc.webdynpro.progmodel.window.ViewController.invokeInboundPlugHandler(ViewController.java:446)

  at com.sap.tc.webdynpro.clientserver.cal.NavigationManager.processInboundPlugQueue(NavigationManager.java:305)

  at com.sap.tc.webdynpro.clientserver.cal.NavigationManager.navigate(NavigationManager.java:320)

  at com.sap.tc.webdynpro.clientserver.phases.NavigationPhase.execute(NavigationPhase.java:63)

  at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)

  at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)

  at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)

  at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)

  at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)

  at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)

  at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)

  at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)

  at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)

  at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)

  at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)

  at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)

  at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:101)

  at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:55)

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

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

  at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)

  at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)

  at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)

  at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)

  at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)

  at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)

  at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)

  at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

  at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)

  at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)

  at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)

  at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

  at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

  at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Please let me know if there is any note/patch update to solve this.

Regards,

Muni

Accepted Solutions (1)

Accepted Solutions (1)

Muniyappan
Active Contributor
0 Kudos

SAP told that PI system has inconsistency in the components. some are in 8 and some are in 10.

CORE-TOOLS PI 7.40 SP 8  PL 0
MESSAGING     PI 7.40 SP 10 PL 7
SAP_XIADMIN   PI 7.40 SP 8  PL 0
SAP_XIAF      PI 7.40 SP 10 PL 7
SAP_XIESR     PI 7.40 SP 8  PL 0
SAP_XIGUILIB  PI 7.40 SP 8  PL 0
SAP_XITOOL    PI 7.40 SP 10 PL 4
SERVERCORE    PI 7.40 SP 8  PL 0
SOAMON        PI 7.40 SP 8  PL 0
SOAMONBASIC   PI 7.40 SP 8  PL 0


we have updated system to SP 11. now monitoring tool works fine.

Regards,

Muni


Answers (3)

Answers (3)

iaki_vila
Active Contributor
0 Kudos

Hi Muniyappan,

I have a PI 7.4 SP08 and i don't remember your issue and any post-installation step relevant for that problem. Do you know what is your patch level?, check my system about the monitoring components:

Talk with your basis team if you have the ultimate patch installed.

Regards.

Muniyappan
Active Contributor
0 Kudos

seems system is having same as yours.

pvishnuvardan_reddy
Active Contributor
0 Kudos

Hi Muniyappan,

Can you please cross check whether you are maintaining proper parameters in the message header for searching the messages.

It looks like something is not right as the error logs are referring to.

Else, you can do one thing, from Message Status Overview tab, click on the successful message value, then it will navigate you to the Database tab. There you can see the sender and receiver details etc..

Cross check whether you are putting the same parameters in the respective headers for searching out.

Regards

Vishnu

Muniyappan
Active Contributor
0 Kudos

it does not help. when i click on successful message in overview tab, getting same error.

if i dont give anything in the filter of database, same error.

pvishnuvardan_reddy
Active Contributor
0 Kudos

Hi Muniyappan,

You mean to say, you are not able to view any messages in database tab with or without filter, am I right?

If yes, then there could be some issue with the post installation steps.

Can you please check with your basis team about the post installation.

Regards

Vishnu

Muniyappan
Active Contributor
0 Kudos

That is correct. i will check with them.

manigram
Active Participant
0 Kudos

Hello ,

Is this new server upgraded or installed, post installation steps has been done or anything pending?

Regards,

Manigandan

Muniyappan
Active Contributor
0 Kudos

Hi,

this is newly installed system. could you please let me know how to check if post installation has benn completed successfully.

former_member183908
Active Contributor
0 Kudos

check the status of the post installation steps in NWA-->Configuration--->Scenarios--->Configuration Wizard-->From drop down history of executed tasks.

make sure the steps were executed successfully with out any issues

also you can disable your functional units and re-run the post installation steps,make sure the user should be Administrator

Thanks

Muniyappan
Active Contributor
0 Kudos

Hi pavan,

please find the installation steps history.