[
http://jira.qos.ch/browse/LBCLASSIC-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12341#action_12341
]
Stuart Roebuck commented on LBCLASSIC-234:
------------------------------------------
Just by way of confirmation I too have been encountering this issue. It took
me a long time to track down, largely because I just wasn't expecting logback
to be the issue. Like Niklas, I found that our server would typically lock up
within any 48 hour period and basically needed a restart. Thread dumps showed
the code locked on ch.qos.logback.core.joran.spi.ConfigurationWatchList in
ReconfigureOnChangeFilter.java
I'm using LogBack 1.0.0
> CLONE -Excessive synchronization in ReconfigureOnChangeFilter.decide
> --------------------------------------------------------------------
>
> Key: LBCLASSIC-234
> URL: http://jira.qos.ch/browse/LBCLASSIC-234
> Project: logback-classic
> Issue Type: Bug
> Affects Versions: 0.917
> Reporter: uri unger
> Assignee: Ceki Gulcu
> Priority: Critical
> Attachments: screenshot-1.jpg
>
>
> The synchronization in ReconfigureOnChangeFilter.decide hurts scalability.
> It seems unnecessary to serialize the code in changeDetected -- it should be
> possible to use atomic updates of nextCheck and lastModified and only
> serialize the actual reconfiguration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/logback-dev
