Thanks,

Daniel and Natalie

It gives a good difference.
How can I try cloud foundry on the local system?
As you were telling about services and add-ons...
we will get these things with the Pivotal cloud foundry.
How can I get services like MySQL or PostgreSQL to try on community
addition?
What could be the steps that I need to follow if I want to connect Mysql
service to apps?

With Regards
Sunil



--
View this message in context: http://cf-dev.70369.x6.nabble.com/Difference-Between-Cloud-foundry-and-Pivotal-Cloud-Foundry-tp7259p7266.html
Sent from the CF Dev mailing list archive at Nabble.com.

Hey, invite pls :)

Sent from my iPhone

On 27 Jul 2017, at 22:35, Michael Maximilien <maxim(a)us.ibm.com> wrote:

FYI...

Please join us for:

1. updates on incubating and proposed projects by respective leaders,
2. overview of https://github.com/cloudfoundry-incubator/cf-extensions project which I will demo and give overview,
3. discussions and QAs

The Zoom info is:
===========
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/5592737187
Or iPhone one-tap (US Toll): +14086380968,,5592737187# or +16465588656,,5592737187#
Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
Meeting ID: 559 273 7187
International numbers available: https://zoom.us/zoomconference?m=92A2yi2UMG55h6OWMvp7GsxQKIou0L3E
===========

If you want an invite for the recurring Zoom call (last Monday every month) then reply directly to me and I will add you.

Zoom you then. Best,

------
dr.max
ibm cloud labs
silicon valley, ca
maximilien.org

--
You received this message because you are subscribed to the Google Groups "cf-extensions-pmc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cf-extensions-pmc+unsubscribe(a)cloudfoundry.org.
To post to this group, send email to cf-extensions-pmc(a)cloudfoundry.org.
To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/cf-extensions-pmc/OFF24EBDF7.42B39E2D-ON0025816A.0075FA52-0025816A.0076983D%40notes.na.collabserv.com.

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Hi Ronak, all,

Thank you for your feedback!

We'll postpone the deletion.
We have built the Diego-Enabler plugin with Golang 1.8.3 and published it to the CF-Community CLI Plugin site as v1.2.4.

Let us consult with the CF community here about deletion again next time something like this comes up.

Cheers,
Dies Koper
Cloud Foundry Product Manager - CLI

To get into a little more detail about the testing differences:

OSS CF is tested extensively. Unit tests, automated acceptance tests,
production monitoring, engineer and PM. We're kind of obsessed with testing.

These tests are run almost entirely on public cloud environments-- mostly
GCP these days.

So with PCF you get an artifact that's also been run through much of the
same testing and more on Openstack, vSphere, and any other IaaSes that are
important to Pivotal customers.

PCF also provides tested upgrade paths beyond "deploy every version," and
backports patches to older versions of CF inside the Elastic Runtime Tile.

- Natalie
Pivotal Cloud Ops





On Wed, Jul 26, 2017 at 1:11 AM Daniel Jones <
daniel.jones(a)engineerbetter.com> wrote:

Pivotal Cloud Foundry adds extra features on top of open source Cloud
Foundry.

Whilst you're best off asking Pivotal sales for the full list of features,
a quick summary includes:

- QA and support - you get packaged releases, that have had testing
performed on them, and support agreements
- Ops Manager and Apps Manager web UIs, in case you don't want to
learn CLIs and underlying technologies
- Additional 'tiles', which are services and add-ons that can be
installed through Ops Manager

Both PCF and OSS CF are used by various folks in production.


Regards,
Daniel Jones - CTO
+44 (0)79 8000 9153
@DanielJonesEB <https://twitter.com/DanielJonesEB>
*EngineerBetter* Ltd <http://www.engineerbetter.com> - UK Cloud Foundry
Specialists

On 25 July 2017 at 10:05, sunil <sunilhvalmiki(a)gmail.com> wrote:

What is difference Between Cloud Foundry and Pivotal Cloud Foundry?




--
View this message in context:
http://cf-dev.70369.x6.nabble.com/Difference-Between-Cloud-foundry-and-Pivotal-Cloud-Foundry-tp7259.html
Sent from the CF Dev mailing list archive at Nabble.com.

Hi Team,

I'm new to cloud foundry and we are setting up CF for our organization.

We have a requirement for one of our apps that it needs openJFX with java 8 . I've tried creating some custom build packs but not successful.
Can some one help me out if there are some build packs which I can use that support openJFX or some steps to add this to default java-buildpack.

Appreciate your help.

Raghuvamsi Uthpala

Office: +91-80-39204567

DevOps - Lead.
Software Engineering Services

Mobile: +91- 9492901250

Email: raghuvamsi.uthpala(a)indegene.com<mailto:raghuvamsi.uthpala(a)indegene.com>

Web: www.indegene.com<http://www.indegene.com/>

[cid:image001.png(a)01D1006F.0E0455B0]<http://www.indegene.com/>

Follow us:

[cid:image002.png(a)01D1006F.0E0455B0]<https://www.linkedin.com/company/68889?trk=tyah&trkInfo=clickedVertical:company,clickedEntityId:68889,idx:2-1-2,tarId:1438602556067,tas:indege>

[cid:image003.png(a)01D1006F.0E0455B0]<https://www.facebook.com/Indegene>



[cid:image004.png(a)01D1006F.0E0455B0]<http://www.indegene.com/atom>



Disclaimer: This email (including any attachments) contains information, which is confidential and may be subject to legal privilege. If you are not the intended recipient, you must not use, distribute, or copy this email. If you have received this email in error, please notify the sender immediately and delete this. Any views expressed in this mail are not necessarily the views of INDEGENE. Thank you.




Disclaimer : This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail to IT(a)Indegene.com and immediately and permanently delete this message and any attachments. Any views expressed in this mail are not necessarily the views of INDEGENE. Thank you.

Pivotal Cloud Foundry adds extra features on top of open source Cloud
Foundry.

Whilst you're best off asking Pivotal sales for the full list of features,
a quick summary includes:

- QA and support - you get packaged releases, that have had testing
performed on them, and support agreements
- Ops Manager and Apps Manager web UIs, in case you don't want to learn
CLIs and underlying technologies
- Additional 'tiles', which are services and add-ons that can be
installed through Ops Manager

Both PCF and OSS CF are used by various folks in production.


Regards,
Daniel Jones - CTO
+44 (0)79 8000 9153
@DanielJonesEB <https://twitter.com/DanielJonesEB>
*EngineerBetter* Ltd <http://www.engineerbetter.com> - UK Cloud Foundry
Specialists

The CF CLI team cut 6.29.0 today.
Deb, yum and Homebrew repos have been updated; binaries, installers and link to release notes are available at:

https://github.com/cloudfoundry/cli#downloads
Org default isolation segments

This release introduces commands to configure a default isolation segment for an org, on which applications are placed from any space that has not explicitly been assigned an isolation segment.
The new commands require a target CF release of v254 (CC API v3.11.0) onwards.
Refer to the documentation<http://docs.cloudfoundry.org/adminguide/isolation-segments.html#set_org_default_is> for details.

Bash tab completion on dash includes long options

Tab completion on a single dash (-) now displays both short and long option names (suppressing short ones when a long one is available) to get a quick overview of all available options to a (sub)command:



$ cf push myapp -<tab><tab>

-b --health-check-type --no-hostname --route-path

-c --help --no-manifest -s

-d --hostname --no-route -t

--docker-image -i --no-start --version

--docker-username -k -p

-f -m --random-route



An enhancement to our upstream Goflags command parser library was accepted to support this. Previously, tab completion on a single dash would only display short options.

Fixed regressions

* add-plugin-repo did not work if the plugin repo URL contained a path in cf CLI v6.28.0. (#1178<https://github.com/cloudfoundry/cli/issues/1178>)
* Refactored commands could fail when obtaining a new access token from an older CF release. (#1175<https://github.com/cloudfoundry/cli/issues/1175>)

Refactored commands

We are in the process of creating a more consistent user experience; our goal is to standardize UI output.
For example, warnings and errors will consistently be outputted to stderr instead of stdout and English table and key-value headers displayed in lowercase.
As we iterate through the list of commands, we are also focusing on improving performance and stability.
Please review your scripts if they depend on the output of these commands.

List of improved commands in this release:

* restage
* restart

Updated commands

* set-org-default-isolation-segment was added to set the default isolation segment used for apps in spaces in an org
* reset-org-default-isolation-segment was added to reset the default isolation segment used for apps in spaces of an org
* org now displays the configured org's default isolation segment
* restage and restart now display a more detailed error message when staging fails
* set-space-isolation-segment and reset-space-isolation-segment now have better command descriptions
* security-groups now won't fail if a security group is deleted while retrieving its details
* enable-feature-flag and disable-feature-flag now have better, concise command descriptions. (#1174<https://github.com/cloudfoundry/cli/issues/1174>)
* set-env now includes unset-env in its SEE ALSO help section. (#1179<https://github.com/cloudfoundry/cli/issues/1179>)

New & updated community plugins

* mysql-plugin v1.4.0: https://github.com/andreasf/cf-mysql-plugin
* network-policy v1.2.0: https://github.com/cloudfoundry-incubator/cf-networking-release
Enjoy!

Regards,
Dies Koper
Cloud Foundry Product Manager - CLI

What is difference Between Cloud Foundry and Pivotal Cloud Foundry?




--
View this message in context: http://cf-dev.70369.x6.nabble.com/Difference-Between-Cloud-foundry-and-Pivotal-Cloud-Foundry-tp7259.html
Sent from the CF Dev mailing list archive at Nabble.com.

Max - The intent is the same and the UX is nearly identical (Scott's uses a service binding but that's the only real difference). This would be part of the OSS distribution is the key difference.

Hi Eric
I am wondering why don't design placement tag just as K8S
label/selector? Let client specify the tag at runtime and choose their own
scheduler is useful



--
View this message in context: http://cf-dev.70369.x6.nabble.com/Isolation-Segments-Question-about-a-Cell-with-mulitiple-placement-tag-s-tp6533p7257.html
Sent from the CF Dev mailing list archive at Nabble.com.

But when started someone out there was guiding me in the wrong direction
new to this but after seeing the results now I know which direction to take
I've had some downtime do to illness with my family members and water
damage to my equipment but even tonight while trying to do something
someone we'll message me they were guided me in the wrong direction I will
focus on the task at hand like stylus I want make something good

On Jul 23, 2017 6:38 AM, "Jenny Hilton [via CF Dev]" <
ml+s70369n7245h87(a)n6.nabble.com> wrote:

Ping :- )


------------------------------
If you reply to this email, your message will be added to the discussion
below:
http://cf-dev.70369.x6.nabble.com/cf-dev-Manage-Cloud-
foundry-Org-space-tp7229p7245.html
To start a new topic under CF Dev, email ml+s70369n1h23(a)n6.nabble.com
To unsubscribe from CF Dev, click here
<http://cf-dev.70369.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=dG9tbXlvc2hpZWxkczcxQGdtYWlsLmNvbXwxfDYzNTk2MjAwOA==>
.
NAML
<http://cf-dev.70369.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>

--
View this message in context: http://cf-dev.70369.x6.nabble.com/Re-cf-dev-Re-Manage-Cloud-foundry-Org-space-tp7246.html
Sent from the CF Dev mailing list archive at Nabble.com.

Ping :- )

Sorry been out of commission water damage on my other phone just glad to be
back
On Jul 18, 2017 7:40 PM, "Mike Youngstrom [via CF Dev]" <
ml+s70369n7221h43(a)n6.nabble.com> wrote:

This sounds like a great solution to a very old nagging problem. I'm
excited to see this issue moving forward. I assume that if the mTLS
handshake fails then the router will try the next instance in the table as
if the TCP connection had failed?

Mike

On Tue, Jul 18, 2017 at 5:25 PM, Shannon Coen <[hidden email]
<http:///user/SendEmail.jtp?type=node&node=7221&i=0>> wrote:

After weeks of exploration by the Routing, Networking, and Diego teams, we
have a solution in mind and will begin implementation shortly.

TL;DR
We plan to install a proxy in every container to terminate mTLS for
requests
from Gorouter, enabling validation of application identity and
optimization
for availability over consistency. The solution will be transparent to
application developers.

Our proposal has been updated with details on this solution, and we
welcome
your comments:
https://docs.google.com/document/d/1zkPVGNnBX18rWdOpinIEtRxt
e3kwpVhIyS9_WM3ITqM/edit?usp=sharing





--
View this message in context: http://cf-dev.70369.x6.nabble.
com/cf-dev-Increasing-Routing-availability-in-the-event-of-f
ailure-with-route-registration-tp6703p7220.html
Sent from the CF Dev mailing list archive at Nabble.com.

------------------------------
If you reply to this email, your message will be added to the discussion
below:
http://cf-dev.70369.x6.nabble.com/cf-dev-Increasing-Routing-
availability-in-the-event-of-failure-with-route-
registration-tp6703p7221.html
To start a new topic under CF Dev, email ml+s70369n1h23(a)n6.nabble.com
To unsubscribe from CF Dev, click here
<http://cf-dev.70369.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=dG9tbXlvc2hpZWxkczcxQGdtYWlsLmNvbXwxfDYzNTk2MjAwOA==>
.
NAML
<http://cf-dev.70369.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>

--
View this message in context: http://cf-dev.70369.x6.nabble.com/Re-cf-dev-Re-Re-Increasing-Routing-availability-in-the-event-of-failure-with-route-registration-tp7244.html
Sent from the CF Dev mailing list archive at Nabble.com.

Hey All -

We are holding a Cloud Foundry meetup at Pivotal in San Francisco on
Tuesday, July 25. This session will focus on how to use CredHub in your
environment to manage platform and service credentials. Further details in
the invite linked below.

https://www.meetup.com/Cloud-Foundry-Users-San-Francisco-Bay-Area/events/241697978/

Hope to see you there.
-Dan

Hi Colleages,

Can somebody tell me cf api which is avaialble to findout duplicated users
in uaadb.

BRs, Gowrisankar

I recognized why token log logged twice .
it was just log4j configuration problem
Thanks.

Thanks Filip for the information for UAA DB. Any idea on Cloud controller
DB (postgresSQL) design ? documetation ?

Thanks Ben Hale for replying

I still have a question about 401 error occurred sometimes

as Ben Hale said, i set the logger and i see the log when 401 error occurs
as you can see, it seems that token is issued
2017-07-21 11:08:10,751 DEBUG [cloudfoundry-client.token] (AbstractUaaTokenProvider.java:151) - Access Token Issued At: 2017-07-21T02:08:14 UTC
2017-07-21 11:08:10,751 DEBUG [cloudfoundry-client.token] (AbstractUaaTokenProvider.java:151) - Access Token Issued At: 2017-07-21T02:08:14 UTC
2017-07-21 11:08:10,751 DEBUG [cloudfoundry-client.token] (AbstractUaaTokenProvider.java:152) - Access Token Expires At: 2017-07-21T02:18:14 UTC
2017-07-21 11:08:10,751 DEBUG [cloudfoundry-client.token] (AbstractUaaTokenProvider.java:152) - Access Token Expires At: 2017-07-21T02:18:14 UTC
reactor.ipc.netty.http.client.HttpClientException: HTTP request failed with code: 401.
Failing URI: /firehose/cf-nozzle

but i received error 401
I don't why error is occurred
and my token log is logged twice
i configured TokenProvider and DopplerClient below
doppler client has @Bean annotation and TokenProvider has no @Bean annotation

public TokenProvider tokenProvider(String password, String username) {
return PasswordGrantTokenProvider.builder()
.password(password)
.username(username)
.build();
}
@Bean
public DopplerClient dopplerClient(NozzleProperties properties) {
return ReactorDopplerClient.builder()
.connectionContext(connectionContext(properties.getApiHost(), properties.isSkipSslValidation()))
.tokenProvider(tokenProvider(properties.getPassword(), properties.getUsername()))
.build();
}
is it wrong?
may these configuration can make token log twice??

Thanks
------
the full log is below

2017-07-21 11:08:10,268 DEBUG [cloudfoundry-client.token] (AbstractUaaTokenProvider.java:264) - Negotiating using token provider
2017-07-21 11:08:10,268 DEBUG [cloudfoundry-client.token] (AbstractUaaTokenProvider.java:264) - Negotiating using token provider
2017-07-21 11:08:10,704 DEBUG [cloudfoundry-client.token] (AbstractUaaTokenProvider.java:193) - Refresh Token: a93d6589d929470880b8e6f8878dea1a-r
2017-07-21 11:08:10,704 DEBUG [cloudfoundry-client.token] (AbstractUaaTokenProvider.java:193) - Refresh Token: a93d6589d929470880b8e6f8878dea1a-r
2017-07-21 11:08:10,725 DEBUG [cloudfoundry-client.token] (AbstractUaaTokenProvider.java:147) - Access Token: eyJhbGciOiJSUzI1NiIsImtpZCI6ImxlZ2FjeS10b2tlbi1rZXkiLCJ0eXAiOiJKV1QifQ.eyJqdGkiOiI1ZjE3Y2YwY2ViZWQ0OTE2YTFjZjA5OTYwZDg2OTdjMCIsInN1YiI6IjI2OGM3MGZhLTExYmUtNGIxNS04ZDgyLTdkM2UxYzA1NDI1ZSIsInNjb3BlIjpbImNsb3VkX2NvbnRyb2xsZXIuYWRtaW4iLCJyb3V0aW5nLnJvdXRlcl9ncm91cHMucmVhZCIsImNsb3VkX2NvbnRyb2xsZXIud3JpdGUiLCJkb3BwbGVyLmZpcmVob3NlIiwib3BlbmlkIiwicm91dGluZy5yb3V0ZXJfZ3JvdXBzLndyaXRlIiwic2NpbS5yZWFkIiwidWFhLnVzZXIiLCJjbG91ZF9jb250cm9sbGVyLnJlYWQiLCJwYXNzd29yZC53cml0ZSIsInNjaW0ud3JpdGUiXSwiY2xpZW50X2lkIjoiY2YiLCJjaWQiOiJjZiIsImF6cCI6ImNmIiwiZ3JhbnRfdHlwZSI6InBhc3N3b3JkIiwidXNlcl9pZCI6IjI2OGM3MGZhLTExYmUtNGIxNS04ZDgyLTdkM2UxYzA1NDI1ZSIsIm9yaWdpbiI6InVhYSIsInVzZXJfbmFtZSI6ImFkbWluIiwiZW1haWwiOiJhZG1pbiIsImF1dGhfdGltZSI6MTUwMDYwMjg5NCwicmV2X3NpZyI6ImRmOThiNTI1IiwiaWF0IjoxNTAwNjAyODk0LCJleHAiOjE1MDA2MDM0OTQsImlzcyI6Imh0dHBzOi8vdWFhLjExNS42OC40Ni4xODYueGlwLmlvL29hdXRoL3Rva2VuIiwiemlkIjoid
WFhIiwiYXVkIjpbImNsb3VkX2NvbnRyb2xsZXIiLCJzY2ltIiwicGFzc3dvcmQiLCJjZiIsInVhYSIsIm9wZW5pZCIsImRvcHBsZXIiLCJyb3V0aW5nLnJvdXRlcl9ncm91cHMiXX0.SOVe6D-N-WHx3r12y6b-eo4Vw7cE8chGqLyavcxwLC239ntikXqnCEZciG0WIh-KkgWA9v3-spyL4QEi5traLQxPhutBRUrh7rvPPEJBc3NJqG4adT4sIBhrdS0ZPF5zMdSQcY1Sm195KNxfOG9rX-AF8_B-KOvJWkbHmokQiMqiOLPbOuTgy5mWhHW_A_zNJ5ChZR7YI7jlY5t_nkc1TousuQg9oVQ89y7-hXq9LSYHcxzWSOGiheyiLSw7oqRYmmWRYphN5jc38H6E_e7-fVvqGYyhwyQvHlrHjy6-56W_hO0DXAWafYQX_JdS0I83SDqXQRz8xg1ungNzT7Eaog
2017-07-21 11:08:10,725 DEBUG [cloudfoundry-client.token] (AbstractUaaTokenProvider.java:147) - Access Token: eyJhbGciOiJSUzI1NiIsImtpZCI6ImxlZ2FjeS10b2tlbi1rZXkiLCJ0eXAiOiJKV1QifQ.eyJqdGkiOiI1ZjE3Y2YwY2ViZWQ0OTE2YTFjZjA5OTYwZDg2OTdjMCIsInN1YiI6IjI2OGM3MGZhLTExYmUtNGIxNS04ZDgyLTdkM2UxYzA1NDI1ZSIsInNjb3BlIjpbImNsb3VkX2NvbnRyb2xsZXIuYWRtaW4iLCJyb3V0aW5nLnJvdXRlcl9ncm91cHMucmVhZCIsImNsb3VkX2NvbnRyb2xsZXIud3JpdGUiLCJkb3BwbGVyLmZpcmVob3NlIiwib3BlbmlkIiwicm91dGluZy5yb3V0ZXJfZ3JvdXBzLndyaXRlIiwic2NpbS5yZWFkIiwidWFhLnVzZXIiLCJjbG91ZF9jb250cm9sbGVyLnJlYWQiLCJwYXNzd29yZC53cml0ZSIsInNjaW0ud3JpdGUiXSwiY2xpZW50X2lkIjoiY2YiLCJjaWQiOiJjZiIsImF6cCI6ImNmIiwiZ3JhbnRfdHlwZSI6InBhc3N3b3JkIiwidXNlcl9pZCI6IjI2OGM3MGZhLTExYmUtNGIxNS04ZDgyLTdkM2UxYzA1NDI1ZSIsIm9yaWdpbiI6InVhYSIsInVzZXJfbmFtZSI6ImFkbWluIiwiZW1haWwiOiJhZG1pbiIsImF1dGhfdGltZSI6MTUwMDYwMjg5NCwicmV2X3NpZyI6ImRmOThiNTI1IiwiaWF0IjoxNTAwNjAyODk0LCJleHAiOjE1MDA2MDM0OTQsImlzcyI6Imh0dHBzOi8vdWFhLjExNS42OC40Ni4xODYueGlwLmlvL29hdXRoL3Rva2VuIiwiemlkIjoid
WFhIiwiYXVkIjpbImNsb3VkX2NvbnRyb2xsZXIiLCJzY2ltIiwicGFzc3dvcmQiLCJjZiIsInVhYSIsIm9wZW5pZCIsImRvcHBsZXIiLCJyb3V0aW5nLnJvdXRlcl9ncm91cHMiXX0.SOVe6D-N-WHx3r12y6b-eo4Vw7cE8chGqLyavcxwLC239ntikXqnCEZciG0WIh-KkgWA9v3-spyL4QEi5traLQxPhutBRUrh7rvPPEJBc3NJqG4adT4sIBhrdS0ZPF5zMdSQcY1Sm195KNxfOG9rX-AF8_B-KOvJWkbHmokQiMqiOLPbOuTgy5mWhHW_A_zNJ5ChZR7YI7jlY5t_nkc1TousuQg9oVQ89y7-hXq9LSYHcxzWSOGiheyiLSw7oqRYmmWRYphN5jc38H6E_e7-fVvqGYyhwyQvHlrHjy6-56W_hO0DXAWafYQX_JdS0I83SDqXQRz8xg1ungNzT7Eaog
2017-07-21 11:08:10,751 DEBUG [cloudfoundry-client.token] (AbstractUaaTokenProvider.java:151) - Access Token Issued At: 2017-07-21T02:08:14 UTC
2017-07-21 11:08:10,751 DEBUG [cloudfoundry-client.token] (AbstractUaaTokenProvider.java:151) - Access Token Issued At: 2017-07-21T02:08:14 UTC
2017-07-21 11:08:10,751 DEBUG [cloudfoundry-client.token] (AbstractUaaTokenProvider.java:152) - Access Token Expires At: 2017-07-21T02:18:14 UTC
2017-07-21 11:08:10,751 DEBUG [cloudfoundry-client.token] (AbstractUaaTokenProvider.java:152) - Access Token Expires At: 2017-07-21T02:18:14 UTC

reactor.ipc.netty.http.client.HttpClientException: HTTP request failed with code: 401.
Failing URI: /firehose/cf-nozzle
Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException:
Assembly trace from producer [reactor.core.publisher.FluxMap] :
reactor.core.publisher.Flux.checkpoint(Flux.java:2914)
org.cloudfoundry.reactor.doppler.ReactorDopplerEndpoints.firehose(ReactorDopplerEndpoints.java:50)
org.cloudfoundry.reactor.doppler._ReactorDopplerClient.firehose(_ReactorDopplerClient.java:44)
org.cloudfoundry.reactor.doppler.ReactorDopplerClient.firehose(ReactorDopplerClient.java:14)
com.skcc.producer.nozzle.FirehoseReader.start(FirehoseReader.java:63)
org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:175)
org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:50)
org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:348)
org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:151)
org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:114)
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:880)
org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.finishRefresh(EmbeddedWebApplicationContext.java:144)
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:546)
org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:122)
org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693)
org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360)
org.springframework.boot.SpringApplication.run(SpringApplication.java:303)
org.springframework.boot.SpringApplication.run(SpringApplication.java:1118)
org.springframework.boot.SpringApplication.run(SpringApplication.java:1107)
com.skcc.producer.CfProducerApplication.main(CfProducerApplication.java:31)
Error has been observed by the following operator(s):
|_ Flux.checkpoint(ReactorDopplerEndpoints.java:50)

I'm pleased to announce the release of Java Buildpacks v3.19 and v4.3. As always there are some bug fixes and a whole load of new functionality. Please see the release notes[1][2] for details about these and past releases.

As described in the release announcement for 4.0, the three month migration period will be completing shortly. During this period we've received no reports of any major problems and are ready to make 4.x the default releases for Cloud Foundry. We expect v3.19 to be both the final 3.x release, and the final 3.x release that is the default. With the release of v4.4 (historically this will be about 3 weeks from now), 4.x will become the default for all Java users on Cloud Foundry.

Thanks to everyone that provided feedback via GitHub and Slack during the migration period.


-Ben Hale
Cloud Foundry Java Experience


[1]: https://github.com/cloudfoundry/java-buildpack/releases/tag/v3.19
[2]: https://github.com/cloudfoundry/java-buildpack/releases/tag/v4.3