850_update_bulletin - Progress Sonic Product Update Bulletin 8.5

Reduce Contention in endpoint.call()
What’s Also New in Sonic ESB and Sonic Workbench
The XQEndpoint.call() operation allows a custom Java service to programmatically
invoke an ESB endpoint.
During calls to the XQEndpoint.call API, ESB sets the ReplyTo destination in the
message from a fixed pool of temporary destinations. After the API call returns, the
temporary destination is returned to the pool and re-used for subsequent API calls. In
events where the API calls exceed the timeout interval, the temporary destinations are
returned to the pool. If a response arrives for the timed out request, then it might be
incorrectly treated as the response for a subsequent request.
To resolve this issue, you can use one of the following methods:
● Set the SonicESB.RefreshDestinationsOnCall system property to true. When you set
this property, a unique temporary destination is used for each call. This can lead to a
large number of temporary destinations if a large number of concurrent
Endpoint.call API calls are expected.
● Set the SonicESB.UniqueJMSCorrelationIDOnCall system property to true. When you
set this property, each message is assigned a unique JMSCorrelationID before the
Endpoint.call API call.
This information has been added to the Sonic Workbench online help in the Workbench
and in its PDF version, Sonic ESB Development Tools guide.
Per-Message URL Override for Sonic Connect
Sonic Connect Service allows you to override the destination URL of a web service
invocation step using a request mapping rule.
This information has been added to the Sonic Workbench online help in the Workbench
and in its PDF version, Sonic ESB Development Tools guide.
Progress Sonic Update Bulletin 8.5 43