I have experienced this issue, and it is due to something ‘hanging’ in the cross-process communication between the inbound and outbound thread. Unfortunately, you can’t define an alert to notifiy you of messages that are post-xlate queued (state 7). We’ve taken the approach to keep all inbound –> outbound threads in the same process; we’ll create ‘bridge’ (localhost tcp/ip) threads if necessary to keep in/out in the same process. For example:
Process 1 Process2
Inbound
> Outbound
becomes:
Process1 Process2
Inbound
> bridgeOut1 ……………….bridgeIn1
> Outbound
(localhost client) (Server)
Hope this helps/makes sense
Jim Cobane
PHNS, Inc.
