Message monitoring link error in RWB

hi,
When we select adapter engine in RWB in SAP XI It throws an error:
java.lang.AbstractMethodError: com/sap/aii/mdt/api/server/AdapterFrameworkHome.create(Ljava/util/Locale;Ljava/util/TimeZone;Ljavax/ejb/Handle;Ljavax/management/ObjectName;Ljava/lang/String;Z)Lcom/sap/aii/mdt/api/server/MessageMonitoring;
Exception id: [E41F131007D0007300000041001E90FE000491736486E774]
kindly help.
Regards,
Priya

hi vijay,
I have upgraded the patch level of LMtools,SAP_XIAFC, and SAP_XIAF to the latest level.
Infact i have updated the entire Java patches to the latest support patch.
Try this. hope this will solve your problem.
Regards,
Priya

Similar Messages

System error in message monitoring

Hello,
Scenario is proxy to database. Status seems to sytem error in message monitoring. Error detail is In audit log of message details as belows:
JDBC Message processing failed, due to Error processing request in sax parser: Error when executing statement for table/stored proc. 'If_test ' (structure 'STATEMENT'): java.sql.SQLException: ORA-00936: missing expression
I should resent this message content. When i press Resend tab in message monitoring, error status is not being changed.
Thanks in advance

Hi,
Check the payload received is correct or not in this case ...
Take payload and check at mapping level...
if you are using insert or update statement you can enable log at the receiver jdbc channel in advance mode(logSQLStaement to true) to see how the statement is getting framed ...
HTH
Rajesh

Browser: Shortcut to Message-Monitoring URL in RWB?

Hi everybody,
does anybody know a shortcut to Message-Monitoring URL in the RWB?
I hate clicking
Regards Mario

Hi,
Do this to get the Short cut to RWB--Message Monitoring
1) Right click on the Desktop-say New-Shortcut
2)provide the location as http://hostname:Port/rwb/index.jsp
3)Say Next
4)Provide what evr the name you want and say Finish
Come to Desktop and double click on the Icon
Regards
Seshagiri

Message Services Message Monitor not opening in MII.

Hi All,
We have deployed MII 14.0/ME 6.1 on Netweaver 7.3.
In MII, Message Services > Message Monitor link not opening and we get the following error message.
Has any one faced this issue? whats the fix for this.
Detailed Error Information
Detailed Exception Chain
java.lang.NoSuchMethodError: com.sap.xmii.ejb.messages.MessageService.count([Ljava/lang/String;Ljava/lang/String;[Ljava/lang/Integer;Ljava/lang/String;Ljava/sql/Timestamp;Ljava/sql/Timestamp;[Ljava/lang/Integer;)J
at com.sap.xapps.xmii.ui.admin.messages.messagesmodel.SearchResultObservableList.getSize(SearchResultObservableList.java:52)
at com.sap.xapps.xmii.ui.admin.messages.messagesmodel.SearchResultObservableList.<init>(SearchResultObservableList.java:33)
at com.sap.xapps.xmii.ui.admin.messages.monitorcomp.MessagesComp.search(MessagesComp.java:395)
at com.sap.xapps.xmii.ui.admin.messages.monitorcomp.wdp.InternalMessagesComp.search(InternalMessagesComp.java:243)
at com.sap.xapps.xmii.ui.admin.messages.monitorcomp.MonitorView.onPlugIn(MonitorView.java:702)
at com.sap.xapps.xmii.ui.admin.messages.monitorcomp.wdp.InternalMonitorView.wdInvokeEventHandler(InternalMonitorView.java:429)
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:89)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:373)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:499)
at com.sap.tc.webdynpro.serverimpl.wdc.ForwardServlet.doPost(ForwardServlet.java:73)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
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:276)
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)
Any help would be highly appreciated.
Thanks,

Hi Shridhar,
Check if XMII and MII_ADMIN are from the same SP. That might happen if they are from different SPs.
Best regards,
Krasi

Monitor input error

Moved recently and Gateway 3250S, reconnected monitor input error showed up on monitor. Computer doctor did virtual diagnostic and said it was the graphics card. Plus fan wasn't working. Sent specs to purchase return hp Pavilion 6000 pro.MXLO180WRK. Bought & set up the desktop yesterday 7/9/15 with appropriate chords. Turned monitor first, then cpu. Received same error message: Monitor input error. Monitor going to sleep. As per where I bought computer switched out chords and monitors. Still same error. Where purchased hp suggested I bring everything in and they'll do a diagnostic. That involves renting a car & finding the time.

The standard Blue & White G3 has a 15-pin 3-row connector that connects to most third-party monitors. So cable adapters should not be the issue here.
There are two places that hold onto the screen resolution. The first is the PRAM, backed up by the PRAM backup/clock battery. If you have had a power failure or pulled the main power plug, and are now having this trouble, that battery is the prime suspect. I suggest you open the side door on the Mac, find the tiny button nearest the battery, and press and hold it for a quarter minute. then allow at least 5 seconds to pass before you attempt to power up. If the symptoms change, consider replacing the battery.
The other place the display resolution is stored is in a Preference file. To accommodate an environment with multiple users on multiple computers, the display setting used after you log in is stored in:
Hard Drive / Users / your_id / Library / Preferences / By Host / com.apple.preference.displays.yourHWAddress.plist
If you can boot to a different software source such as a System CD, you can both bypass the bad value stored in that preference file and gain access to that preference file to move it to another location (which will inactivate it).

Sqlplus stack trace, dynamic link error.

When using sqlplus through the Oracle Enterprise Manager, or on the commandline, if I try to query a XMLType table, it dumps a stack trace, failing with the error message:
Dynamic link error: libxdb.so: cannot open shared object file: No such file or directory
I've done a full Oracle 9.2.0.1.0 Client installation, but this library isn't in my $ORACLE_HOME/lib. How do I get this file?

Hi,
Maybe not much use to you, but on Solaris, with a full Enterprise install, this library is in my $ORACLE_HOME/lib.
So maybe you can find it on the EE CDROM?
Regards
Pete

Jdbc adapter error on confirmation message in message monitor (rwb)

I have the scenario iDoc -> PI 7 - > jdbc (AS400 odbc driver).
When I do INSERT statements, the data is stored in the Database and the RWB message monitoring shows status Successfull.
However, for every insert, an other message shows up in the message monitoring with reversed Sender and Receiver (so it looks like a confirmation message is trying to find its way back to XI). This message first is is Status "Waiting", and after some time gets in Status "System Error".
As I am not expecting any responses in my XI configuration (as I have no place to send them to), I want to stop these messages showing up in the Adapter Engine (as there will be many Error Status messages that are of no interest to me).
How can I stop these messages, or what should I do in XI to process them (and dump them in my receiver determination). I have NO BPM involved .

Hi,
For each open connection a entry is made j2ee stack.So when the it reaches to max and execption is thrown.
In Jdbc adapter configuration -> advance mode -> Set -> Disconnect from the database after processing each message.
Should solve the prob
<b>Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*</b>

Messages remain in Scheduled status in message monitoring in RWB

Hi PI experts,
I have got a situation where there are several messages showing in the Scheduled status. I followed the path RWB > Message Monitoring > Adapter Engine > Database (Overview) > Display.
QoS for these messages is EOIO, however there are no messages stuck in the queue. All other channels are running smoothly. Only with this particular channel the messages remain in Scheduled status for a long time.
I am neither able to make out the roor cause nor reprocess/resend these messages. Pleaes help.
Regards,
Dhawal

Hi Suraj,
What you said is absolutely correct. However, as I mentioned, the error message was not visible in RWB.
My problem just got resolved. What I did is this,
I followed the link http://<server>:<port>/MessagingSystem/monitor/monitor.jsp which is SAP Message Display Tool.
Here in EOIO Sequence Monitor I found the error message and it's predecessor. When I resent the erroneous message from here, all subsequent Holding messages got processed.
Thank you everyone for your help. Have a gr8 day...
Best Regards,
Dhawal

Hi. about monitor message of integration engine from RWB.

I want to monitor message of iintegration engine from RWB.
but i can not open message content tab page and queue monitor tab page.
hint is : SSO login failed. need to logon again.
which user should i use to logon?
i tried so many user not to be able to logon successuflly.

Hi Joy,
if you want to use the SSO functionality for any component you need to maintain it first....i think u SSO configurtion is not yet done ....and hence you are getting the above error.......
Pls chk the below link....thsi is for PI 7.1...
http://help.sap.com/saphelp_nwpi71/helpdata/EN/32/1c1041a0f6f16fe10000000a1550b0/content.htm
Hope this will help..
Regds,
Pinangshuk.

'System Error' status at Message Monitoring( HTTP to FILE )

I have created a scenario HTTP to FTP. I sent message to XI server using the HTTP Client.
After sending the message I am getting the response at browser.
Result:
http-Status: 200 Message accepted
Payload:
But when I look in to the Message monitoring at RWB, I am getting the message status as
System error. while going to the details i can see below error category.
Error Category MAPPING
Error Code EXCEPTION_DURING_EXECUTE
(Is the password different for port 50000 and 8000)
Please help me to solve this issue.
Thanks in Advance,
John

This is the trace message that I got for this error
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:41) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:70) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:231) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:63) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) 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:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_HTTP2File_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46)</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_HTTP2File_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:72) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) 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:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:41) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:70) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:231) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:63) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) 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:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)</Trace>

Java.lang.NullPointerException in Message Monitoring-RWB

Hi Experts,
I am getting java.lang.NullPointerException in Message monitoring.Here is the detail trace of the error message.
Stack trace for the above error message is:
java.lang.NullPointerException
     at com.sap.aii.mdt.util.SelectModel.getComponentLabel(SelectModel.java:192)
     at jsp_monitor_new1226507446052._jspService(jsp_monitor_new1226507446052.java:174)
     at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)
     at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)
     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.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:427)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:358)
     at com.sap.aii.rwb.web.messagemonitoring.viewcontroller.MmDynPage.doProcessBeforeOutput(MmDynPage.java:69)
     at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:123)
     at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
     at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)
     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.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at jsp_FC_Secure1226507436137._jspService(jsp_FC_Secure1226507436137.java:24)
     at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     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:175)
     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)
Wait...
Query being processed
Please help me how to resolve the issue.
Thanks,
Bharath.

Hi Bharath,
Check SAP note no.1250954 for solution. It has the solution to the problem you are facing might be ralated to the SP levels you have, you need to installl some patch from this note.
Thanks!

Error in RWB for EbXML Message

Hello Experts,
We are facing an issue with the Seeburger Adapter. When we trigger message TO THE sEEBURGER sYSTEM USING THE eBxml adapter, the message is successfully processed in PI 7.1 and shows a checkered flag. But on analyzing the related message details in RWB > Message Monitoring > Adapter Engine of Seeburger, it shows the following exception:
Message could not be forwarded to the JCA adapter. Reason: Fatal exception: com.seeburger.xi.connector.queue.TaskBuildException: No message payloads which match <MainDocument> found!, No message payloads which match <MainDocument> found!
Adapter Framework caught exception: Fatal exception: com.seeburger.xi.connector.queue.TaskBuildException: No message payloads which match <MainDocument> found!, No message payloads which match <MainDocument> found!
Delivering the message to the application using connection EbXML_HTTP_http://seeburger.com/xi failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: Fatal exception: com.seeburger.xi.connector.queue.TaskBuildException: No message payloads which match <MainDocument> found!, No message payloads which match <MainDocument> found!.
We had imported the Seeburger metadata of version 2.1.3 and we are using it with PI 7.1.
Pls advice.
Thanks in advance,
Elizabeth.

Have you checked the Audit log in Runtime Workbench? Using it, you could come to know which module of the receiver channel went in error. Are you doing some user mapping or is it a standard one? The problem could be related to the undeployed mapping or mismatch in the format.
Regards,
Prateek

Error in Message Monitoring in XI.

Hi All
Affter clicking Message Monitoring in RWB there is DETAIL button above the message listed when i am trying to click on the detail button it shows the error like "The page cannot be displayed".
pls help me .
Thaking you in advance.

Hi Hiren,
Plz check below mentioned blog. It will help you out:
<a href="/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi:///people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Regards,
Subhasha

Java.lang.OutOfMemoryError during message monitoring in RWB

Java Engine Problem during message monitoring in runtime workbench!!
Posted: Nov 12, 2007 2:13 AM Edit E-mail this message Reply
Hi,
Our integrating processes are processing successfully.
But there is a problem during message monitoring.
When I use message monitoring in RWB,
Integration Engine monitoring has no problem.
But there is a problem during displaying adapter engine monitoring.
The message is "java.lang.OutOfMemoryError: Java heap space".
So I cannot see any adapter engine message.
Actually same error occurred 3 weeks ago.
At that time, we solved the problem with restarting java service.
Does anyone know about this appearance?
And is there any other solution about this problem??
Thank you.

Hi,
As per the error analysis, it seems that the java heap space is low. So need to increase the heap size.
1. Go to the C:\SAP\JP1\JC00\j2ee\configtool folder
2. Start configtool.bat
3. Go to cluster-data -> template - template_javaee -> instance - IDxxxxx
4. Go to the VM Parameters tab and edit the maxHeapSize property
5. Save and restart the system.
I hope this will solve the problem.
Regards,
Sarvesh
***Reward points, if it helped you.

Message processing not visible in RWB Message monitoring

Hi Experts,
There is an issue where messages are visible at ABAP Stack(SXMB_MONI).But same messages are not visible at RWB Message monitoring Integration server(IE and AE) Level.
Previously adapter status for this scenarios was Inactive in integration directory we taught this could be the issue and made adapter status active in Integration Directory. This did not solve the issue.
When payload is taken and processed from test message tab under RWB-Component monitoring-Integration Engine.
Messages are visible in RWB Message monitoring.
Experts could you please help in finding out what could be the issue,Please let me know if any additional information is required,
Thanks in Advacne,
Seshu.K

There is an issue where messages are visible at ABAP Stack(SXMB_MONI).But same messages are not visible at RWB Message monitoring Integration server(IE and AE) Level.
Check if you have chosen the Status filter as ALL and not "Error".
If you are loking for old messages, then you will not be able to see succesful messages beyond a particular period in the past, since all the succesful messages would have been archived.
To see such messages, you have to choose, the option, show message from "Archive" and not "Database".

Message monitoring link error in RWB

Similar Messages

Maybe you are looking for