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.
