rm5248 commented on issue #429: URL: https://github.com/apache/logging-log4cxx/issues/429#issuecomment-2481303611
It seems that current master also has a bug introduced with https://github.com/apache/logging-log4cxx/commit/1a8875ad839a37d2fcf31876c0bbfe61181c9f21, which causes the monitor thread to exit immediately(so it does not reconnect if it can't connect the first time). @stephen-webb has more insight into why the `stopMonitor()` is being called in the private constructor. Commenting that out though, I can't reproduce this bug. Are you sure it's due to network sockets? Can you show the output of the `ls -l /proc/$(pidof log4cxxdemo)/fd` command? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
