activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lionel Cons (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APLO-284) Invalid log position warnings
Date Mon, 04 Feb 2013 13:54:12 GMT

    [ https://issues.apache.org/jira/browse/APLO-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570168#comment-13570168
] 

Lionel Cons commented on APLO-284:
----------------------------------

When the problem happened, the subscription was permanently in "waiting on: dispatch" state.

Here is the config we use:

    <queue auto_delete_after="604800" dlq="dlq.queue.*"/>
    <topic auto_delete_after="604800" slow_consumer_policy="queue">
      <subscription dlq="dlq.topic.*"/>
    </topic>
    <dsub auto_delete_after="604800" dlq="dlq.dsub.*"/>

The messages are quite small (~ 1k body + headers) and they come at a rate of few messages
per second (aggregated from 22 clients).

The problem occurred several in the same scenario:
 - the consumers got disconnected (external reason)
 - messages pile up in the dsubs
 - consumers come back

Usually, the consumer with a selector is fine while the other (on the same topic but without
selector) gets nothing. Restarting that consumer is usually enough to make it work. Maybe
this is a timing issue when both consumers start roughly at the same time?

                
> Invalid log position warnings
> -----------------------------
>
>                 Key: APLO-284
>                 URL: https://issues.apache.org/jira/browse/APLO-284
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>         Environment: apollo-99-trunk-20121221.031630-148
>            Reporter: Lionel Cons
>
> I don't know if this is related to APLO-176 but on a broker running apollo-99-trunk-20121221.031630-148
we see many (>1k) warnings like:
> 2013-01-07 10:02:55,941 | WARN  | Invalid log position: 122526748304 | 
> 2013-01-07 10:02:55,941 | WARN  | Invalid log position: 122526748923 | 
> 2013-01-07 10:02:55,942 | WARN  | Invalid log position: 122526750644 | 
> 2013-01-07 10:02:55,942 | WARN  | Invalid log position: 122526751727 | 
> 2013-01-07 10:02:55,942 | WARN  | Invalid log position: 122526752423 | 
> Does this indicate some kind of data store corruption?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message