tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 51713] Bad Connector protocol causes NullPointerException when using Executor
Date Thu, 25 Aug 2011 00:33:53 GMT

Konstantin Kolinko <> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #3 from Konstantin Kolinko <> 2011-08-25 00:33:53
UTC ---
Fixed the message in Connector constructor in trunk in r1161322.
Backported to 7.0.x and will be in 7.0.21.

Regarding whether or not rethrow the exception from inside of Connector

On one hand, such an error is nearly fatal. If I do not configure an Executor,
there are a lot of failures that follow. None of webapps is able to start
because of NPE in connector.getAttribute() call in
ApplicationContext.populateSessionTrackingModes() - stacktrace is below.

On other hand, Tomcat as a whole does start up and is manageable. There is
*.EXIT_ON_INIT_FAILURE system property that one can use to turn this into a
fatal failure.

If the ClassNotFoundException from Connector constructor were rethrown, the
startup sequence aborts immediately. It might be not what everyone wants.

I think this issue is sufficiently addressed. I do not intend to backport this
to 6.0.

NPE in ApplicationContext.populateSessionTrackingModes():

SEVERE: ContainerBase.addChild: start: 
org.apache.catalina.LifecycleException: Failed to start component
Caused by: java.lang.NullPointerException
  at org.apache.catalina.connector.Connector.getProperty(
  at org.apache.catalina.connector.Connector.getAttribute(

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message