This occurs as a result of the cross-process communication between the inbound & outbound thread; i.e. you have the inbound thread in one process, and the outbound in another:
Process A Process B
Inbound
|
> Outbound
One way to alleviate this is to place the outbound thread in the same process as the inbound. Another option is to configure localhost tcp/ip connections to keep the inbounds & outbounds in the same process:
Process A Process B
Inbound —> Outbound … |… Inbound —> Outbound
(localhost) (localhost)
(client) (server)
You would then also want to move the translation that is being done into process B. If you don’t move the translation work from process A to B, you don’t really gain anything by this approach, and would be just as well served to but the original outbound thread in the same process as the inbound.
Hope this helps (and makes sense).
Jim Cobane
Henry Ford Health
