Author |
Message
|
mart_mq |
Posted: Mon Nov 27, 2006 1:07 am Post subject: Long time during PUT |
|
|
Novice
Joined: 05 Apr 2005 Posts: 14
|
I have following problem: For accessing MQ I'm using the com.ibm.mq.jar library
(for MQ v 6.0.0). I'm realizing PUT through method MQQueue/put(), but sometimes,
this method returns after very long time -- up to 3 seconds (!). What could cause
such a behaviour? It is probable (but we are not sure yet) that there's no
extreme load on MQ at the time of the delay...
Thanks Martin |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Nov 27, 2006 2:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Are you sending a big message over a slow client connection? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
mart_mq |
Posted: Mon Nov 27, 2006 3:15 am Post subject: |
|
|
Novice
Joined: 05 Apr 2005 Posts: 14
|
No. For this I used binding mode and I sending the message via cluster. The message is non-persistent.. |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Nov 27, 2006 6:39 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Could it be taking a long time for the cluster name resolution to take place? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
mart_mq |
Posted: Mon Nov 27, 2006 8:01 am Post subject: |
|
|
Novice
Joined: 05 Apr 2005 Posts: 14
|
I don't know. I used for PUT cluster queue. This queue is define with - Not Fixed in Default bind type param. What do you think of it? Could it be problem here? |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Nov 27, 2006 8:05 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
It could be a problem with cluster name resolution, where the cluster has to go out to the full repository, and this requires starting channels that are slow to start...
But it's just a guess. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
|