Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-3130

TCP plugin does not timeout if there is no response from server.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.14.1
    • None
    • Appenders
    • None

    Description

      We experienced a situation with our ELK stack where ElasticSearch ran out of space. Events sent to it from Logstash were hanging which, in turn, caused socket calls from the TCP SocketAppender to hang. The code currently accounts for connections failing but does not handle requests never responding.

      Attachments

        Issue Links

          Activity

            People

              rgoers Ralph Goers
              rgoers Ralph Goers
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: