[ 
https://issues.apache.org/jira/browse/QPID-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105311#comment-13105311
 ] 

Keith Wall commented on QPID-2672:
----------------------------------

ServerSessionDelegate has been refactored so unroutable messages are no longer 
written to the store.  In addition, an operational logging message has been 
introduced (EXH-1003) that is used when the an unroutable message is received 
by the Broker.   Operational logging message is backported to the 0-8..0-9-1 
code path too.




> unroutable persistent messages should be immediately removed from or never 
> flushed to the message store
> -------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-2672
>                 URL: https://issues.apache.org/jira/browse/QPID-2672
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: 0.6
>            Reporter: Robbie Gemmell
>            Assignee: Keith Wall
>             Fix For: 0.13
>
>
> At present, persistent messages are put into the message store regardless 
> whether they can/will be enqueued on a queue. When it is determined they 
> cannot be routed, they are not removed from the store. As a result, it is 
> left until startup recovery sequence until they are determined to be orphans 
> and are ejected from the store. This process can dramatically slow startup 
> time and should be undertaken as soon as it is known the message is to be 
> discard (or even just stop them being commited/flushed to the store at all - 
> they should be known to the store though to ensure a message id is assigned).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to