You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was thinking the default behaviour it will reconnect to fluentd socket. I was not changing the port, only restarting fluentd. But after fluentd restarted, webapp in tomcat can't forward event to fluentd.
If I use parallel deployment, the new version able to forward the message to fluentd.
How to make webapp still able to forward the message to fluentd?
I'm using spring framework, and I uses the logger like below:
Is there anything I did wrong? Is there any way to achieve what I want? (webapp still able to forward log to fluentd after fluentd get restarted)
The text was updated successfully, but these errors were encountered:
dieend
changed the title
When tomcat is running, and then fluentd restarted, webapp save event to log until it fulls and fails.
When tomcat is running, and then fluentd restarted, webapp save event to buffer until it fulls and fails.
Dec 12, 2014
I was thinking the default behaviour it will reconnect to fluentd socket. I was not changing the port, only restarting fluentd. But after fluentd restarted, webapp in tomcat can't forward event to fluentd.
If I use parallel deployment, the new version able to forward the message to fluentd.
How to make webapp still able to forward the message to fluentd?
I'm using spring framework, and I uses the logger like below:
Is there anything I did wrong? Is there any way to achieve what I want? (webapp still able to forward log to fluentd after fluentd get restarted)
The text was updated successfully, but these errors were encountered: