[
https://issues.apache.org/jira/browse/GERONIMO-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated GERONIMO-4398:
-----------------------------------
Fix Version/s: (was: 2.2)
Wish List
IMO if implemented this needs to be configurable policy rather than hardcoded
behavior. At the opposite extreme, in my experience tomcat provides no
indicate that an app didn't start when you deploy it, so its pretty hard to
know you should take action.
If you've assembled a custom server, you may well want it to shut down if it
can't start completely. The lack of distinction between server plugins and
application plugins means you would need some way to distinguish "port 1099
isn't available, this server wont be manageable or possible to shut down" from
"my experimental app couldn't find its config file and threw an exception".
> Server should not fail to startup if application fails to start up
> ------------------------------------------------------------------
>
> Key: GERONIMO-4398
> URL: https://issues.apache.org/jira/browse/GERONIMO-4398
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: general
> Reporter: Jürgen Weber
> Fix For: Wish List
>
>
> When an application fails to start up, the server will not come up. The
> server should simply ignore the failing application and start up anyway, so
> the user has a chance to remove the failing application without having to
> edit config.xml
> e.g.
> Caused by: org.apache.geronimo.gbean.InvalidConfigurationException:
> Configuration gbean failed to start ldap/LDAPServlet/0.9/war
> reason: Missing dependency: novell/jldap/2008.03.01/jar
> ....
> 2008-11-07 12:58:02,236 DEBUG [AdminConsoleExtensionGBean] Stopped
> AdminConsoleExtensionGBean for Applications/EJB JARs
> 2008-11-07 12:58:02,239 DEBUG [JettyWebAppContext] JettyWebAppContext stopped
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
