[logback-dev] [JIRA] (LOGBACK-1212) Configuration with multiple SocketReceiver does not work

[Maciej Lizewski (JIRA)]

Title: Message Title

Maciej Lizewski commented on LOGBACK-1212   Re: Configuration with multiple SocketReceiver does not work I have found some hint: when I take SocketReceiver code, create my class based on that code with only one single difference - instead using logbacks common ScheduledThreadPoolExecutor I provide one in every Receiver instance (instead of getContext().getScheduledExecutorService().submit(connector) I use: this.executor.submit(connector); Everything starts working just fine... My conclusions is that there is something wrong with ScheduledThreadPoolExecutor and it only uses 2 threads (it is initialised like this in ExecutorServiceUtil: public static ScheduledExecutorService newScheduledExecutorService() { return new ScheduledThreadPoolExecutor(2, THREAD_FACTORY); } ) and when both are busy with logbacks core and single receiver - nothing else works just hanging and waiting for free executor thread which is never available... I think it shoud detect starwation like this and fire another thread (by default ther is max of Integer.MAX_VALUE after all...) anyway - I cannot think of any global solution for now. I will stay with my own receiver with own thread. But I think it might cause other problems in future. Add Comment   This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

_______________________________________________
logback-dev mailing list
logback-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-dev