summaryrefslogtreecommitdiffhomepage
path: root/docs/changes.xml
diff options
context:
space:
mode:
authorAndrew Clayton <a.clayton@nginx.com>2024-03-07 16:16:55 +0000
committerAndrei Zeliankou <zelenkov@nginx.com>2024-03-15 15:12:59 +0000
commit777b7c87827f629a0df00c75d5bd1685c7ce1c35 (patch)
tree93133a2e1a6d713a2ec5d6e43cea6f39b25df27e /docs/changes.xml
parentd7ff6bb4a10e3999f788a2492944c70822441366 (diff)
downloadunit-777b7c87827f629a0df00c75d5bd1685c7ce1c35.tar.gz
unit-777b7c87827f629a0df00c75d5bd1685c7ce1c35.tar.bz2
Wasm-wc: Fix application restarts
Liam reported a problem when trying to restart wasm-wasi-component based applications using the /control/applications/APPLICATION_NAME/restart endpoint. The application would become unresponsive. What was happening was the old application process(es) weren't exit(3)ing and so while we were starting new application processes, the old ones were still hanging around in a non-functioning state. When we are terminating an application it must call exit(3). So that's what we do. We use the return value of nxt_unit_run() as the exit status. Due to exit(3)ing we also need to now explicitly handle the return on error case. Reported-by: Liam Crilly <liam@nginx.com> Fixes: 20ada4b5c ("Wasm-wc: Core of initial Wasm component model language module support") Closes: https://github.com/nginx/unit/issues/1179 Tested-by: Liam Crilly <liam@nginx.com> Tested-by: Danielle De Leo <d.deleo@f5.com> Co-developed-by: Dan Callahan <d.callahan@f5.com> Signed-off-by: Dan Callahan <d.callahan@f5.com> Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
Diffstat (limited to 'docs/changes.xml')
0 files changed, 0 insertions, 0 deletions