Is this related to http://issues.apache.org/activemq/browse/AMQ-1078 ?

On 1/26/07, Waves <[EMAIL PROTECTED]> wrote:

ActiveMQ:4.1.0, spring2.0, jencks1.3. We used jencks2.0 later, the problem
still existed.

Christopher G. Stach II wrote:
>
> Waves wrote:
>> (1)Environment: use Activemq and Spring to send message, use Activemq and
>> Jencks to receive message asynchronously. We use jconsole to monitor.
>> (2)Phenomenon:
>>     We use non-persistent queue to send message asynchronously, use
>> jencks
>> to receive message asynchronously, jencks use multiple-session and
>> consumer's prefetch.
>>     Every time we find that there are always some messages non-delivered
>> in
>> the queue, like "jconsole_information.doc".We have read the Activemq
>> code,
>> find that only when client send "ACK" to broker ,the broke will deal with
>> the message in the queue and the "DequeueCount" in JMX will be updated.
>> So I
>> suspect that the consumer don't send "ACK" message to the broker, so the
>> last messages don't be delivered from broker to client.
>>
>> (2)The attachment file is our client configuration file.
>> (3)The attachment image is jconsole's JMX information.
>>
>>
>> http://www.nabble.com/file/5918/jms-spring-application.xml
>> jms-spring-application.xml
>> http://www.nabble.com/file/5937/jconsole_information.doc
>> jconsole_information.doc
>
> What version?
>
> --
> Christopher G. Stach II
>
>
>

--
View this message in context: 
http://www.nabble.com/Use-jencks-to-async-receive-message%2C-there-are-always-some-messages-are-left-in-the-queue-tf3120301.html#a8648427
Sent from the ActiveMQ - User mailing list archive at Nabble.com.




--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/

Reply via email to