Thank you guys so much!
On Tue, Sep 11, 2018 at 2:50 PM Timothy Bish wrote:
> On 08/30/2018 07:10 PM, Dan Langford wrote:
> > thanks for looking into this. what is the proper way to force for
> testing a
> > redelivery that goes back to the broker without transactions? its
> probably
> > like kil
On 08/30/2018 07:10 PM, Dan Langford wrote:
thanks for looking into this. what is the proper way to force for testing a
redelivery that goes back to the broker without transactions? its probably
like killing the session or connection. that would be if we wanted to test
if non-transacted redeliver
I was able to figure out the issue. The message needed to be in a certain
format so it was getting stuck enqueued
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
I want to know which of my consumers aren't processing data fast enough and
causing messages to expire. I am listening to the advisory
ActiveMQ.Advisory.Expired.Topic. Can I get the consumer id or at least the
client Id of the intended recipient of an expired message? Thank you.
--
Sent from: ht
We need your help to make the Apache Washington DC Roadshow on Dec 4th a
success.
What do we need most? Speakers!
We're bringing a unique DC flavor to this event by mixing Open Source
Software with talks about Apache projects as well as OSS CyberSecurity,
OSS in Government and and OSS Career
I'm glad to hear you solved the problem, and thanks for posting the
solution in case someone else hits this.
Tim
On Mon, Sep 10, 2018, 5:10 PM mtod wrote:
> I found the issue I was missing the "userRoleName=dummyUserRoleName"
> key/value in the login.config
>
> It was throwing an exception when
It means that the consumer did not acknowledge the messages, which might or
might not be because it didn't receive them.
Are any selectors in use for this destination? Those could cause
non-matching messages to not be delivered to the consumer.
Tim
On Mon, Sep 10, 2018, 10:02 AM jsantew wrote:
It sounds like your consumer is not connected. Do you in fact have a TCP
connection from the consumer process to the broker's ActiveMQ port
(typically 61616)?
And what do you see in the logs of both processes (broker and consumer)?
Tim
On Mon, Sep 10, 2018, 10:02 AM jsantew wrote:
> I am tryin
Hi!
Sad to be the only one :(.
I will try if approach suggested by you satisfies my needs (I don't want to
overcomplicate whole setup)
Thanks for response.
I will bump it when I found easiest way to solve my problem :)
Kind regards,
Cezary
--
Sent from: http://activemq.2283324.n4.nabble.com
