AndrewSmith
Member
Hi there!
We have an appserver process, which basically starts, and performs a tight loop (REPEAT block), which checks a Sonic queue for messages.
If I then use asbman -stop (or use Progress Exploder), the process doesn't stop - it carries on looping. A -kill command will do the trick, but I wondered if there was some kind of session attribute I could check for in the REPEAT block to see if the agent had received a STOP signal?
I'm looking for a way to handle the shutdown gracefully.
Many thanks,
Andy.
We have an appserver process, which basically starts, and performs a tight loop (REPEAT block), which checks a Sonic queue for messages.
If I then use asbman -stop (or use Progress Exploder), the process doesn't stop - it carries on looping. A -kill command will do the trick, but I wondered if there was some kind of session attribute I could check for in the REPEAT block to see if the agent had received a STOP signal?
I'm looking for a way to handle the shutdown gracefully.
Many thanks,
Andy.