Skip to Content
avatar image
Former Member

HTTPS connectivity failure-connecting to PI

Hi Gurus,

Scenario: .net application->PI->ECC.(Fail)

ECC->PI->.net application(Pass) working

We are encountering timeout error while connecting to PI from .net application using https.

.net application error: Request channel timed out while waiting a reply.... timeout settings under the .net application is correct. While processing data from SOAPUI, it is reaching to PI and failing when .net application directly sending confirmation back to PI .

.net app uses HTTP 100-Continue header and SOAPUI,PI is based on java and doesn't use this header i guess. Does PI supports HTTP 100-Continue header? is this causing the .net application failure to reach PI? Any one encountered similar issue? any suggestions will be highly appreciated.

Note: HTTP connectivity is working on both sides successfully (SAP->.net and vice versa)

error.jpeg

Thanks,A

error.jpeg (23.9 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers