Re: Artemis activemq jms client all incompatible with artemis server

[Robbie Gemmell]

I added a note to the docs for the next release about not being able to use
the -all clients in the same JVM as the broker:
https://github.com/apache/activemq-artemis/commit/7f4cd2ac56c383e20b72ec37b12fe6f71bebed1d

Artemis moved to requiring Java 11+ from 2.20.0 back in Dec 2021. The
2.19.1 release itself was mainly only done later due to an overlapping CVE
at that time, it is already over 15 months old now and there have been 10
new releases since. No more 2.19.x releases are coming.

On Wed, 10 May 2023, 19:13 PAS Filip,  wrote:

> Hi Robbie,
>
> Thanks for the feedback.
> It was not really an inconvenience to switch to the jms-client after all.
> I was able to use the transitive dependencies like you mentioned to get
> all I need.
> I didn’t get any versioning issues which is what I was worried about.
> That is why I actually liked the idea of using the shaded classes since it
> reduces the chance of conflicts with the libraries I’m using.
>
> The application I’m working on contains several frameworks that are EOL
> and incompatible with java 11.
> I can’t upgrade them and don’t have the time or budget to replace them.
> I hope you will keep providing critical bugfixes for the 2.19.x version
> and that the client remains compatible with the latest artemis servers.
>
> It would be good to provide some warning in the doc about the jms all
> client not being compatible with the embedded broker.
>
> Thanks for the feedback and confirming the issue.
>
> Regards,
>
> Filip
>
>
> From: Robbie Gemmell 
> Sent: Wednesday, May 10, 2023 8:01 PM
> To: users@activemq.apache.org
> Subject: Re: Artemis activemq jms client all incompatible with artemis
> server
>
> The artemis-jms-client-all module is really just intended to be used
> standalone, and it shades things that artemis-server / commons / etc do not
> (the server itself depends on the regular artemis-jms-client etc). There
> are various concessions
> ZjQcmQRYFpfptBannerStart
> This Message Is From an Untrusted Sender
> You have not previously corresponded with this sender.
> ZjQcmQRYFpfptBannerEnd
>
> The artemis-jms-client-all module is really just intended to be used
>
> standalone, and it shades things that artemis-server / commons / etc
>
> do not (the server itself depends on the regular artemis-jms-client
>
> etc). There are various concessions with it, which is why it is the
>
> last thing mentioned in the [current] docs and comes with a warning.
>
> Personally I would always recommend against using it (and have
>
> previously even proposed deleting it).
>
>
>
> I would never personally expect them to work together given the above,
>
> and I dont believe there has ever been a single attempt running them
>
> in the same classloader in the codebase, given all the actual tests
>
> use artemis-jms-client and no tests use artemis-jms-client-all.
>
>
>
> With your initial comments on the 'inconvenience' of
>
> artemis-jms-client, I take it you are precluding build tooling that
>
> can simply pick up the artemis-jms-client transitive dependencies for
>
> you? The classpath details in the latest docs for the clients
>
> 'individual dependencies' is just generated, essentially by listing
>
> the deps coming from having a maven dependency on artemis-jms-client.
>
>
>
>
>
> Obligatory words of caution even though it seems like you know: 2.28.0
>
> is the current release (with 2.29.0 imminent). There are no more
>
> 2.19.x releases coming. There are already 2 newer >8 Java LTS releases
>
> and Java 21 becomes the next in about 4 months.
>
>
>
> On Wed, 10 May 2023 at 17:37, PAS Filip  <mailto:filip@sodexo.com.invalid>> wrote:
>
> >
>
> > Hi Domenico,
>
> >
>
> > Nope both versions are identical.
>
> >
>
> > The broker I connect to remotely is running 2.28 and that connection
> works.
>
> > All jars and classes of activemq in my project are version 2.19.1.
>
> > It’s only an issue in my test suite when combining the two jars both of
> the same version.
>
> >
>
> > Regards,
>
> >
>
> > Filip
>
> >
>
> > From: Domenico Francesco Bruscino  bruscin...@gmail.com>>
>
> > Sent: Wednesday, May 10, 2023 6:34 PM
>
> > To: users@activemq.apache.org<mailto:users@activemq.apache.org>
>
> > Subject: Re: Artemis activemq jms client all incompatible with artemis
> server
>
> >
>
> > Hi Filip, are you running the ActiveMQ Artemis jms client 2. 19. 1 and
> the ActiveMQ Artemis server with a version different from 2. 19. 1 in the
> same JVM? Regards, Domenico On Wed, 10 May 2023 at 18: 20, PAS F

RE: Artemis activemq jms client all incompatible with artemis server

[PAS Filip]

Hi Robbie,

Thanks for the feedback.
It was not really an inconvenience to switch to the jms-client after all.
I was able to use the transitive dependencies like you mentioned to get all I 
need.
I didn’t get any versioning issues which is what I was worried about.
That is why I actually liked the idea of using the shaded classes since it 
reduces the chance of conflicts with the libraries I’m using.

The application I’m working on contains several frameworks that are EOL and 
incompatible with java 11.
I can’t upgrade them and don’t have the time or budget to replace them.
I hope you will keep providing critical bugfixes for the 2.19.x version and 
that the client remains compatible with the latest artemis servers.

It would be good to provide some warning in the doc about the jms all client 
not being compatible with the embedded broker.

Thanks for the feedback and confirming the issue.

Regards,

Filip


From: Robbie Gemmell 
Sent: Wednesday, May 10, 2023 8:01 PM
To: users@activemq.apache.org
Subject: Re: Artemis activemq jms client all incompatible with artemis server

The artemis-jms-client-all module is really just intended to be used 
standalone, and it shades things that artemis-server / commons / etc do not 
(the server itself depends on the regular artemis-jms-client etc). There are 
various concessions
ZjQcmQRYFpfptBannerStart
This Message Is From an Untrusted Sender
You have not previously corresponded with this sender.
ZjQcmQRYFpfptBannerEnd

The artemis-jms-client-all module is really just intended to be used

standalone, and it shades things that artemis-server / commons / etc

do not (the server itself depends on the regular artemis-jms-client

etc). There are various concessions with it, which is why it is the

last thing mentioned in the [current] docs and comes with a warning.

Personally I would always recommend against using it (and have

previously even proposed deleting it).



I would never personally expect them to work together given the above,

and I dont believe there has ever been a single attempt running them

in the same classloader in the codebase, given all the actual tests

use artemis-jms-client and no tests use artemis-jms-client-all.



With your initial comments on the 'inconvenience' of

artemis-jms-client, I take it you are precluding build tooling that

can simply pick up the artemis-jms-client transitive dependencies for

you? The classpath details in the latest docs for the clients

'individual dependencies' is just generated, essentially by listing

the deps coming from having a maven dependency on artemis-jms-client.





Obligatory words of caution even though it seems like you know: 2.28.0

is the current release (with 2.29.0 imminent). There are no more

2.19.x releases coming. There are already 2 newer >8 Java LTS releases

and Java 21 becomes the next in about 4 months.



On Wed, 10 May 2023 at 17:37, PAS Filip 
mailto:filip@sodexo.com.invalid>> wrote:

>

> Hi Domenico,

>

> Nope both versions are identical.

>

> The broker I connect to remotely is running 2.28 and that connection works.

> All jars and classes of activemq in my project are version 2.19.1.

> It’s only an issue in my test suite when combining the two jars both of the 
> same version.

>

> Regards,

>

> Filip

>

> From: Domenico Francesco Bruscino 
> mailto:bruscin...@gmail.com>>

> Sent: Wednesday, May 10, 2023 6:34 PM

> To: users@activemq.apache.org<mailto:users@activemq.apache.org>

> Subject: Re: Artemis activemq jms client all incompatible with artemis server

>

> Hi Filip, are you running the ActiveMQ Artemis jms client 2. 19. 1 and the 
> ActiveMQ Artemis server with a version different from 2. 19. 1 in the same 
> JVM? Regards, Domenico On Wed, 10 May 2023 at 18: 20, PAS Filip  sodexo. com. invalid>

> ZjQcmQRYFpfptBannerStart

> This Message Is From an Untrusted Sender

> You have not previously corresponded with this sender.

> ZjQcmQRYFpfptBannerEnd

>

> Hi Filip,

>

>

>

> are you running the ActiveMQ Artemis jms client 2.19.1 and the ActiveMQ

>

> Artemis server with a version different from 2.19.1 in the same JVM?

>

>

>

> Regards,

>

> Domenico

>

>

>

> On Wed, 10 May 2023 at 18:20, PAS Filip 
> mailto:filip@sodexo.com.invalid<mailto:filip@sodexo.com.invalid%3cmailto:filip@sodexo.com.invalid>>>

>

> wrote:

>

>

>

> > Just a small follow-up, using artemis-jms-client instead of

>

> > artemis-jms-client-all seems to be working fine

>

> > There is are no duplicate shaded classes this way when combining it with

>

> > artemis-server.

>

> >

>

> > From: PAS Filip 
> > mailto:filip@sodexo.com.INVALID<mailto:filip@sodexo.com.INVALID%3cmailto:filip@sodexo.com.INVALID>>

Re: Artemis activemq jms client all incompatible with artemis server

[Robbie Gemmell]

The artemis-jms-client-all module is really just intended to be used
standalone, and it shades things that artemis-server / commons / etc
do not (the server itself depends on the regular artemis-jms-client
etc). There are various concessions with it, which is why it is the
last thing mentioned in the [current] docs and comes with a warning.
Personally I would always recommend against using it (and have
previously even proposed deleting it).

I would never personally expect them to work together given the above,
and I dont believe there has ever been a single attempt running them
in the same classloader in the codebase, given all the actual tests
use artemis-jms-client and no tests use artemis-jms-client-all.

With your initial comments on the 'inconvenience' of
artemis-jms-client, I take it you are precluding build tooling that
can simply pick up the artemis-jms-client transitive dependencies for
you? The classpath details in the latest docs for the clients
'individual dependencies' is just generated, essentially by listing
the deps coming from having a maven dependency on artemis-jms-client.


Obligatory words of caution even though it seems like you know: 2.28.0
is the current release (with 2.29.0 imminent). There are no more
2.19.x releases coming. There are already 2 newer >8 Java LTS releases
and Java 21 becomes the next in about 4 months.

On Wed, 10 May 2023 at 17:37, PAS Filip  wrote:
>
> Hi Domenico,
>
> Nope both versions are identical.
>
> The broker I connect to remotely is running 2.28 and that connection works.
> All jars and classes of activemq in my project are version 2.19.1.
> It’s only an issue in my test suite when combining the two jars both of the 
> same version.
>
> Regards,
>
> Filip
>
> From: Domenico Francesco Bruscino 
> Sent: Wednesday, May 10, 2023 6:34 PM
> To: users@activemq.apache.org
> Subject: Re: Artemis activemq jms client all incompatible with artemis server
>
> Hi Filip, are you running the ActiveMQ Artemis jms client 2. 19. 1 and the 
> ActiveMQ Artemis server with a version different from 2. 19. 1 in the same 
> JVM? Regards, Domenico On Wed, 10 May 2023 at 18: 20, PAS Filip  sodexo. com. invalid>
> ZjQcmQRYFpfptBannerStart
> This Message Is From an Untrusted Sender
> You have not previously corresponded with this sender.
> ZjQcmQRYFpfptBannerEnd
>
> Hi Filip,
>
>
>
> are you running the ActiveMQ Artemis jms client 2.19.1 and the ActiveMQ
>
> Artemis server with a version different from 2.19.1 in the same JVM?
>
>
>
> Regards,
>
> Domenico
>
>
>
> On Wed, 10 May 2023 at 18:20, PAS Filip 
> mailto:filip@sodexo.com.invalid>>
>
> wrote:
>
>
>
> > Just a small follow-up, using artemis-jms-client instead of
>
> > artemis-jms-client-all seems to be working fine
>
> > There is are no duplicate shaded classes this way when combining it with
>
> > artemis-server.
>
> >
>
> > From: PAS Filip 
> > mailto:filip@sodexo.com.INVALID>>
>
> > Sent: Wednesday, May 10, 2023 3:14 PM
>
> > To: users@activemq.apache.org<mailto:users@activemq.apache.org>
>
> > Subject: Artemis activemq jms client all incompatible with artemis server
>
> >
>
> > Hello, I'm working on an application where we are migrating activemq to
>
> > artemis activemq. I'm running into an issue when trying to use the artemis
>
> > server and jms client all together on the same classpath. I'm using version
>
> > 2. 19. 1 of the artemis
>
> > ZjQcmQRYFpfptBannerStart
>
> > External sender
>
> > Check the sender and the content are safe before clicking links or open
>
> > attachments.
>
> > ZjQcmQRYFpfptBannerEnd
>
> >
>
> > Hello,
>
> >
>
> >
>
> >
>
> > I'm working on an application where we are migrating activemq to artemis
>
> > activemq.
>
> >
>
> >
>
> >
>
> > I'm running into an issue when trying to use the artemis server and jms
>
> > client all together on the same classpath.
>
> >
>
> >
>
> >
>
> > I'm using version 2.19.1 of the artemis activemq server since it's the
>
> > last version that's compatible with java 8.
>
> >
>
> > According to the docs I should use this version and it should be able to
>
> > connect fine to a remote activemq broker running java 11.
>
> >
>
> > That seems to work correctly however when running the integration test
>
> > suite I'm replacing the old activemq embedded broker with the one from
>
> > artemis activemq and am running into an issue of incompatibility.
>
> >
>
> >
>
> >
>

RE: Artemis activemq jms client all incompatible with artemis server

[PAS Filip]

Hi Domenico,

Nope both versions are identical.

The broker I connect to remotely is running 2.28 and that connection works.
All jars and classes of activemq in my project are version 2.19.1.
It’s only an issue in my test suite when combining the two jars both of the 
same version.

Regards,

Filip

From: Domenico Francesco Bruscino 
Sent: Wednesday, May 10, 2023 6:34 PM
To: users@activemq.apache.org
Subject: Re: Artemis activemq jms client all incompatible with artemis server

Hi Filip, are you running the ActiveMQ Artemis jms client 2. 19. 1 and the 
ActiveMQ Artemis server with a version different from 2. 19. 1 in the same JVM? 
Regards, Domenico On Wed, 10 May 2023 at 18: 20, PAS Filip 
ZjQcmQRYFpfptBannerStart
This Message Is From an Untrusted Sender
You have not previously corresponded with this sender.
ZjQcmQRYFpfptBannerEnd

Hi Filip,



are you running the ActiveMQ Artemis jms client 2.19.1 and the ActiveMQ

Artemis server with a version different from 2.19.1 in the same JVM?



Regards,

Domenico



On Wed, 10 May 2023 at 18:20, PAS Filip 
mailto:filip@sodexo.com.invalid>>

wrote:



> Just a small follow-up, using artemis-jms-client instead of

> artemis-jms-client-all seems to be working fine

> There is are no duplicate shaded classes this way when combining it with

> artemis-server.

>

> From: PAS Filip 
> mailto:filip@sodexo.com.INVALID>>

> Sent: Wednesday, May 10, 2023 3:14 PM

> To: users@activemq.apache.org<mailto:users@activemq.apache.org>

> Subject: Artemis activemq jms client all incompatible with artemis server

>

> Hello, I'm working on an application where we are migrating activemq to

> artemis activemq. I'm running into an issue when trying to use the artemis

> server and jms client all together on the same classpath. I'm using version

> 2. 19. 1 of the artemis

> ZjQcmQRYFpfptBannerStart

> External sender

> Check the sender and the content are safe before clicking links or open

> attachments.

> ZjQcmQRYFpfptBannerEnd

>

> Hello,

>

>

>

> I'm working on an application where we are migrating activemq to artemis

> activemq.

>

>

>

> I'm running into an issue when trying to use the artemis server and jms

> client all together on the same classpath.

>

>

>

> I'm using version 2.19.1 of the artemis activemq server since it's the

> last version that's compatible with java 8.

>

> According to the docs I should use this version and it should be able to

> connect fine to a remote activemq broker running java 11.

>

> That seems to work correctly however when running the integration test

> suite I'm replacing the old activemq embedded broker with the one from

> artemis activemq and am running into an issue of incompatibility.

>

>

>

> Our integration test suite uses the embedded broker so the artemis server

> is added to the test classpath.

>

> When running the tests the embedded broker seems to start fine:

>

>

>

> [2023-05-10T14:21:58,942|INFO

> |main|org.apache.activemq.artemis.core.server] AMQ221007: Server is now live

>

> [2023-05-10T14:21:58,943|INFO

> |main|org.apache.activemq.artemis.core.server] AMQ221001: Apache ActiveMQ

> Artemis Message Broker version 2.19.1 [localhost,

> nodeID=42455503-ef2d-11ed-8947-00090faa0001]

>

>

>

> However when connecting to it I get an error:

>

>

>

> [2023-05-10T14:22:13,517|WARN |Thread-5

> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@417a98b5<mailto:ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@417a98b5>

> )|org.apache.activemq.artemis.core.server ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl

> $6@417a98b5)|org.apache.activemq.artemis.core.servermailto:$6@417a98b5)|org.apache.activemq.artemis.core.server%3cmailto>:

> ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl

> $6@417a98b5

> )|org.apache.activemq.artemis.core.server%3cmailto:ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@417a98b5)|org.apache.activemq.artemis.core.server>>]

> AMQ25: Sending unexpected exception to the client

> java.lang.NoClassDefFoundError: Could not initialize class

> org.apache.activemq.artemis.core.server.cluster.impl.MessageLoadBalancingType

>

> at

> org.apache.activemq.artemis.core.postoffice.impl.BindingsImpl.(BindingsImpl.java:68)

>

> at

> org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl.createBindings(PostOfficeImpl.java:1989)

>

> at

> org.apache.activemq.artemis.core.postoffice.impl.SimpleAddressManager.addMappingInternal(SimpleAddressMana

Re: Artemis activemq jms client all incompatible with artemis server

[Domenico Francesco Bruscino]

Hi Filip,

are you running the ActiveMQ Artemis jms client 2.19.1 and the ActiveMQ
Artemis server with a version different from 2.19.1 in the same JVM?

Regards,
Domenico

On Wed, 10 May 2023 at 18:20, PAS Filip 
wrote:

> Just a small follow-up, using artemis-jms-client instead of
> artemis-jms-client-all seems to be working fine
> There is are no duplicate shaded classes this way when combining it with
> artemis-server.
>
> From: PAS Filip 
> Sent: Wednesday, May 10, 2023 3:14 PM
> To: users@activemq.apache.org
> Subject: Artemis activemq jms client all incompatible with artemis server
>
> Hello, I'm working on an application where we are migrating activemq to
> artemis activemq. I'm running into an issue when trying to use the artemis
> server and jms client all together on the same classpath. I'm using version
> 2. 19. 1 of the artemis
> ZjQcmQRYFpfptBannerStart
> External sender
> Check the sender and the content are safe before clicking links or open
> attachments.
> ZjQcmQRYFpfptBannerEnd
>
> Hello,
>
>
>
> I'm working on an application where we are migrating activemq to artemis
> activemq.
>
>
>
> I'm running into an issue when trying to use the artemis server and jms
> client all together on the same classpath.
>
>
>
> I'm using version 2.19.1 of the artemis activemq server since it's the
> last version that's compatible with java 8.
>
> According to the docs I should use this version and it should be able to
> connect fine to a remote activemq broker running java 11.
>
> That seems to work correctly however when running the integration test
> suite I'm replacing the old activemq embedded broker with the one from
> artemis activemq and am running into an issue of incompatibility.
>
>
>
> Our integration test suite uses the embedded broker so the artemis server
> is added to the test classpath.
>
> When running the tests the embedded broker seems to start fine:
>
>
>
> [2023-05-10T14:21:58,942|INFO
> |main|org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
>
> [2023-05-10T14:21:58,943|INFO
> |main|org.apache.activemq.artemis.core.server] AMQ221001: Apache ActiveMQ
> Artemis Message Broker version 2.19.1 [localhost,
> nodeID=42455503-ef2d-11ed-8947-00090faa0001]
>
>
>
> However when connecting to it I get an error:
>
>
>
> [2023-05-10T14:22:13,517|WARN |Thread-5
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@417a98b5
> )|org.apache.activemq.artemis.core.server ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl
> $6@417a98b5)|org.apache.activemq.artemis.core.server ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl
> $6@417a98b5
> )|org.apache.activemq.artemis.core.server%3cmailto:ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@417a98b5)|org.apache.activemq.artemis.core.server>>]
> AMQ25: Sending unexpected exception to the client
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.activemq.artemis.core.server.cluster.impl.MessageLoadBalancingType
>
> at
> org.apache.activemq.artemis.core.postoffice.impl.BindingsImpl.(BindingsImpl.java:68)
>
> at
> org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl.createBindings(PostOfficeImpl.java:1989)
>
> at
> org.apache.activemq.artemis.core.postoffice.impl.SimpleAddressManager.addMappingInternal(SimpleAddressManager.java:260)
>
> at
> org.apache.activemq.artemis.core.postoffice.impl.SimpleAddressManager.addBinding(SimpleAddressManager.java:99)
>
> at
> org.apache.activemq.artemis.core.postoffice.impl.WildcardAddressManager.addBinding(WildcardAddressManager.java:95)
>
> at
> org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl.addBinding(PostOfficeImpl.java:878)
>
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.createQueue(ActiveMQServerImpl.java:3833)
>
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.createQueue(ActiveMQServerImpl.java:3765)
>
> at
> org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:740)
>
> at
> org.apache.activemq.artemis.core.protocol.core.ServerSessionPacketHandler.slowPacketHandler(ServerSessionPacketHandler.java:377)
>
> at
> org.apache.activemq.artemis.core.protocol.core.ServerSessionPacketHandler.onMessagePacket(ServerSessionPacketHandler.java:298)
>
> at
> org.apache.activemq.artemis.utils.actors.Actor.doTask(Actor.java:33)
>
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:65)
>
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
>
> at
> 

RE: Artemis activemq jms client all incompatible with artemis server

[PAS Filip]

Just a small follow-up, using artemis-jms-client instead of 
artemis-jms-client-all seems to be working fine
There is are no duplicate shaded classes this way when combining it with 
artemis-server.

From: PAS Filip 
Sent: Wednesday, May 10, 2023 3:14 PM
To: users@activemq.apache.org
Subject: Artemis activemq jms client all incompatible with artemis server

Hello, I'm working on an application where we are migrating activemq to artemis 
activemq. I'm running into an issue when trying to use the artemis server and 
jms client all together on the same classpath. I'm using version 2. 19. 1 of 
the artemis
ZjQcmQRYFpfptBannerStart
External sender
Check the sender and the content are safe before clicking links or open 
attachments.
ZjQcmQRYFpfptBannerEnd

Hello,



I'm working on an application where we are migrating activemq to artemis 
activemq.



I'm running into an issue when trying to use the artemis server and jms client 
all together on the same classpath.



I'm using version 2.19.1 of the artemis activemq server since it's the last 
version that's compatible with java 8.

According to the docs I should use this version and it should be able to 
connect fine to a remote activemq broker running java 11.

That seems to work correctly however when running the integration test suite 
I'm replacing the old activemq embedded broker with the one from artemis 
activemq and am running into an issue of incompatibility.



Our integration test suite uses the embedded broker so the artemis server is 
added to the test classpath.

When running the tests the embedded broker seems to start fine:



[2023-05-10T14:21:58,942|INFO |main|org.apache.activemq.artemis.core.server] 
AMQ221007: Server is now live

[2023-05-10T14:21:58,943|INFO |main|org.apache.activemq.artemis.core.server] 
AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.19.1 [localhost, 
nodeID=42455503-ef2d-11ed-8947-00090faa0001]



However when connecting to it I get an error:



[2023-05-10T14:22:13,517|WARN |Thread-5 
(ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@417a98b5)|org.apache.activemq.artemis.core.server>]
 AMQ25: Sending unexpected exception to the client 
java.lang.NoClassDefFoundError: Could not initialize class 
org.apache.activemq.artemis.core.server.cluster.impl.MessageLoadBalancingType

at 
org.apache.activemq.artemis.core.postoffice.impl.BindingsImpl.(BindingsImpl.java:68)

at 
org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl.createBindings(PostOfficeImpl.java:1989)

at 
org.apache.activemq.artemis.core.postoffice.impl.SimpleAddressManager.addMappingInternal(SimpleAddressManager.java:260)

at 
org.apache.activemq.artemis.core.postoffice.impl.SimpleAddressManager.addBinding(SimpleAddressManager.java:99)

at 
org.apache.activemq.artemis.core.postoffice.impl.WildcardAddressManager.addBinding(WildcardAddressManager.java:95)

at 
org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl.addBinding(PostOfficeImpl.java:878)

at 
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.createQueue(ActiveMQServerImpl.java:3833)

at 
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.createQueue(ActiveMQServerImpl.java:3765)

at 
org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:740)

at 
org.apache.activemq.artemis.core.protocol.core.ServerSessionPacketHandler.slowPacketHandler(ServerSessionPacketHandler.java:377)

at 
org.apache.activemq.artemis.core.protocol.core.ServerSessionPacketHandler.onMessagePacket(ServerSessionPacketHandler.java:298)

at 
org.apache.activemq.artemis.utils.actors.Actor.doTask(Actor.java:33)

at 
org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:65)

at 
org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)

at 
org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)

at 
org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:65)

at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at