karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "gonzalad (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KARAF-4594) Log4J socket collector error handling mutiple clients
Date Thu, 23 Jun 2016 15:09:16 GMT
gonzalad created KARAF-4594:

             Summary: 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


I'm using org.apache.karaf.decanter.collector.log.socketSocketCollector in my project.


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.

log4j.rootCategory=INFO, Socket
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

View raw message