Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of gary.tully@gmail.com
 designates 209.85.218.215 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=cieufJsSyJU+Idx5ocAGRNtREth5cMQHPo78xkQTd5RWDRDXxrl3hvkCrTWp/BuTaM
         ultttZg+j+JNgslFbT7l9sM+eHQh6cdPBofiyPMqBafIVvzLwe+5A8Fw9uErPm0370Xi
         /0BLXe3SpVqwk5rZfW/dGCtfY2ojW67tMs+kk=
MIME-Version: 1.0
In-Reply-To: <26392757.post@talk.nabble.com>
References: <26392757.post@talk.nabble.com>
Date: Wed, 18 Nov 2009 09:49:57 +0000
Message-ID: <3a73c17c0911180149q15eab210kff0a75527fba8746@mail.gmail.com>
Subject: Re: Is property JMSActiveMQBrokerInTime really correct in Activemq
	trunk from svn checkout
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org
Content-Type: multipart/alternative; boundary=0003255553ae55fce80478a22a41

--0003255553ae55fce80478a22a41
Content-Type: text/plain; charset=ISO-8859-1

jmsTimeStamp is set on the client, by the client connection that does a
send.
JMSActiveMQBrokerInTime is set by the broker when it receives the message
and JMSActiveMQBrokerOutTime is set by the broker when it dispatched (or
just before) a message.

So if you appear to have not delivered messages, it looks like they have
been delivered but not acked, as the broker has dispatched them to a
consumer up to its prefetch limit.

2009/11/17 praveen.sharma <praveen.sharma@ll.mit.edu>

>
> Couple of questions:
>
> For jmsMessage
> (1) What is the relation between jmsTimeStamp, and properties:
> JMSActiveMQBrokerInTime, and JMSActiveMQBrokerOutTime?
>
> (2) Which one  is more accurate jmsTimeStamp, and properties:
> JMSActiveMQBrokerInTime?  Reason for asking this question is that I have
> messages in the queue (seen from jconsole) that are not delivered, and yet
> JMSActiveMQBrokerInTime = JMSActiveMQBrokerOutTime.  However, jmsTimeStamp
> gives a different value.
>
> I extracted these values as
>  JmsMessage msg = (JmsMessage) exch.getIn();
> msg.getJmsMessage().getJMSTimestamp()
>  msg.getJmsMessage().getLongProperty("JMSActiveMQBrokerInTime");
> msg.getJmsMessage().getLongProperty("JMSActiveMQBrokerOutTime");
>
>
> Sample output:
> jmsExpiration: 1258474190831 jmsTimeStamp: 1258474189831 jmsPriority: 7
> jmsDeliveryMode: 2 jmsMsgID: ID:padua-44786-1258474186761-0:26:1:1:1
> defaultPriority: 4 defaultTTL: 0 defaultDeliveryMode: 2...........100000
> Latency0.020777777777777777 Jitter 0.010979222222222224 BrokerInTime
> 1258474189832 BrokerOutTime 1258474189832 jmsBrokerQueueLatency 0
> ...........100000
>  jmsExpiration: 1258474190942 jmsTimeStamp: 1258474189942 jmsPriority: 7
> jmsDeliveryMode: 2 jmsMsgID: ID:padua-44786-1258474186761-0:27:1:1:1
> defaultPriority: 4 defaultTTL: 0 defaultDeliveryMode: 2...........100000
> Latency0.020392857142857143 Jitter 0.009979607142857142 BrokerInTime
> 1258474189943 BrokerOutTime 1258474189943 jmsBrokerQueueLatency 0
>
> --
> View this message in context:
> http://old.nabble.com/Is-property-JMSActiveMQBrokerInTime-really-correct-in-Activemq-trunk-from-svn-checkout-tp26392757p26392757.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 
http://blog.garytully.com

Open Source Integration
http://fusesource.com

--0003255553ae55fce80478a22a41--