Yes,
of course your application folks won't trust the opinions of the MQSeries
experts within their own company (or consultants that their company as
hired). But strangers off the Internet - they must know what their talking
about!!! <Big Grin>
-
Steve
-----Original Message-----
From: Michael F Murphy/AZ/US/MQSolutions [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 02, 2002 8:07 PM
To: [EMAIL PROTECTED]
Subject: Re: Starting channel as a service on Windows NT/2000
Thanks Adi, Nikhil, Steve, T. Rob,
I realize all these things but it's good to hear it from other people as reinforcement. It also give me ammunition to show proof that the concept being used is wrong. Many of the people I am dealing with are difficult to convince that there are better ways to do things. We are working to implement BMC Patrol for monitoring but it is a ways off from full implementation so the appl groups are looking for things to monitor. I just need to get them monitoring the right things.
Thanks for the help.
Mike Murphy
Sr. Middleware Consultant
MQ Solutions, LLC
http://www.mqsolutions.com
Adiraju S Rao <[EMAIL PROTECTED]> wrote:
10/02/2002 07:02:25 PM [EMAIL PROTECTED] Re: Starting channel as a service on Windows NT/2000
Mike,
We had a similar experience in one of our projects saying that they want to use
snap-in to even monitor the channel and even implemented in the test
environment, but when we had the exact same issue of the snap-in service of
channel going to "stopped " status, I explained to them indicating that this
status will not necessarily mean having a problem and infact I asked the
application team to send a message and the channel started and the message is
processed successfully. At this point the channel is running but the snap-in
service shows still "stopped". After showing this they are convinced and
agreed to remove that as service.
There are lot of monitoring tools out in the market to monitor MQ which can be
used and also can send automatic pages, so i guess the right approach would be
to educate your sysadmin about the pro's and con's of this implementation, if
they still want to use this the pages should go to them.
Hope this helps.
Adi
From: "Michael F Murphy/AZ/US/MQSolutions" <[EMAIL PROTECTED]>
@AKH-Wien.AC.AT> on 10/01/2002 08:01 PM CST
Please respond to "MQSeries List" <[EMAIL PROTECTED]>
Sent by:"MQSeries List" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject:Starting channel as a service on Windows NT/2000
I am facing an interesting issue regarding how channels are started and how
system administrators and application developers perceive MQSeries to be
"running." I would like to know of any experience, good or bad, you have had
with running channels this way and your opinion overall.
First - there are a large number of Windows NT and 2000 machines running either
MQ 5.1 or 5.2. They have sender channels that are triggered with a disconnect
interval of 1200. They process large volumes of data so the channels run most
of the time. The interesting part is the sender channels are also set up to
run as a service in the MQSeries Services snap-in. I have actually never seen
this before since triggering of channels is pretty much a best practice and
this sort of thing is not needed. The snap-in has the menu item to add the
channel as a service so it must be supported. However, this seems to only be
appropriate if the disconnect interval is set to 0. The way it is set up, the
channel starts as a service initially, but then when the disconnect interval
expires, the channel goes inactive and the services enters a "stopped" status.
Then when the channel gets triggered it starts just fine, but the service still
indicates stopped. I also found that sometimes if I try to start the channel
as a service again, amqmsvrn.exe crashes. This is expected behavior, but it
confuses the sys admins.
Now the interesting part. The application developers and sys admins believe
MQSeries to be channels and so monitoring channels is how they check the health
of MQSeries. The problem is when they see this "service" stopped they believe
there is a problem and page support. I have recommended the practice of
starting the channels as a service be stopped and the services deleted from the
queue managers in the snap-in. This is a real big deal so it must be backed up
really well. This is going to require lots of education too which I am very
happy to supply. I just need a little more evidence to prove this practice is
not a best practice and should be stopped. If anyone has any advice, I would
love to here it.
Sorry for not participating so much in the list over the last year.
Mike Murphy
Sr. Middleware Consultant
MQ Solutions, LLC
http://www.mqsolutions.com
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
