This is when the client is first forced to issue a request to the broker. Are you sure your broker is up? If you are using failover and the broker is down, it will make this call block.
On Fri, Aug 8, 2008 at 10:26 AM, sub3 <[EMAIL PROTECTED]> wrote: > > Hi, > Occasionally, my system locks up (7/31 Snapshot). I've poured though the > logs and can't find any reason for the stoppage. > If I restart a component, it gets locked when it executes > 'connection.setClientID(clientId)'. > > Can any give me any insight as to what ActiveMQ does here? I.e. is it > waiting for a status from some other component, or just trying to determine > uniqueness? > > Thanks for your help. > -- > View this message in context: > http://www.nabble.com/Debugging-a-locked-state-tp18892780p18892780.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
