Okay good. Another thing I've noticed is that the problem does not happen when the broker is running on a Windows box, but two FC3 boxes exhibit the problem (one much more frequently than the other).
Any other suggestions? Is there any more logging I can turn on, at the app or OS level, that may expose the problem? Any network configuration that may be relevant? Is there any way to completely disable the InactivityIOException, short of compiling my own version to ignore it? Thanks, Kevin -- View this message in context: http://www.nabble.com/Channel-was-inactive-for-too-long-t1463069.html#a3971744 Sent from the ActiveMQ - User forum at Nabble.com.
