activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Davies <rajdav...@gmail.com>
Subject Re: Prefetch Limit of 1000 .... without acknowledges
Date Thu, 31 Jan 2008 06:11:28 GMT

On Jan 30, 2008, at 11:20 AM, Eric-AWL wrote:

>
> Hi
>
> Context
>
> A "client" process is on "ytsvmx01s" server, Server process is on
> "ytsvmx02s" server (an other server). A duplex network of brokers is  
> made by
> the client configuration.
>
>     <networkConnector name="pool" uri="static:(tcp://ytsvmx02s:61617)"
>                conduitSubscriptions="false"
>                dynamicOnly="true"
>                networkTTL="3"
>                duplex="true"/>
>
>
> An embedded VM client process, with 100 threads.
> - each thread create a temporary queue
> - each thread sends 10 messages, with ReplyTo the temporary queue
>
> 70 threads send message on queue1, 20 on queue2, 10 on queue3.
>
> An embedded VM server process which has 3 listeners (one on queue1,  
> one on
> queue2, one on queue3)
> -each listener listens messages and send with a specific session an  
> answer
> on the temporary queue defined by the "ReplyTo" field.
>
>
> All sessions are in AUTO_ACKNOWLEDGMENT mode.
>
> When the specific session created by the listener which listens to  
> queue1
> (the most active queue) send exactly 1000 messages (so, on 70  
> differents
> temporary queues), I have a "prefetch limit" in client logfile  
> (log4j debug)
> and no other messages can be sent to queue1.
>
> Other threads continue to send on queue2 and queue3.
>
> You will find the logfile in
> http://www.nabble.com/file/p15180095/client100.log client100.log
>
>
> and the last message sent by ytsvmx02s "queue1" session is
>
> DEBUG ActiveMQMessageConsumer        -
> ID:ytsvmx01s-44878-1201690176105-3:1:115:1 received message:  
> MessageDispatch
> {commandId = 4292, responseRequired = false, consumerId =
> ID:ytsvmx01s-44878-1201690176105-3:1:115:1, destination =
> temp-queue://ID:ytsvmx01s-44878-1201690176105-3:1:114, message =
> ActiveMQTextMessage {commandId = 2440, responseRequired = false,  
> messageId =
> ID:ytsvmx02s-52597-1201689535145-2:1:2:1000:1, originalDestination =  
> null,
> originalTransactionId = null, producerId =
> ID:ytsvmx02s-52597-1201689535145-5:0:1:1, destination =
> temp-queue://ID:ytsvmx01s-44878-1201690176105-3:1:114, transactionId  
> = null,
> expiration = 0, timestamp = 1201689604289, arrival = 0, brokerInTime =
> 1201690235463, brokerOutTime = 1201690235463, correlationId = null,  
> replyTo
> = null, persistent = true, type = null, priority = 4, groupID = null,
> groupSequence = 0, targetConsumerId = null, compressed = false,  
> userID =
> null, content = org.apache.activemq.util.ByteSequence@1410a85,
> marshalledProperties = null, dataStructure = null, redeliveryCounter  
> = 0,
> size = 8222, properties = null, readOnlyProperties = true,  
> readOnlyBody =
> true, droppable = false, text = null}, redeliveryCounter = 0}
>
> and there isn't any message  
> "ID:ytsvmx02s-52597-1201689535145-2:1:2:1001:1"
> after this one and you will see that there is
> DEBUG PrefetchSubscription           - Prefetch limit.
> just after in the logfile.
>
> Eric-AWL
> -- 
> View this message in context: http://www.nabble.com/Prefetch-Limit-of-1000-....-without-acknowledges-tp15180095s2354p15180095.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Hi eric - can you replicate this in a single junit test case - and  
attach it to a jira issue - we will be able to track and resolve it  
much quicker if you do


Rob Davies
'Go further faster with Apache Camel!'
http://rajdavies.blogspot.com/




Mime
View raw message