-
Notifications
You must be signed in to change notification settings - Fork 408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LogstashTcpSocketAppender fails to shutdown #114
Comments
You are shutting down correctly. It should not pause/hang during shutdown. Can you take a thread stack dump during the hang/pause, and post it here?
|
I think I timed this right!
|
Configure the ScheduledThreadPoolExecutor to not wait for cancelled tasks when it is shutdown. This only works on java 1.7+. Java 1.6 and lower will continue to wait on cancelled tasks (or until the timeout occurs), which ever comes first. Also upgrade to disruptor 3.3.2
This only occurred when keepAlive was enabled. The pause during shutdown was caused by the I fixed this by configuring This fix will only work when running on java 1.7+, since that is when the When running <= java 1.6, the shutdown logic will continue waiting until it times out (after 1 min) The fix will be available in the next release (4.5). Note that I also saw that the |
Do you have an idea of when 4.5 will be released? We're waiting for this fix, and I would like to avoid creating an own build if you will be releasing this soon. |
Hi Mike, I plan on releasing 4.5 before Sept 1st. I'm planning on completing #115 for 4.5, but nothing else unless a bug report comes in before then. |
Released in 4.5 |
I have logstash running on a remote server, and a simple test app to verify that logs are being written:
logback.xml excerpt:
Logs are being written as expected, but App hangs during the loggerContext.stop() call. Here are the last few lines of my log output:
Like I said, all logs are being written just fine, but it would be nice if shutting down didn't cause such a long hang and a WARN. Am I shutting down incorrectly or something?
The text was updated successfully, but these errors were encountered: