You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As stated in the docs this should not create errors, specifically port binding errors with undertow but looking at the code it will most likely fail with other containers as well.
Calling this method on an already started container has no effect.
public interface EmbeddedServletContainer {
/**
* Starts the embedded servlet container. Calling this method on an already started
* container has no effect.
* @throws EmbeddedServletContainerException if the container cannot be started
*/
void start() throws EmbeddedServletContainerException;
...
}
I am trying to start the embedded container very early by manually calling start() but the EmbeddedWebApplicationContext will always call start() again and the application fails to start.
Implementations of EmbeddedServletContainer should safe guard from this behavior.
The text was updated successfully, but these errors were encountered:
Update `EmbeddedServletContainer` implementations to ensure that stop
can be called even if start has not. This allows servers that are
partially started during `initialize()` to still be shut down.
This commit fixes a regression caused by commit 0af53b3.
See gh-8036Fixesgh-8224Closesgh-8227
As stated in the docs this should not create errors, specifically port binding errors with undertow but looking at the code it will most likely fail with other containers as well.
I am trying to start the embedded container very early by manually calling
start()
but theEmbeddedWebApplicationContext
will always callstart()
again and the application fails to start.Implementations of
EmbeddedServletContainer
should safe guard from this behavior.The text was updated successfully, but these errors were encountered: