Not that I'm aware of

That said, you can control the maximum memory an instance can allocate and
you can control the maximum memory in the quota. It's not the same but it
may be something you can leverage.

--
Matthew Sykes
matthew.sykes(a)gmail.com

Hi Paul, thank you for your quick response. I added the VSPHERE_HOST settings but it failed to restart. Refer to attached screenshot ' configuration.png '. Also I attached the log file 'restart.log'.

It seems to be a connect issue but I tried to connect the VSPHERE host via vSphere client with the below information:
VSPHERE_HOST: 10.32.70.119
VSPHERE_PASSWORD: Password
VSPHERE_USERNAME: root

And it can connect to the host successfully. Any help will be appreciated.

Hi Alberto,

When BOSH creates a final release, it uploads the packages to the blob
store configured for that BOSH release. You can see this for cf-release
here:
https://github.com/cloudfoundry/cf-release/blob/master/config/final.yml

There is more information on release blobstores in the bosh documentation:
http://bosh.io/docs/s3-release-blobstore.html

- CF Runtime Team

Hi Team,

Glad to hear it!

Cheers,
Vlad

From: Price, Jon [mailto:jon.price(a)intel.com]
Sent: Monday, May 18, 2015 2:43 PM
To: Iovanov, Vlad Mircea; cf-dev(a)lists.cloudfoundry.org
Subject: RE: [cf-dev] visual studio extension - login error

Hi Vlad,

The new version works great! Thank you very much. :)

-- Jon

From: Iovanov, Vlad Mircea [mailto:Vlad.Iovanov(a)hp.com]
Sent: Monday, May 18, 2015 1:51 PM
To: Price, Jon; cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>
Subject: RE: [cf-dev] visual studio extension - login error

Hello Jon,

Can you please try to upgrade the Visual Studio Extensions to latest (1.2.0.4)?
We've published a new version that should address the login problems you've been experiencing. New versions of the .NET SDK and MSBuild tasks have also been published.

Cheers,
Vlad

From: Price, Jon [mailto:jon.price(a)intel.com]
Sent: Friday, May 15, 2015 11:49 AM
To: Iovanov, Vlad Mircea; cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>
Subject: RE: [cf-dev] visual studio extension - login error

Hi Vlad,

We are running CF release 207.

Here is the /v2/info output with some of the data sanitized:

{"name":"vcap","build":"2222","support":"http://url.removed",
"authorization_endpoint":"https://login.paaslab3.xxx.com",
"token_endpoint":"https://uaa.paaslab3.xxx.com","min_cli_version":null,
"min_recommended_cli_version":null,"api_version":"2.25.0",
"logging_endpoint":"wss://loggregator.paaslab3.xxx.com:443"}

We normally have ldap authentication enabled and require ssl between the login server and uaa but even after disabling all of that and running with what I think is a pretty simple and standard configuration we get the error.

Thank you for taking the time to look into this.

-- Jon

From: cf-dev-bounces(a)lists.cloudfoundry.org<mailto:cf-dev-bounces(a)lists.cloudfoundry.org> [mailto:cf-dev-bounces(a)lists.cloudfoundry.org] On Behalf Of Iovanov, Vlad Mircea
Sent: Friday, May 15, 2015 10:52 AM
To: cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>
Subject: Re: [cf-dev] visual studio extension - login error

Hello Jon,

Can you please let me know what version of Cloud Foundry you are running? If you could include the output of your "info" endpoint it would be great (http://apidocs.cloudfoundry.org/208/info/get_info.html)

Cheers,
Vlad

Hi Vlad,

The new version works great! Thank you very much. :)

-- Jon

From: Iovanov, Vlad Mircea [mailto:Vlad.Iovanov(a)hp.com]
Sent: Monday, May 18, 2015 1:51 PM
To: Price, Jon; cf-dev(a)lists.cloudfoundry.org
Subject: RE: [cf-dev] visual studio extension - login error

Hello Jon,

Can you please try to upgrade the Visual Studio Extensions to latest (1.2.0.4)?
We've published a new version that should address the login problems you've been experiencing. New versions of the .NET SDK and MSBuild tasks have also been published.

Cheers,
Vlad

From: Price, Jon [mailto:jon.price(a)intel.com]
Sent: Friday, May 15, 2015 11:49 AM
To: Iovanov, Vlad Mircea; cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>
Subject: RE: [cf-dev] visual studio extension - login error

Hi Vlad,

We are running CF release 207.

Here is the /v2/info output with some of the data sanitized:

{"name":"vcap","build":"2222","support":"http://url.removed",
"authorization_endpoint":"https://login.paaslab3.xxx.com",
"token_endpoint":"https://uaa.paaslab3.xxx.com","min_cli_version":null,
"min_recommended_cli_version":null,"api_version":"2.25.0",
"logging_endpoint":"wss://loggregator.paaslab3.xxx.com:443"}

We normally have ldap authentication enabled and require ssl between the login server and uaa but even after disabling all of that and running with what I think is a pretty simple and standard configuration we get the error.

Thank you for taking the time to look into this.

-- Jon

From: cf-dev-bounces(a)lists.cloudfoundry.org<mailto:cf-dev-bounces(a)lists.cloudfoundry.org> [mailto:cf-dev-bounces(a)lists.cloudfoundry.org] On Behalf Of Iovanov, Vlad Mircea
Sent: Friday, May 15, 2015 10:52 AM
To: cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>
Subject: Re: [cf-dev] visual studio extension - login error

Hello Jon,

Can you please let me know what version of Cloud Foundry you are running? If you could include the output of your "info" endpoint it would be great (http://apidocs.cloudfoundry.org/208/info/get_info.html)

Cheers,
Vlad

Hello Jon,

Can you please try to upgrade the Visual Studio Extensions to latest (1.2.0.4)?
We've published a new version that should address the login problems you've been experiencing. New versions of the .NET SDK and MSBuild tasks have also been published.

Cheers,
Vlad

From: Price, Jon [mailto:jon.price(a)intel.com]
Sent: Friday, May 15, 2015 11:49 AM
To: Iovanov, Vlad Mircea; cf-dev(a)lists.cloudfoundry.org
Subject: RE: [cf-dev] visual studio extension - login error

Hi Vlad,

We are running CF release 207.

Here is the /v2/info output with some of the data sanitized:

{"name":"vcap","build":"2222","support":"http://url.removed",
"authorization_endpoint":"https://login.paaslab3.xxx.com",
"token_endpoint":"https://uaa.paaslab3.xxx.com","min_cli_version":null,
"min_recommended_cli_version":null,"api_version":"2.25.0",
"logging_endpoint":"wss://loggregator.paaslab3.xxx.com:443"}

We normally have ldap authentication enabled and require ssl between the login server and uaa but even after disabling all of that and running with what I think is a pretty simple and standard configuration we get the error.

Thank you for taking the time to look into this.

-- Jon

From: cf-dev-bounces(a)lists.cloudfoundry.org<mailto:cf-dev-bounces(a)lists.cloudfoundry.org> [mailto:cf-dev-bounces(a)lists.cloudfoundry.org] On Behalf Of Iovanov, Vlad Mircea
Sent: Friday, May 15, 2015 10:52 AM
To: cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>
Subject: Re: [cf-dev] visual studio extension - login error

Hello Jon,

Can you please let me know what version of Cloud Foundry you are running? If you could include the output of your "info" endpoint it would be great (http://apidocs.cloudfoundry.org/208/info/get_info.html)

Cheers,
Vlad

Hi Owais,

What are you referring to when you say you're concerned about the LTM
becoming a Monolith? Too much functionality in one component? Too much of
the system depending on one component?

Chip,

Hopefully it's ok to discuss NoRouter here even though it isn't an official
CF project. Let us know if it is not.

Mike

On Fri, May 15, 2015 at 10:55 AM, Chip Childers <cchilders(a)cloudfoundry.org>
wrote:

The "norouter", while interesting, isn't the official CF project approach
to HTTP traffic routing. The TCP router is being built to support TCP
routing as a general solution, with the goal of it becoming an official
part of the CF release when ready.

-chip

Chip Childers | Technology Chief of Staff | Cloud Foundry Foundation

On Fri, May 15, 2015 at 8:58 AM, Mohamed, Owais <
Owais.Mohamed(a)covisint.com> wrote:

Hi,

I attended sessions on both TCP Router (Cloud Foundry and IOT protocol
support by Atul Kshirsagar) and NoRouter (Norouter: Running Cloud
Foundry without the Gorouter by Mike Heath).

I just wanted to start a discussion on the pros and cons of each
approach.

As personal opinion I think NoRouter is a simpler approach and can
definitely be made to support IOT protocols. The main drawback I see with
the NoRouter is the danger of the LTM becoming a Monolith.

Any suggestions\ideas?

Regards,
Owais


_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

Any build-in support for multiline logging would be nice. Seeing content in
one call to log4j's log.error() spreading over numerous logging records
really sucks, especially for exception stacktrace.

I don't believe there is a solution in raw Loggregator to fix this.

Multi line log messages is a major issue we deal with regularly today in
our deployment. Although there are workarounds to the issue like the
logstash config you posted, it is somewhat dependent upon how the
application logs are formatted which is sub optimal.

I'd personally like to see a syslog port available to the app container
that applications can send logs to in addition to channeling STDERR and
STDOUT. That would make issues like much easier to handle downstream and
would help eliminate deployed app specific hacks like we have to do today
in logstash.

I talked with a LAMB engineer at Summit and they didn't believe syslog for
deployed apps was anywhere on the LAMB roadmap. Can anyone confirm that?
I could have sworn I'd heard mention of syslog for app mentioned in the
past.

Mike

On Mon, May 18, 2015 at 9:32 AM, Li, George <guangxing.li(a)pearson.com>
wrote:

James,

so basically Loggregator does not support such correlation itself and it
is totally left to the downstream processor to do the aggregation, right?
When my service write exception stack trace into the log as follows:

2015-05-18 14:40:41 +0000 WARN
com.pearson.grid.registrar.commonutils.logging.LoggingMessageObserver
[LoggingMessageObserver.java:125] GET http://localhost:3004/ threw
exception: FileNotFoundException -
E:\Src\Registrar\escrow\service\config\version.properties (The system
cannot find the file specified)
java.io.FileInputStream.open(Native Method)
java.io.FileInputStream.<init>(FileInputStream.java:138)

com.pearson.grid.registrar.commonutils.Version.readProperties(Version.java:77)

Loggregator sends the following to downstream logstash:

2015-05-18 14:40:41 +0000 [App/0] OUT [escrow] [pool-3-thread-1052] WARN
com.pearson.grid.registrar.commonutils.logging.LoggingMessageObserver
[LoggingMessageObserver.java:142] GET http://escrow.cf.pd-cloud.com/
threw exception: FileNotFoundException - config\version.properties (No such
file or directory)
2015-05-18 14:40:41 +0000 [App/0] OUT java.io.FileInputStream.open(Native
Method)
2015-05-18 14:40:41 +0000 [App/0] OUT
java.io.FileInputStream.<init>(FileInputStream.java:146)
2015-05-18 14:40:41 +0000 [App/0] OUT
com.pearson.grid.registrar.commonutils.Version.readProperties(Version.java:77)

Ideally we want to keep all these as a single log "event" in the final
log. The way to do this in logstash is to config logstash so it would
aggregate all lines not staring with a timestamp (or any identifiable
marker) to previous lines:

input {
file {
codec => multiline {
pattern => "^%{TIMESTAMP_ISO8601} "
...
}
}

So I think my exact question is if there is a similar way to config
loggregator so it does the same thing.

In the previous thread
https://groups.google.com/a/cloudfoundry.org/forum/?utm_medium=email&utm_source=footer#!msg/vcap-dev/B1W6_vO0oyo/84X1eAtFsKoJ,
David Lee said "...As for multiline output, we should have fixed this a
couple of builds back...", I wonder what was really fixed related to
multiline output at that time.

Thanks.

George.

On Sun, May 17, 2015 at 8:26 AM, James Bayer <jbayer(a)pivotal.io> wrote:

george,

can you explain the scenario that is impacting you currently? e.g.
reading a java stack trace? the app index is shown in the log line. when
using the loggregator websocket client to retrieve logs you should also get
the application id. perhaps that is enough to correlate whatever UI you
have on top of logstash?


On Tue, May 12, 2015 at 7:40 AM, Li, George <guangxing.li(a)pearson.com>
wrote:

Hi,

this is a follow up on the archived posting
https://groups.google.com/a/cloudfoundry.org/forum/?utm_medium=email&utm_source=footer#!msg/vcap-dev/B1W6_vO0oyo/84X1eAtFsKoJ.
I cannot find any new postings on that thread.
I am using Cloud Foundry version
"6.11.2-2a26d55-2015-04-27T21:11:44+00:00" and want to know what options I
have to handle multiple line logs in a multi-tenant environment. Since
multiple instances of multiple applications are all sending logs to a
single Logstash server, is it best to avoid having multiple lines in my
log? I can live with sticking to single line logs except for outputting
exception stack trace, not to mention that I only have control over my
code.

Thanks.

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

--
Thank you,

James Bayer

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

Interesting, will do.

Josh Ghiloni
Senior Consultant
303.932.2202 o | 303.590.5427 m | 303.565.2794 f
jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com>

ECS Team
Technology Solutions Delivered
ECSTeam.com<http://ECSTeam.com>

Good news and bad news,

bad news that you have a problem

good news is that it is happening during "./gradlew run" which means it is
easily reproducible and thus, easily fixable.

Since our Travis CI runs the embedded gradle cargo container, we can know
for certain that ./gradlew run does indeed work and the login page will be
available at http://localhost:8080/uaa/login

My first guess is that your gradle cache may contain some library that has
mutated. So, prepare yourself to download the internet and my
recommendation would be to blow away your ~/.gradle directory and try
'./gradlew run' again with the master branch

Let us know the results

Filip

Hi all,

We recently put up CF v207 and are trying to deploy UAA into the apps area that we use for SSO between our micro services. Before this, we’d been running 2.0.3 with no issues. However, when I tried to upgrade to 2.2.6, any pages we tried to hit resulted in an HTTP 404 and redirected to the error page, which renders, though all linked stylesheets and images also returned 404s. We reverted to 2.0.3 because we didn’t need anything in the newer version at this time, but it’s an odd issue, and i’m wondering if anyone else has hit it. FWIW, this also happens with ver 2.1.0, and it happens locally (when I run `gradlew run`) as well for those versions.

Does this have anything to do with the introduction of multi-tenancy? Any insights would be appreciated, because the logs aren’t really showing anything. Thanks!

Josh Ghiloni
Senior Consultant
303.932.2202 o | 303.590.5427 m | 303.565.2794 f
jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com>

ECS Team
Technology Solutions Delivered
ECSTeam.com<http://ECSTeam.com>

James,

so basically Loggregator does not support such correlation itself and it is
totally left to the downstream processor to do the aggregation, right?
When my service write exception stack trace into the log as follows:

2015-05-18 14:40:41 +0000 WARN
com.pearson.grid.registrar.commonutils.logging.LoggingMessageObserver
[LoggingMessageObserver.java:125] GET http://localhost:3004/ threw
exception: FileNotFoundException -
E:\Src\Registrar\escrow\service\config\version.properties (The system
cannot find the file specified)
java.io.FileInputStream.open(Native Method)
java.io.FileInputStream.<init>(FileInputStream.java:138)
com.pearson.grid.registrar.commonutils.Version.readProperties(Version.java:77)

Loggregator sends the following to downstream logstash:

2015-05-18 14:40:41 +0000 [App/0] OUT [escrow] [pool-3-thread-1052] WARN
com.pearson.grid.registrar.commonutils.logging.LoggingMessageObserver
[LoggingMessageObserver.java:142] GET http://escrow.cf.pd-cloud.com/ threw
exception: FileNotFoundException - config\version.properties (No such file
or directory)
2015-05-18 14:40:41 +0000 [App/0] OUT java.io.FileInputStream.open(Native
Method)
2015-05-18 14:40:41 +0000 [App/0] OUT
java.io.FileInputStream.<init>(FileInputStream.java:146)
2015-05-18 14:40:41 +0000 [App/0] OUT
com.pearson.grid.registrar.commonutils.Version.readProperties(Version.java:77)

Ideally we want to keep all these as a single log "event" in the final log.
The way to do this in logstash is to config logstash so it would aggregate
all lines not staring with a timestamp (or any identifiable marker) to
previous lines:

input {
file {
codec => multiline {
pattern => "^%{TIMESTAMP_ISO8601} "
...
}
}

So I think my exact question is if there is a similar way to config
loggregator so it does the same thing.

In the previous thread
https://groups.google.com/a/cloudfoundry.org/forum/?utm_medium=email&utm_source=footer#!msg/vcap-dev/B1W6_vO0oyo/84X1eAtFsKoJ,
David Lee said "...As for multiline output, we should have fixed this a
couple of builds back...", I wonder what was really fixed related to
multiline output at that time.

Thanks.

George.

Good morning.

My question is quite simple: Is there any way to set a maximum number of
instances for applications? The idea is to prevent users from scaling an
application beyond a given limit of instances.

Thank you in advance.

I ran 3 tests over the weekend. These are the results:

- the copy of the application that ran against offline Java buildpack v3 /
tomcat 8.0.21 'crashed' 10 times over the weekend
- the copy of the application that ran against our custom Java buildpack /
tomcat 8.0.22 'crashed' 4 times over the weekend
- the copy of the application than ran against our custom Java buildpack /
tomcat 8.0.18 stayed up all weekend

We're certain this is down to the Tomcat version. Tomcat 8.0.22 doesn't seem
to be much better than 8.0.21 in respect of this memory issue.



--
View this message in context: http://cf-dev.70369.x6.nabble.com/Re-cf-dev-Cf-dev-vcap-dev-Java-OOM-debugging-tp25p112.html
Sent from the CF Dev mailing list archive at Nabble.com.

Love this feature! Thanks JBP team!

Now I have to try really hard to find something in the JBP to complain
about. :)

Mike

On Tue, May 12, 2015 at 9:12 AM, Christopher Frost <cfrost(a)pivotal.io>
wrote:

When deploying a Java application to Cloud Foundry the Java memory
settings for the application are decided based on the configured memory
weighting during staging. This means that, unlike other apps, if the
application is scaled to give it more memory it needs to be *restage*d it
to get updated Java memory settings. This has now been improved with an
improved memory calculator written by Steve Powell[2]. The Memory
Calculator[1] will be run during every application start to ensure the
application gets up-to-date memory settings, its output is shown during
staging.

-----> Downloading Open JDK Like Memory Calculator 1.1.1_RELEASE from
https://download.run.pivotal.io/memory-calculator/trusty/x86_64/memory-calculator-1.1.1_RELEASE
(found in cache)
Memory Settings: -XX:MaxMetaspaceSize=64M -XX:MetaspaceSize=64M
-Xss995K -Xmx382293K -Xms382293K

Then scaling the application to double the memory will result in new
memory settings without having to restage the application.

cf scale my-application -m 1G

-Xmx768M -Xms768M -XX:MaxMetaspaceSize=104857K -XX:MetaspaceSize=104857K
-Xss1M


This new feature is currently available on the master branch of the
buildpack [3] and will be released in due course.


Chris.

[1] https://github.com/cloudfoundry/java-buildpack-memory-calculator
[2] https://github.com/Zteve
[3] https://github.com/cloudfoundry/java-buildpack

--
Christopher Frost - Pivotal UK

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

this setting is because we assume multi-tenant installations. it is
strongly recommended that operators should have their cf configurations and
application security group configurations setup to only allow outbound
connectivity from in containers to other containers by going through the cf
load balancer and not be directly connecting to other cell host/port
mappings of application instances.

--
Thank you,

James Bayer

inline

On Wed, May 13, 2015 at 11:03 PM, Kinjal Doshi <kindoshi(a)gmail.com> wrote:

Hi,

I wanted to understand if orgs and spaces in Pivotal CF contribute towards
accessing services from:

"Pivotal Cloud Foundry" uses open source cloud foundry, so the same
behavior would be in both.

1. Applications deployed in different spaces of same org and

applications can only be directly bound to services in their own space.

you could take credentials from a service in another space and create a
user-provided-service in the space you want to use. however, changing /
deleting the original service would not be directly connected to the
user-provided-service clone you created.

1.
2. Application deployed in different orgs altogether. (spaces would be
different here by default, right?)

yes, an app in a different org from an org/space where a service is would

be in a different org by default and the above still response still applies.

Thanks for your help in advance.

Regards,

Kinjal

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

--
Thank you,

James Bayer

george,

can you explain the scenario that is impacting you currently? e.g. reading
a java stack trace? the app index is shown in the log line. when using the
loggregator websocket client to retrieve logs you should also get the
application id. perhaps that is enough to correlate whatever UI you have on
top of logstash?


On Tue, May 12, 2015 at 7:40 AM, Li, George <guangxing.li(a)pearson.com>
wrote:

Hi,

this is a follow up on the archived posting
https://groups.google.com/a/cloudfoundry.org/forum/?utm_medium=email&utm_source=footer#!msg/vcap-dev/B1W6_vO0oyo/84X1eAtFsKoJ.
I cannot find any new postings on that thread.
I am using Cloud Foundry version
"6.11.2-2a26d55-2015-04-27T21:11:44+00:00" and want to know what options I
have to handle multiple line logs in a multi-tenant environment. Since
multiple instances of multiple applications are all sending logs to a
single Logstash server, is it best to avoid having multiple lines in my
log? I can live with sticking to single line logs except for outputting
exception stack trace, not to mention that I only have control over my
code.

Thanks.

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

--
Thank you,

James Bayer

thanks steve! that's a nice addition to the java buildpack. i think all
java developers have experienced the pain of managing memory explicitly
with -X and -XX args at one point or another. having built-in sane defaults
that auto-adjust is hopefully one less thing java developers have to worry
about when using the java buildpack.

On Tue, May 12, 2015 at 8:12 AM, Christopher Frost <cfrost(a)pivotal.io>
wrote:

When deploying a Java application to Cloud Foundry the Java memory
settings for the application are decided based on the configured memory
weighting during staging. This means that, unlike other apps, if the
application is scaled to give it more memory it needs to be *restage*d it
to get updated Java memory settings. This has now been improved with an
improved memory calculator written by Steve Powell[2]. The Memory
Calculator[1] will be run during every application start to ensure the
application gets up-to-date memory settings, its output is shown during
staging.

-----> Downloading Open JDK Like Memory Calculator 1.1.1_RELEASE from
https://download.run.pivotal.io/memory-calculator/trusty/x86_64/memory-calculator-1.1.1_RELEASE
(found in cache)
Memory Settings: -XX:MaxMetaspaceSize=64M -XX:MetaspaceSize=64M
-Xss995K -Xmx382293K -Xms382293K

Then scaling the application to double the memory will result in new
memory settings without having to restage the application.

cf scale my-application -m 1G

-Xmx768M -Xms768M -XX:MaxMetaspaceSize=104857K -XX:MetaspaceSize=104857K
-Xss1M


This new feature is currently available on the master branch of the
buildpack [3] and will be released in due course.


Chris.

[1] https://github.com/cloudfoundry/java-buildpack-memory-calculator
[2] https://github.com/Zteve
[3] https://github.com/cloudfoundry/java-buildpack

--
Christopher Frost - Pivotal UK

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

--
Thank you,

James Bayer