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.
