thanks a lot .. yes this worked.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
We are using n/w connectors between 3 brokers
is
A->B
A->C
B->A
B->C
C->A
C->B
also we are using synchronous request and reply pattern using camel to send
and receive message in temp queue.
we have question is it good to use networkTTL = 2 in above configuration ?
will it work properly or
is
hi Justin,
just wanted an insight on what i was doing.
We are trying to disable curl/hawtio access to one of our production artemis
instances and only to dead letter queue. I tried one of the suggestions that
you had put in
http://activemq.2283324.n4.nabble.com/Disable-access-to-Dead-Letter-Queue
Are you sending the messages with durable = true set on them?
On Feb 8, 2018 7:21 AM, "bittusrivastava" wrote:
> one thing i want to add that i am using amqp.netlite library for amqp
> protocol
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>
one thing i want to add that i am using amqp.netlite library for amqp
protocol
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi,
I have configured activeMq to use persistence mode like below
http://activemq.apache.org/schema/core";
brokerName="localhost" persistent="true" useShutdownHook="false"
dataDirectory="${activemq.data}">
-