MQSeries.net :: View topic - Is there a way to release a 2042 situation

belchman · Posted: Fri Apr 14, 2006 5:41 am Post subject:

Thanks All for you input.

As PeterPotkay indicated, we were S.O.L. We tried the Get Inhibit and it didn't work. We tried bouncing the App Specific SVRCONN and that did not work.

So at "oh-dark-thirty", we had to bounce the QM which did work.

PeterPotkay: We already have app specific SVRCONNS. I think the root of this problem was the fact that the lock was by the AMQRMPPA that is null. If we have a viable process on the other end of the connection, we proved that the GET INHIBIT worked. I guess this only works if there is a process to handle the 2016 which, in this case, there was not.

All of this indicates to me that MQ is saving the EXCLUSIVE LOCK (semaphore?) somewhere on the file system. How else can it maintain a lock for something that does not exist. It really would be nice if there was an MQ Util to handle this type of situation.

Maybe in ver 6? Sounds like there are a lot of cool tools in ver 6.