qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Peter <richard.pe...@raytheon.com>
Subject Re: 0.18 Java broker not persisting message to derby store
Date Mon, 04 Mar 2013 19:30:56 GMT
I should say it didn't as of version 0.8.  We are upgrading from Qpid 
C++ Broker 0.8 with java/c++/python 0.8 clients, which did not require 
persistent to be set on the message.  Our project has been running this 
way for a couple years and persistent recovery has worked perfectly.

Richard

On 03/04/2013 12:09 PM, Rajith Attapattu wrote:
> On Mon, Mar 4, 2013 at 12:54 PM, Richard Peter
> <richard.peter@raytheon.com>  wrote:
>> Ok, this wasn't an issue with the C++ broker, if a queue was marked durable
>> any message was persisted.  Thanks for the clarification.
> This is not correct. You need to mark the the message as persistent in
> order for it to be written to disk.
>
> Rajith
>
>>
>> On 03/04/2013 10:07 AM, Robbie Gemmell wrote:
>>> Hi Richard,
>>>
>>> The queue statistics suggest that you are not sending persistent messages:
>>> "persistentEnqueuedMessages" : 0,
>>> "totalEnqueuedMessages" : 161134,
>>>
>>> Non-persistent messages are only ever stored in memory on the broker, and
>>> it will only recover persistent messages which are sent to durable queues.
>>>
>>> Robbie
>>>
>>>
>>> On 4 March 2013 15:27, Richard Peter<richard.peter@raytheon.com>   wrote:
>>>
>>>> I noticed that 0.18 Java Broker does not appear to be persisting message
>>>> to the derby store.  Running tests to verify memory thresholds in a
>>>> disaster recovery situation.  Had 100k+ messages on a durable queue with
>>>> no
>>>> consumers.  When I bounced QPID, the memory usage was almost none and
>>>> noticed the log wasn't recovering any messages:
>>>>
>>>> QPID2013-03-04 09:19:03,789 INFO  [main] (Log4jMessageLogger.java:73) -
>>>> [Broker] [vh(/edex)/ms(**DerbyMessageStore)] TXN-1004 : Recovery Start
>>>> 2013-03-04 09:19:03,808 INFO  [main] (Log4jMessageLogger.java:73) -
>>>> [Broker] [vh(/edex)/ms(**DerbyMessageStore)] TXN-1005 : Recovered 0
>>>> messages for queue external.dropbox
>>>> 2013-03-04 09:19:03,809 INFO  [main] (Log4jMessageLogger.java:73) -
>>>> [Broker] [vh(/edex)/ms(**DerbyMessageStore)] TXN-1006 : Recovery Complete
>>>> : external.dropbox
>>>> 2013-03-04 09:19:03,817 INFO  [main] (Log4jMessageLogger.java:73) -
>>>> [Broker] [vh(/edex)/ms(**DerbyMessageStore)] TXN-1006 : Recovery Complete
>>>>
>>>>
>>>> Dug a little more and none of my durable queues are persisting.  Anything
>>>> I'm missing?  I do have the store configured in my virtualhosts.xml:
>>>>
>>>> <store>
>>>> <class>org.apache.qpid.server.**store.derby.DerbyMessageStore<**/class>
>>>> <environment-path>${QPID_WORK}**/messageStore</environment-**path>
>>>> </store>
>>>>
>>>> Here is a sample from the rest interface:
>>>>
>>>> {
>>>>     "id" : "505024de-642d-3572-a80c-**750a1b9819e9",
>>>>     "name" : "external.dropbox",
>>>>     "state" : "ACTIVE",
>>>>     "durable" : true,
>>>>     "lifetimePolicy" : "PERMANENT",
>>>>     "type" : "standard",
>>>>     "exclusive" : false,
>>>>     "maximumDeliveryAttempts" : 0,
>>>>     "queueFlowControlSizeBytes" : 0,
>>>>     "queueFlowResumeSizeBytes" : 0,
>>>>     "queueFlowStopped" : false,
>>>>     "alertThresholdMessageAge" : 60000,
>>>>     "alertThresholdMessageSize" : 2117632,
>>>>     "**alertThresholdQueueDepthBytes" : 5294080,
>>>>     "**alertThresholdQueueDepthMessag**es" : 10000,
>>>>     "alertRepeatGap" : 30000,
>>>>     "statistics" : {
>>>>       "unacknowledgedBytes" : 0,
>>>>       "bindingCount" : 2,
>>>>       "queueDepthBytes" : 12697432,
>>>>       "queueDepthMessages" : 161134,
>>>>       "totalEnqueuedBytes" : 12697432,
>>>>       "persistentDequeuedBytes" : 0,
>>>>       "consumerCount" : 0,
>>>>       "unacknowledgedMessages" : 0,
>>>>       "consumerCountWithCredit" : 0,
>>>>       "totalDequeuedBytes" : 0,
>>>>       "totalDequeuedMessages" : 0,
>>>>       "persistentEnqueuedMessages" : 0,
>>>>       "totalEnqueuedMessages" : 161134,
>>>>       "persistentEnqueuedBytes" : 0,
>>>>       "persistentDequeuedMessages" : 0
>>>>     },
>>>>     "bindings" : [ {
>>>>       "id" : "d24e4587-ee99-3086-bc34-**056be3226f09",
>>>>       "name" : "external.dropbox",
>>>>       "durable" : true,
>>>>       "lifetimePolicy" : "PERMANENT",
>>>>       "exchange" : "amq.direct",
>>>>       "queue" : "external.dropbox",
>>>>       "arguments" : {
>>>>       }
>>>>     }, {
>>>>       "id" : "ac57bb00-a0aa-3c4e-a6d9-**276d3d520f39",
>>>>       "name" : "external.dropbox",
>>>>       "durable" : true,
>>>>       "lifetimePolicy" : "PERMANENT",
>>>>       "exchange" : "<<default>>",
>>>>       "queue" : "external.dropbox",
>>>>       "arguments" : {
>>>>       }
>>>>     } ]
>>>> }
>>>>
>>>> Thanks,
>>>> Richard
>>>>
>>>> Thanks,
>>>> Richard
>>>>
>>>> ------------------------------**------------------------------**---------
>>>> To unsubscribe, e-mail:
>>>> users-unsubscribe@qpid.apache.**org<users-unsubscribe@qpid.apache.org>
>>>> For additional commands, e-mail: users-help@qpid.apache.org
>>>>
>>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>>
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message