tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 49030] Processing of Tomcat Connector configuration can leave some connectors uninitialized
Date Wed, 23 Jun 2010 13:08:45 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=49030

--- Comment #4 from Konstantin Kolinko <knst.kolinko@gmail.com> 2010-06-23 09:08:38
EDT ---
I like this, but there are caveats implementing this feature:

1. Connectors that fail in a call to initialize() will also likely to fail in
start(), pause(), stop(). Thus all the loops over connectors have to be
safeguarded.

This includes loops over array returned by StandardService.findConnectors(),
e.g. in ServerLifecycleListener#destroyMBeans(Service).


2. Need to reimplement support for 

org.apache.catalina.startup.EXIT_ON_INIT_FAILURE=true

configuration property [1], [2].

[1] http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html
[2] https://issues.apache.org/bugzilla/show_bug.cgi?id=48625

As a test case for this feature one can try to start a second instance of
Tomcat using the same configuration.

If the above EXIT_ON_INIT_FAILURE setting is added to conf/catalina.properties,
Tomcat 6.0.27 will abort startup on the first init() failure.

If the init() exception were caught and startup continued, as proposed patch
does, the abort does not happen.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message