ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Requester Channel

Post new topic  Reply to topic
 Requester Channel « View previous topic :: View next topic » 
Author Message
ping master
PostPosted: Thu Apr 10, 2003 10:17 am    Post subject: Requester Channel Reply with quote

Centurion

Joined: 20 Sep 2002
Posts: 116
Location: USA

when the DISC INT causes the channel to drop, it goes to an "inactive" state rather than a "stopped" state-

problem is, when I then issue a channel status cmd on that chl, it bombs.. but only when the channel is inactive of course, any other state it works great.

Any ideas how to make the channel go to a stopped state instead of inactive..if that is not possible, is it normal to write error handling logic to assume it is inactive set it to a status? (win Xp/ver 5.3)

thx

$PM
Back to top
View user's profile Send private message
meekings
PostPosted: Thu Apr 10, 2003 10:26 am    Post subject: Reply with quote

Voyager

Joined: 28 Jun 2001
Posts: 86
Location: UK, South West

Where are you issuing a channel status command from? And what is it that bombs?

I think the only way to get a channel into STOPPED state is to stop it manually.
_________________
Brian Meekings
Information Design, Inc.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
ping master
PostPosted: Thu Apr 10, 2003 10:57 am    Post subject: Reply with quote

Centurion

Joined: 20 Sep 2002
Posts: 116
Location: USA

Im issuing a mqexecute mqai command to the command server for MQCMD_INQUIRE_CHANNEL_STATUS.

Code:

mqreplybag =  mqadminbag.Execute(QueueManager,42,optsbag,RequestQueue,ReplyQueue);


strange, because when we were on NT/ ver2.1 it would drop to a stopped state unlike what it is doing in 5.3.



also if the channels are disabled, they will be in a stopped state, but what about if they have a message sequence error...stoppped also?

thanks


Last edited by ping master on Fri Apr 11, 2003 10:30 am; edited 1 time in total
Back to top
View user's profile Send private message
kevinf2349
PostPosted: Fri Apr 11, 2003 6:32 am    Post subject: Reply with quote

Grand Master

Joined: 28 Feb 2003
Posts: 1311
Location: USA

IMHO I wouldn't want my channel in a STOPPED state...period.

An INACTIVE channel can easily be restarted using triggering and as far as I recall (and maybe this has changed since 1998) this state is the only state that allows that to happen.

We use reasonable short disconnect intervals (10 minutes) and we trigger to restart whenever a message hits the XMITQ so we are not in the least bit worried by a channel being INACTIVE. In fact we dislike them being in a STOPPED state.

I am prepared to be corrected on the triggering requirements as I haven't really checked on that recently.

Another good reason for having a disconnect interval on the channel is that the encrytpion key (if you are using them) is negotiated at bind time and they exist for the duration of the channel connection. The longer the channel is active the greater the window of opportunity to break the encryption key.

I am not sure there is any real hard and fast ROTs for the disconnect interval or even whether to use one or not. that should be down to your own site (and data) requirements, and there is an overhead (read delay) while a channel gets started, but in my experience the delay usually isn't even.

Just my 2 cents worth.
Back to top
View user's profile Send private message
ping master
PostPosted: Fri Apr 11, 2003 10:29 am    Post subject: Reply with quote

Centurion

Joined: 20 Sep 2002
Posts: 116
Location: USA

thanks Kevin.

currently our system is set up exactly the same, our disconnect interval is set so after 4 min, it drops to inactive - we also have a trigger monitor on the xmitq to start the channel when a message drops in..
But in this case...

IYHO, if i have a monitoring tool, and I want to check the channel status, what scenario would you do then..


1-check channel status automatically on loading the application
2-if channel has no status(inactive)
3-output a message to user "Channel is Inactive"
4-then issue a start channel command programmatically
5-again check channel status
6-now output a message to user "Channel Running"

thanks

$ PM
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Requester Channel
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.