geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-1458) Sequence logger thread can die on startup and should not be enabled by default
Date Wed, 25 May 2016 22:28:13 GMT

    [ https://issues.apache.org/jira/browse/GEODE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301007#comment-15301007
] 

ASF subversion and git services commented on GEODE-1458:
--------------------------------------------------------

Commit 1d11d94dfe600b99007ccdc28f178d98fd86fd30 in incubator-geode's branch refs/heads/feature/GEODE-835
from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=1d11d94 ]

GEODE-1458: Prevent sequence logger from launching and closing a thread

The sequence logger code was launching a thread from a static block,
even if it was not enabled. The thread was then immediately dying.
Fixing the code to not launch the thread unless it is enabled, and to
not die immediately if it is.


> Sequence logger thread can die on startup and should not be enabled by default
> ------------------------------------------------------------------------------
>
>                 Key: GEODE-1458
>                 URL: https://issues.apache.org/jira/browse/GEODE-1458
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Dan Smith
>            Assignee: Dan Smith
>             Fix For: 1.0.0-incubating.M3
>
>
> The SequenceLoggerImpl class always creates a thread in the static block.
> However, if the logger class is loaded before the cache, the thread dies immediately.
> Since sequence logging is usually not enabled, we shouldn't even start this thread unless
it is enabled and in that case it should not die if a cache is not present.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message