Hi Clebert,
Thanks for your response, the issue is the other way around.
- I have a Artemis Server 1.5.5 (In Cluster) using exclusive diverts. If the
client use the version 2.6.2 the message got duplicate.
Let me know if I can provide more details on the issue.
Thanks & Best Regards,
Luis
-
I'm currently working on Docker integration for ActiveMQ Artemis. K8s
is next on the list.
On Tue, Oct 30, 2018 at 7:06 AM COURTAULT Francois
wrote:
>
> Hello everyone,
>
> Is there technical documentation/white papers of the ActiveMQ/Artemis usage
> in Docker/K8s environment ?
>
> Best Regards
There's a break on prefixes between 1.x and 2.x.
The fact that you have a divert on a prefixes address.. I'm not sure
what could happen between your routes.
Can you remove the prefixes and only use 2.x clients?
if you really want to mix this.. we would need to look at
compatibility tests betwe
I'm trying to understand the issue... you have a 2.6.2 server.. and
the issue happens when y ou use a 1.5.x client? is that correct?
On Tue, Oct 30, 2018 at 2:41 PM ldebello wrote:
>
> Hi,
>
> I have just raised a JIRA Ticket
> https://issues.apache.org/jira/browse/ARTEMIS-2156. We are facing an i
What are pros and cons of using Session::CLIENT_ACKNOWLEDGE?
One more thing, why do we need to concern about our message delivery?
What happened when a message is not delivered successfully with using
Session::CLIENT_ACKNOWLEDGE?
Thanks in advance.
Regards,
Sateesh Pathak
--
Sent from: http://a
