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: <19842686.post@talk.nabble.com>
Date: Mon, 6 Oct 2008 10:41:06 -0700 (PDT)
From: bears <nabble@mjberry.com>
To: users@activemq.apache.org
Subject: Re: AMQ 5.1 Broken Pipe
In-Reply-To: <19802726.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <19802726.post@talk.nabble.com>


spatel wrote:
> 
> I know there were some previous posts about broken pipe exceptions
> happening in 5.0.0, and this issue was supposed to be fixed in 5.1. I got
> this exception, and was wondering if anyone else has experienced this in
> 5.1 and their solution. 
> 

I was surprised to see this in 5.1, too.  Resetting the connection allows my
application to proceed, but I'm interested to know (1) if anyone has any
insight into the underlying cause and (2) if there's a better way of
handling the error condition.  

My setup involves a Java application sending JMS messages to an activemq
process running on the same machine.  The Java application also uses JDBC
and RMI connections to other processes on the same machine, but those seem
to be stable.  
-- 
View this message in context: http://www.nabble.com/AMQ-5.1-Broken-Pipe-tp19802726p19842686.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.