activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dejan Bosanac <de...@nighttale.net>
Subject Re: Persisting Queues when passed through Mule
Date Mon, 07 Dec 2009 08:30:45 GMT
Hi,

It seems everything is fine here. Topics you're seeing are for
advisory messages (http://activemq.apache.org/advisory-message.html).
Also these debug messages you're seeing are journal related and shows
how messages are added/removed from the journal, nothing wrong here as
well.

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net



On Fri, Dec 4, 2009 at 3:03 PM, eric tice <eric.tice@lifeway.com> wrote:
>
> I am using Mule and ActiveMQ together.  ActiveMQ version 5.2.0.  I am
> noticing something I don't get in the logs.  I set the config in
> activemq.xml to persistent=true at the broker level and created a
> destination of type queue.  I set to journal persistance and I see in the
> console that my message is received and it is being picked up by the
> consumer, but it also appears to be removed (See Below).  The console would
> also lead me to believe that active mq is treating my queue as a topic.  I
> would appreciate any help/clarification:
>
> - Adding destination: topic://ActiveMQ.Advisory.Producer.Queue.b2bqueue
> DEBUG AbstractRegion                 - Adding destination:
> temp-queue://ID:FA2275059.local-64357-1259934819940-0:0:1
> DEBUG AbstractRegion                 - Adding destination:
> topic://ActiveMQ.Advisory.TempQueue
> DEBUG AMQMessageStore                - Journalled message add for:
> ID:FA2275059.local-64357-1259934819940-0:0:1:1:1, at: offset = 19525, file =
> 1, size = 1327, type = 1
> DEBUG AMQMessageStore                - Doing batch update... adding: 1
> removing: 0
> DEBUG AMQMessageStore                - Batch update done.
> DEBUG AbstractRegion                 - Adding consumer:
> ID:FA2275059.local-64357-1259934819940-0:0:1:1
> DEBUG AbstractRegion                 - Adding destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:FA2275059.local-64357-1259934819940-0:0:1
> DEBUG InactivityMonitor              - 10001 ms elapsed since last write
> check.
> DEBUG InactivityMonitor              - 9998 ms elapsed since last write
> check.
> DEBUG AbstractRegion                 - Removing consumer:
> ID:FA2275059.local-64357-1259934819940-0:0:1:1
> DEBUG AbstractRegion                 - Removing destination:
> temp-queue://ID:FA2275059.local-64357-1259934819940-0:0:1
> DEBUG AbstractRegion                 - Removing destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.ID:FA2275059.local-64357-1259934819940-0:0:1
>
> --
> View this message in context: http://old.nabble.com/Persisting-Queues-when-passed-through-Mule-tp26635892p26635892.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

Mime
View raw message