Message priority and processing

[Michael Lacriola]

An oldie but a goodie. First of, all messages are given a default priority of 5120. 5100 would then be a lower priority, correct?

Now, about processing. If I have a bunch of engine processes with bunches of threads in those processes, and I lower the priority of a message in the tps_outbound of a particular thread:

1) is the message priority for all the messages in that thread honored based  on higher priority first then FIFO, or

2) is the message priority for all messages in that engine process honored as highest first, the FIFO, or, yes, one more,

3) is the message priority for all messages in the recovery database honored as highest first, then FIFO.

Hard to believe I’m level 3 and never used this feature – 15 years of Cloverleaf lack of experience. My guess is it’s at the engine process meaning all messages within the threads in the engine process are honored as highest first, then FIFO. Did I win a hat and a free bowl of soup?

Topic

[David Barr]

From the Cloverleaf docs: “Cloverleaf

[Rich Brant]

I’m very interested in the answer to the first question posed here: “An oldie but a goodie. First of, all messages are given a default priority of 5120. 5100 would then be a lower priority, correct? “

Could someone shoot us the answer to that one please?

[Bob Richardson]

Greetings,

Default priority is 5120 FIFO order unless (!) you create messages within a TCL procedure (for example) – then the engine will toss the messages in random sequence IF (!) set with the same priority.  Testing proved that out when developing a TCL to create a merge message (A18 or A34) from (say) an A08.

In the latter case where we had to send the Merge before the A08 we set the priority higher like 5130 then disposed (returned) the list of message handles to the engine.

The higher priority message goes first then the default guy.

Hope this answers your question.

[Author]

Replies