ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » tcp problem.urgent

Post new topic  Reply to topic Goto page 1, 2, 3  Next
 tcp problem.urgent « View previous topic :: View next topic » 
Author Message
jpeela
PostPosted: Fri Dec 01, 2006 2:10 am    Post subject: tcp problem.urgent Reply with quote

Centurion

Joined: 23 Jan 2006
Posts: 139

Hi all,

I have this problem occuring on one of the windows machine.we are sending messages from MQ5.3 on windows to MB 5.0 on windows.
The respective channel to the MB machine is going to retry mode regularly.Checked in the event logs the folllowing problem.
Quote:


Remote host '156.5.30.49 (1423)' not available, retry later.

The attempt to allocate a conversation using TCP/IP to host '156.5.30.49 (1423)' was not successful. However the error may be a transitory one and it may be possible to successfully allocate a TCP/IP conversation later.

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 10060 (X'274C'). 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 '156.5.30.49 (1423)' was not running. If this is the case, perform the relevant operations to start the TCP/IP listening program, and try again.



Found that this is a network issue showing that TCP Connect Failed with WSAETIMEDOUT .can some one suggest me some solution as this is an urgent issue.

awiting ur reply.
thanks in advance.
_________________
Jogi
Back to top
View user's profile Send private message AIM Address Yahoo Messenger
Gaya3
PostPosted: Fri Dec 01, 2006 2:12 am    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

Hi

Start listener,

The listener is not running in this host '156.5.30.49 (1423)'

it will work afterwards

Thanks and regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Dec 01, 2006 2:14 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Okay, so 10060 is "Connection timed out". Have you checked (as per the message) that the listening program at 156.5.30.49(1423) is running & there's nothing in the logs for it.

Also what is the channel's short retry & long retry set to?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Dec 01, 2006 2:15 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

And of course you've assured yourself there are no transatory network issues affecting connection.....?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
jpeela
PostPosted: Fri Dec 01, 2006 2:27 am    Post subject: Reply with quote

Centurion

Joined: 23 Jan 2006
Posts: 139

hi gayatri listener is runnning fine and other channels are already running on that port and able to get messages successfuly.
its not the problem with listener
_________________
Jogi
Back to top
View user's profile Send private message AIM Address Yahoo Messenger
Gaya3
PostPosted: Fri Dec 01, 2006 2:31 am    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

Hi

Hope your IP address is correct.

Please ping to that ip and find out whether its working.

Check if any fire wall is also set for that IP

Thanks and Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Dec 01, 2006 2:34 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Gaya3 wrote:

Please ping to that ip and find out whether its working



jpeela wrote:
other channels are already running on that port and able to get messages successfuly


That would imply the address is working fairly well. Or are you proposing that there's an intermittant firewall between the 2 affected machines?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Gaya3
PostPosted: Fri Dec 01, 2006 2:38 am    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

Hi

All other channels are using same port is it. (1423).

So there are lot of sockets opened in your channels.

Thanks and regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Dec 01, 2006 2:39 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Gaya3 wrote:
So there are lot of sockets opened in your channels.


Which means....?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Gaya3
PostPosted: Fri Dec 01, 2006 2:42 am    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

Hi

The Recvr's socket will be up and as well as running, so the sender is trying to communicate with recvr but recvr is rejecting 'coz the socket it up and running

Check the tcpip keep alive

Thanks and Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
jpeela
PostPosted: Fri Dec 01, 2006 2:44 am    Post subject: Reply with quote

Centurion

Joined: 23 Jan 2006
Posts: 139

hi vitor,

Quote:
Also what is the channel's short retry & long retry set to?


the short retry count is 10 and interval 60
long retry count is 999999999 and interval1200.

gayatry,


Quote:
Check if any fire wall is also set for that IP


there used to be a fire wall which is disabled now.

and we are able to ping the ip successfully
_________________
Jogi
Back to top
View user's profile Send private message AIM Address Yahoo Messenger
Vitor
PostPosted: Fri Dec 01, 2006 2:47 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Gaya3 wrote:
Hi

The Recvr's socket will be up and as well as running, so the sender is trying to communicate with recvr but recvr is rejecting 'coz the socket it up and running

Check the tcpip keep alive

Thanks and Regards
Gayathri


Wouldn't all this show up in the log at the receiving end? And where is this socket limit documented?

I ask because we have multiple senders to a single receiver all over the place & if there's a limit it's the sort of thing I need to know.....
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Dec 01, 2006 2:47 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

You might as well check the activity against the max number of channels on the receiving machine....
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
jpeela
PostPosted: Fri Dec 01, 2006 3:49 am    Post subject: Reply with quote

Centurion

Joined: 23 Jan 2006
Posts: 139

hi Saper,

We have KAINT set to auto and from services snap in there are know max channels and maxactive channels are blank.

here we have more than 100 sender aswell as receiver channels.on the MB machhine running on the same port.
any suggesions for how to resolve this.
_________________
Jogi
Back to top
View user's profile Send private message AIM Address Yahoo Messenger
jpeela
PostPosted: Fri Dec 01, 2006 3:59 am    Post subject: Reply with quote

Centurion

Joined: 23 Jan 2006
Posts: 139

hi all,

sorry to inform you people late but,

we are unable tyo ping the channel,which is saying that command server not responding AMQ4032.this was the issue previously when there was fire wall enabled.Later it worked fine when the firewall was disabled.
But now again we are having the same problem.Should this be because of some network issue or configuration issue.
I doubt this because there are other queumanagers which are able to send msgs but this is the only qmanager which is causing problems.
any help.

Thanks in advance.
_________________
Jogi
Back to top
View user's profile Send private message AIM Address Yahoo Messenger
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2, 3  Next Page 1 of 3

MQSeries.net Forum Index » General IBM MQ Support » tcp problem.urgent
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.