Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

There is no way to set socket read timeout

Open
#82 1 comment 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
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
backend, networking

Research direction

Start by locating where the logger creates and configures its socket, then inspect the current socket.setSoTimeout() usage. Determine how a caller could configure the read timeout and verify that logging threads no longer wait indefinitely when Fluentd is unresponsive or packets are lost.

Written by the indexing model from the issue text.

Description

There is no way to set a socket read timeout.

socket.setSoTimeout() is not configurable.

So if there are network issues (packet loss for a certain duration) OR if fluentd process itself is not responding then all logging threads could get blocked and bring the application to a standstill.

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.