| Author |
Message
|
| cactus |
 Posted: Sat Oct 12, 2002 6:19 pm Post subject: Websphere MQ 5.3.. channel in retrying mode... |
 |
|
Apprentice
Joined: 12 Oct 2002
Posts: 30
|
Hi,
Installed Websphere MQ 5.3 on win 2000.when trying to start SDR channel its going in retrying mode and RCVR channel in inactive mode (even when trying to start ).Local communication address parameter value left blank.
below are the error from
mqseries\errors\
AMQ9213: A communications error for TCP/IP occurred.
EXPLANATION:
An unexpected error occurred in communications.
ACTION:
The return code from the TCP/IP (ioctlsocket) call was 10038 (X'2736'). Record
these values and tell the systems administrator.
mqseries\qmgrs\errors\
AMQ9202: Remote host 'mycomp (99.9.9.9.9) (1416)' not available, retry
later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'mycomp
(99.9.9.9.9) (1416)' was not successful. However the error may be a
transitory one and it may be possible to successfully allocate a TCP/IP
conversation later.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
10061 (X'274D'). The reason for the failure may be that this host cannot reach
the destination host. It may also be possible that the listening program at
host 'mycomp (99.9.9.9.9) (1416)' was not running. If this is the case,
perform the relevant operations to start the TCP/IP listening program, and try again.
ur help will be greatly appreciated
thanks
cactus |
|
| Back to top |
|
 |
| dgolding |
| Posted: Sun Oct 13, 2002 11:06 pm Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
Is the listener or whatever on the receiving side running? If it's NT/2000, are you doing a runmqlsr -p 1416, or if unix, have got port 1416 configured with INETD?
Try a ping channel on the sending side to see if anything is there, it appears that there is nothing running on the receiving side... |
|
| Back to top |
|
|
| cactus |
| Posted: Mon Oct 14, 2002 9:10 pm Post subject: |
|
|
Apprentice
Joined: 12 Oct 2002
Posts: 30
|
Thanks for you response...,here all are running
Queue Manager 'QM1' is: Running
0 Queue Manager (Running)
1 Command Server (Running)
2 Channel Initiator (Running)
3 Listener (Running)
Queue Manager 'QM2' is: Running
0 Queue Manager (Running)
1 Command Server (Running)
2 Channel Initiator (Running)
3 Listener (Running)
when trying to ping ,this is the error...,
AMQ4048 Unexpected error.
Explanation: An unexpected error occurred during the
operation.
User Response: Examine the problem determination
information on this computer and also on the queue
manager’s computer to establish the cause of the error.
pls help me out..
thanks...
Cactus |
|
| Back to top |
|
|
| dgolding |
| Posted: Mon Oct 14, 2002 9:35 pm Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
| What does the error log from the other side (QM2) say? Are you sure the port number for QM2 is 1416 (not the default?) |
|
| Back to top |
|
|
| bduncan |
| Posted: Mon Oct 14, 2002 9:53 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Yes, normally the port defaults to 1414. Are you sure you've configured your queue manager (channel listener) for a non-standard port (1416)? Also, the IP address looked curious enough: 99.9.9.9.9. Is that the real IP address, or did you change it so we wouldn't know your machine's IP, or perhaps that is an internal IP behind your firewall? At any rate, just check to make sure it's correct. Especially if the CONNAME attribute on your sender channel is specified by the hostname. Remember, while most stuff in runmqsc isn't case sensitive, the hostname is. Make sure it exactly matches the machine name.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| dgolding |
| Posted: Mon Oct 14, 2002 10:00 pm Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
Brandon, thanks, all good points, but I think you'll find that hostname IS case insensitive.....  |
|
| Back to top |
|
|
| Tibor |
| Posted: Mon Oct 14, 2002 11:16 pm Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
Cactus,
Both qmgrs are localized same way? Just these errors remember me for a CCSID conflict.
Tibor |
|
| Back to top |
|
|
| bduncan |
| Posted: Tue Oct 15, 2002 9:17 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Don,
You caught me 
I posted several responses to people's posts last night, and came away thinking I probably botched some (or all) of them because I had just gotten done doing 14 hours straight of bug fixes (of someone else's code no less) and my brain was definitely on its way to shutting off for the night
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| dgolding |
| Posted: Wed Oct 16, 2002 4:20 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
| No worries Brandon... I thought it was a bit late in the night for you, you were probably well past your best! |
|
| Back to top |
|
|
| cactus |
| Posted: Wed Oct 16, 2002 10:03 am Post subject: |
|
|
Apprentice
Joined: 12 Oct 2002
Posts: 30
|
Hi,
QM1 = port is default(1414).
Remote Queue defined
Xmit queue defined
Sender Channel defined with IPaddress and port(1416)
QM2 = Port is 1415.
Local queue defined
Receiver channel defined.
All the objects are running and seems to be fine,when i try to start the channel.chl goes in retrying mode.and the error says...
AMQ9202: Remote host 'BMW78TPPT8 (121.168.0.101) (1416)' not available, retry
later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'BMW78TPPT8
(121.168.0.101) (1416)' was not successful. However the error may be a
transitory one and it may be possible to successfully allocate a TCP/IP
conversation later.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
10061 (X'274D'). The reason for the failure may be that this host cannot reach
the destination host. It may also be possible that the listening program at
host 'BMW78TPPT8 (121.168.0.101) (1416)' was not running. If this is the case,
perform the relevant operations to start the TCP/IP listening program, and try
again.
pls help
thanks
Cactus |
|
| Back to top |
|
|
| dgolding |
| Posted: Wed Oct 16, 2002 10:07 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
First thing straight away - you configure port numbers to Queue Managers, not channels! I take it both QMs are on the same box. If Qm1 is on 1414, and QM2 on 1415, then the sender channel on QM1 to QM2 should connect to "mycomp(1415)".
Can you try that and see what happens?
HTH
Don |
|
| Back to top |
|
|
| cactus |
| Posted: Wed Oct 16, 2002 10:54 am Post subject: |
|
|
Apprentice
Joined: 12 Oct 2002
Posts: 30
|
Don ,
No improvement......,defined the sender channel on QM1 to QM2 connected to "mycomp(1415)". But still its going in retrying mode.
thnaks
cactus |
|
| Back to top |
|
|
| dgolding |
| Posted: Wed Oct 16, 2002 11:06 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
| And you're SURE you doing a "runmqlsr -t tcp -p 1415 -m QM2" somewhere - I take it this is an NT/2000 machine... |
|
| Back to top |
|
|
| cactus |
| Posted: Wed Oct 16, 2002 11:18 pm Post subject: |
|
|
Apprentice
Joined: 12 Oct 2002
Posts: 30
|
No,Don......its giving same thing......I have taken care of listeners but still,
CCSID IS 437 that's default one .This is simple one but i don't know where its going wrong.
anything to be taken care in WEB MQ 5.3
regards
Cactus |
|
| Back to top |
|
|
| dgolding |
| Posted: Wed Oct 16, 2002 11:30 pm Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
Well, according to the Microsoft Web site, a 10061 TCP/IP (socket) error is caused by a bad address. I notice you had the IP address as 99.9.9.9.9 - that's one dot too many. Is this the address you'e actually using?
I don't think CCSID comes into it all at this stage - we're just trying to get the connection up, sending a message comes later!  |
|
| Back to top |
|
|
|
|
