| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| System Resource shortage in Windows 2000 Server environment. |
« View previous topic :: View next topic » |
| Author |
Message
|
| kodiakk |
 Posted: Mon Oct 27, 2008 6:35 am Post subject: System Resource shortage in Windows 2000 Server environment. |
 |
|
Acolyte
Joined: 04 Dec 2007
Posts: 58
Location: Jacksonville, Fl.
|
After a recent Windows upgrade, I'm seeing odd behavior in MQ. It originally started by showing channels in "initializing" status, and I was unable to stop/start them. Basically, it seemed the queue manager was non-responsive to commands (all other functionality was working, meaning: channels already running were working, queues were getting and putting messages, etc, but anything NEW was not responding).
I eventually had to disconnect the server from the MQ Explorer, and execute the commands via command line (which is fine for me, but some of my co-workers don't have the command-line experience to make this work).
We saw the same behavior again this morning on a different queue manager (this machine has about 20 queue managers)
In the MQ system-error logs, I'm seeing the following entry:
EXPLANATION:
WebSphere MQ has detected that an agent process has terminated unexpectedly.
The queue manager connection(s) that this process is responsible for will be
broken.
ACTION:
Use any previous FFSTs to determine the reason for the failure. Try to
eliminate the following reasons before contacting your IBM support center.
1) A user has inadvertently terminated the process.
2) The system is low on resources. Some operating systems terminate processes
to free resources. If your system is low on resources, it is possible that
the operating system has terminated the process so that a new process can be
created.
Because of this message, I'm certain that the issue is with system resources, but is there any way to pinpoint just WHICH resources are in question here?
Any help would be greatly appreciated.
Thanks!
_________________
"Don't take life too seriously... you won't get out of it alive..." |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Mon Oct 27, 2008 7:55 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Interesting. I had the same problem on a Windows 2003 SP1 server this past weekend, right after the Windows guys applied the latest security patches from Microsoft. The server has 2 QMs. Its a DEV server. One of the QMs was fine, the other one had two XMITQs that were being held by two separate channel processes that no longer existed, not even in Task Manager. Consequently a new instance of the SNDR channel would not start because the XMITQ was being held exclusively. Finally I restarted the one QM and all is OK. The other channels on the QM were fine. The other QM on the system was fine. About 9 other servers that got their MSFT patches that night are all OK. This one is the only one running more than 1 QM, and it is a very old server that used to run Windows 2000 years ago. Hmmmm.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| kodiakk |
| Posted: Mon Oct 27, 2008 9:35 am Post subject: |
|
|
Acolyte
Joined: 04 Dec 2007
Posts: 58
Location: Jacksonville, Fl.
|
Ok, that's good to know. Sounds like it might a definite route to keep looking down, then.
I know that there haven't been any other changes to these systems, so this windows patch is highly suspect.
I've recommended that we move to the backup server, just to see if it's machine specific or not. I'm hoping it is, otherwise...
Thank you very much for your response. I appreciate it, and hope to hear more if anything else comes up.
_________________
"Don't take life too seriously... you won't get out of it alive..." |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
