Testing consumer proxy with external service

[konstantinos_vassiliadis]

Dear experts,

I have a consumer proxy defined for an external web service. Until yesterday the communication was successful. Since then any calls to the methods of the external service hang. Even when I test the consumer proxy via SE80 using the created logical port also the method calls hang. The provider of the external service confirmed that they received no call from SAP.

I used the log facility from SOAMANAGER. For example, the Payload trace for a specific method call shows the following:

Can anyone figure out where is the problem? I forgot to mention that the proxy is consistent.

[konstantinos_vassiliadis]

Hello Patrick

I used HttpRequester Firefox extension and performed a GET request successfully

[weberpat]

Hi Konstantinos,

I was thinking of a test from the actual server your SAP system is running on.

Regards,

Patrick

[konstantinos_vassiliadis]

Can you help me regarding your thought? Some guidance...

[konstantinos_vassiliadis]

From within SE80 and Service Consumer test, after 30 minutes it comes up with the message

[weberpat]

There could be network configuration preventing your SAP system from establishing a connection to the service. Testing the service from your local PC using a tool like HttpRequester will not necessarily detect this as the request is originating from a different machine (your local PC vs the SAP application server).

Somebody with access to the OS level of your SAP system could test the basic connectivity using ping or even send a test request using a test tool like CURL, which would help establish whether from a networking perspective the two systems can talk to each other.

[konstantinos_vassiliadis]

We just tested from application server:

- ping

- RFC destination (via SM59)

In both cases the connection was established successfully. In the second case we also got a response from the target host.

Still the problem persists when testing the consumer proxy.

[weberpat]

Can you get somebody to try

- pinging the remote server

- invoking the service with a test tool like CURL from the application server of your SAP system

Just to make sure that this isn't a network problem.

[konstantinos_vassiliadis]

After 30 minutes (1800s) the error returned in Soamanager trace is the following

Connection to partner timed out after 1800s.

and the stack trace is the following

Does this mean that the error is within SAP Application Server? And that the problem is not connecting to the external web service? In fact, using web tools outside SAP I can connect