Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <18804433.post@talk.nabble.com>
Date: Sun, 3 Aug 2008 18:41:33 -0700 (PDT)
From: beyond005 <beyond005@gmail.com>
To: users@activemq.apache.org
Subject: How to deal with blocked transport
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


There are some comments about blocked transport in slow consumer topic:

when using TCP there can be occasions when a network outage can result in a
blocked write. This can cause the entire broker to freeze - and the socket
may never be unblocked. Currently we have a Thread that checks for blocked
sockets - using a sweep protocol to detect if there are connections that are
blocked writing for more than a configurable period. This can work but there
is no way to unblock the calling thread that is associated with the send
down the socket (which will be the publishing thread in non-durable topics).

Could anybody give a feasible way to resolve this problem in a product
environment. Currently we just can reboot the whole activemq to restart the
socket.

BTW, we are using 4.1.1 version of activemq in our environment. Could I
assume that activemq 5.1 has beat it?
-- 
View this message in context: http://www.nabble.com/How-to-deal-with-blocked-transport-tp18804433p18804433.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.