Re: [xmlblaster-devel] How do I get rid of QueuePropertyBase.checkConsistency

[Michele Laghi <michele at laghi.eu>]

Hi Matt,

500 should absolutely not be a problem.

What you specify in queue/history/maxEntriesCache affects (only
marginally) the RAM memory. queue/history/maxEntries only affects
database resources so it should not be a problem setting it high (also
100000 should not be a problem).

The parameters which most affect memory consumption are:
persistence/msgUnitStore/maxEntriesCache and
persistence/msgUnitStore/maxBytesCache

since these contain the real "meat" of the messages. History queues,
callback queues and subject queues currently only store references of
the real content.

Regards
Michele




Matthew Sargent wrote:
> Michele,
> 
> Thanks for the info, I do indeed need to keep every message that was
> published available since when a client comes along and makes a subscription
> they will want all the old messages for that topic as well as any new ones
> that will come along. We would rarely need to hold more than 30 messages,
> but there are cases where more than 100 will be published. Is there any
> problem setting the history to 500 since we would rarely use that many?
> 
> matt
> 
> ----- Original Message ----- 
> From: "Michele Laghi" <michele at laghi.eu>
> To: <xmlblaster-devel at server.xmlBlaster.org>
> Sent: Wednesday, May 31, 2006 1:43 PM
> Subject: Re: [xmlblaster-devel] How do I get rid of
> QueuePropertyBase.checkConsistency
> 
> 
>> Hi Matt,
>> great that you found the problem. Of course if you need more entries in
>> the history you can change this setting. The history queue however is
>> only used in case you want messages which have been published before you
>> subscribed (or before you invoked a get).
>>
>> You can publish how many messages you want. The history queue will only
>> keep the last ones (up to what you specified as maximum).
>>
>> Note that if you subscribed before a publish is made you can ignore the
>> history queue since your messages will be hold by your (session
>> dedicated) callback queue.
>>
>> Regards
>> Michele
>>
>>
>> Matthew Sargent wrote:
>>
>>> OK, I checked my .properties file and it had the correct settings, so I
>>> looked in my code to publish and I removed this code:messages:
>>>
>>>             HistoryQueueProperty prop = new
> HistoryQueueProperty(this.glob,
>>> null);
>>>             prop.setMaxEntries(1000);
>>>             topicProperty.setHistoryQueueProperty(prop);
>>>
>>> and now the log says (which I assume is good):
>>>
>>> INFO | jvm 1 | 2006/05/31 12:42:53 | May 31, 2006 12:42:52 PM INFO
>>> 21-XmlBlaster.SOCKET.tcpListener-Cad2Cap
> org.xmlBlaster.engine.TopicHandler
>>> administrativeInitialize: New topic is ready, history/maxEntries=10,
>>> persistence/msgUnitStore/maxEntries=100000000
>>>
>>> I am concerned however, that 10 history entries is not enough, will I
> still
>>> be able to publish up to 100 messages on a topic?
>>>
>>> Matt
>>>
>>> ----- Original Message ----- 
>>> From: "Michele Laghi" <michele at laghi.eu>
>>> To: <xmlblaster-devel at server.xmlBlaster.org>
>>> Sent: Tuesday, May 30, 2006 6:02 PM
>>> Subject: Re: [xmlblaster-devel] How do I get rid of
>>> QueuePropertyBase.checkConsistency
>>>
>>>
>>>> Hi Matt,
>>>> its difficult to say what is wrong but my guess is that something is
>>>> still wrong in your configuration or you have some persistent stuff
> from
>>>> previous runs.
>>>>
>>>> Please make sure that you have in your ${HOME}/xmlBlaster.properties
>>>> file the following:
>>>> a)
>>>> queue/history/maxEntriesCache = 10
>>>> queue/history/maxEntries = ${queue/history/maxEntriesCache}
>>>>
>>>> (and only one time)
>>>>
>>>> b)
>>>> delete in your temp directory (on *nix ${HOME}/tmp/) all xmlBlaster*
> and
>>>> client* files (this way you make sure you don't have old stuff around)
>>>>
>>>> c)
>>>> make sure the xmlBlaster.properties file you checked on a) is the one
>>>> which is used. If you are unsure try to start the xmlBlaster with:
>>>>
>>>> java org.xmlBlaster.Main -queue/history/maxEntriesCache 10\
>>>> -queue/history/maxEntries 10
>>>>
>>>> (all in one line)
>>>>
>>>> And if this does not help please send to me directly your configuration
>>>> file (xmlBlaster.properties) and a log file (possibly with -logging
> FINE).
>>>> Regards
>>>> Michele
>>>>
>>>>
>>>>
>>>>
>>>> Matthew Sargent wrote:
>>>>> I keep getting the following message, and I think I have configured
>>> things correctly, but I still get it. Can anyone help?
>>>>> [org.xmlBlaster.util.qos.storage.QueuePropertyBase.checkConsistency]
>>> history maxEntriesCache=10 is bigger than maxEntries=0, we reduce
>>> maxEntriesCache to maxEntries and continue.
>>>>> Matt
>>>
>>>
>>
> 
> 
>