cancel
Showing results for 
Search instead for 
Did you mean: 

No message reach into Integration Engine ...

zbynek_kabrt3
Participant
0 Kudos

Hello,

I have following problem. I send message to XI through SOAP adapter. But the message doesn't reach of Integration Engine. It is delivered into Adapter Engine and then it stays in status "Waiting". When open message detail in RWB I get these information:

Message Data

Attribute Value

----


Engine Adapter Engine

Status Waiting

Repeatable Yes

Cancelable Yes

Start 29.08.2008 12:14:59

End 29.08.2008 12:14:59

+Sender Party +

Sender Service BS_GetSupperior

Sender Interface http://sntcz.cz/xmlns/holidays

MI_Holiday

+Receiver Party +

+Receiver Service +

+Receiver Interface +

Quality of Service Exactly Once

Error Category XI_J2EE_ADAPTER_XI_HANDLER

Error Code GENERAL_ERROR

Message 55C9628075B311DDABE200301875333B

+Reference +

... and in defaultTrace file occures this message:

#1.5#00301875333B0057000000DE0000109C00045596D2CD72D8#1220006176812#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage, boolean)#J2EE_GUEST#0##srvbr05_NW4_2798750#XISUPER#18255d00759d11ddc1a500301875333b#SAPEngine_Application_Thread[impl:3]_31##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during conversion of XI message#http://srvbr05:8000/sap/xi/engine?type=entry#

#1.5#00301875333B004B0000009D0000109C00045596D2CE9B64#1220006176890#com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension#sap.com/com.sap.aii.af.soapadapter#com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension#XISUPER#2919##srvbr05_NW4_2798750#XISUPER#ecff64f075af11dda90200301875333b#XI SOAP[BS_GetSupperior_SOAP/BS_GetSupperior/]_2449##0#0#Error##Plain###no message ID available#

#1.5#00301875333B0049000001270000109C00045596D3111C00#1220006181250#XIRWB.com.sap.aii.mdt.api.server.MessageMonitoringBean#sap.com/com.sap.xi.mdt#XIRWB.com.sap.aii.mdt.api.server.MessageMonitoringBean#XISUPER#2920##srvbr05_NW4_2798750##f03f74c075af11ddb4ce00301875333b#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/Applications/ExchangeInfrastructure/RuntimeWorkbench#Plain###enrichMessageData(): Error during retrieving the end-to-end-monitoring information

Thrown:

com.sap.aii.rwb.endtoendmonitoring.util.Sxmb_Get_Pmi_Info_Fault_Exception:

at sun.reflect.GeneratedConstructorAccessor358.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:274)

at java.lang.Class.newInstance0(Class.java:308)

at java.lang.Class.newInstance(Class.java:261)

at com.sap.aii.proxy.framework.core.JcoMarshaler.unmarshalException(JcoMarshaler.java:429)

at com.sap.aii.proxy.framework.core.JcoProxy.send(JcoProxy.java:82)

at com.sap.aii.proxy.framework.core.AbstractProxy$JcoProxyHelper.send(AbstractProxy.java:173)

at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:141)

at com.sap.aii.rwb.endtoendmonitoring.util.PMI_PortType.sxmb_Get_Pmi_Info(PMI_PortType.java:28)

at com.sap.aii.mdt.api.server.MessageMonitoringBean.enrichMessageData(MessageMonitoringBean.java:965)

at com.sap.aii.mdt.api.server.MessageMonitoringBean.setMessageList(MessageMonitoringBean.java:762)

at com.sap.aii.mdt.api.server.MessageMonitoringBean.getPureMessageList(MessageMonitoringBean.java:568)

at com.sap.aii.mdt.api.server.MessageMonitoringObjectImpl0.getPureMessageList(MessageMonitoringObjectImpl0.java:1016)

at com.sap.aii.mdt.api.server.MessageMonitoring_Stub.getPureMessageList(MessageMonitoring_Stub.java:1772)

at com.sap.aii.mdt.server.integrationserver.IntegrationServerMonitoringBean.getMessageList(IntegrationServerMonitoringBean.java:354)

at com.sap.aii.mdt.api.server.MessageMonitoringBean.setMessageList(MessageMonitoringBean.java:744)

at com.sap.aii.mdt.api.server.MessageMonitoringBean.getMessageList(MessageMonitoringBean.java:552)

at com.sap.aii.mdt.api.server.MessageMonitoringObjectImpl1_1.getMessageList(MessageMonitoringObjectImpl1_1.java:657)

at com.sap.aii.mdt.api.server.MessageMonitoring_Stub.getMessageList(MessageMonitoring_Stub.java:810)

at com.sap.aii.mdt.util.WebUtil.generateTableViewModel(WebUtil.java:1254)

at jsp_monitor_new1219936385390._jspService(jsp_monitor_new1219936385390.java:9)

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.doPost(PageProcessorServlet.java:22)

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

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:160)

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)

#

If I try to send message to XI directly through HTTP adapter the message is not delivered into Integration Engine.

Do you have any idea what to check or where could be problem?

Thank you in advance for every advice!

Best regards,

Zbynek

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Zbynek,

I think the problem is in the structure of the xml you want to send. I mean, that the structure of the message you are sending by means of SOAP adapter is not the same that the structure in the Inegration Repository.

When you test your message with a wrong BS it is sent to the IE and you can see this message in sxmb_moni with error status. It`s obvius, there is no configuration for this scenario. However if you test your scenario with right parametes but the content (xml structure) is wrong, the step when the content of the call is converted to the structure of the IR will fail. And the message doesn`t get the IE.

So check the content of your call.

I hope it is useful for you.

Regards,

Carlos

zbynek_kabrt3
Participant
0 Kudos

Yes, I can see the messages in SXMB_MONI. But their content (e.g. payload) seems to be right in accordance with interface definition. I think we are very close by resolving the issue. Do you have any else idea?

Former Member
0 Kudos

see if any error coming in SXMB_moni,

u can check the trace log.....for more info on error if any...

Answers (3)

Answers (3)

Former Member
0 Kudos

HI,

stop and start ur communication channel.Hope this works.

Thanks,

Durga

Former Member
0 Kudos

Hi,

Check in Message Monitoring of RWB for any Strucked or Waiting or Holding messages.

Check with this

REgards

Seshagiri

zbynek_kabrt3
Participant
0 Kudos

I have just execute test of Integration Engine in RWB and try to send test message to URL http://srvbr05:8000/sap/xi/engine?type=entry.

1. When I sent message to existing business service the message was not sent. Error " Error while sending message 500 Error during conversion of XI message" occured.

2. When I sent message to non-existing business service the message was sent succesfully and I can see it in message monitor.

Do you have any idea?

Regards,

Zbynek

Former Member
0 Kudos

Hi,

Follow this Blog to Send the Message through RWB--IE

Regards

Seshagiri

Former Member
0 Kudos

hi,

If the message doesnt reach the integration engine, it has failed in Adapter engine.

Please check the communication channel in component monitoring and see the audit log in message monitoring for Adapter Engine.

Can you please tell what is the scenario.

Thanks,

Durga