cancel
Showing results for 
Search instead for 
Did you mean: 

Receiver SOAP Error

former_member237514
Participant
0 Kudos

Hi All,

my scenario is IDOC --to--SOAP asynchronous.here i am getting below error plz suuggest me how to resolve .

In receiver soap comm channel in module configuration i maintain as XMBWS.Timeout  300000. even though i am getting below error.

Plz help me its little bit urgent

Message Details

Message Content

Message Log

Further Links

Time

Status

Description

10/5/2016 5:24:01.164 PMInformationTrying to put the message into the send queue
10/5/2016 5:24:01.170 PMInformationMessage successfully put into the queue
10/5/2016 5:24:01.170 PMInformationThe application sent the message asynchronously using connection IDoc_AAE_http://sap.com/xi/XI/System. Returning to application
10/5/2016 5:24:01.177 PMInformationThe message was successfully retrieved from the send queue
10/5/2016 5:24:01.180 PMInformationExecuting Request Mapping "http://OMNI_B2B_Material/OM_OMNI_B2B_Material" (SWCV 550c2f0047ea11e6802bdd5eac1f16f2)
10/5/2016 5:24:01.180 PMInformationMessage status set to DLNG
10/5/2016 5:24:01.192 PMInformationDelivering to channel: CC_RCVR_SOAP_OMNI_B2B_Material
10/5/2016 5:24:01.192 PMInformationMP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
10/5/2016 5:24:01.192 PMInformationXI packaging (bulk mode) is not enabled. Switching to normal processing....
10/5/2016 5:24:01.192 PMInformationXISOAP: XI message received for processing
10/5/2016 5:24:01.193 PMInformationSOAP: Request message entering the adapter processing with user Guest
10/5/2016 5:24:01.193 PMInformationSOAP: Target url: http://50.27.156.211/ws/MaterialMaster.asmx
10/5/2016 5:24:16.676 PMErrorSOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached.
10/5/2016 5:24:16.676 PMInformationSOAP: Processing completed
10/5/2016 5:24:16.678 PMErrorMP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached.
10/5/2016 5:24:16.678 PMErrorSOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached.
10/5/2016 5:24:16.681 PMErrorException caught by adapter framework: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached.
10/5/2016 5:24:16.681 PMErrorTransmitting the message to endpoint <local> using connection IDoc_AAE_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached.
10/5/2016 5:24:16.685 PMInformationThe asynchronous message was successfully scheduled to be delivered at Wed Oct 05 17:29:16 UTC 2016
10/5/2016 5:24:16.685 PMInformationMessage status set to WAIT

Thanks

Kavitha

Accepted Solutions (1)

Accepted Solutions (1)

manoj_khavatkopp
Active Contributor
0 Kudos

Kavitha,

Try with Parameter XI.Timeout = milliseconds in module parameter


Timeout in asynchronous File to SOAP scenario | SCN

Br,

Manoj

former_member237514
Participant
0 Kudos

Hi Manoj,

I all ready maintain module config in soap receiver side

Answers (2)

Answers (2)

former_member237514
Participant
0 Kudos

Hi All,

Thank for your's support.

Issue got resolved.We did one full  round testing for all web services that time all services are got success without any issue.

Thanks

Kavitha

former_member190293
Active Contributor
0 Kudos

Hi Kavi!

Did you try sending request to WS from SOAP UI with same data?

Regards, Evgeniy.

former_member237514
Participant
0 Kudos

Hi Evgeiny,

How to check this . my scenario is IDOC -TO -SOAP.

former_member190293
Active Contributor
0 Kudos

Hi Kavi!

1. Import wsdl of your target web service into SOAP UI.

2. Open request for needed operation and set user/password for webservice call.

3. Set your payload after request mapping as request payload in SOAP UI and perform the call.

Regards, Evgeniy.

former_member237514
Participant
0 Kudos

Hi Evgeiny,

I tested client wsdl in soap UI .i got below information .

Kindly suggest me how to resolve this issue.

Thanks

Kavitha

former_member182412
Active Contributor
0 Kudos

Hi Kavitha,

Your target web service .NET web service, this error happen when there are no more database connections available in the pool, It is may be problem with connection leaks because they are not closing the connections properly in their application and all the connections open and no more connections available for new requests.

Regards,

Praveen.

former_member190293
Active Contributor
0 Kudos

Hi Kavitha!

As you can see, response time for your request is 15947ms (about 16 sec). This means that it's definitely not SOAP call timeout. I guess there is an error on server side. Try to ask target web service supporting team for assistance.

Regards, Evgeniy.

iaki_vila
Active Contributor
0 Kudos

Hi,

I agree with Evgeniy. I think the problem could be in your XML request that generates a dump in the endpoint. Talk with the endpoint guys to provide to you an XML example. When you have it, you can compare with your request, may be to set the material value like "test" or another tag generates the dump in the endpoint.

Regards.

former_member237514
Participant
0 Kudos

Hi Inaki,

If i tested with orignal data also we are getting same problem.

Thanks

Kavitha

former_member237514
Participant
0 Kudos

Hi Praveen, Evgeniy,

Thanks For your response.

Once again we are try to post the data to remain web service as well, based the output we are going to inform client.

Thanks

Kavitha