Because the errors occured on the ActiveMQ Connection, I guess activemq could be the main cause of that.
However it also has influence on the netty time out, servicemix and even runtime environments. In my test case, about 200 of data per a second are sent by the socket client and it is also critical part of this issue. After testing more concretely, I'll make a conclusion whether or not activemq has some problems. thanks -- View this message in context: http://activemq.2283324.n4.nabble.com/Interrupted-Exception-within-spring-JmsTemplate-tp2525340p2529362.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
