i have queue reader consumes messages under sycpoint , ended abruptly. caused 2 messages left in uncommitted state. "msgage" property keeps increasing message , "uncom" property of queue remains same 2, though restarted consumer application , no long running uow.
anyway can reset these properties without restarting mq?
presuming application connecting in client mode (over tcp) expect although application has gone away, queue manager's point of view still active.
when network socket application opened closes, mq should roll 2 messages they're eligible consumption application.
the network socket close when operating system notices remote end of tcp connection unresponsive - triggers 'connection reset peer' type socket closure. it's operating system queue manager running on this, not remote one.
some operating systems can take hours notice duff socket in default configuration. 'tcp keepalive' settings on operating system tune how long takes.
Comments
Post a Comment