The message size actually doesn’t matter at all. The problem is simply calling
updateBlob when the connection string contains replication. It appears that
they have fixed very similar looking issues recently so I’m hopeful it won’t
take long on their side.
From: Vilius Šumskas
Date: Thursday,
Certainly: https://bugs.mysql.com/bug.php?id=108500
From: Justin Bertram
Date: Thursday, September 15, 2022 at 3:06 PM
To: users@activemq.apache.org
Subject: Re: Critical error sending large messages to mysql
Thanks for following up. I was about to comment that I didn't see what the
broker could
During investigation on trimming down the kahadb log files, these messages are
repeating in the acticemq.log:
failed: java.io.EOFException |
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport:
any guidance?
The information contained in this e-mail message is privile
Greetings,
We have an issue where business is reporting the messages are not processing.
Upon checking, we saw that messages were sitting in the delivery count which
were not browsable in the hawtio jolokia console. At the same time this issue
has happened multiple times in both nonprod env a
Hi,
how large is the message? Have you checked max_allowed_packet configuration
parameter, specifically
https://dev.mysql.com/doc/mysql-replication-excerpt/8.0/en/replication-features-max-allowed-packet.html
?
--
Vilius
-Original Message-
From: Stephen Baker
Sent: Thursday, Sep
Thanks for following up. I was about to comment that I didn't see what the
broker could do about this issue as it appeared related to the connector
itself.
It might be helpful for posterity if you followed up with a link to the
issue/ticket for the connector. Any folks who hit this in the future c
Typically performance improvement is an iterative process involving
detailed testing where use-cases are benchmarked against a performance goal
and then bottlenecks are identified and configuration (or code) changes are
made to address those bottlenecks until the performance goal is reached.
There
To follow up, I have tracked this down to a bug in connector/j. I am working on
a simple proof of concept and a ticket for them now.
For any artemis mysql users that are curious, the problem only happens when
using a jdbc:mysql:replication:// connection string. It seems that updateBlob
is broke
Hello, are there any performance improbement guidelines for ActiveMQ and
would using GC1 help to improve performance within the JVM?
I don’t have exact reproduction steps yet (otherwise I would have filed an
issue), but on Artemis 2.22 using a mysql backed journal our QA can reliably
send messages that crash the server:
```
2022-09-15 10:42:24,843 WARN [org.apache.activemq.artemis.journal] AMQ142021:
Error on IO callback, c
10 matches
Mail list logo
