Skip to content

Environment variables are not bound properly when unknown fields are not ignored #3745

Closed
@wujek-srujek

Description

@wujek-srujek

When deploying to Cloud Foundry, the embedded web server (Undertow in my case) must use the port defined in the PORT env variable. Simply deploying the repackaged jar to CF used to work for M2.
After an upgrade to M3, Undertow always starts on its default port 8080, which results in an error: 'Instance (index 0) failed to start accepting connections'. This issue is caused by CF checking if the application listens on the port it defined for it, and if it doesn't, it's an error and the app is killed.
I'm not sure if this is a Boot issue, or maybe Undertow's (I think M3 upgrades Untertow, among others).

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions