MQSeries.net :: View topic

mkurley · Posted: Thu Jul 03, 2003 5:13 am Post subject:

I am experiencing a deadlock when running my application. I have just recently upgraded to the latest version of the MA88 package. I have also upgrade to MQ 5.2.0.6. The code in question has been running just fine for two years on the old version of MA88.

Here is the problem. I have triggering enabled for the first message. This starts up a monitor process which creates/manages worker threads. These worker threads are responsible for receiving and processing the messages. The monitor process checks the depth at a configurable interval and spawns new threads. It also prints out the current depth after each time it checks. When I configure it to start 10 threads the monitor process and all of the threads deadlock. Each thread creates it own QueueConnection, QueueSession, QueueReceiver, and Queue objects. No jms objects are shared among the threads. Also note that I have changed this piece of code in over two years.

This leads me to believe that the newer MA88 package is doing some synchonization within the api which is causing the deadlock.
Has anyone else experienced this problem?
Does anyone have any suggestions? This is really causing us a problem because we must upgrade to the new MA88 for performance gains.
Any help or suggestions would be great.
Thanks
-mark