Open lmsurpre opened 2 years ago
plan: issue a kill and ask java to leave a dump, then see what threads are running.
note: shutdown happens immediately if the server hasn't serviced any requests yet. but i just ran an experiment where we issues a GET /metadata
and then a couple requests that errored out...after that it took the full 30 seconds to shut down.
Is your feature request related to a problem? Please describe. When you sent SIGINT to liberty (e.g. by asking the container to stop) it has a quiesce period that is 30s by default. But if there's nothing happening, it should shut down sooner.
Unfortunately, in our container, this never seems to happen.
Describe the solution you'd like Figure out what is holding up our shutdown and fix it.
Describe alternatives you've considered
Acceptance Criteria
GIVEN a running ibm-fhir-server container (use
-i
and-t
unless we fix #3565) AND its not processing any requests WHEN you interupt the process (e.g. via control+c) THEN it should shut down right away (e.g. within 2 seconds)Additional context