Providing REST services - the HTTP response header is 200 ok, but the response body is empty?

Hello group,

We are facing a problem while trying to provide REST web services and were wondering if anybody in this group has faced the same problem and have suggestions.

It seems that when we use an external node to consume the service we are providing, the body of the message is not read correctly.

If we test the service in the Integration Broker’s service operation tester, using the local node, everything works fine.

When calling the web service using soapUI (external), the HTTP response header is 200 ok, but the response body is empty. ("{} in json")

Looking at the trace and log, we can observe the message is received and a response is built, so the handler is working fine. In the synchronous message monitor, we can see the request and response messages have data in its body, but the data in the response body does not reach soapUI.