Hi, You maybe also want to give it a try for the *keepAlive* option as well [1] (set it to false, however there would be a performance-trade-off doing this here) and send your messages in chunks (sleep in between long enough so that all your open socket connections you've opened in each chunk-send are properly closed), so that instead of 15000 *at once* send them for example in 1000 block-loop. And if you run on Windows-Box then [2] should give you also some hints as well. Maybe also make use of the 'netstat' command to see how your TCP/IP connection states look like on your box.
[1] http://camel.apache.org/netty [2] http://kb2.adobe.com/cps/400/kb400700.html Babak -- View this message in context: http://camel.465427.n5.nabble.com/camel-netty-No-buffer-space-available-maximum-connections-reached-tp5088918p5089027.html Sent from the Camel - Users mailing list archive at Nabble.com.
