Hello,
We lose our kahadb NFS mounts when our scaled out nas is upgraded. They upgrade
one node at a time and the mount migrates to a different node. The mount can be
unavailable for several seconds. ActiveMQ sometimes fails when this happens. We
are considering using autofs, to reacquire the m
t: Re: ActiveMQ 5.16.4 Data Corruption
Karl-
Is this on a local disk, RAID, SAN or NAS? First step is to confirm there was
no disk corruption-- check your syslog and dmesg output for anyI/O error
messages.
Thanks,
Matt
> On Jun 14, 2022, at 2:48 PM, Nordstrom, Karl wrote:
>
> Hell
Hello,
We have activemq-5.16.4 and java-1.8.0-openjdk.x86_64 1:1.8.0.332.b09-1.el7_9
running on rhel7.
The following was done on our acceptance cluster.
I check activemq.log for messages to determine if activemq has corrupt data
files:
[kxn2@amq-a02 scheduler]$ sudo grep "Failed to start job
Please give me access to the ASF slack channel.
Thanks,
---
Karl Nordström
Systems Administrator
Penn State IT | Application Platforms
From: Justin Bertram
Sent: Monday, June 13, 2022 9:55 AM
To: users@activemq.apache.org
Subject: Re: Request for invitation
Hello,
I check activemq.log for messages like these to determine if activemq has
corrupt data files:
[kxn2@amq-a02 scheduler]$ sudo grep "Failed to start job scheduler store"
/opt/local/activemq/data/activemq.log | head -1
2022-06-03 16:00:46,670 | ERROR | Failed to start job scheduler store:
jolokia, that's maybe related. Did you try to disable
authentication on jolokia ?
Regards
JB
On Tue, Mar 15, 2022 at 4:05 PM Nordstrom, Karl wrote:
> Hello,
>
> After upgrading from ActiveMQ 5.16.0 to 5.16.4, we are getting telegraf
> errors.
>
> amq-p01 ~]$ sudo systemc
Hello,
After upgrading from ActiveMQ 5.16.0 to 5.16.4, we are getting telegraf errors.
amq-p01 ~]$ sudo systemctl status telegraf | cat
● telegraf.service - The plugin-driven server agent for reporting metrics into
InfluxDB
Loaded: loaded (/usr/lib/systemd/system/telegraf.service; enabled; ve
Hello ActiveMQ users,
We have two hosts in each of our ActiveMQ v5.16.x clusters.
They both NFS mount the following at boot time via /etc/fstab
/opt/local/apache-activemq-5.16.0/data/kahadb
/opt/local/apache-activemq-5.16.0/data/amq-prod-cluster
The NFS mounts are provided by an EMC Isilon Scale
into garbage collection logging and GC tuning options for
your version of the JDK.
Thanks,
Matt
> On Feb 7, 2022, at 2:57 PM, Nordstrom, Karl wrote:
>
> Hello activemq users,
>
> We are running v5.16.3 on our amq dev nodes and hit these errors today. Has
> anybody else encount
ault GC settings may not force garbage collection frequently enough in
> order to keep memory resources available.
>
> I suggest you look into garbage collection logging and GC tuning options
> for your version of the JDK.
>
> Thanks,
> Matt
>
> > On Feb 7, 2022, at 2:5
Hello activemq users,
We are running v5.16.3 on our amq dev nodes and hit these errors today. Has
anybody else encounter these? The heap size on dev is 1G while it's 4G on
acceptance. I wonder if 5.16.3 requires more space than 5.15.12 did?
2022-02-07 15:22:39,325 | ERROR | JobScheduler: JMS Ca
for your organization and its
culture.
Tim
On Thu, Nov 18, 2021, 12:07 PM Nordstrom, Karl wrote:
> Hello Matt,
>
> Thanks for the reply. Yes, I meant 5.15.12 and 5.16.3. I doubt I'll be
> able to get the software engineers to drain the production queues. I have
> an active a
this helps!
Thanks,
Matt
> On Nov 18, 2021, at 10:12 AM, Nordstrom, Karl wrote:
>
> Is there documentation on how to upgrade ActiveMQ classic?
> I want to upgrade our test cluster from 1.15.12 to 1.16.3 and
> our production cluster from 1.16.0 to 1.16.3.
> We are using
Is there documentation on how to upgrade ActiveMQ classic?
I want to upgrade our test cluster from 1.15.12 to 1.16.3 and
our production cluster from 1.16.0 to 1.16.3.
We are using KahaDB version 6.
Thanks
---
Karl Nordström
Systems Administrator
Penn State IT | Application Platforms
14 matches
Mail list logo
