org.apache.cxf.interceptor.Fault: Could not send Message.
Last night, I started seeing this error while POSTING data to a RESTful service via TESB open studio 6.3.1 deployed in Karaf Runtime container. I am accepting requests via tRestRequest in the job and deployed the .kar file on the runtime environment.
I have never seen this before and I have no clue how to address it. is it a server side/ client side error?
One thing I did is reduce the data being posted, and this error went away. I don't remember the exact size of the data posted.
I have a SAM feature running saving data in SQLSERVER DB.
My version is TESB Open - 6.3.1. Any comments/ feedback appreciated.
Hi
@Tobi,
When I was running my code on local network, it never gave an issue (regardless of the payload size). Howecer, when deployed on production, with all the unknown security settings, we were able to see that the client connection was cutoff after some 10MB of payload or similar. After we got that figured, we just had to open this endpoint for no limits and it's been going great.
Sorry this may not be what you wanna hear, but work a shot to check the network/ firewall settings.
org.apache.cxf.interceptor.Fault: Could not send Message. This error is usually due to the server being unavailable or the endpoint is not right. I think your case is the server is down for some reason. Does it occurs randomly?
It just happened once when a huge payload was sent. Other than that, I have not seen it go crazy. I am not sure if that big payload is the root cause. Anything else I can scout for? Thanks
any news from your side? I am randomly experiencing this error as well on an OData interface in Dynamics 365. Do you think increasing the connection timeout in the tRestClient component could help? From my perspective it is an error, which is tough to handle, as it appears within the flow. I don't see a way to recover from this error and retry to post the record. How did you handle it?
Hi
@Tobi,
When I was running my code on local network, it never gave an issue (regardless of the payload size). Howecer, when deployed on production, with all the unknown security settings, we were able to see that the client connection was cutoff after some 10MB of payload or similar. After we got that figured, we just had to open this endpoint for no limits and it's been going great.
Sorry this may not be what you wanna hear, but work a shot to check the network/ firewall settings.
