[SOLVED] Events sitting in $publishWait queue (v4.5)

andyp222 · #1 (**permalink**) July 17th, 2007, 11:00

Hi,

We were doing a bulk load test of Release and Shipment XML's and they were all processing OK until at some point the transactions all started appearing in the $publishWait queues, until this built to a high backlog, with processing continuning very slowly (it seemed that every few minutes something was pulled from the queue and processed by the Agents). Transmissions remained in FRESH status. Eventually we had to restart the system, and the transmission status went to REDO.

After restart, if we re-load one of the XML's via the GUI it processes immediately. However if we try to re-process the REDO transmissions (even in small batches, i.e. 10) they just get put back on the $publishWait queue, sit there for 5-10 minutes before starting the Agent processing. There is no other activilty going on on the box.

Seems that it might be specific to Release's, as TransOrders do not seem to show this same behavior (or at least not to the same extent).

Any ideas, explanations?

rkuruba · #2 (**permalink**) July 19th, 2007, 21:12

I remember similar thing happened when we used HTTP Post mechanism. When bulk load is done after some transmissions get process rest of them go to Fresh status. When we bounce GC3 4.5 all these transmissions go to REDO status. We talked to Oracle regarding this and they provided us with the fix. (some .jar file). I would suggest you to talk to oracle and followup with them. This issue is supposed to be corrected in later versions.

andyp222 · #3 (**permalink**) July 20th, 2007, 09:08

Thanks for the response. I will raise an Oracle ticket and see what they say, but if you can remember any other information (e.g. version it was fixed, any patch ID) this would be very useful.

andyp222 · #4 (**permalink**) July 24th, 2007, 14:45

Was due to the using a RAISE EVENT within the Shipment Modify Agent. For various reasons we had a main Shipment Modify agent that did a series of RAISE EVENT actions to call other Agents (working on the same Shipment). This caused the original agent to hang and never complete. Also tried FOR EACH, but this had the same issue.

RAISE EVENT on objects other than the shipment (e.g. related OR's seems to work fine).

To workaround this we took all the code and put it into a single Shipment Modify Agent and all works OK now.