lu-xiaoshuang commented on issue #3442: URL: https://github.com/apache/logging-log4j2/issues/3442#issuecomment-2652418157
> [@lu-xiaoshuang](https://github.com/lu-xiaoshuang), > > > At present, a SocketAppender only supports one address-port. Seems that remote server represented by this address-port is very likely the bottleneck (network traffic) and single point failure endpoint (without gateway). > > > It would be great if there are no additional prerequisites. > > The `Socket` appender is based on the basic Java socket classes. These classes don't provide support for connection pooling, so we would need additional libraries (like Apache MINA or Netty) or a lot of custom code to handle multiple connections. > > Since TCP does not guarantee a reliable delivery without message loss, it is probably better to look at [message queue appenders](https://logging.apache.org/log4j/2.x/manual/appenders/message-queue.html). Some of them do support multiple servers. Thanks, @ppkarwasz KafkaAppender is not the capable of sending logs generated by org.apache.kafka:kafka-clients:jar, is it? By the way, If community decides to make SocketAppender support server list, what about creating multiple sockets? When append method is invoked, log4j2 can choose a socket randomly. I think this simple solution is free of connection pool stuff. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
