[
https://issues.apache.org/jira/browse/KAFKA-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985881#comment-14985881
]
Rajini Sivaram commented on KAFKA-2719:
---------------------------------------
[~geoffra] If system tests are guaranteed to start only one java process on
each VM, then services could always grep for _java_ to find processes instead
of grepping for the classname as they do now (since _java_ is at the start and
classname is at the end). But in general, it is useful to see what is running
when you run _ps_, and not just in system tests. Hence the PR. Also, the
changes to kafka-run-class.sh only change the parts of the script that are used
to run from the development build, not from a release build. It felt like the
simplest fix (because it is contained in one file), but I dont have a strong
opinion either way.
> Kafka classpath has grown too large and breaks some system tests
> ----------------------------------------------------------------
>
> Key: KAFKA-2719
> URL: https://issues.apache.org/jira/browse/KAFKA-2719
> Project: Kafka
> Issue Type: Bug
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
> Fix For: 0.9.0.0
>
>
> The jars added under KAFKA-2369 makes the Kafka command line used in system
> tests much higher than 4096 due to more jars in the classpath. Since the ps
> command used to find processes in system tests truncates the command line,
> some system tests are failing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
