Question Re: VERTEX - java.net.SocketException: Connection reset in Technology Q&A

VERTEX - java.net.SocketException: Connection reset

philip0929 — Fri, 17 Apr 2020 08:30:43 GMT

Hi guys,

I would like to seek your help. We have an issue that happens intermittently. Meaning once in a while this issue happens.

There was a job failure of a finance job below:

The integration is like the below:

I've checked the VERTEX SIC and found the below SIC log error entry:

Do you guys have any idea about the issue? Connection from SAP to VERTEX is working fine and issue happens intermittently. The steps I've done so far,

1. Increased the heap memory in VERTEX SIC to 2GB.

2. Increased the load distribution of the job

The issue still occurs intermittently. I suspect that the issue is on O series side. Can you please advise what might be causing this issue?

Thank you in advance!!

Re: VERTEX - java.net.SocketException: Connection reset

Isaias_SAP — Mon, 20 Apr 2020 13:33:35 GMT

Hello Philip,

The error I see in the VERTEX log is "SocketException: connection reset".

This suggests that VERTEX is losing the network connection to "something".

I do not work with VERTEX, so it is not clear to me what could be the remote end.

It seems it would not be SAP, as the VERTEX error message is seen at the job log.

So, to what else does VERTEX connect to?

Regards,

Isaías

Re: VERTEX - java.net.SocketException: Connection reset

philip0929 — Tue, 21 Apr 2020 02:17:26 GMT

In the image, Vertex connects to O series web services.

Re: VERTEX - java.net.SocketException: Connection reset

Isaias_SAP — Sat, 25 Apr 2020 18:10:06 GMT

Hello Philip,

Then check what happened at the O series web services end.

If it also shows a network related error, then involve your network team.

They would likely have to capture data / monitor the network while the issue happens.

Analyzing it while the connection is working fine will likely not show anything helpful.

Regards,

Isaías

Re: VERTEX - java.net.SocketException: Connection reset

former_member107601 — Wed, 07 Jul 2021 14:30:53 GMT

Hi,

I have the same exact issue for months, were you able to get this resolved by any chance? philip0929

Re: VERTEX - java.net.SocketException: Connection reset

philip0929 — Wed, 07 Jul 2021 14:36:31 GMT

No resolution yet but you can:

1. Increase the memory of your SAP system

2. Increase the Xms and Xmx of you Vertex SIC process

3. Check some timeout parameters in O-series (assuming you are on-demand customer or else patch as well) and SIC side

4. Patch or upgrade the Vertex SIC

5. Use proxy on your Vertex SIC

Re: VERTEX - java.net.SocketException: Connection reset

former_member107601 — Wed, 07 Jul 2021 14:41:08 GMT

I already upgraded it to recent version 9.1.7, the SIC server has plenty of memory (12 GB) and i allocated 3 GB of heap

We are ondemand customer but we dont have any visibility to the oseries infrastructure, its in cloud

If its not resolved for you, i am assuming you have already tried these things?

What are Xms and Xmx and where do i change these and to what?

Re: VERTEX - java.net.SocketException: Connection reset

philip0929 — Wed, 07 Jul 2021 14:43:24 GMT

It seems the job is too big so try to increase the CPU and Memory of SAP system

Re: VERTEX - java.net.SocketException: Connection reset

philip0929 — Wed, 07 Jul 2021 14:44:42 GMT

Have you upgrade the SIC to latest version?

Re: VERTEX - java.net.SocketException: Connection reset

former_member107601 — Wed, 07 Jul 2021 14:45:47 GMT

it happens at the same time every morning and there are no major jobs running at the time, its a non-prod system. I dont see any indication that its the memory of SAP system, sorry but thanks for the help

Re: VERTEX - java.net.SocketException: Connection reset

former_member107601 — Wed, 07 Jul 2021 14:46:27 GMT

Yes the SIC version has been upgraded a few times. I guess if you have not resolved it either we might be in the same boat

Re: VERTEX - java.net.SocketException: Connection reset

philip0929 — Wed, 07 Jul 2021 14:51:47 GMT

The issue here is there is a process that runs too long (maybe processing too large data) causing the timeout.