tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 60152] New: Allow exceptions from Connector.start() to be caught and handled in code that embeds Tomcat
Date Tue, 20 Sep 2016 10:48:44 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=60152

            Bug ID: 60152
           Summary: Allow exceptions from Connector.start() to be caught
                    and handled in code that embeds Tomcat
           Product: Tomcat 9
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Catalina
          Assignee: dev@tomcat.apache.org
          Reporter: awilkinson@pivotal.io

Currently, when a Connector fails to start, Tomcat logs the exception twice
(once in the protocol and once in the service) and then swallows the exception.
This isn't very friendly when embedding Tomcat as it means that handling of the
exception and reporting it to the user is out of the embedder's control. We'd
like a couple of things to be possible:

1. Catching the exception that's thrown when the Connector is started.
2. Tomcat not to log anything

This would allow an embedder to take complete control of how the problem is
reported to a user.

In discussing this with Mark Thomas, one possibility that he raised was a
Connector equivalent of failCtxIfServletStartFails that both StandardContext
and StandardHost have today.

-- 
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