Alex Salauyou:
En nuestro proyecto, tenemos varios módulos basados en primavera, que se desplieguen en Era como aplicaciones web. Tenemos que saltar despliegue, o detener un módulo si su inicialización contexto primavera falla (es decir, ContextLoaderListener#contextInitializedo DispatcherServlet#initse produce una excepción). Ahora bien, si tal sucede, se consiguió aplicación desplegada y aperturas, pero vuelve HTTP 500 para cualquier solicitud.
Websphere 8.5.5
Pregunta relacionada: https://stackoverflow.com/a/272747/3459206
Thomas Bitonti:
Este APAR parece ser relevante:
https://www-01.ibm.com/support/docview.wss?uid=swg1PI58875
A partir del texto APAR:
Listener exceptions typically should not stop the application
from starting up for service. However, some applications depend
on their listeners to do the necessary setup before the
application is started for service. Such applications prefer to
stop the application from starting up when there is any
exception in their listeners.
conclusión problema
The WebContainer Container code was modified to provide an
option to stop the application when there is any listener
exception during the application starting up process.
A new WebContainer custom property needs to be set to enable the
behavior provided by this APAR:
For Full Profiles
com.ibm.ws.webcontainer.stopappstartuponlistenerexception = true
(default is false)
For Liberty Profile
stopappstartuponlistenerexception=true
The fix for this APAR is currently targeted for inclusion in
WebSphere Application Server fix packs 8.5.5.11 and 9.0.0.2,
and Liberty 16.0.0.3
Vea el enlace de APAR para obtener información adicional.