[
https://issues.apache.org/jira/browse/LOG4J2-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16120891#comment-16120891
]
Colin Hillman commented on LOG4J2-1604:
---------------------------------------
[~garydgregory]
hey Gary - wow thanks! I seem to have missed your email but welcome the change!
I downloaded the latest log4j 2.8.2 and jcommander-1.29.jar and launching with:
exec $JAVA_HOME/bin/java -Xmx1g \
-cp
$LIB_DIR/jcommander-1.29.jar:$LIB_DIR/log4j-api-2.8.2.jar:$LIB_DIR/log4j-core-2.8.2.jar
\
org.apache.logging.log4j.core.net.server.TcpSocketServer --port ${LOGPORT}
--config ${BASEDIR}/etc/log4j2.xml &
but getting this:
Exception in thread "main" java.lang.NoSuchMethodError:
com.beust.jcommander.JCommander.setCaseSensitiveOptions(Z)V
at
org.apache.logging.log4j.core.util.BasicCommandLineArguments.parseCommandLine(BasicCommandLineArguments.java:28)
at
org.apache.logging.log4j.core.net.server.TcpSocketServer.main(TcpSocketServer.java:200)
Any thoughts?
> Log4j2 TcpSocketServer in background
> ------------------------------------
>
> Key: LOG4J2-1604
> URL: https://issues.apache.org/jira/browse/LOG4J2-1604
> Project: Log4j 2
> Issue Type: Question
> Components: Core
> Affects Versions: 2.6.2
> Environment: Linux geotst01 2.6.32-504.3.3.el6.x86_64 #1 SMP Wed Dec
> 17 01:55:02 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Colin Hillman
> Assignee: Gary Gregory
> Priority: Minor
>
> I've been using the log4j version 1 SocketServer in background without
> problem. Changing to the TcpSocketServer works in foreground, but when I put
> it in the background, it shuts down. I've managed to get it working
> redirecting input from /dev/zero but as this will give continuous nulls, I'm
> not sure it's an ideal solution:
> exec $JAVA_HOME/bin/java -cp
> $LIB_DIR/log4j-api-2.6.2.jar:$LIB_DIR/log4j-core-2.6.2.jar \
> org.apache.logging.log4j.core.net.server.TcpSocketServer \
> $\{LOGPORT} $\{BASEDIR}/etc/log4j2.xml </dev/zero >/dev/null 2>&1 &
> Is the code intended to be used in background and, if yes what's the
> recommended way to launch TcpSocketServer? Could a parameter be added to make
> it a daemon not needing input?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
