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 » Why Does Listener Stop (but orphaned process ties up port)?

Post new topic  Reply to topic
 Why Does Listener Stop (but orphaned process ties up port)? « View previous topic :: View next topic » 
Author Message
queuetip
PostPosted: Tue Feb 13, 2007 1:39 pm    Post subject: Why Does Listener Stop (but orphaned process ties up port)? Reply with quote

Acolyte

Joined: 03 Feb 2005
Posts: 67

ENVIRONMENT:
I am running MQ V5.3 on a Windows server using a MQM Domain group under the MQM group on the local machine. I belong to the MQM Domain group.

PROBLEM:
Via Service window, the queue manager starts and all 4 tasks appear as running. The listener is running on port 1401 just fine. I can put messages on local queues via client connection and amqsputc utility.

An hour or two later, in MMC service console the queue manager and repository are running BUT the channel initiator and listener are both stopped for no apparent reason. I check error logs, FDC errors and Window event file - nothing obvious.

I try to restart the two services and get a message indicating the listener is already running. Sure enough I loook in Process Explorer and see the listener is running on port 1401...but MMC shows it stopped. Thus, I have to kill the process and it starts fine.

Now, this whole process repeats. I would love to hear some ideas on how to prevent the listener from "stopping". Thank you!

Mike
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Feb 13, 2007 3:40 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

May be the mmc is just reporting wrong?
To check if the listener is really stopped you might try to:
telnet <host> <port>
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
queuetip
PostPosted: Wed Feb 14, 2007 7:00 am    Post subject: Reply with quote

Acolyte

Joined: 03 Feb 2005
Posts: 67

Yes - unfortunately I did check that out. After it stopped, I tried to put a message out on a local queue using amqsputc and could not connect. Originally, I could put a message out there just fine.

I appreciate the idea - have any others?

Thanks,
Mike
Back to top
View user's profile Send private message
SAFraser
PostPosted: Fri Feb 16, 2007 9:28 am    Post subject: Reply with quote

Shaman

Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA

What CSD level is your 5.3 queue manager? I recollect that early CSDs on Windows had some listener issues....

Shirley
Back to top
View user's profile Send private message
tosaurav
PostPosted: Fri Feb 16, 2007 1:38 pm    Post subject: Reply with quote

Acolyte

Joined: 16 Jan 2007
Posts: 62

Post Top of FDC file
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 » Why Does Listener Stop (but orphaned process ties up port)?
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.