Repository: brooklyn-docs Updated Branches: refs/heads/master 513953afb -> e4187b668
Move to Java 8, remove MaxPermSize options Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/e16181dc Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/e16181dc Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/e16181dc Branch: refs/heads/master Commit: e16181dcb257835a9e47b3c87a4ae4718500610d Parents: 1139c02 Author: Svetoslav Neykov <[email protected]> Authored: Fri May 19 15:58:27 2017 +0300 Committer: Svetoslav Neykov <[email protected]> Committed: Fri May 19 15:58:27 2017 +0300 ---------------------------------------------------------------------- guide/dev/env/maven-build.md | 2 +- guide/dev/tips/debugging-remote-brooklyn.md | 4 ++-- guide/ops/server-cli-reference.md | 2 +- guide/ops/troubleshooting/memory-usage.md | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/e16181dc/guide/dev/env/maven-build.md ---------------------------------------------------------------------- diff --git a/guide/dev/env/maven-build.md b/guide/dev/env/maven-build.md index 1c95dd9..68f6510 100644 --- a/guide/dev/env/maven-build.md +++ b/guide/dev/env/maven-build.md @@ -31,7 +31,7 @@ Other tips: * You may need more JVM memory, e.g. at the command-line (or in `.profile`): - ``export MAVEN_OPTS="-Xmx1024m -Xms512m -XX:MaxPermSize=256m"`` + ``export MAVEN_OPTS="-Xmx1024m -Xms512m"`` * Run ``-PIntegration`` to run integration tests, or ``-PLive`` to run live tests ([tests described here](../code/tests.html)) http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/e16181dc/guide/dev/tips/debugging-remote-brooklyn.md ---------------------------------------------------------------------- diff --git a/guide/dev/tips/debugging-remote-brooklyn.md b/guide/dev/tips/debugging-remote-brooklyn.md index 9b0c1bb..3b0a100 100644 --- a/guide/dev/tips/debugging-remote-brooklyn.md +++ b/guide/dev/tips/debugging-remote-brooklyn.md @@ -49,11 +49,11 @@ root of the Brooklyn installation: {% highlight bash %} # NOTE: Running this kill command will lose existing apps and machines if persistence is disabled. % kill `cat pid_java` -% export JAVA_OPTS="-Xms256m -Xmx1g -XX:MaxPermSize=256m -agentlib:jdwp=transport=dt_socket,address=127.0.0.1:8888,server=y,suspend=n" +% export JAVA_OPTS="-Xms256m -Xmx1g -agentlib:jdwp=transport=dt_socket,address=127.0.0.1:8888,server=y,suspend=n" % bin/brooklyn launch & {% endhighlight %} -If `JAVA_OPTS` is not set, Brooklyn will automatically set it to `"-Xms256m -Xmx1g -XX:MaxPermSize=256m"`, which is why +If `JAVA_OPTS` is not set, Brooklyn will automatically set it to `"-Xms256m -Xmx1g"`, which is why we have prepended the agentlib settings with these values here. You should see the following in the console output: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/e16181dc/guide/ops/server-cli-reference.md ---------------------------------------------------------------------- diff --git a/guide/ops/server-cli-reference.md b/guide/ops/server-cli-reference.md index 102b6b0..eddf2d9 100644 --- a/guide/ops/server-cli-reference.md +++ b/guide/ops/server-cli-reference.md @@ -69,7 +69,7 @@ For a standard Brooklyn deployment, the defaults are to start with 256m, and to These numbers can be overridden by setting the environment variable `JAVA_OPTS` before launching the `brooklyn script`, as follows: - JAVA_OPTS="-Xms1g -Xmx4g -XX:MaxPermSize=256m" + JAVA_OPTS="-Xms1g -Xmx4g" (On Java 8 and later the last entry has no effect and can be dropped.) http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/e16181dc/guide/ops/troubleshooting/memory-usage.md ---------------------------------------------------------------------- diff --git a/guide/ops/troubleshooting/memory-usage.md b/guide/ops/troubleshooting/memory-usage.md index bb95342..b7baf77 100644 --- a/guide/ops/troubleshooting/memory-usage.md +++ b/guide/ops/troubleshooting/memory-usage.md @@ -41,7 +41,7 @@ memory should shrink dramatically then increase until the problem recurs. This can be fixed by passing `-XX:SoftRefLRUPolicyMSPerMB=1` to the JVM, as described in [Brooklyn issue 375](https://issues.apache.org/jira/browse/BROOKLYN-375). -Other common JVM options include `-Xms256m -Xmx1g -XX:MaxPermSize=256m` +Other common JVM options include `-Xms256m -Xmx1g` (depending on JVM provider and version) to set the right balance of memory allocation. In some cases a larger `-Xmx` value may simply be the fix (but this should not be the case unless many or large blueprints are being used).
