On Thu, Oct 13, 2022 at 2:41 PM Stephen Baker <
stephen.ba...@rmssoftwareinc.com> wrote:
> Fancy, that upgrade tool sounds great – much better than the pile of sed
> scripts I usually write for migrations.
>
> Is there anywhere I can read more about it yet?
Not yet.
I had exchanged some ideas w
If you are able to reproduce with 2.26.0 please follow up with a Jira [1],
and attach the test you're using to reproduce it (or some other equivalent
way to reproduce the CCE). Thanks!
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS
On Thu, Oct 13, 2022 at 2:31 PM Thorsten Meinl
wrote
Am Donnerstag, dem 13.10.2022 um 11:38 -0500 schrieb Justin Bertram:
> It looks like perhaps the responses are being read by the client out
> of order or something like that. Are you using both the core JMS
> client and broker from 2.24.0?
Yes, both client and broker are 2.24.0.
> How often do you
Fancy, that upgrade tool sounds great – much better than the pile of sed
scripts I usually write for migrations.
Is there anywhere I can read more about it yet?
Thanks for the quick patch!
From: Clebert Suconic
Date: Thursday, October 13, 2022 at 2:03 PM
To: users@activemq.apache.org
Subject:
you have to replace the script...
We will have by next week, a tool where you would
/path/to/newVersion/bin/artemis upgrade /path/to/old/instance
We would replace the artemis script, and the logging configuration.
On Thu, Oct 13, 2022 at 1:52 PM Stephen Baker
wrote:
>
> Because bin/artemis
Because bin/artemis includes references to the jboss logmanager causing artemis
to fail on startup
Diffing my two instances I see:
# Set Defaults Properties
ARTEMIS_LOGGING_CONF="$ARTEMIS_INSTANCE_ETC_URI/logging.properties"
ARTEMIS_LOG_MANAGER=org.jboss.logmanager.LogManager
# finding the Log
I think the record would pile up unacked at the source mirror.
and @Stephen baker: sorry about my mistake on this fix...
Why would the upgrade be difficult on 2.27? it's just adding a
log4j2.properties.. everything else should be the same.
You should probably bring a patched version yourself
It looks like perhaps the responses are being read by the client out of
order or something like that. Are you using both the core JMS client and
broker from 2.24.0? How often do you see this? Have you tried reproducing
with the latest release (i.e. 2.26.0)?
Justin
On Thu, Oct 13, 2022 at 9:51 AM
Hi all,
Very occasionally we get the following exception when creating a new
topic in Artemis (2.24.0):
Caused by: java.lang.ClassCastException: class
org.apache.activemq.artemis.core.protocol.core.impl.wireformat.NullResp
onseMessage_V2 cannot be cast to class
org.apache.activemq.artemis.core.pr
Your patch does resolve the error. Artemis 2.27 looks like it will be a
difficult upgrade, I ended up making a new instance and merging config over.
I have pasted a trace in https://issues.apache.org/jira/browse/ARTEMIS-4045
What is the impact of this issue? I’m trying to decide whether to advis
10 matches
Mail list logo
