| Author |
Message
|
| ustcboy |
 Posted: Sun Dec 09, 2007 3:58 am Post subject: Help please: AMQ4059 - Could not establish a connection to t |
 |
|
Novice
Joined: 02 Dec 2007
Posts: 10
|
Help please: AMQ4059 - Could not establish a connection to the queue manager
Pls help me : my xp client can't connect aix env mq 6.0
aix server user:mq/mqm
$ crtmqm -q cap
There are 89 days left in the trial period for this copy of WebSphere MQ.
WebSphere MQ queue manager created.
Creating or replacing default objects for cap.
Default objects statistics : 40 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
$ strmqm
There are 89 days left in the trial period for this copy of WebSphere MQ.
WebSphere MQ queue manager 'cap' starting.
5 log records accessed on queue manager 'cap' during the log replay phase.
Log replay for queue manager 'cap' complete.
Transaction manager state recovered for queue manager 'cap'.
WebSphere MQ queue manager 'cap' started.
$ runmqsc
5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
Starting MQSC for queue manager cap.
define qlocal(QUEUE1)
1 : define qlocal(QUEUE1)
AMQ8006: WebSphere MQ queue created.
define channel(channel1) chltype(svrconn) trptype(tcp) mcauser('mq')
2 : define channel(channel1) chltype(svrconn) trptype(tcp) mcauser('mq')
AMQ8014: WebSphere MQ channel created.
alter listener(system.default.listener.tcp) trptype(tcp) port(1414)
3 : alter listener(system.default.listener.tcp) trptype(tcp) port(1414)
AMQ8623: WebSphere MQ listener changed.
start listener(system.default.listener.tcp)
4 : start listener(system.default.listener.tcp)
AMQ8021: Request to start WebSphere MQ Listener accepted.
display lsstatus(*)
5 : display lsstatus(*)
AMQ8631: Display listener status details.
LISTENER(SYSTEM.DEFAULT.LISTENER.TCP) STATUS(RUNNING)
PID(6952)
end
6 : end
5 MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.
clinet
---
windows client webspherer explorer
error report
----
AMQ4059
Severity
10 : Warning
Message
Could not establish a connection to the queue manager.
Explanation
The attempt to connect to the queue manager failed. This could be because the queue manager is incorrectly configured to allow a connection from this system, or the connection has been broken.
Response
Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded.
[/img]
Last edited by ustcboy on Sun Dec 09, 2007 7:11 am; edited 2 times in total |
|
| Back to top |
|
 |
| ustcboy |
| Posted: Sun Dec 09, 2007 4:00 am Post subject: |
|
|
Novice
Joined: 02 Dec 2007
Posts: 10
|
win client can ping 172.16.80.12 is alive
win aix both have user(mq) .
if chanel name =channel1 ,but it can't connect ,It's disconnected
$ netstat -an|grep 1414
*.1414 *.* 0 0 49152 0 LISTEN
172.16.80.12.1414 172.16.110.142.3644 32768 0 49608 0 ESTABLISHED
*.1414 *.* 0 0 49152 0 LISTEN
windows client :
MQSERVER =cap/TCP/172.16.80.12(1414)
$ who
root console Nov 26 01:18
root pts/2 Dec 9 19:31 (172.16.110.142)
bash-3.00$ netstat -an|grep 1414
*.1414 *.* 0 0 49152 0 LISTEN
172.16.80.12.1414 172.16.110.142.3662 32732 0 49608 0 FIN_WAIT_2
*.1414 *.* 0 0 49152 0 LISTEN
D:\>amqsputc cap
Sample AMQSPUT0 start
MQCONN ended with reason code 2059
Last edited by ustcboy on Sun Dec 09, 2007 4:34 am; edited 1 time in total |
|
| Back to top |
|
|
| ustcboy |
| Posted: Sun Dec 09, 2007 4:30 am Post subject: |
|
|
Novice
Joined: 02 Dec 2007
Posts: 10
|
$ netstat -an|grep 1414
*.1414 *.* 0 0 49152 0 LISTEN
172.16.80.12.1414 172.16.110.142.3826 32152 0 49608 0 TIME_WAIT
*.1414 *.* 0 0 49152 0 LISTEN
$ who
root console Nov 26 01:18
mq pts/1 Dec 9 20:33 (172.16.110.142)
$ dspmq
QMNAME(venus.queue.manager) STATUS(Running)
QMNAME(queue.manager.1) STATUS(Running)
QMNAME(cap) STATUS(Running)
now windows client websphere explorer is error
+++++++++++++++++++++++++
AMQ4059
Severity
10 : Warning
Message
Could not establish a connection to the queue manager.
Explanation
The attempt to connect to the queue manager failed. This could be because the queue manager is incorrectly configured to allow a connection from this system, or the connection has been broken.
Response
Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded
++++++++++++++++++ |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Sun Dec 09, 2007 6:36 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1231
Location: Gold Coast of Florida, USA
|
well, the MCAUSER is mq.
Don't you want MCAUSER('mqm')?
Otherwise, you would have had to create an ID of 'mq' and grant permission to it to do what you want to do.
And this will give every one on your network anonymous administrative privilege.
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| ustcboy |
| Posted: Sun Dec 09, 2007 6:55 am Post subject: |
|
|
Novice
Joined: 02 Dec 2007
Posts: 10
|
| JosephGramig wrote: |
well, the MCAUSER is mq.
Don't you want MCAUSER('mqm')?
Otherwise, you would have had to create an ID of 'mq' and grant permission to it to do what you want to do.
And this will give every one on your network anonymous administrative privilege. |
because I use winXP professional ,can't both create mqm group &mqm user,so I create username call mq
winxp user mq is administrator member
-----
My aix server create mq user ,too
---
now |
|
| Back to top |
|
|
| ustcboy |
| Posted: Sun Dec 09, 2007 6:58 am Post subject: |
|
|
Novice
Joined: 02 Dec 2007
Posts: 10
|
DISPLAY CHANNEL(channel1)
2 : DISPLAY CHANNEL(channel1)
AMQ8414: Display Channel details.
CHANNEL(CHANNEL1) CHLTYPE(SVRCONN)
ALTDATE(2007-12-09) ALTTIME(22.45.3
COMPHDR(NONE) COMPMSG(NONE)
DESCR( ) HBINT(300)
KAINT(AUTO) MAXMSGL(4194304)
MCAUSER(mq) MONCHL(QMGR)
RCVDATA( ) RCVEXIT( )
SCYDATA( ) SCYEXIT( )
SENDDATA( ) SENDEXIT( )
SSLCAUTH(REQUIRED) SSLCIPH( )
SSLPEER( ) TRPTYPE(TCP)
AMQ8630: Display listener information details.
LISTENER(LISTENER1) CONTROL(QMGR)
TRPTYPE(TCP) PORT(1414)
IPADDR(172.16.80.12) BACKLOG(0)
DESCR( ) ALTDATE(2007-12-09)
ALTTIME(23.02.20)
now error no:
----
AMQ4059
Severity
10 : Warning
Message
Could not establish a connection to the queue manager.
Explanation
The attempt to connect to the queue manager failed. This could be because the queue manager is incorrectly configured to allow a connection from this system, or the connection has been broken.
Response
Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Dec 09, 2007 10:05 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
| ustcboy wrote: |
because I use winXP professional ,can't both create mqm group &mqm user,so I create username call mq
winxp user mq is administrator member
-----
My aix server create mq user ,too
---
now |
But is the mq user member of the mqm group?
As well are you sure there is no firewall problem?
What happens when you do telnet mqhost 1414 ?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Sun Dec 09, 2007 12:42 pm Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1231
Location: Gold Coast of Florida, USA
|
ustcboy,
Your first post seems to indicate your QMGR is running on AIX.
| ustcboy wrote: |
Pls help me : my xp client can't connect aix env mq 6.0
aix server user:mq/mqm |
I assume you mean "my xp client can't connect to my aix env mq 6.0".
Assuming this, it does not matter what your XP ID is as when you set the MCAUSER. That value will over ride all inbound IDs. You certainly can and must have the ID mqm in the mqm group on the AIX machine.
Now, follow fjb_saper's instructions to test your connectivity to the QMGR.
Please let us know what you want to achieve and maybe we can point you in the right direction. I assume your goal is not to have a QMGR with anonymous administrative access.
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
|
|
