Hey Daniel, I'll let the documentation team know about this issue. Joaquin, thanks! I did not know that. Best, Amit, CF Release Integration PM daniel.jones(a)engineerbetter.com> wrote:

the only option here is to route the log output to something like graylog or logstash and to my knowledge what i understood from release 215 you can set a longer retention log for the --recent log

Thanks Joaquin! I found out the long way that just setting the region will do. Sadly last time I used a light stemcell non-US-east regions weren't supported. Given that the documentation suggested

Setting the JBP_CONFIG_OPEN_JDK_JRE only works in JBP ver. 3.0.0.+ see http://chrisfrost.com/cloudfoundry/configuring-the-cloud-foundry-java-buildpack/ for some context. -cheers, Rohit -- Pivotal

To add more native memory to the JVM provisioned by the buildpack, you need to change the memory heuristics of the algorithm that generates the JVM -X memory settings.

Exactly. That is why we are not pursuing changing the BP option. Thanks for the confirmation. -- http://www.twitter.com/sivabalans

Tweaking the buildpack is less dynamic, and every time you want to make a change you will have to tweak again, create the new buildpack, and upload it to the CC. Moreover, maintaining your own fork

Thanks for the clarification Sabha and Amit. We are using JavaBP and our usecase is to have additional native memory headroom for the app. One option is to tweak the open_jdk.yml file in the JavaBP to

Hi, all, Quick reminder that the CAB call for September is next week Wednesday September 9th @ 8a PDT. Please add any project updates to Agenda here:

Ah, I was mistaken. If you set MEMORY_LIMIT, it will not get overwritten. So if you don't set it, it will be set to the container memory limit. But if you do set it, then the java buildpack can take

The MEMORY_LIMIT is used by the java buildpack to configure the various heap parameters for a java app. This variable value is set to the container size by default by the Cloud controller when you

Thanks for the response. But what I am observing is, by setting MEMORY_LIMIT as an environment variable does take effect when I restage the app and it reduces the memory allocated to the java app(not

This is not a environment variable you can set. To scale down the memory allocated to your instances, do cf scale <app-name> -m 1024M This will tell Warden/Garden to allocate that much memory to

Memory limits are set via cf scale. `cf scale <app-name> -m 512M` will scale your app to 512MB per instance. The cli will then tell you to restage your application so the buildpacks can observe the

We are not using Diego and we are on CF version 211. I had my application started with 2GB of memory set in the manifest file. I then ran the following command and restaged the app: cf set-env

The current way of sending metrics as either Values or Counters through the pipeline makes the development of a downstream consumer (=nozzle) pretty easy. If you look at the datadog nozzle[0], it just

Hi Daniel! What I've done while testing is to set the variable BOSH_AWS_REGION to the region I needed. export BOSH_AWS_REGION=<your region here> Regards!! Joaquin

Thanks for the help I had some permission issues on several files. Since diego run docker containers with user vcap. I created a user named as vcap and gave the file permission to vcap in advanced.

Thanks James, I've just corrected the three issues you've noted so far

The error message suggests that in `/etc/passwd` in the Docker image, the entry for `vcap` lists a path for the home dir that doesn't exist. I'm afraid I don't understand Diego well enough to know why