Good to know, Robbie. Thanks for the clarification!
Justin
On Fri, Nov 3, 2023 at 12:45 PM Robbie Gemmell
wrote:
> nitpick: AMQP 1.0 also supports 'named producers'. Thats actually all
> the protocol supported until an additional capability was documented
> for doing 'anonymous producer'
nitpick: AMQP 1.0 also supports 'named producers'. Thats actually all
the protocol supported until an additional capability was documented
for doing 'anonymous producer' stuff as e.g needed by some of JMS 1.1.
Though its worth noting all producers on the 'simplified api' added in
JMS 2.0 are
The broker does its best to track producers, but most protocols don't even
have the concept of a "named" producer (i.e. a producer that's registered
on the server to a particular endpoint). Most protocols only support
"anonymous" producers which can send to any endpoint at any time which
means in
Classification: Public
Hello,
Today I noticed that an address was auto-removed while it still had a producer
active.
The producer has a very low production rate, its interval was above the value
of auto-delete-addresses-delay, so the timing constraints were still ok.
Nothing was broken and I
Hi Raymond-
ActiveMQ 6 (ActiveMQ 5.x w/ Jakarta support) supports JDK 21.
The Jakarta dependencies are transitive, if you just use the client then the
list is Jakarta JMS and (optionally Transaction).
If you add in the Jakarta-based broker it can expand depending on if you are
using JDBC or
Yes that list looks correct re: Jakarta..
For 5.x/6.x there are some relevant details at
https://activemq.apache.org/jms2 around the ongoing JMS 2 and now
Jakarta Messaging 3.1 work that might answer your questions.
For Artemis, there are relevant details at
I'm planning to move to Jakarta namespace (JEE10). What I understand is:
1. ActiveMQ Classic Server: Jakarta is not supported (but will be soon from
version 6).
2. ActiveMQ Classic Client: Jakarta is supported.
3. ActiveMQ Artemis Server: Jakarta is supported.
4. ActiveMQ Artemis Client: Jakarta
