[
https://issues.apache.org/jira/browse/KARAF-4594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347082#comment-15347082
]
ASF subversion and git services commented on KARAF-4594:
--------------------------------------------------------
Commit bfe15529e72ad9828be43a7ed0910999cb835ab0 in karaf-decanter's branch
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=bfe1552 ]
[KARAF-4594] Update log4j socket documentation. This closes #15
> 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)
