[
https://issues.apache.org/jira/browse/FLUME-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304619#comment-15304619
]
ASF subversion and git services commented on FLUME-2913:
--------------------------------------------------------
Commit f4f15bee1e4ba109c6a21f639668911a13241014 in flume's branch
refs/heads/trunk from [~mpercy]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=f4f15be ]
FLUME-2913. Don't strip SLF4J from imported classpaths
It is no longer necessary to strip other versions of SLF4J from
classpaths imported from hadoop or hbase. With recent versions of SLF4J,
when multiple connectors are found, one of them "wins" and the logging
does not break. A warning is printed once, however. This is acceptable
because having too long of a classpath can cause major problems on
systems with a low ARG_MAX.
(Bessenyei Balázs Donát via Mike Percy)
> 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)
