Feb 5th, 2008, 02:30 PM
DefaultMessageListenerContainer start call hangs
I have a client/server application, with separate client, server and shared spring configurations. In the JMS portion of these definitions, I have a org.springframework.jms.listener.DefaultMessageLis tenerContainer bean defined in the shared spring JMS definitions.
When I start the app in any other way (command-line), the app starts fine. However, when I start the application via JNLP, the shared DefaultMessageListenerContainer bean takes much longer to complete when its start() method is called. Any ideas?
No ports are blocked. And remember the app doesn't experience this pause when I start it sans WebStart.
Feb 20th, 2008, 03:48 PM
I dug into this a bit further (increased logging) and found that the jndi ldap Connection class has a call to "Set the clock daemon for the thread factory" in its static initializer.
So now my question is whether anyone knows how to eagerly trigger this.