Hi
I use ActiveMQ 5.13.1.
When I start ActiveMQ, An java.util.ConcurrentModificationException occured,
and failed to start MQ.
The following log was output.
-
INFO | Recovery replayed 1
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 wrote:
> Sorry, my inf
Sorry, my information is not enough.
I changed the ActiveMQ setting as follows, and restarted.
-
offlineDurableSubscriberTimeout="12"
offlineDurableSubscriberTaskSchedule="18"
-
In this case, the clien
Sorry, my information is not enough.
I changed the ActiveMQ setting as follows, and restarted.
-
offlineDurableSubscriberTimeout="12"
offlineDurableSubscriberTaskSchedule="18"
-
In this case, the clien
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,
http://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.ht
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 activem
t; 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 not found in
> fileMap:
> 2018-03-22 17:21:56,222 | ERROR | Failed to start Apa
> 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 5
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 | ERROR | Looking for key 531 b
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.
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 forw
>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 initialization)
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
> occurred
Uh, sorry, context
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
occurred has not been deleted,
so I restart ActiveMQ then this trouble is occrred.
Do you th
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
org.apache.activemq.store.kahadb.disk.journal.D
Hi.
When I started ActiveMQ (5.3.1) , the following logs are output and can not
be started.
What kind of cause can be considered?
2018-03-09 11:43:32,468 | INFO | Refreshing
org.apache.activemq.xbean.XBeanBrokerFactory$1@2eeda025: startup date [Fri
Mar 09 11:43:32 JST 2018]; root of context hier
Hi.
When I started ActiveMQ (5.3.1) , the following logs are output and can not
be started.
What kind of cause can be considered?
2018-03-09 11:43:32,468 | INFO | Refreshing
org.apache.activemq.xbean.XBeanBrokerFactory$1@2eeda025: startup date [Fri
Mar 09 11:43:32 JST 2018]; root of context hier
://activemq.apache.org/ | org.apache.activemq.broker.BrokerService |
main
2012-12-23 16:35:22,636 | ERROR | Failed to start ActiveMQ JMS Message
Broker. Reason: java.lang.NullPointerException |
org.apache.activemq.broker.BrokerService | main
java.lang.NullPointerException
at
org.apache.kahadb.index.BTreeNode
18 matches
Mail list logo
