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 work. In
other words this doesn't work:
public void start (BundleContext context)
{
Thread t = new Thread(new Runnable()
{
public void run()
{
// [snip] Obtain connection
connection.start();
}
});
t.start();
t.join();
}
AFinnell wrote:
>
> 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 framework now.
>
> Stefan I appreciate your help.
>
--
View this message in context:
http://www.nabble.com/Will-pay-%24-to-fix-problem-with-connections-failing.-Simple-example-included.-tp22163371p22167311.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
