You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Jean-Louis Monteiro <jl...@tomitribe.com> on 2026/02/24 20:01:24 UTC
Jakarta Messaging 3.1 TCK
Hi team,
I've been trying to set up the Jakarta Messaging 3.1 TCK on Apache
ActiveMQ. I should have a PR ready by tomorrow. It won't pass all the tests
of course, so it won't run on any CI for the moment. But it's interesting
to get a bit more coverage on ActiveMQ and also good to help filling the
gaps.
I'm not sure if there is any willingness to become a
compatible implementation listed on the Jakarta website, but it won't hurt
either.
We are currently at 90%. My experience on various TCK work is that the last
tests usually are harder to get to pass.
I'll keep you posted tomorrow when I know more about the first runs.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
Re: Jakarta Messaging 3.1 TCK
Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
Hi all,
I pushed some minor fixes for sed on mac and to set the local to en_US
because for instance it does not work with number in France ;-)
Here are the results so far
[javatest.batch]
********************************************************************************
[javatest.batch] Number of tests completed: 903 (799 passed, 103 failed, 1
with errors)
[javatest.batch] Number of tests remaining: 0
[javatest.batch]
********************************************************************************
[javatest.batch] Completed running 903 tests.
[javatest.batch] Number of Tests Passed = 799
[javatest.batch] Number of Tests Failed = 103
[javatest.batch] Number of Tests with Errors = 1
[javatest.batch]
********************************************************************************
I'll do some triage and create issues for it.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Wed, Feb 25, 2026 at 7:12 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi Jean-Louis,
>
> Thanks for your work on this, as we discussed offline.
>
> It is great to have this for two main reasons:
>
> 1. It provides a clear assessment of our current Jakarta Messaging 3.1
> support and identifies the remaining gaps.
> 2. It gives us the opportunity to be listed as a compatible implementation
> on the Jakarta website.
>
> I am moving forward with the receiveBody() implementation, so I estimate we
> are currently between 88% and 92%. Some remaining parts will require more
> significant effort, such as durable subscribers, which require updates to
> the OpenWire protocol and KahaDB internals.
>
> If we can make the TCK runnable via a Maven profile, that would be
> excellent, as it would allow us to run it on the CI on a weekly basis.
>
> Thanks again!
>
> Regards,
> JB
>
> On Tue, Feb 24, 2026 at 9:02 PM Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> wrote:
>
> > Hi team,
> >
> > I've been trying to set up the Jakarta Messaging 3.1 TCK on Apache
> > ActiveMQ. I should have a PR ready by tomorrow. It won't pass all the
> tests
> > of course, so it won't run on any CI for the moment. But it's interesting
> > to get a bit more coverage on ActiveMQ and also good to help filling the
> > gaps.
> >
> > I'm not sure if there is any willingness to become a
> > compatible implementation listed on the Jakarta website, but it won't
> hurt
> > either.
> >
> > We are currently at 90%. My experience on various TCK work is that the
> last
> > tests usually are harder to get to pass.
> >
> > I'll keep you posted tomorrow when I know more about the first runs.
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
>
Re: Jakarta Messaging 3.1 TCK
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Awesome !
Thanks a lot Jean-Louis !
I like the use of the profile for now. We can run it locally while working
on JakartaMessaging 3 features.
When we have almost complete spec support, I propose to run the TCK
periodically.
As quickly discussed together on slack, I think the approach for async send
is fine: reusing the existing sendAsync feature from ActiveMQ and creating
new command.
I will do a more detailed review on the PR.
In the meantime, I will have the PR about receiveBody updated.
Regards
JB
On Thu, Feb 26, 2026 at 4:27 PM Jean-Louis Monteiro <
jlmonteiro@tomitribe.com> wrote:
> Alright.
>
> The PR to add the TCK module is available at
> https://github.com/apache/activemq/pull/1712
> It's not green because of flaky tests fixed in
> https://github.com/apache/activemq/pull/1711 still not merged (but it's
> green).
>
> The PR adds a module with the TCK but they don't run until you add the
> profile, so it's a no-op PR with the current build. So waiting for all the
> tests to pass is not necessary in my opinion. As soon as the reactor is
> happy ....
>
> I ran the TCK entirely and added the report in the PR itself.
> I created the Github issue https://github.com/apache/activemq/issues/1713
> wich is the top level issue.
> Then I created a bunch of small issues for each failures or group of
> failure and started assigning some to me and adding commits to fix the
> quick win.
>
> I started also on the async send which passes the TCK and is green. We
> already had the ProducerAck in OpenWire and an AckCallback in the session,
> so I basically wrapped it into a CompletionListener. I'm not sure if we
> need more or want more. The rest of the changes are basically TCK related
> for the exceptions (edge cases).
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Feb 25, 2026 at 4:03 PM Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> wrote:
>
> > Awesome, I think I created sub-issues in the global TCK issue in Github.
> > You might have it already, otherwise, please create one so we can track
> the
> > work.
> > Let me know if I can help.
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Wed, Feb 25, 2026 at 3:43 PM Matt Pavlovich <ma...@apache.org>
> > wrote:
> >
> >> I have a PR for message delay feature that we can go with without
> >> updating OpenWire protocol.
> >>
> >> I’ll refresh it and get it ready for 6.3.0
> >>
> >> > On Feb 25, 2026, at 12:10 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
> >> wrote:
> >> >
> >> > Hi Jean-Louis,
> >> >
> >> > Thanks for your work on this, as we discussed offline.
> >> >
> >> > It is great to have this for two main reasons:
> >> >
> >> > 1. It provides a clear assessment of our current Jakarta Messaging 3.1
> >> > support and identifies the remaining gaps.
> >> > 2. It gives us the opportunity to be listed as a compatible
> >> implementation
> >> > on the Jakarta website.
> >> >
> >> > I am moving forward with the receiveBody() implementation, so I
> >> estimate we
> >> > are currently between 88% and 92%. Some remaining parts will require
> >> more
> >> > significant effort, such as durable subscribers, which require updates
> >> to
> >> > the OpenWire protocol and KahaDB internals.
> >> >
> >> > If we can make the TCK runnable via a Maven profile, that would be
> >> > excellent, as it would allow us to run it on the CI on a weekly basis.
> >> >
> >> > Thanks again!
> >> >
> >> > Regards,
> >> > JB
> >> >
> >> > On Tue, Feb 24, 2026 at 9:02 PM Jean-Louis Monteiro <
> >> > jlmonteiro@tomitribe.com> wrote:
> >> >
> >> >> Hi team,
> >> >>
> >> >> I've been trying to set up the Jakarta Messaging 3.1 TCK on Apache
> >> >> ActiveMQ. I should have a PR ready by tomorrow. It won't pass all the
> >> tests
> >> >> of course, so it won't run on any CI for the moment. But it's
> >> interesting
> >> >> to get a bit more coverage on ActiveMQ and also good to help filling
> >> the
> >> >> gaps.
> >> >>
> >> >> I'm not sure if there is any willingness to become a
> >> >> compatible implementation listed on the Jakarta website, but it won't
> >> hurt
> >> >> either.
> >> >>
> >> >> We are currently at 90%. My experience on various TCK work is that
> the
> >> last
> >> >> tests usually are harder to get to pass.
> >> >>
> >> >> I'll keep you posted tomorrow when I know more about the first runs.
> >> >>
> >> >> --
> >> >> Jean-Louis Monteiro
> >> >> http://twitter.com/jlouismonteiro
> >> >> http://www.tomitribe.com
> >> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
> >> For additional commands, e-mail: dev-help@activemq.apache.org
> >> For further information, visit: https://activemq.apache.org/contact
> >>
> >>
> >>
>
Re: Jakarta Messaging 3.1 TCK
Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
Alright.
The PR to add the TCK module is available at
https://github.com/apache/activemq/pull/1712
It's not green because of flaky tests fixed in
https://github.com/apache/activemq/pull/1711 still not merged (but it's
green).
The PR adds a module with the TCK but they don't run until you add the
profile, so it's a no-op PR with the current build. So waiting for all the
tests to pass is not necessary in my opinion. As soon as the reactor is
happy ....
I ran the TCK entirely and added the report in the PR itself.
I created the Github issue https://github.com/apache/activemq/issues/1713
wich is the top level issue.
Then I created a bunch of small issues for each failures or group of
failure and started assigning some to me and adding commits to fix the
quick win.
I started also on the async send which passes the TCK and is green. We
already had the ProducerAck in OpenWire and an AckCallback in the session,
so I basically wrapped it into a CompletionListener. I'm not sure if we
need more or want more. The rest of the changes are basically TCK related
for the exceptions (edge cases).
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Wed, Feb 25, 2026 at 4:03 PM Jean-Louis Monteiro <
jlmonteiro@tomitribe.com> wrote:
> Awesome, I think I created sub-issues in the global TCK issue in Github.
> You might have it already, otherwise, please create one so we can track the
> work.
> Let me know if I can help.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Feb 25, 2026 at 3:43 PM Matt Pavlovich <ma...@apache.org>
> wrote:
>
>> I have a PR for message delay feature that we can go with without
>> updating OpenWire protocol.
>>
>> I’ll refresh it and get it ready for 6.3.0
>>
>> > On Feb 25, 2026, at 12:10 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
>> wrote:
>> >
>> > Hi Jean-Louis,
>> >
>> > Thanks for your work on this, as we discussed offline.
>> >
>> > It is great to have this for two main reasons:
>> >
>> > 1. It provides a clear assessment of our current Jakarta Messaging 3.1
>> > support and identifies the remaining gaps.
>> > 2. It gives us the opportunity to be listed as a compatible
>> implementation
>> > on the Jakarta website.
>> >
>> > I am moving forward with the receiveBody() implementation, so I
>> estimate we
>> > are currently between 88% and 92%. Some remaining parts will require
>> more
>> > significant effort, such as durable subscribers, which require updates
>> to
>> > the OpenWire protocol and KahaDB internals.
>> >
>> > If we can make the TCK runnable via a Maven profile, that would be
>> > excellent, as it would allow us to run it on the CI on a weekly basis.
>> >
>> > Thanks again!
>> >
>> > Regards,
>> > JB
>> >
>> > On Tue, Feb 24, 2026 at 9:02 PM Jean-Louis Monteiro <
>> > jlmonteiro@tomitribe.com> wrote:
>> >
>> >> Hi team,
>> >>
>> >> I've been trying to set up the Jakarta Messaging 3.1 TCK on Apache
>> >> ActiveMQ. I should have a PR ready by tomorrow. It won't pass all the
>> tests
>> >> of course, so it won't run on any CI for the moment. But it's
>> interesting
>> >> to get a bit more coverage on ActiveMQ and also good to help filling
>> the
>> >> gaps.
>> >>
>> >> I'm not sure if there is any willingness to become a
>> >> compatible implementation listed on the Jakarta website, but it won't
>> hurt
>> >> either.
>> >>
>> >> We are currently at 90%. My experience on various TCK work is that the
>> last
>> >> tests usually are harder to get to pass.
>> >>
>> >> I'll keep you posted tomorrow when I know more about the first runs.
>> >>
>> >> --
>> >> Jean-Louis Monteiro
>> >> http://twitter.com/jlouismonteiro
>> >> http://www.tomitribe.com
>> >>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
>> For additional commands, e-mail: dev-help@activemq.apache.org
>> For further information, visit: https://activemq.apache.org/contact
>>
>>
>>
Re: Jakarta Messaging 3.1 TCK
Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
Awesome, I think I created sub-issues in the global TCK issue in Github.
You might have it already, otherwise, please create one so we can track the
work.
Let me know if I can help.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Wed, Feb 25, 2026 at 3:43 PM Matt Pavlovich <ma...@apache.org> wrote:
> I have a PR for message delay feature that we can go with without updating
> OpenWire protocol.
>
> I’ll refresh it and get it ready for 6.3.0
>
> > On Feb 25, 2026, at 12:10 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
> >
> > Hi Jean-Louis,
> >
> > Thanks for your work on this, as we discussed offline.
> >
> > It is great to have this for two main reasons:
> >
> > 1. It provides a clear assessment of our current Jakarta Messaging 3.1
> > support and identifies the remaining gaps.
> > 2. It gives us the opportunity to be listed as a compatible
> implementation
> > on the Jakarta website.
> >
> > I am moving forward with the receiveBody() implementation, so I estimate
> we
> > are currently between 88% and 92%. Some remaining parts will require more
> > significant effort, such as durable subscribers, which require updates to
> > the OpenWire protocol and KahaDB internals.
> >
> > If we can make the TCK runnable via a Maven profile, that would be
> > excellent, as it would allow us to run it on the CI on a weekly basis.
> >
> > Thanks again!
> >
> > Regards,
> > JB
> >
> > On Tue, Feb 24, 2026 at 9:02 PM Jean-Louis Monteiro <
> > jlmonteiro@tomitribe.com> wrote:
> >
> >> Hi team,
> >>
> >> I've been trying to set up the Jakarta Messaging 3.1 TCK on Apache
> >> ActiveMQ. I should have a PR ready by tomorrow. It won't pass all the
> tests
> >> of course, so it won't run on any CI for the moment. But it's
> interesting
> >> to get a bit more coverage on ActiveMQ and also good to help filling the
> >> gaps.
> >>
> >> I'm not sure if there is any willingness to become a
> >> compatible implementation listed on the Jakarta website, but it won't
> hurt
> >> either.
> >>
> >> We are currently at 90%. My experience on various TCK work is that the
> last
> >> tests usually are harder to get to pass.
> >>
> >> I'll keep you posted tomorrow when I know more about the first runs.
> >>
> >> --
> >> Jean-Louis Monteiro
> >> http://twitter.com/jlouismonteiro
> >> http://www.tomitribe.com
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
> For additional commands, e-mail: dev-help@activemq.apache.org
> For further information, visit: https://activemq.apache.org/contact
>
>
>
Re: Jakarta Messaging 3.1 TCK
Posted by Matt Pavlovich <ma...@apache.org>.
I have a PR for message delay feature that we can go with without updating OpenWire protocol.
I’ll refresh it and get it ready for 6.3.0
> On Feb 25, 2026, at 12:10 AM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> Hi Jean-Louis,
>
> Thanks for your work on this, as we discussed offline.
>
> It is great to have this for two main reasons:
>
> 1. It provides a clear assessment of our current Jakarta Messaging 3.1
> support and identifies the remaining gaps.
> 2. It gives us the opportunity to be listed as a compatible implementation
> on the Jakarta website.
>
> I am moving forward with the receiveBody() implementation, so I estimate we
> are currently between 88% and 92%. Some remaining parts will require more
> significant effort, such as durable subscribers, which require updates to
> the OpenWire protocol and KahaDB internals.
>
> If we can make the TCK runnable via a Maven profile, that would be
> excellent, as it would allow us to run it on the CI on a weekly basis.
>
> Thanks again!
>
> Regards,
> JB
>
> On Tue, Feb 24, 2026 at 9:02 PM Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> wrote:
>
>> Hi team,
>>
>> I've been trying to set up the Jakarta Messaging 3.1 TCK on Apache
>> ActiveMQ. I should have a PR ready by tomorrow. It won't pass all the tests
>> of course, so it won't run on any CI for the moment. But it's interesting
>> to get a bit more coverage on ActiveMQ and also good to help filling the
>> gaps.
>>
>> I'm not sure if there is any willingness to become a
>> compatible implementation listed on the Jakarta website, but it won't hurt
>> either.
>>
>> We are currently at 90%. My experience on various TCK work is that the last
>> tests usually are harder to get to pass.
>>
>> I'll keep you posted tomorrow when I know more about the first runs.
>>
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
For additional commands, e-mail: dev-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
Re: Jakarta Messaging 3.1 TCK
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Jean-Louis,
Thanks for your work on this, as we discussed offline.
It is great to have this for two main reasons:
1. It provides a clear assessment of our current Jakarta Messaging 3.1
support and identifies the remaining gaps.
2. It gives us the opportunity to be listed as a compatible implementation
on the Jakarta website.
I am moving forward with the receiveBody() implementation, so I estimate we
are currently between 88% and 92%. Some remaining parts will require more
significant effort, such as durable subscribers, which require updates to
the OpenWire protocol and KahaDB internals.
If we can make the TCK runnable via a Maven profile, that would be
excellent, as it would allow us to run it on the CI on a weekly basis.
Thanks again!
Regards,
JB
On Tue, Feb 24, 2026 at 9:02 PM Jean-Louis Monteiro <
jlmonteiro@tomitribe.com> wrote:
> Hi team,
>
> I've been trying to set up the Jakarta Messaging 3.1 TCK on Apache
> ActiveMQ. I should have a PR ready by tomorrow. It won't pass all the tests
> of course, so it won't run on any CI for the moment. But it's interesting
> to get a bit more coverage on ActiveMQ and also good to help filling the
> gaps.
>
> I'm not sure if there is any willingness to become a
> compatible implementation listed on the Jakarta website, but it won't hurt
> either.
>
> We are currently at 90%. My experience on various TCK work is that the last
> tests usually are harder to get to pass.
>
> I'll keep you posted tomorrow when I know more about the first runs.
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
Re: Jakarta Messaging 3.1 TCK
Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
I still have some small fixes to push to the branch I started (see my last
PR).
It's running on my mac currently. I'll add the numbers tomorrow and create
the github issues for it.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Tue, Feb 24, 2026 at 11:57 PM Matt Pavlovich <ma...@apache.org> wrote:
> IIRC, at one points ActiveMQ was able to pass higher than 90% of the TCK
> for JMS 1.1. It may require special config on certain destinations (for
> things like priority that are disabled by default, etc).
>
> Please make a GH issue to track the failing tests, I’m happy to help
> configure a TCK-ready activemq.xml config.
>
> > On Feb 24, 2026, at 2:01 PM, Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> wrote:
> >
> > Hi team,
> >
> > I've been trying to set up the Jakarta Messaging 3.1 TCK on Apache
> > ActiveMQ. I should have a PR ready by tomorrow. It won't pass all the
> tests
> > of course, so it won't run on any CI for the moment. But it's interesting
> > to get a bit more coverage on ActiveMQ and also good to help filling the
> > gaps.
> >
> > I'm not sure if there is any willingness to become a
> > compatible implementation listed on the Jakarta website, but it won't
> hurt
> > either.
> >
> > We are currently at 90%. My experience on various TCK work is that the
> last
> > tests usually are harder to get to pass.
> >
> > I'll keep you posted tomorrow when I know more about the first runs.
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
> For additional commands, e-mail: dev-help@activemq.apache.org
> For further information, visit: https://activemq.apache.org/contact
>
>
>
Re: Jakarta Messaging 3.1 TCK
Posted by Koteswararao Gundapaneni <ap...@gmail.com>.
Hi
I have been working the collection which is active mq
Please approve my request
On Wednesday, February 25, 2026, Matt Pavlovich <ma...@apache.org> wrote:
> IIRC, at one points ActiveMQ was able to pass higher than 90% of the TCK
> for JMS 1.1. It may require special config on certain destinations (for
> things like priority that are disabled by default, etc).
>
> Please make a GH issue to track the failing tests, I’m happy to help
> configure a TCK-ready activemq.xml config.
>
> > On Feb 24, 2026, at 2:01 PM, Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> wrote:
> >
> > Hi team,
> >
> > I've been trying to set up the Jakarta Messaging 3.1 TCK on Apache
> > ActiveMQ. I should have a PR ready by tomorrow. It won't pass all the
> tests
> > of course, so it won't run on any CI for the moment. But it's interesting
> > to get a bit more coverage on ActiveMQ and also good to help filling the
> > gaps.
> >
> > I'm not sure if there is any willingness to become a
> > compatible implementation listed on the Jakarta website, but it won't
> hurt
> > either.
> >
> > We are currently at 90%. My experience on various TCK work is that the
> last
> > tests usually are harder to get to pass.
> >
> > I'll keep you posted tomorrow when I know more about the first runs.
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
> For additional commands, e-mail: dev-help@activemq.apache.org
> For further information, visit: https://activemq.apache.org/contact
>
>
>
Re: Jakarta Messaging 3.1 TCK
Posted by Matt Pavlovich <ma...@apache.org>.
IIRC, at one points ActiveMQ was able to pass higher than 90% of the TCK for JMS 1.1. It may require special config on certain destinations (for things like priority that are disabled by default, etc).
Please make a GH issue to track the failing tests, I’m happy to help configure a TCK-ready activemq.xml config.
> On Feb 24, 2026, at 2:01 PM, Jean-Louis Monteiro <jl...@tomitribe.com> wrote:
>
> Hi team,
>
> I've been trying to set up the Jakarta Messaging 3.1 TCK on Apache
> ActiveMQ. I should have a PR ready by tomorrow. It won't pass all the tests
> of course, so it won't run on any CI for the moment. But it's interesting
> to get a bit more coverage on ActiveMQ and also good to help filling the
> gaps.
>
> I'm not sure if there is any willingness to become a
> compatible implementation listed on the Jakarta website, but it won't hurt
> either.
>
> We are currently at 90%. My experience on various TCK work is that the last
> tests usually are harder to get to pass.
>
> I'll keep you posted tomorrow when I know more about the first runs.
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
For additional commands, e-mail: dev-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact