| Author |
Message
|
| rajak |
 Posted: Thu Jul 20, 2006 1:20 am Post subject: amqsputc is hanging and giving 2059 error after some time |
 |
|
Newbie
Joined: 18 Jul 2006
Posts: 8
|
Hi,
The QM Is in Linux and client is windows.
I am trying to connect through MQSERVER as env variable.
AMQSPUTC hangs and after some time it gives 2059 error.
Can somebody help me on this.
The error msg in Event viewer is
"
Event Type: Error
Event Source: WebSphere MQ
Event Category: None
Event ID: 9213
Date: 7/20/2006
Time: 2:03:15 PM
User: N/A
Computer: INDAS3IBM427
Description:
A communications error for TCP/IP occurred.
An unexpected error occurred in communications.
The return code from the TCP/IP(recv) [TIMEOUT] 180 seconds call was 0 (X'0'). Record these values and tell the systems administrator. "  |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Jul 20, 2006 1:31 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Have a search through this forum for 2059 - it is the most popular reason code! 
Have you ever got this to work? If not are you certain that the MQSERVER elements are spelt correctly (obvious I know but you'd be amazed how many times I've seen a duff channel name - or perhaps you wouldn't...). Also are you certain there's no firewall between client and server, and if there is that the relevant ports are open? Are you using DNS names or IP addresses? If the former try the latter.
And of course, my personal favorite - are you sure the MQSERVER variable is in scope for amqsputc? (Yes, people do get that wrong. Hard to believe but true. I was one of them once....  )
If it works and then doesn't what changes? Can you pin down a pattern?
Do the search. Everybody's had this problem at one time or another and most of them have posted 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rajak |
| Posted: Thu Jul 20, 2006 3:10 am Post subject: |
|
|
Newbie
Joined: 18 Jul 2006
Posts: 8
|
This is the environment variable i have set,.
MQSERVER=SYSTEM.AUTO.SVRCONN/TCP/10.128.33.168(1480)
Ya i am able to connect and use amqsputc in a AIX MQ, but i am unable to do it in Linux. I even done a full search and done most of the things said in the discussion, but it didnt help me.
There is no firewall, i can able to ping and telnet to the MQ Server from Client. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 20, 2006 3:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I notice you have another thread running about a Linux listener - is that the same queue manager? If it is, the listener in that thread is defined to use 1460 not 1480 as shown above!
Are there any log messages or FDCs that seem associated with the connection attempt (i.e. about the same time)?
Try defining your own SVRCONN; I never entirely trust the automatic objects. Also try a telnet to the port; if something answers but telnet goes over the listener's correctly attached to that port. If you get something like "Connection Refused" the listener's not working.
2059 is not only the most common reason code, it's the hardest to pin down. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rajak |
| Posted: Thu Jul 20, 2006 4:19 am Post subject: |
|
|
Newbie
Joined: 18 Jul 2006
Posts: 8
|
Hi,
That is a different Q manager.
And i found this error in /var/mqm/errors directory.
07/20/2006 05:20:07 PM
AMQ9213: A communications error for bind occurred.
EXPLANATION:
An unexpected error occurred in communications.
ACTION:
The return code from the bind(/tmp/MQSeries.3662) call was 13 (X'D'). Record
these values and tell the systems administrator.
And also i am not sure, whether my two threads depends and one is the cause of other?
Thanks.. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 20, 2006 4:30 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rajak wrote: |
That is a different Q manager.
|
Felt it was worth posing the question (not the first time I've seen a confused port number)... 
So you've got two queue managers, one that throws 2059 when you try and connect to it, both complaining about TCP/IP bind errors? As you say, if it's a coincidence it's an odd one! 
If you shut down one of them (including the listener object) does the bind problem go away? Also does the other queue manager exhibit a 2059 on connect?
(And did you try a new SVRCONN channel? It's looking increasingly like a long shot but still worth a spin IMHO).
Also worth investigating what the return code means....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
