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

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

The same broker now also logs:

2013-01-07 10:30:28,018 | WARN  | Queue 'xxx' detected store dropped message at seq: 1573226 | 
2013-01-07 10:30:28,018 | WARN  | Queue 'xxx' detected store dropped message at seq: 1573227 | 
2013-01-07 10:30:28,018 | WARN  | Queue 'xxx' detected store dropped message at seq: 1573228 | 
2013-01-07 10:30:28,018 | WARN  | Queue 'xxx' detected store dropped message at seq: 1573229 | 

FWIW, xxx is a durable subscription that has accumulated a lot of (>10M) messages and that is now being drained.
                
> 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