| Author |
Message
|
| cvrachak |
 Posted: Sat Oct 12, 2002 2:25 pm Post subject: MQ Client 5.2 connecting to MQ Server 5.2 |
 |
|
Novice
Joined: 06 Jul 2002
Posts: 17
|
Hi all,
I am using MQ Series 5.2 in this setup.
I have an MQ Queue Manager running on Server1
I have installed MQ Client on Server2 and trying to communicate to Server1.
I have created a Server Connection Channel on Server1 called BTM
and set the following environment variable on Server2
set MQSERVER=BTM/TCP/SERVER1(PORT)
all the communication between server2 to server1 is fine.
I am trying to do some load Test from server2 to server1 and after some time, I get the following error on the server2
MQRC_Q_MGR_NOT_AVAILABLE
I have tried looking MQSeries Information Center and found the following info
ListenerBacklog=number
When receiving on TCP/IP, a maximum number of outstanding connection requests is set. This can be considered to be a backlog of requests waiting on the TCP/IP port for the listener to accept the request.
I have changed the ListenerBacklog in the MQ Series Service Explorer for the Queue Manager on Server1 to a max value of 65534.
Restarted the Queue Manager on the Server1 and still getting the error on Server2.
Any one faced this problem earlier?
Appreciate your help in this regards
Thanks
Chandra Sekhar |
|
| Back to top |
|
 |
| clindsey |
| Posted: Sat Oct 12, 2002 6:30 pm Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
Take a look at your MQ error logs. You may see some indication of the problem, like max channels exceeded. Look at AMQERR01.LOG in <mqmtop>/errors
<mqmtop>/qmgrs/@SYSTEM/errors
<mqmtop>/qmgrs<qmgr-name>/errors.
Charlie |
|
| Back to top |
|
|
| cvrachak |
| Posted: Sun Oct 13, 2002 8:42 am Post subject: MQ Client 5.2 connecting to MQ Server 5.2 |
|
|
Novice
Joined: 06 Jul 2002
Posts: 17
|
10/12/2002 19:35:49
AMQ9208: Error on receive from host server1(113.128.150.155).
EXPLANATION:
An error occurred receiving data from server1 (113.128.150.155) over TCP/IP.This may be due to a communications failure.
ACTION:
The return code from the TCP/IP (recv) call was 10053 (X'2745'). Record these values and tell the systems administrator.
-------------------------------------------------------------------------------
10/12/02 20:08:39
AMQ6119: An internal MQSeries error has occurred (WinNT error 1352 from LookupAccountSid.)
EXPLANATION:
MQSeries detected an unexpected error when calling the operating system. The MQSeries error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
10/12/02 20:08:52
AMQ6183: An internal MQSeries error has occurred.
EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been called. The failing process is process 988.
ACTION:
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
10/12/02 20:09:12
AMQ6119: An internal MQSeries error has occurred (WinNT error 2226 from NetLocalGroupGetInfo.)
EXPLANATION:
MQSeries detected an unexpected error when calling the operating system. The MQSeries error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
these are the various errors I could find.
But didn't find any thing related to reaching maximum limit of Channels or things like that.... |
|
| Back to top |
|
|
| clindsey |
| Posted: Sun Oct 13, 2002 5:46 pm Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
The 9208 message usually means a client process closed without doing a MQDISC. If you have many of these in the log, you may want to make sure the clients are disconnecting properly.
Just for p.d. when the clients can no longer connect, see if you can make a connection in bindings mode on the server, i.e. with amqsput or amqsget to make sure the MQRC_Q_MGR_NOT_AVAILAILABLE is truly related to socket connections.
Charlie |
|
| Back to top |
|
|
| KAKEZ |
| Posted: Thu Oct 31, 2002 3:20 am Post subject: Re: MQ Client 5.2 connecting to MQ Server 5.2 |
|
|
Centurion
Joined: 10 Oct 2002
Posts: 117
|
Chandra?
have you checked that the client application has been linked with the client mqseries stub and not with the server mqseries stub?
in that case the reason code you get is always: MQRC_Q_MGR_NOT_AVAILABLE
Jack |
|
| Back to top |
|
|
| vpamaresh |
| Posted: Thu Oct 31, 2002 8:50 am Post subject: Did you get the answer for your question |
|
|
Newbie
Joined: 31 Oct 2002
Posts: 1
|
Chandra,
Did you get the answer for your problem of connecting client to the server. I am also hitting the same problem. If you have any feedback, please email me or update here.
My email address is vpamaresh@yahoo.com
Thanks
Amaresh |
|
| Back to top |
|
|
| ghoose |
| Posted: Wed Nov 13, 2002 11:53 am Post subject: |
|
|
Novice
Joined: 23 Apr 2002
Posts: 16
|
whats the platform u guys are on.
I guess there is a limit on number of connection to server thru client and if u dont use MQDISC it will cause problem.
for solaris its 10 i think.
hoep this help
ghoose |
|
| Back to top |
|
|
|
|
