See if you can enable Java mission control and then use a threaded profile
of it in production. I’m REALLY happy with JMC. The license says you can
use it for development which I think is ok if you have a production box to
debug a problem and then disable it afterwards. Either way it’s very easy
t
Scratch that. Your real question is, "Why does does a Socket.connect() on
Windows wait the full timeout period when attempting to connect to a host
that's down, while on Linux it fails almost immediately." You can probably
find that out using the debugger; set a breakpoint client at
FailoverTrans
It sounds like you're seeing exponential backoff disabled in Linux; if
exponential backoff is in use then the delay will increase quickly from
10ms up to whatever max is set (see lines 1145-1151 of
http://grepcode.com/file/repo1.maven.org/maven2/org.apache.activemq/activemq-all/5.11.1/org/apache/ac
Here's what I understood your question to be; please tell me if I've
misunderstood. "My application throws a 'Connection Refused' exception
when it can't connect to my ActiveMQ broker if the broker is not running,
which crashes my application. I want my application to keep running even
if the Act
Here's a theory for what those threads are, though it doesn't explain why
they got created. Maybe every 5 minutes, something happens that requires
lots of threads. The thread pools create a bunch of new threads, the tasks
all end quickly, and then the threads sit around waiting for work (which is
