RFC 2 SOAP Scenario -- Batch job failing

[Former Member]

Hi,

I have created RFC to Soap scenario in XI.

On executing the RFC individually, it successfully worked. Then I executed a batch job program involving the same RFC. It ran for twelve minutes successfully and after that a dump was thrown. The request message has reached the integration engine and no response has been obtained back.

Now trying to execute the RFC individually, even it is failing now.

Could someone please suggest me as to how do I rectify this issue?

Thanks,

Ravi Kiran

[MichalKrawczyk]

Hi Ravi,

the first thing you need to do is to check

if there are any error messages on the XI

(TCODE - SXMB_MONI) maybe there was some timeout

or some other issue which needs to be taken care of

- SXMB_MONI - then search for errors

Regards,

michal

-

---

<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

[Former Member]

Hi Michal,

Thanks a lot for your reply.

I have been facing this issue from last Friday. (April 07,2006). At that time the error being shown is: Received HTTP response code 500 :Timeout.

The program had successfully run for 12 minutes and then it threw this error.

When I tried to recheck it today morning, it was referring to the program id not being registered.

I deleted and entered the program id again. The program id issue is gone.

Now on executing the RFC individually, the request is not reaching the Integration engine. For, I have checked the Adapter engine in Message Monitoring of Runtime Workbench.

Please find below the copy pasted content from that screen:

Time Stamp Status Thread ID Sequence No. Description

2006-04-10 13:29:10 Success RfcServer[chSenderRFC]1 1144655950529 RFC adapter received sRFC for ZTEST_GET_ACCOUNT_INFO from CDS/100. Attempting to send message synchronously

2006-04-10 13:29:10 Success SAPEngine_Application_Thread[impl:3]_123 1144655950529 Application attempting to send an XI message synchronously using connection AFW.

2006-04-10 13:29:10 Success SAPEngine_Application_Thread[impl:3]_123 1144655950529 Trying to put the message into the call queue.

2006-04-10 13:29:10 Success SAPEngine_Application_Thread[impl:3]_123 1144655950529 Message successfully put into the queue.

2006-04-10 13:29:10 Success SAPEngine_System_Thread[impl:5]_9 1144655950529 The message was successfully retrieved from the call queue.

2006-04-10 13:29:10 Success SAPEngine_System_Thread[impl:5]_9 1144655950545 The message status set to DLNG.

2006-04-10 13:29:10 Error SAPEngine_System_Thread[impl:5]_9 1144655950545 Failed to parse the XI system response.

2006-04-10 13:29:10 Error SAPEngine_System_Thread[impl:5]_9 1144655950545 Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to invalid content type for SOAP: APPLICATION/OCTET-STREAM.

2006-04-10 13:29:10 Error SAPEngine_Application_Thread[impl:3]_123 1144655950545 Transmitting the message using connection http://blrkecsaptst2:8000/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to invalid content type for SOAP: APPLICATION/OCTET-STREAM.

2006-04-10 13:29:10 Error SAPEngine_Application_Thread[impl:3]_123 1144655950545 The message status set to FAIL.

2006-04-10 13:29:10 Error SAPEngine_Application_Thread[impl:3]_123 1144655950545 Returning to application. Exception: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to invalid content type for SOAP: APPLICATION/OCTET-STREAM

Please suggest further steps to diagnose the issue and rectify it.

Regards,

Ravi kiran

[Former Member]

Hi Michal,

I have a similar situation. SOAP(sender)->XI->RFC(receiver). It runs successfully the first 40+ times then it throws out this time out message. I think it has something to do with the max connections. I think XI has a max connect of 50 as default. Also I am using a syncronous connection so there may be an issue with releasing the connection afterwards. Maybe this will put you on the right track -please respond back if you find a solution.