Thanks Olivier - please let us know if the latest snapshot works!

On Jan 21, 2008, at 7:10 AM, Olivier Bigard wrote:


Hi,

Here is the extract of my "activemq.xml" configuration file:

   <destinationPolicy>
     <policyMap>
       <policyEntries>
         <policyEntry queue=">" producerFlowControl="false">
           <dispatchPolicy>
                 <simpleDispatchPolicy/>
           </dispatchPolicy>
         </policyEntry>
       </policyEntries>
     </policyMap>
   </destinationPolicy>

I put this part at the beginning of the file, just after the "broker" tag. I also tested with the exact name of the queue I'm using in my testcase...
still the same freeze...

Today I'll try with the last SNAPSHOT.

Thank you



Juergen.Schumacher wrote:

Hi,

do you really use a topic named FOO.* in your tests?
You probably will have to adapt the topic="..." attribute
of <policyEntry> to your topic name - or replace it with
queue="..." if you are using a queue.

Cheers,
Jürgen

-----Original Message-----
From: Olivier Bigard [mailto:[EMAIL PROTECTED]
Sent: Friday, January 18, 2008 2:15 PM
To: users@activemq.apache.org
Subject: Re: High message frequency causes ActiveMQ to freeze


We retry our testcase with the following lines in "activemq.xml" file to
disable "flow control":

<destinationPolicy>
     <policyMap>
       <policyEntries>

         <policyEntry topic="FOO.>" producerFlowControl="false"
memoryLimit="1mb">
           <dispatchPolicy>
             <strictOrderDispatchPolicy/>
           </dispatchPolicy>
           <subscriptionRecoveryPolicy>
             <lastImageSubscriptionRecoveryPolicy/>
           </subscriptionRecoveryPolicy>
         </policyEntry>

       </policyEntries>
     </policyMap>
</destinationPolicy>

but it doesn't seem to solve the problem: ActiveMQ still freezes after
some messages...




--
View this message in context: 
http://www.nabble.com/High-message-frequency-causes-ActiveMQ-to-freeze-tp14919292s2354p14992214.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Reply via email to