Author |
Message
|
shilpa.sabade |
Posted: Fri Nov 15, 2013 1:56 pm Post subject: SVRCONN channel shows incorrect 127.0.0.1 IP - |
|
|
Voyager
Joined: 23 Feb 2011 Posts: 76
|
Hi All ,
MQ 7.5 , AIX
I have a small MQ client connecting to MQ queue manager using a server connection channel.
MQSERVER variable is set to use server DNS .
ie MQSERVER = CLIENT.SVRCONN/TCP/XXXXXX(1414).
but ,
When i check channel status , it shows CONNAME(127.0.0.1) for channel and hence MQ client is not working .
Need your help to understand ,
why 127.0.0.1 ip is showing up.
I checked ifconfig file .. localhost resolves to 127.0.0.1 ..( for security reasons .. as per my server admin)
but , none of out MQ configurations use localhost ..
Thank you |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri Nov 15, 2013 2:34 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Moved to Configuration Support forum. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri Nov 15, 2013 2:39 pm Post subject: Re: SVRCONN channel shows incorrect 127.0.0.1 IP - |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
shilpa.sabade wrote: |
I have a small MQ client connecting to MQ queue manager using a server connection channel.
MQSERVER variable is set to use server DNS .
ie MQSERVER = CLIENT.SVRCONN/TCP/XXXXXX(1414).
but ,
When i check channel status , it shows CONNAME(127.0.0.1) for channel and hence MQ client is not working .
Need your help to understand ,
why 127.0.0.1 ip is showing up.
I checked ifconfig file .. localhost resolves to 127.0.0.1 ..( for security reasons .. as per my server admin)
but , none of out MQ configurations use localhost ..
Thank you |
Can you successfully tcpip ping from the client to the qmgr?
Try specifying the actual ipaddress(port) of the queue-manager to see if that works. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
PaulClarke |
Posted: Fri Nov 15, 2013 6:02 pm Post subject: |
|
|
 Grand Master
Joined: 17 Nov 2005 Posts: 1002 Location: New Zealand
|
I'm a bit confused about what you are saying. Are you saying:
1/ That the client and server are different boxes and regardless of what you specify in MQSERVER the client always connects to the local host (ie. it's own machine).
or
2/ That the client and server are different boxes. The client correctly connects to the server box but the channel status report, erroneously, that the connection is from 127.0.0.1.
or perhaps some other combination.
Cheers,
Paul. _________________ Paul Clarke
MQGem Software
www.mqgem.com |
|
Back to top |
|
 |
shilpa.sabade |
Posted: Fri Nov 15, 2013 7:06 pm Post subject: |
|
|
Voyager
Joined: 23 Feb 2011 Posts: 76
|
PaulClarke wrote: |
I'm a bit confused about what you are saying. Are you saying:
1/ That the client and server are different boxes and regardless of what you specify in MQSERVER the client always connects to the local host (ie. it's own machine).
or
2/ That the client and server are different boxes. The client correctly connects to the server box but the channel status report, erroneously, that the connection is from 127.0.0.1.
or perhaps some other combination.
Cheers,
Paul. |
Paul,
Client and Server are on same box .......and Client is not able to make connection to server queue manager , the time client attempts connection , channel status shows 127.0.0.1 |
|
Back to top |
|
 |
shilpa.sabade |
Posted: Fri Nov 15, 2013 7:08 pm Post subject: Re: SVRCONN channel shows incorrect 127.0.0.1 IP - |
|
|
Voyager
Joined: 23 Feb 2011 Posts: 76
|
bruce2359 wrote: |
shilpa.sabade wrote: |
I have a small MQ client connecting to MQ queue manager using a server connection channel.
MQSERVER variable is set to use server DNS .
ie MQSERVER = CLIENT.SVRCONN/TCP/XXXXXX(1414).
but ,
When i check channel status , it shows CONNAME(127.0.0.1) for channel and hence MQ client is not working .
Need your help to understand ,
why 127.0.0.1 ip is showing up.
I checked ifconfig file .. localhost resolves to 127.0.0.1 ..( for security reasons .. as per my server admin)
but , none of out MQ configurations use localhost ..
Thank you |
Can you successfully tcpip ping from the client to the qmgr?
Try specifying the actual ipaddress(port) of the queue-manager to see if that works. |
Client and Server are on same server .... so connectivity is not a issue.
tried with IP .. same results  |
|
Back to top |
|
 |
PaulClarke |
Posted: Sat Nov 16, 2013 12:41 am Post subject: |
|
|
 Grand Master
Joined: 17 Nov 2005 Posts: 1002 Location: New Zealand
|
So, what you're saying is that the TCP stack detects that the address you are trying to connect to is the same local server and, instead of actually making a 'normal' TCP network connection it uses the more efficient localhost stack.
I'm not entirely sure what your problem is, this seems to me like a good thing.
However, if you're not happy about it for some reason then what we're looking for is a TCP setting which will switch this behaviour off, is that right ? Seems to me that it might be a question that would be better answers on a TCP/IP forum.
Cheers,
Paul. _________________ Paul Clarke
MQGem Software
www.mqgem.com |
|
Back to top |
|
 |
fjb_saper |
Posted: Sat Nov 16, 2013 3:38 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Also you do not tell us what the failure is.
The /etc/hosts might force any connection that is local whether by ip or hostname to the localhost stack (127.0.0.1 or ::1)
Have you configured the channel auth records to allow 127.0.0.1 ?
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
rammer |
Posted: Sun Nov 17, 2013 8:12 am Post subject: |
|
|
Partisan
Joined: 02 May 2002 Posts: 359 Location: England
|
Does it connect if you change the connection to use 127.0.0.1 just for a test rather than DNS?
Also Channel Security is set?
Just thoughts |
|
Back to top |
|
 |
shilpa.sabade |
Posted: Mon Nov 18, 2013 6:53 am Post subject: |
|
|
Voyager
Joined: 23 Feb 2011 Posts: 76
|
fjb_saper wrote: |
Also you do not tell us what the failure is.
The /etc/hosts might force any connection that is local whether by ip or hostname to the localhost stack (127.0.0.1 or ::1)
Have you configured the channel auth records to allow 127.0.0.1 ?
Have fun  |
Failure Details :
When ever Client tries to connect to queue manager :
Below errors occur :
AMQ9202: Remote host 'loopback (127.0.0.1) (1414)' not available, retry later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'loopback
(127.0.0.1) (1414)' for channel CLIENT.AMQTMP was not successful. However the
error may be a transitory one and it may be possible to successfully allocate a
TCP/IP conversation later.
In some cases the remote host cannot be determined and so is shown as '????'.
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
79 (X'4F'). 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
'loopback (127.0.0.1) (1414)' was not running. If this is the case, perform
the relevant operations to start the TCP/IP listening program, and try again.
AMQ9209: Connection to host 'loopback (127.0.0.1)' for channel 'CLIENT.AMQP1'
closed.
EXPLANATION:
An error occurred receiving data from 'loopback (127.0.0.1)' over TCP/IP. The
connection to the remote host has unexpectedly terminated.
The channel name is 'CLIENT.AMQP1'; in some cases it cannot be determined and
so is shown as '????'.
AMQ9208: Error on receive from host loopback (127.0.0.1).
EXPLANATION:
An error occurred receiving data from loopback (127.0.0.1) over TCP/IP. This
may be due to a communications failure.
ACTION:
The return code from the TCP/IP read() call was 73 (X'49'). Record these values
and tell the systems administrator.
Last edited by shilpa.sabade on Mon Nov 18, 2013 7:23 am; edited 1 time in total |
|
Back to top |
|
 |
shilpa.sabade |
Posted: Mon Nov 18, 2013 7:15 am Post subject: |
|
|
Voyager
Joined: 23 Feb 2011 Posts: 76
|
fjb_saper wrote: |
Also you do not tell us what the failure is.
The /etc/hosts might force any connection that is local whether by ip or hostname to the localhost stack (127.0.0.1 or ::1)
Have you configured the channel auth records to allow 127.0.0.1 ?
Have fun  |
I checked /etc/hosts - we have no entry corresponding to localhost and there is a explicit entry mapping DNS to IP for the server am testing.
I have set ADDRESSMAP type CHLAUTH records for the channel am using , and do not see any auth errors in queue manager logs. |
|
Back to top |
|
 |
rammer |
Posted: Mon Nov 18, 2013 7:22 am Post subject: |
|
|
Partisan
Joined: 02 May 2002 Posts: 359 Location: England
|
Are you able to Telnet to the IP Address / Port successfully? Im presuming you can given that MQ is capturing a connection error although against local address |
|
Back to top |
|
 |
shilpa.sabade |
Posted: Mon Nov 18, 2013 7:26 am Post subject: |
|
|
Voyager
Joined: 23 Feb 2011 Posts: 76
|
rammer wrote: |
Are you able to Telnet to the IP Address / Port successfully? Im presuming you can given that MQ is capturing a connection error although against local address |
Just tried from a different server to the server am testing , TELNET and PING both show positive results. |
|
Back to top |
|
 |
rammer |
Posted: Mon Nov 18, 2013 7:41 am Post subject: |
|
|
Partisan
Joined: 02 May 2002 Posts: 359 Location: England
|
This is just another test.
On the MQ Server can you set a temporary environment variable for the SVRCONN and then use something like amqsputc to put to a test message? Lets see if we can try to rule it out being issue at network level outside of the server or not.
export 'MQSERVER=CLIENT.SVRCONN/tcp/x.x.x.x(1414)'
amqsputc TESTQUEUE |
|
Back to top |
|
 |
markt |
Posted: Mon Nov 18, 2013 8:02 am Post subject: |
|
|
 Knight
Joined: 14 May 2002 Posts: 508
|
LOCLADDR would probably force the client to use a particular network interface. |
|
Back to top |
|
 |
|