| Author |
Message
|
| mqsi |
 Posted: Wed Jul 27, 2005 11:36 pm Post subject: SDR-RCVR Channels not coming up |
 |
|
Apprentice
Joined: 11 Jun 2004
Posts: 33
|
Hi -
I am configuring QM (MQ 5.3) on a new solaris svr. I am trying to connect to remote MQ servers on os/390 and Windows2000. Created SDR-RCVR channels properly and when SDR chl is started, the chl is not connecting to the remote svr and status is in BINDING mode only instead of RUNNING.
MQ on the old solaris svr is working fine and is connected properly to os/390 and Windows2000. Verified the listerner ports on target servers and they are fine. Couldn't identify what the reason would be.
SDR Chl running on old solaris svr is able to connect to the host efd1. Is it something to do with network which is hindering the connectivity to external servers. See the mq error log below
********
The attempt to allocate a conversation using TCP/IP to host 'efd1
(xxxx)' 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
145 (X'91'). 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
'efd1 (xxxx)' was not running. If this is the case, perform
the relevant operations to start the TCP/IP listening program, and try again.
*******
someone pls help me out... |
|
| Back to top |
|
 |
| csmith28 |
| Posted: Thu Jul 28, 2005 2:26 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
have you confirmed the IP or DNS names of the servers that you are trying to connect to?
Are said servers configured to listen for MQ Connection on port 1414 or some other port?
The list possible problems goes on and on but these are things I would check first.
If the efd1 entity is confirmed to be up the error you quoted indicates that there is some kind of network problem.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| mqsi |
| Posted: Thu Jul 28, 2005 3:23 am Post subject: |
|
|
Apprentice
Joined: 11 Jun 2004
Posts: 33
|
DNS Name is properly configured to point to efd1
target host efd1 is listening on its port and is available for external servers.
From different solaris svr we are able to connect to efd1 (os/390) mq server.
Anothehr point is that, the new solaris servers are clustered appservers.
Not sure if the clustered appserver environment needs different configuration from MQ perspective. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jul 28, 2005 3:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| mqsi wrote: |
| Not sure if the clustered appserver environment needs different configuration from MQ perspective. |
They don't.
Assuming that you mean "WebSphere Application Server" by "appserver" and "Clustered under Deployment Manager" by "clustered".
If, however, you mean "JBoss" (or something else) by "appserver" and you mean "behind a network load balancer" by "clustered", then that's something else entirely, and you should be more specific.
The error indicates network problems. Look at the network configuration.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqsi |
| Posted: Thu Jul 28, 2005 4:25 am Post subject: |
|
|
Apprentice
Joined: 11 Jun 2004
Posts: 33
|
it is WebSphere Application Server clustering under Deployment Manager only.
But, the MQ connectivity issue from chl perspective has nothing to do with deployment manager.. yes?
Telnet connection is not established from solaris svr to efd1 host & port.
telnet efd1 port_num is not connecting to efd1.
Can someone confirm if this could be a port issue in the solaris svr or in efd1
thanks |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jul 28, 2005 4:29 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| mqsi wrote: |
it is WebSphere Application Server clustering under Deployment Manager only.
But, the MQ connectivity issue from chl perspective has nothing to do with deployment manager.. yes? |
Yes.
| mqsi wrote: |
Telnet connection is not established from solaris svr to efd1 host & port.
telnet efd1 port_num is not connecting to efd1.
Can someone confirm if this could be a port issue in the solaris svr or in efd1
thanks |
Yes. It's a network issue.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Anirud |
| Posted: Thu Jul 28, 2005 7:48 am Post subject: |
|
|
Master
Joined: 12 Feb 2004
Posts: 285
Location: Vermont
|
| mqsi wrote: |
Telnet connection is not established from solaris svr to efd1 host & port.
telnet efd1 port_num is not connecting to efd1. |
Any firewall in between the Solaris server and efd1?
In that case, you will have to add the Solaris server in the known servers list of the firewall rules.
Hope this helps. |
|
| Back to top |
|
|
|
|
