activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie McCrindle" <>
Subject Re: hung connecting to broker
Date Fri, 02 Jun 2006 10:22:09 GMT

It's happened and here's  a little more info:

> I wonder if you've hit this issue?

not sure. or at least, those aren't the symptoms I'm seeing. The
output from the broker is:

ACTIVEMQ_HOME: C:\Java\incubator-activemq-4.0\bin\..
Loading message broker from: xbean:activemq.xml
INFO  BrokerService                  - ActiveMQ 4.0 JMS Message Broker (localhos
t) is starting
INFO  BrokerService                  - For help or more information please see:
INFO  ManagementContext              - JMX consoles can connect to service:jmx:r
INFO  JDBCPersistenceAdapter         - Database driver recognized: [apache_derby
INFO  JournalPersistenceAdapter      - Journal Recovery Started from: Active Jou
rnal: using 5 x 20.0 Megs at: C:\Java\incubator-activemq-4.0\activemq-data\journ
INFO  JournalPersistenceAdapter      - Journal Recovered: 1 message(s) in transa
ctions recovered.
INFO  TransportServerThreadSupport   - Listening for connections at: tcp://SIM-J
WARN  MulticastDiscoveryAgent        - brokerName not set
INFO  TransportConnector             - Connector default Started
INFO  TransportServerThreadSupport   - Listening for connections at: tcp://SIM-J
INFO  TransportConnector             - Connector stomp Started
INFO  NetworkConnector               - Network Connector default Started
INFO  BrokerService                  - ActiveMQ JMS Message Broker (localhost, I
D:SIM-JamesM-2205-1149180591980-1:0) started
WARN  ManagedTransportConnection     - Failed to unregister mbean:

the stack dump is:

"main" prio=6 tid=0x000379d0 nid=0x93d0 in Object.wait() [0x0007e000..0x0007fc40
        at java.lang.Object.wait(Native Method)
        - waiting on <0x02b66278> (a
        at java.lang.Object.wait(
        - locked <0x02b66278> (a
        at org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatN
        at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.ja
        - locked <0x02b64098> (a java.lang.Object)
        at org.apache.activemq.transport.ResponseCorrelator.asyncRequest(Respons
        at org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorr
        at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnect
        at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(Activ
        - locked <0x02b602c0> (a org.apache.activemq.ActiveMQConnection)
        at org.apache.activemq.ActiveMQConnection.start(

I'm not setting a clientId but I'm not using a durable topic either (I
am using an Exclusive consumer, though).

Apologies if this isn't much to go on but I'm at a loss as to what is
happening. Will get source and start debugging soon, though, which
might give me a few more clues.


On 6/1/06, James Strachan <> wrote:
> On 6/1/06, Jamie McCrindle <> wrote:
> > Hi James,
> >
> > Thanks for the quick reply. To complicate things a little, I've
> > rewritten JmsTemplate to behave a little more like how I believe
> > ActiveMQ would prefer a JmsTemplate to behave, along with a whole
> > bunch of utility methods that JmsTemplate is missing. This could be
> > what's causing the issue and I wouldn't expect you guys to solve it.
> Cool.
> > I didn't see any broker errors but I'll keep a look out for next time
> > it happens. It seems to go away if I get rid of my activemq-data
> > directory.
> >
> > Once it's stuck, it always freezes trying to make an initial
> > connection to the broker, i.e. it hasn't had time to do anything too
> > smart (but it could be some kind of unclean shutdown that causes the
> > issue).
> I wonder if you've hit this issue?
> --
> James
> -------

View raw message