| Author |
Message
|
| AkankshA |
 Posted: Thu Jun 19, 2008 3:49 am Post subject: |
 |
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
did that work ??
_________________
Cheers |
|
| Back to top |
|
 |
| skoesters |
| Posted: Thu Jun 19, 2008 3:51 am Post subject: |
|
|
Acolyte
Joined: 08 Jun 2008
Posts: 73
|
i can tell you tomorrow.
at the moment the channel is running |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Thu Jun 19, 2008 4:58 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| AkankshA wrote: |
remove triggering...
set discint
restart channels.... QM if need be..
and ur channels wont go down..
PS: keeping channels active all the time is a resource consuming act... |
Don't remove triggering. Setting the DISINT to 0 is sufficirnt. In fact removing triggering will result in more issue than it solves....especially after a queue manager restart.
Why? I will let you tell us why that would be.
Apart from it being a resource comsuming act it is also not a very good idea to keep a channel running from a security and an operational standpoint either, but as always it really depends on your business requirements and service levels.
While setting DISCINT to 0 may seem like the perfect solution to your needs it is not always the case but it is very hard to make the call without understanding the business needs.
If you don't mind insecure channels and wasted processor cycles, plus you have good operational recovery processes in place then DISCINT=0 is fine.  |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Jun 19, 2008 5:44 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
Years ago it was burned into my mind that DISCINT = 0 is bad. Do you really want the channel to run F-OR-E-V-E-R? Of course not. I have some channels that I do need to run all the time because the app can't incur the overhead of the the triggering. So I set the DISINT to 300000, or ~ 83 hours. That's enough to cover a slow 3 day weekend when some messages may not be flowing.
The reason against the DISCINT = 0 was something related to channels inside a cluster. Something about an orphaned channel that was left behind would hang around forever with DISCINT = 0 while its new Adopted replacement handled new work. But with 300000 it would have a chance to time out. Now that was years ago, MQ 5.2 or maybe even older. It may not be an issue nowadays.
But still, I don't use DISCINT = 0 on the few channels that have a business requirement for not having to incur channel triggering overhead. In all other case I use DISCINT. An Inactive channel can't be effected by network problems. Why have your channel running in the middel of the night whe there is no MQ work to move and IT gremlins running around messing with routers and switches?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| skoesters |
| Posted: Thu Jun 19, 2008 5:55 am Post subject: |
|
|
Acolyte
Joined: 08 Jun 2008
Posts: 73
|
for the moment i am only learning about mq series. i have a test installation with about 10 QMGR and play with them. it was interessting for me to know how to keep the channel alive forever.
in production use we will use (i think so) the triggering or DISCINT = xxxxxx like you do.
thanks for your help |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Jun 19, 2008 7:54 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
| skoesters wrote: |
in production use we will use (i think so) the triggering or DISCINT = xxxxxx like you do.
|
use triggering AND DISCINT please. 
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
