Update JAVA_OPTS documentation - #520
Conversation
|
Hey youngm! Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA. |
|
Looks great. What do you think about removing |
|
We could. Though I actually set that for an application, as a stop gap, that was having trouble staying within the container memory size while I study the problem. We set it to a value that we believed should leave plenty of head room for everything else. It was convenient. That said I won't have a problem with making it an undocumented feature if you would prefer. |
|
Yeah, let's make it undocumented. I understand your use case, but I don't want any indication in our docs that it's an appropriate thing for most users to do. Those who really need it should be able to divine that it's possible for the pattern of the rest. |
A stab at updating some JAVA_OPTS documentation for JBP4.
|
@nebhale done. |
|
Hey youngm! Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA. |
Previously the JAVA_OPTS documentation erroneously stated that there were a set of allowed and disallowed memory arguments. With the advent of the new memory calculator all flags are now allowed. This change updates the docs to reflect that. [resolves #520]
A stab at updating some JAVA_OPTS documentation for JBP4.