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 » Reasons for TCPIP Resets (RST) 461 10054

Post new topic  Reply to topic
 Reasons for TCPIP Resets (RST) 461 10054 « View previous topic :: View next topic » 
Author Message
PeterPotkay
PostPosted: Mon May 19, 2008 4:24 pm    Post subject: Reasons for TCPIP Resets (RST) 461 10054 Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

Came across this on the Tech Notes page on IBM's MQ Support page. Since these errors get asked about so often, I thought I'd post it here.

http://www-1.ibm.com/support/docview.wss?rs=171&context=SSFKSJ&dc=DB520&dc=DB560&uid=swg21305235&loc=en_US&cs=utf-8&lang=en

Quote:

Question
Why does TCPIP reset a connection?


Answer
Reasons for TCP/IP resets:

If a connection is un-orderly terminated, such as when a client box is recycled, TCP will reset the connection.

If an application requests a connect to a port and IP address on which no server is listening, TCP will send a reset.

If an application closes a socket with data still in the application receive buffer, the connection is reset to allow the remote partner to know that the data was not delivered.

If data arrives for a connection that has been closed the connection will be reset.

If an application closes a socket and sets the linger socket option to zero, TCP will reset the connection; as linger 0 instructs TCP not allow the connection to linger waiting for retransmitted packets.

If an invalid TCP segment arrives for a connection, for example, a bad acknowledge or sequence number can cause a reset.

When the connect request times out, TCP will stop trying to connect to a particular port and ip address and reset the connection.

A Firewall can reset connections if the packet does not adhere to the firewall rules and policies. For example a source or destination port or IP address does not match the firewall rule or policy.

When the retransmit timer expires, TCP will stop trying to retransmit a packet and reset the connection.

A bad hardware device can cause a TCP reset.

_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Reasons for TCPIP Resets (RST) 461 10054
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.