[
https://issues.apache.org/jira/browse/BOOKKEEPER-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401982#comment-13401982
]
Uma Maheswara Rao G commented on BOOKKEEPER-296:
------------------------------------------------
{quote}
log4j:WARN No such property [maxFileSize] in
org.apache.log4j.DailyRollingFileAppender.
log4j:WARN No such property [maxBackupIndex] in
org.apache.log4j.DailyRollingFileAppender.
{quote}
I am seeing this in test log4j.properties. I suggested to file a separate JIRA
for log related changes in my above comment. This JIRA mainly providing the
scripts for stop.
Is it fine with you Sijie? If yes, Nijel, could you please file a JIRA for
log4j fixes?
> It's better provide stop script for bookie
> ------------------------------------------
>
> Key: BOOKKEEPER-296
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-296
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Affects Versions: 4.0.0
> Reporter: Brahma Reddy Battula
> Attachments: BOOKKEEPER-296.1.patch, BOOKKEEPER-296.2.patch,
> BOOKKEEPER-296.3.patch, BOOKKEEPER-296.patch
>
>
> Currently there is no command to stop bookie in 4.0.0..It's better to provide
> stop command for bookie.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
