Re: Issue with crashing Windows apps on Diego
On Tue, Feb 2, 2016 at 9:31 AM, Matthew Horan <mhoran(a)pivotal.io> wrote:
On Mon, Feb 1, 2016 at 7:06 PM, aaron_huber <aaron.m.huber(a)intel.com>In talking with a former team member, I came across the story  where we
made this change. The WebAppServer will listen on the port immediately upon
starting, even if the app has not successfully loaded. This was undesirable
for the common case -- but obviously causes issues for slow apps, or apps
which require authentication. As mentioned in the story, the developers
pointed out that this behavior should be configurable -- but this was never
Hopefully we can see some progress on the proposed healthcheck changes,
which would better address your issue. In the meantime, I'm not sure of the
best course of action. It's quite easy to push an unlaunchable app to
Windows, and there will be little to no debug information available to help
the developer figure out why their app is inaccessible. The current
implementation has its drawbacks, but can be worked around by "disabling"
the health check.