If you decide to try rebuilding the KahaDB index without the corrupted
file(s), https://access.redhat.com/solutions/276323 gives steps for doing
that. I'd highly recommend you back up the KahaDB data directory and that
you try the process in a development broker using a copy of the data files.
Not
Hi Tim
Maybe you have a process that remove or compress kahadb journal log files
(something like logrotate for instance ) ?
Regards
JB
> Le 23 nov. 2021 à 14:10, TRULIS Timothy (Tim) a
> écrit :
>
> Hello all,
>
> I am running KahaDB v6 w/ ActiveMQ v5.15.12 in Docker container with mapped
Hello all,
I am running KahaDB v6 w/ ActiveMQ v5.15.12 in Docker container with mapped
data/conf volumes to host.
Starting the container, I receive the following errors.
ERROR | [0:ActiveMQ.DLQ] references corrupt locations
ERROR | Failed to start Apache ActiveMQ (localhost, null)
java.io.IOExc
Hi,
Yes !! The broker process was still running. I verified it with "ps"
command.
I have updated the JIRA with details as you mentioned in last update.
Thanks,
Anuj
--
View this message in context:
http://activemq.2283324.n4.nabble.com/kahadb-corruption-Checkpoint-fail
delwalanuj"
wrote:
> Hi,
>
> Master was not completely killed. Master has stopped it's transport
> connectors and plugins but it didn't release it's lock from the kahadb.
>
> Thanks,
> Anuj
>
>
>
> --
> View this message in context:
&g
Hi,
Master was not completely killed. Master has stopped it's transport
connectors and plugins but it didn't release it's lock from the kahadb.
Thanks,
Anuj
--
View this message in context:
http://activemq.2283324.n4.nabble.com/kahadb-corruption-Checkpoint-failed-java-io-IO
?
>
> Thanks,
> Anuj
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/kahadb-corruption-Checkpoint-failed-java-io-IOException-Input-output-error-tp4690378p4690470.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
-5540
To handle this can ActiveMQ provide a configuration in
http://activemq.apache.org/configurable-ioexception-handling.html which can
kill the master completely and let the failover take over ?
Thanks,
Anuj
--
View this message in context:
http://activemq.2283324.n4.nabble.com/kahadb
this problem.
On Jan 26, 2015 11:24 PM, "khandelwalanuj"
wrote:
> Did anyone get a chance to look at this ?
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/kahadb-corruption-Checkpoint-failed-java-io-IOException-Input-output-error-t
Did anyone get a chance to look at this ?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/kahadb-corruption-Checkpoint-failed-java-io-IOException-Input-output-error-tp4690378p4690442.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Attaching the complete stack trace for more details.
ActiveMQ_prod_25_Jan.txt
<http://activemq.2283324.n4.nabble.com/file/n4690379/ActiveMQ_prod_25_Jan.txt>
--
View this message in context:
http://activemq.2283324.n4.nabble.com/kahadb-corruption-Checkpoint-failed-java-io-IOException
ase.java:1481)
at
org.apache.activemq.store.kahadb.MessageDatabase.checkpointCleanup(MessageDatabase.java:929)
at
org.apache.activemq.store.kahadb.MessageDatabase$3.run(MessageDatabase.java:353)
/
Thanks,
Anuj
--
View this message in context:
http://activemq.2283324.n4.nabble.com/kahadb-corruption-Checkpoint-failed-java-io-IOExc
data will need to be identify and resent to the ActiveMQ appropriate
queue.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/KahaDB-corruption-tp3321382p4668099.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
lution is something I'm comfortable with at all. If I
> was ok with losing messages, I'd rather make my broker non-persistent and
> forget about this whole issue.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/KahaDB-corr
ething I'm comfortable with at all. If I
was ok with losing messages, I'd rather make my broker non-persistent and
forget about this whole issue.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/KahaDB-corruption-tp3321382p4668100.html
Sent from the ActiveMQ
(AbstractStoreCursor.java:277)
... 7 more
This is my kahadb configuration:
--
View this message in context:
http://activemq.2283324.n4.nabble.com/KahaDB-corruption-tp3321382p4656773.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
l operation the queues should be empty for our application so
>>> that was not an issue for me.
>>>
>>> Thanks
>>> Joe
>>>
>>> On 23 February 2011 18:06, Gary Tully <gary.tu...@gmail.com> wrote:
>>>> 5.4.2 is better w.r.t abortive shutdown, but for this case, rebuilding
>>>> the index should work.
>>>> remove kahadb/db.data and restart, it will parse the journal to
>>>> rebuild the index.
>>>>
>>>
>>
>>
>> --
>> View this message in context:
>> http://activemq.2283324.n4.nabble.com/KahaDB-corruption-tp3321382p3695392.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
>
>
> --
> http://fusesource.com
> http://blog.garytully.com
>
<gary.tu...@gmail.com> wrote:
>>> 5.4.2 is better w.r.t abortive shutdown, but for this case, rebuilding
>>> the index should work.
>>> remove kahadb/db.data and restart, it will parse the journal to
>>> rebuild the index.
>>>
>>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/KahaDB-corruption-tp3321382p3695392.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
http://fusesource.com
http://blog.garytully.com
move kahadb/db.data and restart, it will parse the journal to
>> rebuild the index.
>>
>
--
View this message in context:
http://activemq.2283324.n4.nabble.com/KahaDB-corruption-tp3321382p3695392.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
That's great. Cheers James.
Ozan
-Original Message-
From: James Green [mailto:james.mk.gr...@gmail.com]
Sent: 10 June 2011 09:21
To: users@activemq.apache.org
Subject: Re: Kahadb Corruption Scenarios
http://fusesource.com/docs/broker/5.4/persistence/KahaDB-Recovery.html
Don
http://fusesource.com/docs/broker/5.4/persistence/KahaDB-Recovery.html
Don't forget there are hardware-level performance improvements from the
operating system down to the disks which may affect reliability.
James
On 8 June 2011 16:53, Ozan Seymen wrote:
> Hi all,
>
> Can you please explain th
Hi all,
Can you please explain the scenarios where we might have AMQ message storage
(kahadb) corrupted in a way that it is not recoverable?
In the solution I am working on, I simply cannot afford to lose any messages.
In order to secure this, I will:
* Rely on transactions on the pub
I've upgraded to 5.4.2 and will let you know how it goes.
I didn't rebuild the index as I've already restarted the process.
In normal operation the queues should be empty for our application so
that was not an issue for me.
Thanks
Joe
On 23 February 2011 18:06, Gary Tully wrote:
> 5.4.2 is bette
My experience with rebuilding the kahadb index after a crash (AMQ 5.3.0) is
that it can take hours, even for a modest (< 100 MB) message store. Has this
improved in 5.4.x?
Joe Niski
IS Development | NWEA
PHONE 503.548.5207 | FAX 503.639.7873
NWEA.ORG<3D%22http://www.nwea.org/%22> | Partne
5.4.2 is better w.r.t abortive shutdown, but for this case, rebuilding
the index should work.
remove kahadb/db.data and restart, it will parse the journal to
rebuild the index.
On 23 February 2011 17:11, Joe Carter wrote:
> When using ActiveMQ 5.4.0 I can get KahaDB corruption that
When using ActiveMQ 5.4.0 I can get KahaDB corruption that is unrecoverable.
This is after a hard crash (unrelated kernel panic).
This prevents the server restarting and my only workaround is to
remove (or rename) the KahaDB directory.
I've enabled ignoreMissingJournalfile
26 matches
Mail list logo
