[
https://issues.apache.org/jira/browse/FLUME-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304587#comment-15304587
]
Mike Percy commented on FLUME-2913:
-----------------------------------
[~bessbd] and I worked together offline to test this and it looks fine. When
multiple versions of an slf4j plugin are on the classpath, even if they are
different versions, one "wins" despite printing a warning and the logging
functions as expected.
Here is a test repo I put together to verify:
https://github.com/mpercy/slf4j-test
> Flume classpath too long
> ------------------------
>
> Key: FLUME-2913
> URL: https://issues.apache.org/jira/browse/FLUME-2913
> Project: Flume
> Issue Type: Bug
> Reporter: Bessenyei Balázs Donát
> Assignee: Bessenyei Balázs Donát
> Attachments: FLUME-2913.patch
>
>
> Starting Flume generates the FLUME_CLASSPATH variable dynamically, adding
> jars one by one.
> In some cases, the classpath can grow too long, sometimes exceeding ARG_MAX,
> maximum length of arguments for a new process (
> http://www.in-ulm.de/~mascheck/various/argmax/ )
> Thus, being unable to start Flume:
> flume-ng/bin/flume-ng: line 239: /usr/java/jdk1.7.0_67/bin/java: Argument
> list too long
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
