[
https://issues.apache.org/jira/browse/FLUME-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304762#comment-15304762
]
Hudson commented on FLUME-2913:
-------------------------------
FAILURE: Integrated in Flume-trunk-hbase-1 #159 (See
[https://builds.apache.org/job/Flume-trunk-hbase-1/159/])
FLUME-2913. Don't strip SLF4J from imported classpaths (mpercy:
[http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=f4f15bee1e4ba109c6a21f639668911a13241014])
* bin/flume-ng
> 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
> Fix For: v1.7.0
>
> 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)
