Skip to Content
0
Oct 05, 2016 at 05:29 PM

Receiver SOAP Error

581 Views

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 PM Information Trying to put the message into the send queue 10/5/2016 5:24:01.170 PM Information Message successfully put into the queue 10/5/2016 5:24:01.170 PM Information The 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 PM Information The message was successfully retrieved from the send queue 10/5/2016 5:24:01.180 PM Information Executing Request Mapping "http://OMNI_B2B_Material/OM_OMNI_B2B_Material" (SWCV 550c2f0047ea11e6802bdd5eac1f16f2) 10/5/2016 5:24:01.180 PM Information Message status set to DLNG 10/5/2016 5:24:01.192 PM Information Delivering to channel: CC_RCVR_SOAP_OMNI_B2B_Material 10/5/2016 5:24:01.192 PM Information MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean 10/5/2016 5:24:01.192 PM Information XI packaging (bulk mode) is not enabled. Switching to normal processing.... 10/5/2016 5:24:01.192 PM Information XISOAP: XI message received for processing 10/5/2016 5:24:01.193 PM Information SOAP: Request message entering the adapter processing with user Guest 10/5/2016 5:24:01.193 PM Information SOAP: Target url: http://50.27.156.211/ws/MaterialMaster.asmx 10/5/2016 5:24:16.676 PM Error 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.676 PM Information SOAP: Processing completed 10/5/2016 5:24:16.678 PM Error MP: 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 PM Error SOAP: 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 PM Error Exception 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 PM Error Transmitting 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 PM Information The asynchronous message was successfully scheduled to be delivered at Wed Oct 05 17:29:16 UTC 2016 10/5/2016 5:24:16.685 PM Information Message status set to WAIT

Thanks

Kavitha