Our messages stopped working when we switched to HTTP 1.1 from 1.0
Summary: While switching from http 1.0 to 1.1 - our middleware stopped receiving messages
Content (please ensure you mask any confidential information):
We have messages to integrate our source ERP system with OFSC. These messages carry completion / update information back to our source ERP through our middleware (SOA).
This is behavior we observed.
- We switch to HTTP 1.1 > Trigger the transaction > Transaction is in New status and eventually times out.
- When we switch back to HTTP 1.0 > The transaction is triggered > within 2 minutes - our middleware receives the message and acknowledges it.
Our Channel setup is straightforward - we have Default Encryption and Host Port are pointed to our SOA servers and URL points to the composite.
Tagged:
0