Re: failed to start ActiveMQ

OK, it sounds like I understood you correctly, then. Did you use the tools and techniques outlined in the wiki page I provided to determine which destination(s) contain the messages that are preventing the files from being deleted? Tim On Wed, Apr 4, 2018, 6:02 PM norinos

Re: failed to start ActiveMQ

Sorry, my information is not enough. I changed the ActiveMQ setting as follows, and restarted. - offlineDurableSubscriberTimeout="12" offlineDurableSubscriberTaskSchedule="18" - In this case, the

Re: failed to start ActiveMQ

Sorry, my information is not enough. I changed the ActiveMQ setting as follows, and restarted. - offlineDurableSubscriberTimeout="12" offlineDurableSubscriberTaskSchedule="18" - In this case, the

Re: failed to start ActiveMQ

I'm not understanding. Are you saying that after those durable subscriptions were deleted, there were no more unconsumed messages and so the journal files should have been deleted but were not? If I've understood correctly,

Re: failed to start ActiveMQ

I tried deleting db.data and db.redo files, and starting up ActiveMQ. This try succeeded.(ActiveMQ start successfuly, and recreated db.data and db.redo) But when the offline durable subscription cleanup is started, journal file could not be deleted. The following message was logged to the

Re: failed to start ActiveMQ

I've submitted https://issues.apache.org/jira/browse/AMQ-6938 to capture the fact that the broker failed to start due to the missing journal file, even though ignoreMissingJournalFiles was set to true. Please add any information to it that you think would be useful. I think the next workaround is

Re: failed to start ActiveMQ

> You need to set ignoreMissingJournalFiles. See > http://activemq.apache.org/kahadb.html for more information. Thank you for the information. I tryed the above settings, but the following error occured and failed to start ActiveMQ. 2018-03-22 17:21:56,218 | ERROR | Looking for key 531 but

Re: failed to start ActiveMQ

On Tue, Mar 20, 2018, 4:18 AM norinos wrote: > Hi Tim. > > I deleted "db-531.log" and re-started ActiveMQ, but failed to start because > of following error. > > > > 2018-03-20 17:16:15,890 |

Re: failed to start ActiveMQ

Hi Tim. Sorry, because it contains confidential information, I can not attach the file to the issue. > So the question now is how you move forward. If you're able to live with > reprocessing the 511 messages that those acks acknowledged, then just > delete that file and continue on without it.

Re: failed to start ActiveMQ

I submitted https://issues.apache.org/jira/browse/AMQ-6931 to capture this issue. Please add any additional information you think might be useful. If possible, please attach the db-531.log file to the issue in case that helps whoever investigates the issue. So the question now is how you move

Re: failed to start ActiveMQ

>1. Download the 5.13.1 source code (via a sources JAR or Git). >2. In your debugger, set a breakpoint on the catch block in >DataFileAccessor.readRecord (). >3. Attach a debugger to the broker when starting it (use suspend=y > since >this is occurring during

Re: failed to start ActiveMQ

On Sat, Mar 10, 2018 at 12:50 AM, norinos wrote: > Hi, Tim ! > > Yes. I'm using 5.13.1. > > I will try debugging and check the location size. > > > In this case, my KahaDB size is very large. > It seems that the message in which the offlineDurableSubscriberTimeout >

Re: failed to start ActiveMQ

Looking through your stack trace, I can see you're using 5.13.1, not 5.3.1, which is a good thing. (If you were using 5.3.1, I'd tell you no one was likely to help you with a version that old.) It looks like that exception is probably being thrown in