so, you're seeing this when you close the consumer?
Perhaps the server consumer has been closed.. and your client is
issuing an ack on the message but the consumer had already redelivered
the messages when the disconnect event happened?
If that's the case the message could be ignored.. you could/
ActiveMQ 5.12
When messages are dispatched to a consumer, how long will the broker wait
before it considers the consumer "slow" assuming the consumer does not ack
the message and the connection remains active? We're not using any slow
consumer strategy in the broker, so when I found this I wasn't
You sent this same message about CONNECT messages 2 weeks ago, and the
answer is the same as before. All current releases only support
intercepting PUBLISH messages. However, the code has been changed so all
message types are now interceptable. If you want this functionality I
suggest you just b
I added an mqtt interceptor into my artemis broker in order to intercept mqtt
client subscription:
public class SimpleMQTTInterceptor implements MQTTInterceptor
{
@Override
public boolean intercept(final MqttMessage mqttMessage,
RemotingConnection connection) throws ActiveMQE
Hi Oliver
In that case I'd suggest when speaking with a vendor you ask them to provide
contacts of organisations willing to discuss the benefits they've had with you,
via other channels.
Cheers
Mike
Sent from my iPhone
> On 25 Aug 2017, at 10:44, Oliver B. Fischer wrote:
>
> Hi Mike,
>
>
Hi Mike,
you are right. We are aware of pros and cons you mentioned. The actual
reason for asking here on the list is/was to find people who know if it
is worth to pay for JBoss AMQ or not. Such a decision is not easy in our
environment because of the consequences.
But thanks a lot for your
