Conflict with Spring Webflux

Open
#87 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java, spring
Domain
backend

Research direction

Start by reproducing the logger reset behavior with Spring WebFlux and trace where the appender is restarted. Inspect the appender and sender initialization lifecycle, then verify that a reset does not leave the sender null or permanently uninitialized.

Written by the indexing model from the issue text.

Description

Spring reset loggers your appender restarted and sender becomes null and never initialized again.

Dominant language
Java
Stars
210
Forks
86
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fluent/fluent-logger-java

All issues in fluent/fluent-logger-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.