The first time the service user attempts wget of war file they'll be prompted to accept the JLab CA self-signed intercepting TLS proxy cert and this demonstrates the need to have a timeout on deploy because at the moment if you don't manually accept the certificate on behalf of the service user the command hangs indefinitely. If you su to the service user and manually run the deploy command the prompt looks like:
Accept certificate? [N]o, [T]emporarily, [P]ermanently : P
Note: The web request times out after 30 seconds or so. However, the backend Java thread remains hung, and worse, is holding an Oracle DB connection open which results in resource exhaustion as the current pool only allows 3-5 connections before failing.
The first time the service user attempts wget of war file they'll be prompted to accept the JLab CA self-signed intercepting TLS proxy cert and this demonstrates the need to have a timeout on deploy because at the moment if you don't manually accept the certificate on behalf of the service user the command hangs indefinitely. If you
suto the service user and manually run the deploy command the prompt looks like:Note: The web request times out after 30 seconds or so. However, the backend Java thread remains hung, and worse, is holding an Oracle DB connection open which results in resource exhaustion as the current pool only allows 3-5 connections before failing.