I tried to be smart about the connection by waiting on the thread that is
establishing the connection to simulate the synchronous nature that I wanted
but this didn't work. It appears that the bundle establishing the connection
needs to exit out of the activation in order for the connection to wor
Establishing the connection in another thread does appear to alleviate the
problems. This is a little disconcerting though. It might be worth someone
with a debug build investigating the problems that are occuring as this puts
doubt on the robustness of the connections and failover within an OSGi
We also encountered this if the start method was called directly in the
activator. It seems that the connection/session thread of ActiveMQ conflicts
with the OSGi classloader (we saw some hint in the error log). We know call
start() in a Job (org.eclipse.core.runtime.jobs.Job) which is executed
as
