Hi Mike,
+1 to Matt. We have seen, in some cases, it can take up to 10 hours or so.
Here are a few things you can do:
- Check your KahaDB logs - in your data directory, check the size of
db.redo, db-*.log. If they are huge, during a restart, it can take a long
time to recover if the inst
Hi Mike-
No, that is abnormal. Is the disk locally attached or a volume (SAN, NAS, etc)?
Review the ActiveMQ logs for targeted messages related to disk corruption, etc.
-Matt
> On Jul 19, 2024, at 7:23 AM, Mike Prest
> wrote:
>
> We're running ActiveMQ Classic Windows (5.16.3) and every time
We're running ActiveMQ Classic Windows (5.16.3) and every time we need to do a
restart this is taking like 4 hours.
Is this normal or do we have some kind of config issue? Many thanks - Mike Prest
