[
https://issues.apache.org/jira/browse/SAMZA-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028059#comment-14028059
]
Chris Riccomini commented on SAMZA-20:
--------------------------------------
bq. Yes. However, if the option is enabled and not supported by the JVM, there
is an error that prevents creating the JVM (see below). Unrecognized VM option
'+UseGCLogFileRotation' Could not create the Java virtual machine.
Rather than the version parsing logic, could we simply start a java process
with the UseGCLogFileRotation set, and check the exit code? Something like:
{noformat}
java -XX:+UseGCLogFileRotation -version
{noformat}
> Roll gc logs in run-class.sh
> ----------------------------
>
> Key: SAMZA-20
> URL: https://issues.apache.org/jira/browse/SAMZA-20
> Project: Samza
> Issue Type: Bug
> Components: container
> Affects Versions: 0.6.0
> Reporter: Chris Riccomini
> Assignee: Raul Castro Fernandez
> Labels: newbie
> Attachments: samza-20.patch
>
>
> The run-class.sh script defaults to setting up a gc.log file, if SAMZA_OPTS
> is undefined.
> Newer versions of Java 6, and Java 7 allow you to roll gc log files with
> -XX:+UseGCLogFileRotation. See
> http://stackoverflow.com/questions/3822097/rolling-garbage-collector-logs-in-java
> for details.
> Should also validate that the change doesn't break with older Java 6 versions.
> Also, [~sureshms] was saying that there's an alternate way to do this. Suresh
> - care to chime in?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
