activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Shannon <christopher.l.shan...@gmail.com>
Subject Re: Ignoring sub command log messages
Date Tue, 10 Jan 2017 17:34:08 GMT
Did this happen while replaying the journal?  This message means that
an acknowledgement was processed in the journal that doesn't have a
matching message.  This log message would typically print out if you
were replaying the journal from the beginning to rebuild the index
because it's possible that the original journal files that contained
those messages have already been garbage collected but the journal
file that contains the acks hasn't been garbage collected yet.  If
this is the case then this is normal and nothing to worry about (which
is why it's a debug statement only)

On Tue, Jan 10, 2017 at 2:25 AM, xabhi <xabhi91@gmail.com> wrote:
> Hi,
>
> I saw below log messages in my ActiveMQ instance's logs. When does this
> happen and what effects can it have?
>
> [20170108 15:29:19.584 EST (main)
> org.apache.activemq.store.kahadb.MessageDatabase#updateIndex 1405 DEBUG] -
> no message sequence exists for id:
> ID:geneva13.nyc.43322-1482156880537-3:13196:1:1:3 and sub:
> gear-munshi-geneva.gear.sync.listener.GelbaseGenevaMessageListener
> [20170108 15:29:19.584 EST (main)
> org.apache.activemq.store.kahadb.MessageDatabase#updateIndex 1405 DEBUG] -
> no message sequence exists for id:
> ID:geneva13.nyc.43322-1482156880537-3:13196:1:1:4 and sub:
> gear-munshi-geneva.gear.sync.listener.GelbaseGenevaMessageListener
> [20170108 15:29:19.584 EST (main)
> org.apache.activemq.store.kahadb.MessageDatabase#updateIndex 1405 DEBUG] -
> no message sequence exists for id:
> ID:geneva13.nyc.43322-1482156880537-3:1:2:1:5946 and sub:
> gear-munshi-listener:geneva.gear.sync.listener.GelbaseGenevaMessageListener
> [20170108 15:29:19.585 EST (main)
> org.apache.activemq.store.kahadb.MessageDatabase#process 1047 DEBUG] -
> ignoring add sub command during recovery replay:destination {
>   type: TOPIC
>   name: geneva.loader.messageTopic
> }
> subscriptionKey:
> gear-munshi-listener:geneva.gear.sync.listener.GelbaseGenevaMessageListener
> retroactive: false
> subscriptionInfo: org.apache.activemq.protobuf.Buffer@ffffffc5
>
> [20170108 15:29:19.585 EST (main)
> org.apache.activemq.store.kahadb.MessageDatabase#process 1047 DEBUG] -
> ignoring add sub command during recovery replay:destination {
>   type: TOPIC
>   name: gear.tdpBundleCompletionTopic
> }
> subscriptionKey:
> post-tdp-bundle-listener:geneva.gear.sync.listener.PostTdpMessageListener
> retroactive: false
> subscriptionInfo: org.apache.activemq.protobuf.Buffer@ffffffea
>
>
> Thanks,
> Abhi
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Ignoring-sub-command-log-messages-tp4720928.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message