activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bhole, Ulhas" <>
Subject FW: [celtix-dev] RE: [activemq-user] Strange blocking createDurableSubscriber() call in ActiveMQ 3.2
Date Tue, 14 Feb 2006 11:09:07 GMT

Hi all,

Does anyone know what may be wrong from the stack trace? I also seeing Broker startup failure
once in a while after the following problem with the stack trace attached because of the size
restricition. The only option I have here is to cleanup var directory and start over clean.

Any help is appriciated.


Ulhas Bhole.

-----Original Message-----
From:   Bhole, Ulhas
Sent:   Tue 07/02/2006 18:03
Subject:        [activemq-user] Strange blocking createDurableSubscriber() call in ActiveMQ


I am trying to use ActiveMQ 3.2 Durable Topic Subscrition in one of the ObjectWeb Celtix ESB
samples. I am working on Redhat Linux 9 but saw similar problem on Windows also. I am getting
problem using the durable subscription in a way that It is blocking on createDurableSubscriber()
The problem occures after some repeated shutdown and restart of JMS Broker and my Client/Server

I tried to reproduce the problem with the pure JMS client(producer) and server(receiver) but
was unable to produce it. However, once I get the problem with the my Celtix demo. my Pure
Server(receiver) which also would block in the same call with similar stack trace.

Here is a stack trace of the blocking call from Pure Server(receiver).

"JmsSessionDispatcher: 1" prio=1 tid=0x083f4380 nid=0x271a in Object.wait() [0xbe7ff000..0xbe7ff5dc]
        at java.lang.Object.wait(Native Method)
        - locked <0x659e0060> (a java.lang.Object)

"TcpTransportChannel: Socket[addr=localhost/,port=61616,localport=33917]" prio=1
tid=0x083b0340 nid=0x2717 runnable [0xbe9ff000..0xbe9ff75c]
        at Method)
        - locked <0x65ef9f38> (a

"Low Memory Detector" daemon prio=1 tid=0x080a50f0 nid=0x2714 runnable [0x00000000..0x00000000]

"CompilerThread0" daemon prio=1 tid=0x080a3c70 nid=0x2713 waiting on condition [0x00000000..0xbefff1c4]

"Signal Dispatcher" daemon prio=1 tid=0x080a2be0 nid=0x2712 waiting on condition [0x00000000..0x00000000]

"Finalizer" daemon prio=1 tid=0x0809bf38 nid=0x2711 in Object.wait() [0xbf3ff000..0xbf3ff4dc]
        at java.lang.Object.wait(Native Method)
        - waiting on <0x65e5ac20> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(
        - locked <0x65e5ac20> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(
        at java.lang.ref.Finalizer$

"Reference Handler" daemon prio=1 tid=0x0809b240 nid=0x2710 in Object.wait() [0xbf5ff000..0xbf5ff65c]
        at java.lang.Object.wait(Native Method)
        - waiting on <0x65e5aca0> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(
        at java.lang.ref.Reference$
        - locked <0x65e5aca0> (a java.lang.ref.Reference$Lock)

"main" prio=1 tid=0x0805bce0 nid=0x270d in Object.wait() [0xbfffc000..0xbfffce78]
        at java.lang.Object.wait(Native Method)
        - waiting on <0x6598dde0> (a java.lang.Object)
        at org.activemq.message.ReceiptHolder.getReceipt(
        - locked <0x6598dde0> (a java.lang.Object)
        at org.activemq.transport.TransportChannelSupport.send(
        at org.activemq.ActiveMQConnection.syncSendPacket(
        at org.activemq.ActiveMQConnection.syncSendPacket(
        at org.activemq.ActiveMQSession.addConsumer(
        at org.activemq.ActiveMQMessageConsumer.<init>(
        at org.activemq.ActiveMQTopicSubscriber.<init>(
        at org.activemq.ActiveMQSession.createDurableSubscriber(
        at org.activemq.ActiveMQTopicSession.createDurableSubscriber(
        at DurableSubscriberServer.main(

"VM Thread" prio=1 tid=0x080967e0 nid=0x270f runnable

"VM Periodic Task Thread" prio=1 tid=0x080c7df8 nid=0x2715 waiting on condition

Can anyone help me in telling what the problem might be?

If required I have the state of the ActiveMQ Journal and Database on which this problem is
occuring. One more thing that I observed is after coming at this state If I Ctrl-C the JMS
Broker It shuts down TCP transport Adapter and hangs in Shutdown Hook.


Ulhas Bhole

View raw message