Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 227AE200B32 for ; Thu, 23 Jun 2016 18:06:18 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 2018A160A35; Thu, 23 Jun 2016 16:06:18 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 64295160A69 for ; Thu, 23 Jun 2016 18:06:17 +0200 (CEST) Received: (qmail 11623 invoked by uid 500); 23 Jun 2016 16:06:16 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 11594 invoked by uid 99); 23 Jun 2016 16:06:16 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Jun 2016 16:06:16 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 7AA0A2C1F64 for ; Thu, 23 Jun 2016 16:06:16 +0000 (UTC) Date: Thu, 23 Jun 2016 16:06:16 +0000 (UTC) From: "Christian Schneider (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (KARAF-4594) Log4J socket collector error handling mutiple clients MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 23 Jun 2016 16:06:18 -0000 [ https://issues.apache.org/jira/browse/KARAF-4594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved KARAF-4594. ---------------------------------------- Resolution: Fixed > Log4J socket collector error handling mutiple clients > ----------------------------------------------------- > > Key: KARAF-4594 > URL: https://issues.apache.org/jira/browse/KARAF-4594 > Project: Karaf > Issue Type: Bug > Components: decanter > Affects Versions: decanter-1.1.0 > Reporter: gonzalad > Assignee: Christian Schneider > Fix For: decanter-1.1.1 > > > Hello, > I'm using org.apache.karaf.decanter.collector.log.socketSocketCollector in my project. > *Summary* > Once SocketCollector accepts a client socket, it seems to loop forever on this client socket (it won't accept another client socket - unless the previous client socket disconnects). > Perhaps SocketCollector should handle client sockets in another thread ? > Code : https://github.com/apache/karaf-decanter/blob/master/collector/log4j-socket/src/main/java/org/apache/karaf/decanter/collector/log/socket/SocketCollector.java#L75 > *My application setup* > I have 2 client applications both using Log4J 1.x with the following configuration. > {code} > log4j.rootCategory=INFO, Socket > log4j.appender.Socket=org.apache.log4j.net.SocketAppender > log4j.appender.Socket.Threshold=INFO > log4j.appender.Socket.RemoteHost=127.0.0.1 > log4j.appender.Socket.Port=4560 > log4j.appender.Socket.ReconnectionDelay=5000 > log4j.appender.Socket.LocationInfo=true > {code} > When I start the first application, everything works fine, I see decanter agent output my application logs. > When I start the second one, no logging happens (my app starts fine, but no logging). -- This message was sent by Atlassian JIRA (v6.3.4#6332)