| Author |
Message
|
| rammer |
 Posted: Mon Nov 18, 2013 8:04 am Post subject: |
 |
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
I think its worth trying a few variants.
127.0.0.1
Localhost
DNS |
|
| Back to top |
|
 |
| shilpa.sabade |
| Posted: Mon Nov 18, 2013 8:18 am Post subject: |
|
|
Voyager
Joined: 23 Feb 2011
Posts: 76
|
| rammer wrote: |
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 |
We do not have amqsputc utility , but i tried RfhUtilc with same server connection channel , am able put and get messages from queue. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Nov 18, 2013 8:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shilpa.sabade wrote: |
| We do not have amqsputc utility |
Yes you do - it's a sample that comes with the product.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rammer |
| Posted: Mon Nov 18, 2013 8:20 am Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
[quote="shilpa.sabade"]
| rammer wrote: |
We do not have amqsputc utility , but i tried RfhUtilc with same server connection channel , am able put and get messages from queue. |
Does rfhutilc run on the same server that the client you are having an issue with runs from? |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Nov 18, 2013 8:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
[quote="rammer"]
| shilpa.sabade wrote: |
| rammer wrote: |
We do not have amqsputc utility , but i tried RfhUtilc with same server connection channel , am able put and get messages from queue. |
Does rfhutilc run on the same server that the client you are having an issue with runs from? |
And in the same command shell?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shilpa.sabade |
| Posted: Mon Nov 18, 2013 8:23 am Post subject: |
|
|
Voyager
Joined: 23 Feb 2011
Posts: 76
|
| Vitor wrote: |
| shilpa.sabade wrote: |
| We do not have amqsputc utility |
Yes you do - it's a sample that comes with the product. |
We have not installed Samples fileset . |
|
| Back to top |
|
|
| shilpa.sabade |
| Posted: Mon Nov 18, 2013 8:39 am Post subject: |
|
|
Voyager
Joined: 23 Feb 2011
Posts: 76
|
[quote="rammer"]
| shilpa.sabade wrote: |
| rammer wrote: |
We do not have amqsputc utility , but i tried RfhUtilc with same server connection channel , am able put and get messages from queue. |
Does rfhutilc run on the same server that the client you are having an issue with runs from? |
RFHUTIL - was on different windows server , but PUT was successful,
now , on same server ; imported amqsputc from test server "
$ export 'MQSERVER=CLIENT.AMQP1/tcp/x.x.x.x(1414)' ( replaced x.x.x.x with server IP)
$ amqsputc TEST AMQTMP
Sample AMQSPUT0 start
target queue is TEST
test
Sample AMQSPUT0 end
but Message did not make to queue. queue manager log shows :
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. |
|
| Back to top |
|
|
| shilpa.sabade |
| Posted: Mon Nov 18, 2013 8:59 am Post subject: |
|
|
Voyager
Joined: 23 Feb 2011
Posts: 76
|
| markt wrote: |
| LOCLADDR would probably force the client to use a particular network interface. |
LOCLADDR - attribute does not hold good for SVRCONN type channels right ? |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Mon Nov 18, 2013 9:00 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
Is it possible that you just haven't started the loopback adapter ?
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| shilpa.sabade |
| Posted: Mon Nov 18, 2013 9:18 am Post subject: |
|
|
Voyager
Joined: 23 Feb 2011
Posts: 76
|
| PaulClarke wrote: |
| Is it possible that you just haven't started the loopback adapter ? |
How do we check that please ?
my netstat command and ipconfig command do give outputs ... |
|
| Back to top |
|
|
| rammer |
| Posted: Mon Nov 18, 2013 9:57 am Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
I dont think I can offer any more help as it sounds netoworkie, however what is puzzling is that it will connct from another host but not from the MQ Server locally.
Telnet 127.0.0.1 1414 works? Would that prove loopback is ok Paul? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Nov 26, 2013 10:38 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
Any update on this?
_________________
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 |
|
|
| fjb_saper |
| Posted: Tue Nov 26, 2013 2:29 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY
|
| rammer wrote: |
I dont think I can offer any more help as it sounds netoworkie, however what is puzzling is that it will connct from another host but not from the MQ Server locally.
Telnet 127.0.0.1 1414 works? Would that prove loopback is ok Paul? |
No it may just prove that you do not have the channel auth record set for 127.0.0.1 which is why you can connect from a different host but not the localhost...
Did you check Morag's post about what to do when you have no access?
https://www.ibm.com/developerworks/mydeveloperworks/blogs/aimsupport/entry/blocked_by_chlauth_why?lang=en
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Tue Nov 26, 2013 3:33 pm Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
| Quote: |
| Telnet 127.0.0.1 1414 works? Would that prove loopback is ok Paul? |
Yes, if you can get telnet to connect with that then I think it would prove the adapter is up and functioning. Of course telnet itself won't work and more than likely you'll generate an FDC out of the listener at the back end but it would prove that the network is doing it's thing.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
|
|
