Hi Team,
We have
implemented a scenario in our project where in the Sender System (out of BLAN)
sends an asynchronous SOAP request to SAP PI where we are doing a one to one
transformation and posting the data in the Target System through a synchronous
JDBC call (a stored procedure is being executed and is configured in request
mapping). In order to capture the JDBC response from the target system, we have
configured a Request/Response Standard Module in SOAP Sender channel through
which are capturing the response log in a file and storing it in the local file
system through NFS protocol.
Now that, the volume of the data
being triggered from Source system is high, few of the messages are being timed
out in SAP PI with an OUTBOUND message expired exception. Post this error
message, the connection from Source system to SAP PI is being disconnected and
the subsequent messages are being failed in Source system without even reaching
SAP PI.
And
Then we
have changed our build to Virtual receiver concept and configured a
Request/Response Standard Module in Receiver JDBC channel through which are
capturing the response log in a file. Now, If we triggered the huge volume of
data from Source system, Few messages are failed in source system without even
reaching SAP PI and
post
the below error message in the sender system.
“System.Net.WebException:
The underlying connection was closed: The connection was closed unexpectedly.”
We have
asked the source system to change the parameters as per the below blog, But
still issues persists.
https://blogs.sap.com/2005/10/21/xi-the-underlying-connection-was-closed-an-unexpected-error-occurre...
Can you
please advise us on the resolutions. Also can you please suggest if any
modifications needs to be done to the system parameters such as timeouts etc.
This is a production issue where
we are replicating the same in SAP PI FOF environments.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.