activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Closed] (AMQ-3444) Fail Fast or Warn on using fileCursors/fileQueueCursors when <broker persistent="false">
Date Tue, 31 Jul 2012 18:12:34 GMT


Timothy Bish closed AMQ-3444.

       Resolution: Duplicate
    Fix Version/s: 5.7.0

This is resolved by AMQ-3912
> Fail Fast or Warn on using fileCursors/fileQueueCursors when <broker persistent="false">
> ----------------------------------------------------------------------------------------
>                 Key: AMQ-3444
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.5.0
>            Reporter: Jason Whaley
>             Fix For: 5.7.0
> When working with a broker config for a client, we attempted to use fileCursors and fileQueueCursors
on all destinations.  What we noticed when monitoring JMX for specific queues was behavior
of vmCursors.  Once the memoryLimit for an individual destination hit 100%, the broker then
tried to spool the messages to disk but instead failed and the following exceptions were written
to log:
> 2011-08-09 13:50:22,892 [Usage Async Task                   ] ERROR FilePendingMessageCursor
      - Caught an IO Exception getting the DiskList 315_PendingCursor:FLEXNET-RX-REALTIME-QUEUE
> java.lang.NullPointerException
> 	at
> 	at
> 	at
> 	at org.apache.activemq.usage.Usage$
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
> 	at java.util.concurrent.ThreadPoolExecutor$
> 	at
> After eyeing the config a little more we noticed that <broker persistent="false">.
 Turning that back to "true" caused messages to spool to disk as expected.
> This was obviously a misconfiguration, but there was no warning or indication that our
configuration was basically invalid and destined to fail.  At a minimum it would be useful
to have a message at WARN log level that states that fileCursor/fileQueueCursors will fail
if <broker persistent="false">.  

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message