Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <24098450.post@talk.nabble.com>
Date: Thu, 18 Jun 2009 12:13:15 -0700 (PDT)
From: mkeenan <keenan@p2sol.com>
To: users@activemq.apache.org
Subject: Re: led to mark the Journal:
 org.apache.activeio.journal.InvalidRecordLocationException
In-Reply-To: <22108427.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <22108427.post@talk.nabble.com>


rahul_k123 wrote:
> 
> The following is the exception in our production logs.
> 
> Feb 17, 2009 10:03:01 PM
> org.apache.activemq.store.journal.JournalPersistenceAdapter doCheckpoint
> SEVERE: Failed to mark the Journal:
> org.apache.activeio.journal.InvalidRecordLocationException: The location
> is less than the last mark.
> org.apache.activeio.journal.InvalidRecordLocationException: The location
> is less than the last mark.
>         at
> org.apache.activeio.journal.active.JournalImpl.setMark(JournalImpl.java:340)
> 
> I have mq server on one box and multiple consumers and producers on diff
> boxes.  We have 2 queues configured on this box.
> 
> This exception is happening like 20 times in a day not often and most of
> the messages are being successfull.
> 
> But i'm worried whether it might be a problem going further.
> 
> Any help is appreciated
> 

Background:

We are using ActiveMQ 5.2 on Ubuntu Server 8.04, all of the
producers/consumers are .NET using the ActiveMQ C# client and Spring.NET
messaging.

Unfortunately I don't have any answers for you, but I did want to mention we
also see this regularly in the logs and it does not seem to be having any
negative impact.  We can't afford to lose a single message so we have built
in several layers of external checks to verify that every message put on a
queue is eventually processed.  

I find the error message disconcerting but AFAIK we can ignore it as it does
not cause lost messages.  All messages are persistent/transactional, so
maybe this problem is being auto-corrected behind the scenes for us.

-- 
View this message in context: http://www.nabble.com/led-to-mark-the-Journal%3A-org.apache.activeio.journal.InvalidRecordLocationException-tp22108427p24098450.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.