MQSeries.net :: View topic - CLUSSDR only calls message exit once, then stops.

coreyb · Posted: Wed Jul 28, 2004 4:32 am Post subject:

Hi!

I've got a message exit that logs off message details (time, MD fields, size) to a log file and want to get it working for cluster sender channels. The exit works fine on normal channels, and is working in our production environment with a fair load already.

If I define the message exit either in the CLUSRCVR definition, or by using another Channel Auto Definition exit to change the CLUSSDR the exit fails. It is called 3 times, once with MQXR_INIT, once with MQXR_MSG (which logs the first message away as expected) and then with MQXR_TERM. The problem is the second or subsequent messages don't seem to do anything. The message exit never gets called (In debug mode it logs to a separate file what it's doing, and the first thing it does is write that itâ€™s been called) and the message never gets transported. The channel still shows in "Running" state but no messages pass through it. It times out (I set it to 60 seconds) and I restart it, then once again 1 message is transported (and logged) but nothing else goes through. The exit logs the message and shows that the MD time is 5 seconds after the first message, but wasnâ€™t logged until ~2 minutes after the 1st message because I had to manually restart the channel. If I put a 3rd message after the channel times out rather than restarting the channel by hand, it'll fire off the 2nd message I put just after the first, log it and leave the 3rd message waiting to be transmitted. Seems the channel triggering is still working, just the channel getting messages off the queue seems to no longer work.

Iâ€™ve written a dummy exit that just logs that itâ€™s been called, and sets the ExitResponse to MQXCC_OK, which the real exit is also doing the 3 times it does get calledâ€¦ this seems to work fine and multiple message pass through it.

Is there something different that I need to do to cater for cluster senders that I'm missing? I'm not getting any errors logged to either MQ error or Windows Event Log, although the same effect can be seen under AIX which I'm also testing this on. Could I be doing something in the exit that I shouldnâ€™t be? In which case what? Basically I just build up a string with all the data I wish to log, and then call a procedure to write it to file (a separate thread under AIX, but non-threaded on windows) I can post the code if anyone needs a closer look to see if Iâ€™m doing something obviously silly.

Regards,
Corey