[
https://issues.apache.org/jira/browse/APLO-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652906#comment-13652906
]
Hiram Chirino commented on APLO-284:
------------------------------------
Ok. I think I've found the reason the 'Invalid log position' warnings were
being generated.
It was being caused because log files there were referenced in by
recovery/replay records had been GCed before shutdown.
This could also lead to log files which did not get GCed after restart. Fix now
in trunk.
> 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
