Hi All,
Thank you for the suggestions.
With regard to other brokers supporting JMS 2.0, ActiveMQ Artemis allows
the creation of multiple shared consumers on a single JMSContext and
messages are received as expected. However even the shared consumer example
made available in Artemis [1] uses two J
Hi Maryam,
On Mon, Jun 19, 2017 at 5:09 PM, Maryam Ziyad wrote:
> Hi All,
>
> We have implemented support for basic functionality with JMS 2.0 as
> proposed [1].
>
> This includes partial support for JMSContext, JMSProducer and JMSConsumer
> with support for:
>
>- Simple synchronous send/rec
Shall we also check how the other brokers handle this ?
The JMS 2.0 specification mentions that the restriction of not allowing
shared topic subscriptions was removed because "it did not allow sharing of
work among multiple connections, threads or JVMs" (JMS_SPEC-40). Thus even
though not explicit
Hi All,
We have implemented support for basic functionality with JMS 2.0 as
proposed [1].
This includes partial support for JMSContext, JMSProducer and JMSConsumer
with support for:
- Simple synchronous send/receive
- Asynchronous receive
- Durable subscription
We will now be working o
Hi Pamod,
Will there be any frame definitions we might need to change in the existing
> AMQP 0_91 to work with JMS 2.0 ?
>
We have not had to modify any frames so far, to provide basic support for
JMS 2.0. However since we are still to implement the new functionality
provided by JMS 2.0, we may h
Hi Maryamm,
Will there be any frame definitions we might need to change in the existing
AMQP 0_91 to work with JMS 2.0 ?
Thanks,
Pamod
On Tue, Jun 6, 2017 at 8:36 AM, Maryam Ziyad wrote:
> Hi All,
>
> We are currently working on providing JMS 2.0 support with MB4.
>
> *JMS 1.1 vs JMS 2.0*
>
>
