activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APLO-284) Invalid log position warnings
Date Sat, 02 Feb 2013 14:08:12 GMT

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

Hiram Chirino commented on APLO-284:
------------------------------------

FYI: the  "waiting on: dispatch" message means that there is a message loaded in memory ready
to be sent to the consumer and the consumer should be able to accept it.  Typically a message
should not stay in that state very long, since when messages go into that state, they should
trigger the 'dispatching' process which basically picks the best possible consumers for the
given message, and actually sends it.

I'll try to setup a scenario like you described.  multiple producers sending to one topic
with 2 durables subs each sub with just one consumer.  Are you using a default queue/topic
configuration for that topic/dsub ?  About how big are the messages and what's the send frequency?
 
                
> 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