I have something in code which demonstrates how to construct the embedded
broker and it is working. However I am still not sure how to address it
(vm://ip address?). How would I commit this as a demo?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/How-to-configure-embedd
I have set the WILL message to send a LOST payload on a status topic which I
have defined (QoS = 2). The keep alive time is set to 20 seconds. According
to the MQTT spec
The Will message defines that a message is published on behalf of the client
by the
server when either an I/O error is encounter
I have established a connection to an embedded running of the MQTT server and
am able to publish and subscribe to messages from the remote client side.
However, when I invoke an MqttClient.disconnect() from the client side
(using the paho MqttClient) I get the following message from the MQTT server
It is definitely not an ActiveMQ issue... You can look into PKI software from
various vendors or try to implement something yourself for example using web
services...
Sent from my HTC One on the Verizon Wireless 4G LTE network
- Reply message -
From: "darkrwe [via ActiveMQ]"
To: "mikme
Hi, thanks for answer. I will try the configuration you proposed later. But
today I noticed that the number of messages left in the queue is exactly the
same as the number of messages dispatched to consumers.
5056 messages left in queue
when I list queue connections from
http://localhost:8161/admi
lazy means doing it async and possibly in a batch (so waiting for the
next ack or some % of the prefetch) . Having received the message at
the application level does not ensure that the broker knows about the
receipt.
In the event of a connection failure, the app can think it won't see
the message
don't use spring jms template. Just use a simple message producer and
transacted session.
send(..);send(..);...;session.commit()
On 29 November 2013 05:48, Sophia Wright wrote:
> Yes, there is no documentation provided by ActiveMQ, to use batch message
> receiving.. Please help !!
>
>
>
> --
> V
DLQ ( dead letter) is for failed messages, so messages that are acked
as poison - the consumer saying I cannot delivery this message, I have
retried and it gets rolledback of there is an exception.
If there is client ack, then the message is acked. There is no DLQ processing.
So DLQ processing is
Hi,
I'm new to JMS, can somebody please tell me differences between the Spring's
CachingConnectionFactory vs ActiveMQ's PooledConnectionFactory? Which is
suited for which use case? Benefits ? Drawbacks.
Many thanks in advance!
Thanks,
Sophia
--
View this message in context:
http://activemq.22
