| Author |
Message
|
| RAHULTHOTA |
 Posted: Tue Mar 04, 2003 7:00 am Post subject: URGENT PROBLEM |
 |
|
Novice
Joined: 13 Dec 2002
Posts: 13
|
| I am facing a peculiar problem.After creating a message of size 2Mb(5 messages) I find that the messages in my Transmission Queue.After sometime it shows a depth of 0 but then again after sometime when i refresh i find it still has 5 messages.All my channels at both ends are running.All the queues and QMangers are persistent.I am not able to understand why the messages r still in the queue.Kindly some one help me out!!!!!!!! |
|
| Back to top |
|
 |
| Troilus |
| Posted: Tue Mar 04, 2003 7:31 am Post subject: |
|
|
Apprentice
Joined: 12 Jul 2002
Posts: 28
Location: Belgium
|
Difficult to help you this way.
Looks like you have some communication problem. I bet the channel is in retrying mode. Be carefull on how you interprete curdepth. The channel might read all messages to send them in one batch, you look, curdepth is zero, batch fails, messages are backed out (put back on transmisson queue), curdepth is five again. |
|
| Back to top |
|
|
| RAHULTHOTA |
| Posted: Tue Mar 04, 2003 9:24 am Post subject: |
|
|
Novice
Joined: 13 Dec 2002
Posts: 13
|
Thanks Troilus,
But unfortunately the channels are running and even after restarting the Qmanager the problem still persists |
|
| Back to top |
|
|
| mqonnet |
| Posted: Tue Mar 04, 2003 11:08 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Try with only 1 message instead of 5.
Check to see if you can put this message fine on a local queue.
Any error messages on either mqerrrlogs.
By any chance do you have a loop back scenario. RM(qm1)--->RM(qm2)... This would also fit your problem description.
What platforms are in question and what level of code???
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| bduncan |
| Posted: Tue Mar 04, 2003 4:01 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Or perhaps the destination queue is full, as well as the dead letter queue on the destination queue manager? This would cause your messages to pile up on the transmission queue.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| leongor |
| Posted: Wed Mar 05, 2003 1:23 am Post subject: |
|
|
Master
Joined: 13 May 2002
Posts: 264
Location: Israel
|
Channels transfer persistent messages using batches.
By default batch size is 50. That means if you transfer <= 50 messages it will be sent as 1 transaction.
If you have communication problems, then you need to decrease the batch size to 1 ( it's ok to set it on one of the sides ).
Thus MQ will commit every message and not all together.
_________________
Regards.
Leonid.
IBM Certified MQSeries Specialist. |
|
| Back to top |
|
|
| emiranda |
| Posted: Wed Mar 05, 2003 5:15 am Post subject: |
|
|
Disciple
Joined: 21 Nov 2002
Posts: 196
Location: Dublin, Ireland
|
You can try to increase the BATCHINT also... and The message logs on the remote side will help you too.
_________________
Warm Regards,
EM |
|
| Back to top |
|
|
| Keka |
| Posted: Wed Mar 05, 2003 6:34 am Post subject: |
|
|
Voyager
Joined: 28 Dec 2002
Posts: 96
|
Here is my 2 cents.
IF the message is persistant, as it appears to me because you tried with restarting the QueueManager, Then if the destination queue is full and no dead letter queue or full dead letter queue will make the messages backed out on the xmit queue and also the channel will be stopped. If this is not happening then your destination side is OK.
Since nobody mentioned, you might want to check and see what is the MaxMesage size set at your QueueManager level. If this is less than 2MB then you will see error messages in the logs and you need to modify it.
hope this helps.
_________________
Keka |
|
| Back to top |
|
|
|
|
