[ https://issues.apache.org/jira/browse/APLO-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568546#comment-13568546
]
Lionel Cons commented on APLO-284:
----------------------------------
I have just restarted the consumer that was not getting its messages. It is now getting _some_
messages (the new ones it seems).
The web console now shows:
queue size: 24,631 messages [this is constant, these messages seem stuck in the broker]
enqueued: 31,124 messages [this is growing]
dequeued: 6,493 messages [this is growing too]
dispatched: 6,493 messages [so the consumer got all dequeued - good]
waiting on: producer
It seems these 24,631 messages will stay on the broker forever :-(
FWIW, I do see more "store compaction" messages.
> 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
|