Skip to Content
0

PI Unable to create a socket

Jul 03, 2017 at 10:45 AM

167

avatar image

Hello, dears

I know, that this question has already been asked many times. None of the existing answers could help me. I have been searching for the solution for about 6 months.

We have several simple PI scenarious. The third party calls synchronous SOAP web-service, which is replaced on ERP side. So, we have Caller side -> PI -> ERP.

Everything worked fine for a long time. We suppose, that the problem appeared, when the load on system has increased (many services calls).

Now, we have the fllowing situation. All such services in one of our several ERP systems (we have several ERPs, but such problem is only in one of them) periodically failed with error "Communication over HTTP. Unable to create a socket.".

This is not a network problem, because sometimes the service is called fine, and sometimes it fails. And it failes many times a day. Maybe, about 50% of calls are failed.

The basis team said, that they configure the ERP system to get a huge number of connections, but it doesn't help.

I will be very appreceated for any help.

Thanks a lot.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Evgeniy Kolmakov Jul 03, 2017 at 12:57 PM
0

Hi Ekaterina!

Maybe this blog could help:

https://blogs.sap.com/2011/01/26/tuning-the-pi-messaging-system-queues/

Regards, Evgeniy.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Evgeniy, thanks a lot. But I haven't found any useful information there...

0
Hari Joshyam Jul 03, 2017 at 02:23 PM
0

Hello,

Do you have any other SAP system like SCM linked with your ECC? Have you verified what are the processes that were running during the same interval? This could be due to heavy load processing in ECC and not able to accept new messages.

Another thing, can you verify if the issue is related to 1 specific cluster node may be. Try to see the failed message and try to check if it was related to 1 specific cluster may.

Cheers!

Hari

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hello, Hari

Yes, it could be due to heavy load processing in ECC. I have written about it in my answer ("We suppose, that the problem appeared, when the load on system has increased (many services calls)."). But can we do something with it?

I have checked, the issue is appeared on all cluster nodes (two in our case).

0
Ekaterina Pozdnyakova Jul 10, 2017 at 11:41 AM
0

Hello! Does anybody know the answer? Or maybe somebody has some useful information? I will be very appreceated for any help.

Show 6 Share
10 |10000 characters needed characters left characters exceeded

Hi Ekaterina!

Did you try to enable temporarily HTTP tracing at receiver SOAP adapter? Just to get HTTP log of the request. Maybe you could find out if this error occurs during connect to backend system or not. I guess you should determine first if this "bottle neck" takes place on PI's side or on backend ERP's side.

Regards, Evgeniy.

0

Hi, Evgeniy

Thanks a lot for your answer. I didn't try to enable HTTP trace, but I think, that this is obviously, that the issue is on backend ERP's side. We have a lot of SOAP services in PI, which work with several backend systems (CRM, HR, etc.) and we have no such problems with them.

Just in case I will try to enable HTTP tracing for a while. Thanks for advice.

0

Hi Ekaterina!

I'm fully agree with you. Problem lays on ERP's side. But since you've mentioned that BASIS team reported that they've fixed the issue I recommended to use the trace to ensure that problem is not resolved yet and let your BASIS team know about that.

Regards, Evgeniy.

0
Hello, Evgeniy

I have enabled the HTTP trace on SOAP receiver. So, at time, when problem occurs, I don't see connections in this trace. I suppose, that means that the call doesn't reach the receiver side, am I right?

Thanks a lot for your help!

0

Hi Ekaterina!

I thought that it would be the possible reason when PI hasn't enough threads for establishing SOAP connection to target system. For this case I provided the link to blog telling about tuning messaging queues in PI. May be increasing threads count for SOAP adapter could help.

0

But in that case, why a great amount of SOAP services to the other our systems work fine through PI? How can it be, that PI cuts only connections to single ERP system, but not to the others?

0