> Is that means artemis is created based on HornetQ code base.
A modified version of the HornetQ code-base was the basis for the initial
donation to the ActiveMQ community back in late October 2015. Of course,
since that time the code-base has been heavily modified via over 9,000
commits from over
So, Is that means artemis is created based on HornetQ code base. At the same
time, how to support activemq was considered.
-邮件原件-
发件人: Justin Bertram [mailto:jbert...@apache.org]
发送时间: 2021年12月21日 0:50
收件人: users@activemq.apache.org
主题: Re: The difference between ActiveMQ classic and art
The current behavior is hard-coded and is not configurable. A Jira [1] was
opened about this a while back.
I'll look at amending the documentation.
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS-1983
On Thu, Mar 3, 2022 at 11:49 AM Edson Richter
wrote:
> Hi, Justin, thanks for you
Hi, Justin, thanks for you very fast answer.
One more question about “ActiveMQ Artemis discards the message”: it is a
default behavior that can be customized someway, or this is a fixed by code
behavior?
I think this clarification would be a great addition to documents.
Thanks,
ER.
Enviado
Yes, STOMP supports a NACK frame. The STOMP 1.2 specification [1] says this
about the NACK frame:
> NACK is the opposite of ACK. It is used to tell the server that the
client did not consume the message. The server can then either send the
message to a different client, discard it, or put it in a
I’m writing a Go client using Stomp protocol.
I’ve read all the chapter about Stomp protocol in Artemis Docs. I understand I
can’t use transactional Ack as per this paragraph:
“The STOMP specification identifies transactional acknowledgements as an
optional feature. Support for transactional ac
