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 Fri, 08 Feb 2013 07:23:12 GMT

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

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

FWIW, I have upgraded to apollo-99-trunk-20130208.033447-187 and the problem is still present.
After restart:
 - the broker logs "detected store dropped message"
 - for one dsub, the broker does not send messages although there is a consumer waiting for
them
 - after restarting the consumer, some messages get sent (the most recent ones) but others
stay in the dsub

Here is what the console reports:

swapped in: 0 messages 0 bytes
swapped out: 25,507 messages 390.264 mb
percent swapped out: 100.00 % of the messages
swapping out: 0 bytes
swapping in: 0 bytes
total swap outs : 4,905 messages (8.106 mb)
total swap ins : 3,720 messages (7.003 mb)

Strangely, "total swap outs" is lower than "swapped out".

We can also see "queue size: 25,507 messages 390.264 mb" and clicking on "Entries Dump (Show)"
shows:

State   Size        consumers, prefetched  position:count
head    0 bytes   0, false                         0:0
tail       0 bytes   1, false                         2,864,262:0
                
> 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