Author |
Message
|
sarasu |
Posted: Wed May 03, 2006 6:04 am Post subject: How to make channel "active" automatically? |
|
|
Master
Joined: 02 Feb 2006 Posts: 229
|
I am using MQ 5.3 on AIX. I have created a QMGR , local Q ,Channel. WHen the applications starts, it recieves a message from workflow and triggers another application.
When there are no messages comming, My channel becoming inactive after sometime. Can we make it active automatically, when it recieves a message. Or can we make it active always?
Replies are appreciated |
|
Back to top |
|
 |
Vitor |
Posted: Wed May 03, 2006 6:11 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
This behaviour is as designed - look up channels in the manuals for a fuller description of the various timeouts than I could possibly put here. Are you saying that once a channel becomes inactive no more messages flow, because if all goes well the next message attempting to cross it will automatically restore it to a running status.
If this is the case (the messages are not flowing), check your channel initiator. The only status that should stop messages going across a channel should be "stopped" i.e. manually shut down. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mrlinux |
Posted: Wed May 03, 2006 6:22 am Post subject: |
|
|
 Grand Master
Joined: 14 Feb 2002 Posts: 1261 Location: Detroit,MI USA
|
If you want the channels active all the time (Not Recommended),
change the sender channel attribute DISCINT to 0, and start the channel.
The reason it is not recommened, is if the channel is active during a network
hiccup, it will generate errors in the log(even no MQ Traffic), you will be amazed at how many network hiccups happen through out the day. _________________ Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
Back to top |
|
 |
elvis_gn |
Posted: Wed May 03, 2006 6:23 am Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Hi sarasu,
You can.
I am not very sure, but i think it is by triggering your Transmission queue on queue depth 1....This should start the channel automatically.
If it does not work, read for it in the Primer.pdf...i'm sure it works.
Maybe i'll tell you the reason why i'm sure once you find out how
Regards. |
|
Back to top |
|
 |
sirsi |
Posted: Wed May 03, 2006 7:01 am Post subject: |
|
|
Disciple
Joined: 11 Mar 2005 Posts: 177
|
|
Back to top |
|
 |
sarasu |
Posted: Wed May 03, 2006 10:01 am Post subject: |
|
|
Master
Joined: 02 Feb 2006 Posts: 229
|
Thanks you guys...it is working fine now.
I have one more question about "dead letter queue" if i put the "Backout Threshold" to 5, it mean it will try to send it again for 5 times right? if i am right will that try automatically or we have to do that manually??
If this is not the case where should i mension this option of retry sending these messages for couple of times? |
|
Back to top |
|
 |
vennela |
Posted: Wed May 03, 2006 10:12 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
You should probably post it as a different post.
Anyway, couple of things here.
1. Channel will keep trying to send the message foeever. It'll never put it in the DLQ.
2. If it is the application queue, it is the duty of the application to look at the BackOut count and BackOut threshold and increment them. |
|
Back to top |
|
 |
sarasu |
Posted: Wed May 03, 2006 10:36 am Post subject: |
|
|
Master
Joined: 02 Feb 2006 Posts: 229
|
But in our case we have got 2 messsages in DLQ. I found it in the document that either the Q is full or with the queue the process has not continued further the messages will go into DLQ. What we can do if they go into DLQ? |
|
Back to top |
|
 |
mrlinux |
Posted: Wed May 03, 2006 10:39 am Post subject: |
|
|
 Grand Master
Joined: 14 Feb 2002 Posts: 1261 Location: Detroit,MI USA
|
Well first the channel will place messages in the DLQ if it cant deliever them to the correct queue, and setting the backout thresshold will not help, what you want to look into is the runmqdlq program _________________ Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
Back to top |
|
 |
kevinf2349 |
Posted: Wed May 03, 2006 10:43 am Post subject: |
|
|
 Grand Master
Joined: 28 Feb 2003 Posts: 1311 Location: USA
|
Quote: |
What we can do if they go into DLQ? |
What does the business want you to do? That isn't our choice it is yours. The dead letter handler program can do several things, resend, delete, move to another queue.
You need to read up on runmqdlq (or whatever it is for your platform). |
|
Back to top |
|
 |
sarasu |
Posted: Wed May 03, 2006 12:49 pm Post subject: |
|
|
Master
Joined: 02 Feb 2006 Posts: 229
|
I donot want to see them in DLQ. Generally why it will go in to DLQ? I want it to retry until the message has been sent. Can i do something here in DLQ? |
|
Back to top |
|
 |
kevinf2349 |
Posted: Wed May 03, 2006 1:20 pm Post subject: |
|
|
 Grand Master
Joined: 28 Feb 2003 Posts: 1311 Location: USA
|
Quote: |
I donot want to see them in DLQ. Generally why it will go in to DLQ? |
Then don't let the destination queue fill up then.
Quote: |
Can i do something here in DLQ? |
I have already told you that you can. The answer is still the same, you have to run runmqdlq |
|
Back to top |
|
 |
|