You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by tthrone <tt...@novell.com> on 2008/07/24 08:32:39 UTC

SIGPIPE when connection to local broker is broken

In activemq-cpp-2.1.3 your exception listener would get called when the
connection to your local broker went away, in activemq-cpp-2.2 your app gets
a signal SIGPIPE.

I'm assuming this is an apr_network_io limitation?  Is this a known issue?
Is there a work around?

Thanks,
Todd

-- 
View this message in context: http://www.nabble.com/SIGPIPE-when-connection-to-local-broker-is-broken-tp18626095p18626095.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: SIGPIPE when connection to local broker is broken

Posted by Timothy Bish <ta...@gmail.com>.

This is not a known issue, please open a Jira issue and provide some
info on what platform / OS / Compiler you are using.  Also any
information on how to reproduce the problem would be helpful.

Regards
Tim

On Wed, 2008-07-23 at 23:32 -0700, tthrone wrote:
> In activemq-cpp-2.1.3 your exception listener would get called when the
> connection to your local broker went away, in activemq-cpp-2.2 your app gets
> a signal SIGPIPE.
> 
> I'm assuming this is an apr_network_io limitation?  Is this a known issue?
> Is there a work around?
> 
> Thanks,
> Todd
>