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 » Very Urgent: 'SYSTEM.AUTO.SVRCONN' ended abnormally

Post new topic  Reply to topic
 Very Urgent: 'SYSTEM.AUTO.SVRCONN' ended abnormally « View previous topic :: View next topic » 
Author Message
jolonm
PostPosted: Mon Aug 17, 2009 12:04 am    Post subject: Very Urgent: 'SYSTEM.AUTO.SVRCONN' ended abnormally Reply with quote

Apprentice

Joined: 31 Dec 2008
Posts: 25

We received following error message in queue manger error log:

AMQ9513: Maximum number of channels reached.

EXPLANATION:
The maximum number of channels that can be in use simultaneously has been
reached. The number of permitted channels is a configurable parameter in the
queue manager configuration file.
ACTION:
Wait for some of the operating channels to close. Retry the operation when some
channels are available.


AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.AUTO.SVRCONN' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.AUTO.SVRCONN' in
the error files to determine the cause of the failure.


Can anybody help us quickly :
- The auto-definition is disabled for the QM, so why these 'SYSTEM.AUTO.SVRCONN is created. any why this channel ended abnormally?
- How channels reached to its max limit?

Thanks.
Back to top
View user's profile Send private message
Mr Butcher
PostPosted: Mon Aug 17, 2009 12:34 am    Post subject: Reply with quote

Padawan

Joined: 23 May 2005
Posts: 1716

Looks like an application or someone is using the SYSTEM.AUTO.SRVCONN channel to connect to your queuemanager.?!?
however, it also looks like it is eating up all of the allowed connections to the queuemanager. i would check the channel status trying to find out about these connections (maybe also queue status can help). for the max. number of connections check the AMQ9513 message in the manual, it gives you a hint what to do if you want to modify the number of connections.
_________________
Regards, Butcher
Back to top
View user's profile Send private message
jolonm
PostPosted: Mon Aug 17, 2009 12:44 am    Post subject: Reply with quote

Apprentice

Joined: 31 Dec 2008
Posts: 25

Thank you for your quick response:

Even if we have disabled to auto-definition for the qm, can somebody use SYSTEM.AUTO.SRVCONN to connect to QM. and if that party is using then this auto channel will be at their end and the error message should be logged into their QM error log, right?
Just to give you some more information - we transmit our messages to another QM using remote queue, and the transmision was stopped when we receive this error. we had to restart the QM.

About allowable connection - i tried to read manuals and 'Intercommunication.pdf' but it didnt help me lot - it seems to me that there will be channel for each connection, mean number of connections and channels will be same.
To prove this i set the max channel to 10 for the QM, and started 100+ connections with QM but didnt find any error (even max channel reached error).
Back to top
View user's profile Send private message
exerk
PostPosted: Mon Aug 17, 2009 1:13 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

What it means is that someone is connecting via client to an insecure queue manager, and if they can do that, what else can they do?

As to your other questions:

Quote:
- The auto-definition is disabled for the QM, so why these 'SYSTEM.AUTO.SVRCONN is created. any why this channel ended abnormally?


SYSTEM.AUTO.SVRCONN can be used just like any other SVRCONN, unless it's secured. If people know it's there (as any good WMQ Admin should) and it's unsecured, well, you've already seen the consequences.

Quote:
- How channels reached to its max limit?


Because, as Mr Butcher pointed out, someone "...is eating up all of the allowed connections to the queue manager..."

Secure the SVRCONN's, then wait for someone to scream, and you'll have identified the culprit.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
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 » Very Urgent: 'SYSTEM.AUTO.SVRCONN' ended abnormally
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.