[logback-dev] [JIRA] (LOGBACK-1413) 1.3.0-alpha4 LoggerContext's ExecutorService no longer executes

QOS.CH (JIRA) noreply-jira at qos.ch
Thu Aug 2 12:51:00 CEST 2018


paul hinds created LOGBACK-1413:
-----------------------------------

             Summary: 1.3.0-alpha4 LoggerContext's ExecutorService  no longer executes
                 Key: LOGBACK-1413
                 URL: https://jira.qos.ch/browse/LOGBACK-1413
             Project: logback
          Issue Type: Bug
          Components: logback-classic
    Affects Versions: 1.3.0-alpha4
         Environment: Windows 10, Java 8, Running in JUnit tests in IntelliJ

 
            Reporter: paul hinds
            Assignee: Logback dev list


LoggerContext provides an ExecutorService. I am using this to start a TCP appender similar to the one provided by logback.

{{Context context = {color:#cc7832}new {color}LoggerContext(){color:#cc7832};{color}ExecutorService ses = context.getExecutorService(){color:#cc7832};{color}ses.submit(() -> System.{color:#9876aa}out{color}.println({color:#6a8759}"ScheduledExecutorService running"{color})){color:#cc7832};{color}}}

{color:#cc7832}Would print the text.{color}

{color:#cc7832}Running with 1.3.0-alpha4 version, the lambda is no longer executed{color}

 

{color:#cc7832}N.B.  context.getExecutorService() has been deprecated the same applies to context.getScheduledExecutorService(){color}

{color:#cc7832}
 
 {color}



--
This message was sent by Atlassian JIRA
(v7.3.1#73012)


More information about the logback-dev mailing list