users@glassfish.java.net

un-acked messages in jms queues

From: <forums_at_java.net>
Date: Tue, 3 May 2011 17:15:30 -0500 (CDT)

Hello, I'm trying to find out, why (sporadic) some of the jms messages are
hanging in the jms queues in state "unacknowledged". I don't see any problems
on the cosumer side (MDBs deployed in GF 3.1 Cluster, JMS (OpenMQ 4.5)
confgured as LOCAL). I'd like to ask, how to proceed on the JMS side: 1. how
to increase verbosity of the OpenMQ Brokers? Starting with
-Dimq.log.console.output=INFO was not very helpful. 2. how to configure
OpenMQ Cluster to make sure, that the messages will be load-balanced? We are
running in RANDOM-mode and imq.autocreate.queue.localDeliveryPreferred is set
to false and imq.autocreate.queue.consumerFlowLimit set to 50. However, the
differences in number of stored messages are huge. 3. how to decipher message
ID? I see it consists of an IP - is it a producer- or broker- IP? And
assuming it is a broker IP - it seems it is the IP of the original broker
(which has stored the message at first and than evtl. forwared). thanks in
advance for any hints, makiey


--
[Message sent by forum member 'makiey']
View Post: http://forums.java.net/node/798046