Tim, I'm not sure if the Java application ever gets the exception, but if it is, then it's reconnecting quickly.
I don't think my application can really control which port it is getting moved to, that would be decided after I connect to the server on 61616 and we negotiate to a new port. Are there any transport connector options on the client or server that could help me here? Thanks, Jeffrey Tim Bain wrote > Do you ever get the channel inactivity exception in the Java client? If > so, does it reconnect gracefully? > > Those error messages make it sound like the TCP connection is being reused > instead of starting a fresh one. Is there any chance you're reusing the > same ephemeral port, where the server wouldn't be able to tell that it > wasn't simply additional data on the old connection? > > Tim -- View this message in context: http://activemq.2283324.n4.nabble.com/unable-to-reconnect-after-exception-Channel-was-inactive-for-too-long-tp4697843p4697923.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
