I haven't used it, but isn't this exactly what NIO is supposed to fix? Try
having your clients connect via the nio transport and see if things improve.
Tim
On Oct 19, 2015 10:34 AM, "kal2" wrote:
> I tested with 1 connection with 10 threads and that was running fine.
> 1 connection with 15 or m
I tested with 1 connection with 10 threads and that was running fine.
1 connection with 15 or more threads seems to be an issue with reading from
TCP and servicing all the threads??
In our test we tried with 6 connections and we were able to just use 25
threads. For our app we needs to service 10
How many connections are in your connection pool?
On Oct 14, 2015 11:47 AM, "kal2" wrote:
> The FutureResponse becomes the bottleneck when we use more than 10 threads
> to
> send msgs out through connections.. We need to support large number of
> threads on producer side and they also send jms ms
