|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
deadlock bug of MQ? |
« View previous topic :: View next topic » |
Author |
Message
|
ext2xhb |
Posted: Sun Jun 27, 2010 7:07 pm Post subject: deadlock bug of MQ? |
|
|
Newbie
Joined: 24 Jun 2010 Posts: 2
|
Hi:
if I create a new thread and in the thread to create QCF and using the QCF to create connection. the createConnection() operation will blocked.
there is no any other concurrent operation on MQ, just createConnection in a new thread, so why to deadlock?
Is it a MQ's bugs?
By the way, I have notice some other confusing things about the "deadlocked" operation;
case 1)If I first create a JMS connection in the main thread; then in the new-created-thread to create a new QCF and a new Connection, they will never deadlock;
case 2) :beside the case 1), I find another way to unlock the deadlock, that's if I create two threads, the threads both create it's own QCF and connection. the first thread will blocked on createConnection, but when the second thread executing createConnection, the first thread's deadlock will be un-locked, then both threads can create their own connection successfully.
Why? is it a MQ's bug? and Is there a fix to resolve the bug?
I am using MQ6.0.2.9 on windows XP sp3. and the JMS program and MQ Server both run in the same machine. and the JMS client 's transport to MQ Server is using "BIND"; |
|
Back to top |
|
 |
fjb_saper |
Posted: Sun Jun 27, 2010 9:23 pm Post subject: Re: deadlock bug of MQ? |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
ext2xhb wrote: |
Hi:
if I create a new thread and in the thread to create QCF and using the QCF to create connection. the createConnection() operation will blocked.
there is no any other concurrent operation on MQ, just createConnection in a new thread, so why to deadlock?
Is it a MQ's bugs?
By the way, I have notice some other confusing things about the "deadlocked" operation;
case 1)If I first create a JMS connection in the main thread; then in the new-created-thread to create a new QCF and a new Connection, they will never deadlock;
case 2) :beside the case 1), I find another way to unlock the deadlock, that's if I create two threads, the threads both create it's own QCF and connection. the first thread will blocked on createConnection, but when the second thread executing createConnection, the first thread's deadlock will be un-locked, then both threads can create their own connection successfully.
Why? is it a MQ's bug? and Is there a fix to resolve the bug?
I am using MQ6.0.2.9 on windows XP sp3. and the JMS program and MQ Server both run in the same machine. and the JMS client 's transport to MQ Server is using "BIND"; |
The MOST expensive operation in JMS is the creation of a connection. This is why the JNDI layer in the appserver provides you with connection pooling. Use it!
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|