I finally managed to get to the bottom of this one.
The problem seems to have been that the sending machine's clock (which is
also where the broker is) was 13 minutes behind the receiving machine's
clock and messages were being sent with a TTL of 10 minutes. This seemingly
caused them to just sit
I've also tried removing the filter/selector from the receiver, and it still
seems to receive nothing.
I'm sure it's just something simple and dumb that has suddenly caused this
problem, but I can't figure out what.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Messages-
I've added logging in the receiver and it never seems to receive the message.
Messages are all auto-acknowledge.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Messages-stuck-in-pending-tp4617979p4631844.html
Sent from the ActiveMQ - User mailing list archive at Nabble.co
the selector is:
destinationHostId = '17d7400f-3623-4279-a9d5-5bbb2a56e573' and
MESSAGE_TYPE
is null
Message properties are:
destinationHostId 17d7400f-3623-4279-a9d5-5bbb2a56e573
It's nothing complex.
--
View this message in context:
http://activemq.2283324.n4.nabble.
There are 5 consumers on the queue.
They each have a different filter, but I have checked the filters against
stuck messages, and there are consumer that should match each message.
There is not heavy load, it gets stuck with just one message sent.
If I view consumers in the web admin, the one wh
I have a problem where messages seem to be getting stuck in a pending state.
Initially it seemed they only got stuck in this state if there was no
consumer when the message was sent, and even after a consumer was started,
they just sat there. They then seemingly caused all subsequent messages to
