activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: No cleanup on scheduler logs
Date Mon, 30 Nov 2015 21:34:49 GMT
On 11/30/2015 04:31 PM, Tim Bain wrote:
> Ah, good to know.  I knew about the 5.12 incompatibility with the new
> version of Openwire, but didn't know about that change in 5.11.  Your
> description makes it sound like the change you referenced affects only the
> scheduler store but not the main store; is that accurate?

Yes, the scheduler store is a separate store from the main KahaDB store,
it is based on the KahaDB design now with recovery options similar to
the main store. 

> On Nov 30, 2015 7:37 AM, "Timothy Bish" <tabish121@gmail.com> wrote:
>
>> On 11/30/2015 08:55 AM, Tim Bain wrote:
>>> If you copy the 5.11.1 data files onto a test server and start 5.9.1
>> there
>>> (using them), what happens?
>> Your broker probably crashes as the scheduler store was rewritten for
>> 5.11.0 to provide recovery options from the journal on index corruption.
>>
>>> On Nov 30, 2015 5:09 AM, "Richard Sinek" <rsinek@intouchgps.com> wrote:
>>>
>>>> I have several instances of 5.11.1 where cleanup is not occurring on
>>>> scheduler logs in the data/localhost/scheduler folder. The log files
>> data
>>>> back to the instance creation. I have enabled the kahadb logging and it
>>>> never shows those files as a candidate for garbage collection.
>>>>
>>>> log4j.appender.kahadb=org.apache.log4j.RollingFileAppender
>>>> log4j.appender.kahadb.file=${activemq.base}/data/kahadb.log
>>>> log4j.appender.kahadb.maxFileSize=1024KB
>>>> log4j.appender.kahadb.maxBackupIndex=5
>>>> log4j.appender.kahadb.append=true
>>>> log4j.appender.kahadb.layout=org.apache.log4j.PatternLayout
>>>> log4j.appender.kahadb.layout.ConversionPattern=%d [%-15.15t] %-5p
>>>> %-30.30c{1} - %m%n
>>>> log4j.logger.org.apache.activemq.store.kahadb.MessageDatabase=TRACE,
>> kahadb
>>>>
>>>> I have one instance of 5.9.1 that has the same configuration but the
>>>> scheduler logs are cleaned up as expected.
>>>>
>>>> Are there any known bugs or new configuration settings that apply in
>> later
>>>> versions?
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>>
>> http://activemq.2283324.n4.nabble.com/No-cleanup-on-scheduler-logs-tp4704382.html
>>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>>
>>
>> --
>> Tim Bish
>> Sr Software Engineer | RedHat Inc.
>> tim.bish@redhat.com | www.redhat.com
>> twitter: @tabish121
>> blog: http://timbish.blogspot.com/
>>
>>


-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.bish@redhat.com | www.redhat.com 
twitter: @tabish121
blog: http://timbish.blogspot.com/


Mime
View raw message