Help – Explanation of Post-Xlate Queue Depth Alert?

[Jason Alexander]

I’m looking at the online documentation of the Post-Xlate Queue Depth alert and it is not helping me since if I knew what the Post-Xlate Queue was for use it would be self explanatory.

Can someone explain to me what the Post-Xlate Queue is?  Which thread owns the message in this queue, what engine state would it report in the recovery database and which process, if we were performing inter-process communication, would the message be in?

Topic

[James Cobane]

Hi Jason,

The post-xlate queue is where messages are after being translated, but not yet transitioned to the outbound data queue.  This is where you might see a route turn ‘red’.  The post-xlate queue is associated with the inbound thread (and it’s process).  So, given a set of threads:

from_inbound —> to_outbound

You would set a post-xlate queue depth alert based on the inbound thread (from_inbound).  You might see post-xlate queue depths if you get a big influx of messages.  The engine will process the inbound messages before pushing them out to the outbound data queue.

Messages post-xlate are in state 7.

Hope this helps.

Jim Cobane

Henry Ford Health

[Jason Alexander]

Thanks, James.  That was my suspicion but I had not had a chance to confirm it and that was exactly the information I needed.

[Author]

Replies