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 » WebSphere Message Broker (ACE) Support » 2059 and 2009 again

Post new topic  Reply to topic Goto page 1, 2  Next
 2059 and 2009 again « View previous topic :: View next topic » 
Author Message
alma
PostPosted: Tue Feb 15, 2011 6:02 am    Post subject: 2059 and 2009 again Reply with quote

Apprentice

Joined: 26 Jan 2011
Posts: 36

Hi,

I can not connect to a remote broker.
It is odd for me because it has already worked before.
I checked the channel, the listener and queue manager.
I read about SYSTEM.ADMIN.SVRCONN channel, it is not in queue manager.
I also tried the rfhutilc and it gave this error:
Quote:
14.32.53 2537 Channel not available or all connections in use
2537 Channel not available or all connections in use
2537 Channel not available or all connections in use
Error getting queue names


My question is what I should check yet?

Thank you.
Back to top
View user's profile Send private message
alma
PostPosted: Tue Feb 15, 2011 6:32 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jan 2011
Posts: 36

I defined the SYSTEM.ADMIN.SVRCONN channel but it didn't help.
Back to top
View user's profile Send private message
Mr Butcher
PostPosted: Tue Feb 15, 2011 6:42 am    Post subject: Reply with quote

Padawan

Joined: 23 May 2005
Posts: 1716

don't run around headless defining objects that you may not require. find out which objects you are using and if they exist. did you try telnet to ip / port to verify you have connectivity? did you check the queuemanager log? what about the number of connections? did you verify you did not exhaust that? what has been changed between "it worked before" and "now" ?

2537 returncore reads:

Code:
An MQCONN call was issued from a client to connect to a queue manager but 
the channel is not currently available. Common causes of this reason code 
are:                                                                       
                                                                           
   The channel is currently in stopped state.                             
                                                                           
   The channel has been stopped by a channel exit.                         
                                                                           
   The queue manager has reached its maximum allowable limit for this     
    channel from this client.                                             
                                                                           
   The queue manager has reached its maximum allowable limit for this     
    channel.                                                               
                                                                           
   The queue manager has reached its maximum allowable limit for all       
    channels.   


did you verify all that?
_________________
Regards, Butcher
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Feb 15, 2011 6:58 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Is it a zOS queue manager without a Client Connection Facility, and thus limited to only five client connections?
Back to top
View user's profile Send private message
alma
PostPosted: Tue Feb 15, 2011 7:29 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jan 2011
Posts: 36

Dear Mr Butcher,

I've read the lack of SYSTEM.ADMIN.SVRCONN channel would cause this type of error.
The telnet is OK.
I checked the channels and port.
This connection worked a half year before.I don't know what has been changed because I was given this task lately. I try to learn it nowadays.
There are no connections on queue manager, yet.
As regard queue manager log I have just read it.
Back to top
View user's profile Send private message
alma
PostPosted: Tue Feb 15, 2011 7:35 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jan 2011
Posts: 36

It is on an AIX and I haven't the faintest idea about the limitation of connections.
I'll check up.
Back to top
View user's profile Send private message
alma
PostPosted: Tue Feb 15, 2011 7:58 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jan 2011
Posts: 36

There are no any limitations in qm.ini.
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Feb 15, 2011 8:01 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

alma wrote:
There are no any limitations in qm.ini.


So it's just the normal default limit on connections then?

When you say "the connection worked half a year before" are you saying that no connections have been made to this queue manager in 6 months? It's been inert? If not, when was the last time a successful connection was made?

Has the AIX been restarted since the last successful connection?

When you say "the telnet is OK" does that mean you can telnet to the box (which proves nothing) or that you can telnet to the WMQ listener and see it react (which proves no network issues)?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
alma
PostPosted: Tue Feb 15, 2011 8:26 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jan 2011
Posts: 36

What is the best device to read qm logs, please?
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Feb 15, 2011 8:38 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

alma wrote:
What is the best device to read qm logs, please?


Typically the disc device they're stored on.

If you mean "what application" then vi, cat or any other text based tool works fine.

If they look like rubbish, then you're looking at the queue manager's transaction log files. These are in a binary format and contain nothing of any value to you.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
alma
PostPosted: Tue Feb 15, 2011 8:39 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jan 2011
Posts: 36

Yes, it is a default limit on connections.
I connected to the server IP and the listener port by telnet.
Yes, the AIX was restarted due to a storage error.
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Feb 15, 2011 8:45 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

alma wrote:
I connected to the server IP and the listener port by telnet.


And have you located the response the queue manager logs now?

alma wrote:
Yes, the AIX was restarted due to a storage error.


When? Has a successful connection been made since?

Better information, better advice.

Or raise a PMR. And be guided on what to look for.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
alma
PostPosted: Tue Feb 15, 2011 9:01 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jan 2011
Posts: 36

Hm, my mother didn't tell me that this is just like Windows.
I restarted the queue manager and now it is OK.


Now again I thank you very much for helping me.
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Feb 15, 2011 9:05 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

alma wrote:
Hm, my mother didn't tell me that this is just like Windows.
I restarted the queue manager and now it is OK.


AIX tends not to be. In any sense. Including the "just restart it and it's fine".

I'd look (or get the sys admins to look) a bit closer at this "storage error" of yours.

But if it's working, that's a result.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
JosephGramig
PostPosted: Tue Feb 15, 2011 1:36 pm    Post subject: Reply with quote

Grand Master

Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA

I would be willing to bet that a process needed to make the connection died. That might indicate you system needs maintenance.

You might want to check that and apply maintenance as necessary. For both WMQ and WMB.
Back to top
View user's profile Send private message AIM Address
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » 2059 and 2009 again
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.