> Will queues allows us to subscribe multiple messages at same time?
I don't understand what you're asking. Can you clarify?
Justin
On Fri, Jul 2, 2021 at 1:06 PM NawazAli Shaik <
nawazali.sh...@sainsburys.co.uk> wrote:
> Thanks Chris and Justin. One more query, if we create a virtual topic to
Thanks Chris and Justin. One more query, if we create a virtual topic to send
messages to a physical queue I am able to create the subscriber from multiple
nodes.
Will queues allows us to subscribe multiple messages at same time? If yes can
you please let me know the configurations we have to a
It's worth noting that while the options that Chris mentioned (i.e. virtual
topics and composite queues) are technically feasible they are specific to
ActiveMQ "Classic." If you implement them your application will no longer
be portable to any other JMS broker. Generally speaking, application
porta
If you don't want want to use Artemis you can also just look into virtual
topics or composite queues. https://activemq.apache.org/virtual-destinations
On Fri, Jul 2, 2021 at 11:17 AM Justin Bertram wrote:
> The ability to share a JMS subscription like you want was added in JMS 2.0.
> However, Ac
The ability to share a JMS subscription like you want was added in JMS 2.0.
However, ActiveMQ 5.x doesn't support JMS 2.0. You'd need to use ActiveMQ
Artemis instead.
Justin
On Fri, Jul 2, 2021 at 10:06 AM NawazAli Shaik <
nawazali.sh...@sainsburys.co.uk> wrote:
> Hi Robbie,
>
> Thanks for the
Hi Robbie,
Thanks for the response. We are trying to connect from multiple nodes to the
durable subscriber to balance the load but it seems active mqueue is not
allowing connection with same client ID.
If we use different client id from second node it is providing duplicate
message to us. We n
It would seem you aren't failing to subscribe, but rather failing to
create a Connection upon which attempt could even be made to
subscribe. The exception looks to give the reason fairly clearly, it
seems you are trying to create a connection using a ClientID that is
already in use for another conn
Hi Tim,
Yes you are correct we are failing to subscribe the messages from topic. Below
is the error which we are getting:
com.wm.app.b2b.server.jms.JMSSubsystemException: [ISS.0134.9064] Error creating
connection: javax.jms.InvalidClientIDException: Broker:
app-intg-platform-sit-retail-corp-br
Nawaz,
Are your threads failing to subscribe to the destination, or failing to
receive messages as expected after subscribing? You said that enabling the
trigger in the client is failing, so am I right to understand that this is
a failure to subscribe to the topic, not a failure to process message
As JB says, you need to ensure that the messages are sent as persistent
messages and that the broker configures a persistence store whose data will
survive the restart of the container. I'll go into some detail about
various possible options, and if what I write doesn't go deep enough to
answer you
Hi Tim,
The active mq version is recently updated to Apache ActiveMQ 5.16.2. We are
trying to subscribe the messages from active mqueue topic parllely .
In webmethods we have triggers to subscribe the messages from topics/queues, we
are not able to enable the triggers itself from the client sid
Can you please tell us more about what you're doing and in what way it's
not working? Is this a queue or a topic? Are your threads failing to
subscribe to the destination, or failing to receive messages as expected
after subscribing? What behavior are you expecting, and what behavior are
you observ
12 matches
Mail list logo
