We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The New Relic service broker tile fails to install with Java Buildpack 4.0+ because of the -m 512M flag:
-m 512M
+ cf push NewRelicServiceBroker-v1 -p /var/vcap/packages/newrelic_service_broker/new-relic-service-broker.jar -n newrelic-broker -d apps.pcfdev-us-west-2.aws-nonprod.fmrcloud.com -t 180 -m 512m --no-start ++++++++++++ 2017-11-08T07:04:29.82-0500 [APP/PROC/WEB/0] ERR Cannot calculate JVM memory configuration: There is insufficient memory remaining for heap. Memory limit 512M is less than allocated memory 669939K (-XX:ReservedCodeCacheSize=240M, -XX:MaxDirectMemorySize=10M, -XX:MaxMetaspaceSize=89745K, -XX:CompressedClassSpaceSize=16993K, -Xss1M * 300 threads) ++++++++++++
More information on this error is available at: https://discuss.pivotal.io/hc/en-us/articles/115011717548-Insufficient-memory-when-using-Java-Buildpack-4-0-
The recommended solution is just to scale memory up to 1G or more.
The text was updated successfully, but these errors were encountered:
Whoops, looks like this was resolved in 1.11.4.
Sorry, something went wrong.
No branches or pull requests
The New Relic service broker tile fails to install with Java Buildpack 4.0+ because of the
-m 512M
flag:More information on this error is available at: https://discuss.pivotal.io/hc/en-us/articles/115011717548-Insufficient-memory-when-using-Java-Buildpack-4-0-
The recommended solution is just to scale memory up to 1G or more.
The text was updated successfully, but these errors were encountered: