cancel
Showing results for 
Search instead for 
Did you mean: 

PI to SFDC-Error- Cause Exception: 'java.net.SocketException: Connection reset'.

Former Member
0 Kudos

Dear All,

PI messages are failing with error as "Cause Exception: 'java.net.SocketException: Connection reset'".

BPM to SFDC is the scenario - sync. udf in the message mapping fetches the session id, during fetching session ids, messages are failing.

Not all messages are failing some of the messages are failing.

Error screenshot:

What is the reason for this issue ? how to solve it.

if I resend the failed message its getting successful. Though it seems a temporary issue, 50+ failed and manually I am resending them.

Thanks,

Let me know if you need any other details.

reg, avinash

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member204100
Active Participant
0 Kudos

Hi Avinash,

try to collect deeper level traces about the used SOAP receiver channel in mapping lookup.

You will need to check what was the request message and how the response message look like - including the HTTP headers.

Hopefully you will see there more details why this operation fails.

Maybe the error message is thrown by something between the target server and PI interrupts this connection, like proxy, web dispatcher, ICM, ...

Best Regards,

Viktor

Former Member
0 Kudos

Hello Viktor,

I have checked the audit log. I just see the java exception and some method names.

Apart from that I am not finding any clue.

reg, avinash

former_member186851
Active Contributor
0 Kudos

Hello Avinash,

Are you sending multiple requests at a time?

Issue could be at the webservice side as well.

Check if the below note helps you

Large messages from SOAP receiver channel fail

Former Member
0 Kudos

Hello Raghu,

Are you sending multiple requests at a time? Yes, multiple requests happening parallely.


reg, avi

former_member186851
Active Contributor
Former Member
0 Kudos

Hello Raghu,

Yes, we are sending multiple messages to SFDC.Load is high.

SAP Note you have mentioned is for large message we are not transferring large message to SFDC rather small multiple messages to SFDC.

in the link, there is no information about issue I am facing.

Are there any other alternative ?

reg, avinash

former_member186851
Active Contributor
0 Kudos

Avinash,

The below query was addressed I guess

The same parameter or the link shared by Engg in the discussion didn't help you ?

Former Member
0 Kudos

Yes. correct.

This is a new issue poped up now.

Any solution for this issue?

reg, avin

former_member186851
Active Contributor
0 Kudos

check the below One Avinash

Former Member
0 Kudos

It talks about timeout issue. I am facing different issue.