activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Israel (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMQ-4136) Broker freezes on peak burst producer persistent message delivery
Date Thu, 25 Oct 2012 21:35:12 GMT
David Israel created AMQ-4136:
---------------------------------

             Summary: Broker freezes on peak burst producer persistent message delivery
                 Key: AMQ-4136
                 URL: https://issues.apache.org/jira/browse/AMQ-4136
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.6.0
         Environment: Java 1.6.0_35
Mac OSX 10.7.5
            Reporter: David Israel


Expected: throttled messages when tempStorage reaches 100%
Actual: broker hangs and no longer delivers messages and cannot be cleanly shutdown

Configuration:
- /conf/activemq.xml configuration: memoryUsage: 200MB, storeUsage: 1GB, tempUsage: 400MB
- test configuration (/example/build.xml): max (# of messages): 65000, messageSize: 10000
-> total message size: 65000 * 10000 bytes = 650 MB
Result: 
- burst of 65000 messages to queue, initially loads into memory but quickly gets dumped to
tempStorage (12% memoryUsage)
- messages persisted in database
- producer throttling does NOT occur, potentially b/c memoryUsage is at 0% in this peak/burst
scenario when activmq stops responding
- activemq process hangs at 104% tempUsage, 0% memoryUsage, and can't be shutdown without
force kill

commands:
Start amq:
/bin$ ./activemq console

start producer:
ant producer -Ddurable=true -DsleepTime=0

(Bug experienced with higher sleep times also.)

if you want to use consumers:
ant consumer -Durl=tcp://localhost:61616?jms.prefetchPolicy.queuePrefetch=1

- watch memory and disk usage in jconsole
[10/25/12 2:28:07 PM] Joel Fischer: blog notes about expected behavior of tempStorage:
http://tmielke.blogspot.com/2011/02/observations-on-activemqs-temp-storage.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message