You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Lionel Cons (JIRA)" <ji...@apache.org> on 2013/03/25 09:27:17 UTC

[jira] [Commented] (APLO-284) Invalid log position warnings

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

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

FWIW, I have upgraded to apollo-99-trunk-20130322.033735-216 and the problem is still present:
 - the broker logs "detected store dropped message"
 - for one dsub, the broker does not send messages although there is a consumer waiting for them
 - the dsub does have a registered consumer (consumer_count=1)
 - the consumer connection does exist but it has (waiting_on='client request'), looking at the write_counter, Apollo just sends heart-beats (i.e. single bytes)
 - after restarting the consumer, some messages get sent (the most recent ones) but others stay in the dsub (queue_items'=25507 and this does not decrease)
                
> 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