When AwsApiProxyTestServer is closed, it should release all of its resources.
Actual Behaviour
AwsApiProxyTestServer creates a custom Jetty web server handler AwsProxyHandler. This handler has its own application context. AwsApiProxyTestServer never calls AwsProxyHandler.destroy(), so the application context is never stopped. Since the application context will typically contain a data source, we also have leaked DB connections as a result.
Expected Behavior
When
AwsApiProxyTestServer
is closed, it should release all of its resources.Actual Behaviour
AwsApiProxyTestServer
creates a custom Jetty web server handlerAwsProxyHandler
. This handler has its own application context.AwsApiProxyTestServer
never callsAwsProxyHandler.destroy()
, so the application context is never stopped. Since the application context will typically contain a data source, we also have leaked DB connections as a result.Steps To Reproduce
No response
Environment Information
No response
Example Application
No response
Version
4.3.2