Re: [tomcat] branch main updated: Switch from Cobertura to JaCoCo for code coverage

2021-11-27 Thread Mark Thomas

On 27/11/2021 04:17, Christopher Schultz wrote:

Mark,

On 11/8/21 08:55, Mark Thomas wrote:

On 08/11/2021 12:42, ma...@apache.org wrote:

This is an automated email from the ASF dual-hosted git repository.

markt pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat.git


The following commit(s) were added to refs/heads/main by this push:
  new b15b713  Switch from Cobertura to JaCoCo for code coverage
b15b713 is described below

commit b15b7130ced07cfe36961531dad4642a422e9500
Author: Mark Thomas 
AuthorDate: Mon Nov 8 12:41:36 2021 +

 Switch from Cobertura to JaCoCo for code coverage


Thoughts on back-porting this? We don't need to back-port it. The 
primary benefit I see is consistency.


I only just read this; sorry for not seeing it earlier in the month.

I don't mind the back-port; I was just curious why you decided to switch 
code-coverage tools. I don't recall seeing a discussion on the list. I'm 
not demanding such a discussion, it's just that you are usually very 
good about asking for feedback before making a tooling change like that.


I think I mentioned the reasoning somewhere but I can't find it now so I 
am happy to provide an explanation here.


The short version is that Cobertura doesn't work with Java 11 and there 
was no indication that Java 11 support was going to be available soon.


This has been a problem for a while but I only noticed it when I was 
trying to get the builds working on the upgraded BuildBot CI 
infrastructure. I did a little research and saw JaCoCo which was a name 
a recognised from other ASF projects using it - primarily Commons.


In addition to Java 11 support, a big advantage of JaCoCo is that it can 
handle tests running in parallel. That reduces the overnight CI runs 
that generate the coverage reports from ~4 hours to ~1 hour.


I've no objection to considering alternatives if folks want to propose 
one as I didn't do an exhaustive search. Equally, I'm happy sticking 
with JaCoCo.


Mark

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



Re: default context path

2021-11-27 Thread Christopher Schultz

Mark,

On 11/25/21 17:18, Mark Thomas wrote:

Hi all,

I am working on updating the Servlet TCK for Servlet 6 and I have been 
discussing with the Jakarta Servlet community whether or not we could 
disable the TCK test that checks default-context-path support.


Tomcat doesn't implement this feature as the container is allowed to 
override this default and we always do - primarily to avoid a bunch of 
edge cases.


Just how dangerous are these edge cases? How are other containers 
implementing these safely? Or is it a question of underlying 
implementation-specific details that make supporting this safely kind of 
a pain in Tomcat?


Other containers do implement the feature and the preference looks to be 
keeping the TCK test enabled.


If we want to fully pass the TCK, one option is to hard-code the 
deployer to deploy the specific TCK WAR to the correct path if 
STRICT_SERVLET_COMPLIANCE was enabled. This is a fairly ugly hack but it 
would enable Tomcat to fully pass the TCK.


What do we think?
a) Do we want to fully pass the TCK? Is a hack along the lines I
    described an acceptable way to do this?


I think we'd like to be able to pass the TCK, even if it requires a bit 
of a hack to get it done.


Some users run Tomcat in STRICT_SERVLET_COMPLIANCE mode. Would that 
auto-deploy some weird TCK-only WAR file into their environments? That's 
obviously not okay to do. I'm not sure I'm fully understanding your 
suggestion.



b) Do we do nothing now and keep this as an option if we get to the
    point where we do want to fully pass the TCK and certify compliance?


-0


c) Do we make a formal challenge of the TCK test on the grounds the
    little documentation there is says the container can override this
    default so the test is invalid on the basis it doesn't allow for the
    override?


+0

For many standards, there are "must address" verses "may address" 
line-items. This one seems to be "may address" and I think therefore the 
TCK needs to treat it as such. If the EG chooses not to 
clarify^H^H^H^H^H^H^H change the rules to make this feature required, 
they should change the test such that the TCK report says 
"default-context-path: NOT ADDRESSED (OK)" instead of 
"default-context-path: FAILED".


Assuming the Servlet team decides to keep the test, I am leaning towards 
b) or maybe a)


Thoughts?

The last time we discussed this:
https://tomcat.markmail.org/thread/4g7nb36fzf4byrej


-chris


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



Re: default context path

2021-11-27 Thread Mark Thomas

On 27/11/2021 19:03, Christopher Schultz wrote:

Mark,

On 11/25/21 17:18, Mark Thomas wrote:

Hi all,

I am working on updating the Servlet TCK for Servlet 6 and I have been 
discussing with the Jakarta Servlet community whether or not we could 
disable the TCK test that checks default-context-path support.


Tomcat doesn't implement this feature as the container is allowed to 
override this default and we always do - primarily to avoid a bunch of 
edge cases.


Just how dangerous are these edge cases?


The edge cases are around conflicts. If the default-context-path 
conflicts with a WAR, DIR or XML file. Is there a priority order? Should 
behaviour be consistent regardless of deployment order?


No dangerous but it creates potential for inconsistent and/or unexpected 
behaviour.



How are other containers implementing these safely?


Generally they are failing deployments. Which ones in which scenarios 
will vary as none of this is specified in the spec.


Or is it a question of underlying 
implementation-specific details that make supporting this safely kind of 
a pain in Tomcat?


It is more that handling the edge cases is non-trivial and is 
particularly annoying as we have a deployment system designed to avoid 
exactly these sort of conflicts.


Other containers do implement the feature and the preference looks to 
be keeping the TCK test enabled.


If we want to fully pass the TCK, one option is to hard-code the 
deployer to deploy the specific TCK WAR to the correct path if 
STRICT_SERVLET_COMPLIANCE was enabled. This is a fairly ugly hack but 
it would enable Tomcat to fully pass the TCK.


What do we think?
a) Do we want to fully pass the TCK? Is a hack along the lines I
    described an acceptable way to do this?


I think we'd like to be able to pass the TCK, even if it requires a bit 
of a hack to get it done.


Yes but how much? We haven't passed this particular test for years. We 
have been happy saying we pass the TCK except the one test we expect to 
fail because Tomcat always overrides the setting (as allowed for this 
feature).


I'd like to pass the TCK but I don't think we need to. If we wanted to 
certify Tomcat as compliant then that would be different.


Some users run Tomcat in STRICT_SERVLET_COMPLIANCE mode. Would that 
auto-deploy some weird TCK-only WAR file into their environments? That's 
obviously not okay to do. I'm not sure I'm fully understanding your 
suggestion.


The suggestion is something along the lines of:

if (STRICT_SERVLET_COMPLIANCE &&
nameOfWar.equals("servlet_spec_defaultcontextpath.war") {
dirName = "defaultContextPath";
} else {
// derive DIR name from WAR name as usual
...
}

HTH,

Mark


b) Do we do nothing now and keep this as an option if we get to the
    point where we do want to fully pass the TCK and certify compliance?


-0


c) Do we make a formal challenge of the TCK test on the grounds the
    little documentation there is says the container can override this
    default so the test is invalid on the basis it doesn't allow for the
    override?


+0

For many standards, there are "must address" verses "may address" 
line-items. This one seems to be "may address" and I think therefore the 
TCK needs to treat it as such. If the EG chooses not to 
clarify^H^H^H^H^H^H^H change the rules to make this feature required, 
they should change the test such that the TCK report says 
"default-context-path: NOT ADDRESSED (OK)" instead of 
"default-context-path: FAILED".


Assuming the Servlet team decides to keep the test, I am leaning 
towards b) or maybe a)


Thoughts?

The last time we discussed this:
https://tomcat.markmail.org/thread/4g7nb36fzf4byrej


-chris


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



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



Bug report for Taglibs [2021/11/28]

2021-11-27 Thread bugzilla
+---+
| Bugzilla Bug ID   |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved)   |
| |   +-+
| |   | Severity: BLK=Blocker CRI=Critical  REG=Regression  MAJ=Major   |
| |   |   MIN=Minor   NOR=NormalENH=Enhancement TRV=Trivial |
| |   |   +-+
| |   |   | Date Posted |
| |   |   |  +--+
| |   |   |  | Description  |
| |   |   |  |  |
|38193|Ass|Enh|2006-01-09|[RDC] BuiltIn Grammar support for Field   |
|38600|Ass|Enh|2006-02-10|[RDC] Enable RDCs to be used in X+V markup (X+RDC)|
|42413|New|Enh|2007-05-14|[PATCH] Log Taglib enhancements   |
|46052|New|Nor|2008-10-21|SetLocaleSupport is slow to initialize when many l|
|48333|New|Enh|2009-12-02|TLD generator |
|57548|New|Min|2015-02-08|Auto-generate the value for org.apache.taglibs.sta|
|57684|New|Min|2015-03-10|Version info should be taken from project version |
|59359|New|Enh|2016-04-20|(Task) Extend validity period for signing KEY - be|
|59668|New|Nor|2016-06-06|x:forEach retains the incorrect scope when used in|
|61875|New|Nor|2017-12-08|Investigate whether Xalan can be removed  |
|64649|New|Nor|2020-08-06|XSLT transformation - document('') doesn't return |
|65491|New|Nor|2021-08-09|Behavior differences with c:import when flushing o|
+-+---+---+--+--+
| Total   12 bugs   |
+---+

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



Bug report for Tomcat 8 [2021/11/28]

2021-11-27 Thread bugzilla
+---+
| Bugzilla Bug ID   |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved)   |
| |   +-+
| |   | Severity: BLK=Blocker CRI=Critical  REG=Regression  MAJ=Major   |
| |   |   MIN=Minor   NOR=NormalENH=Enhancement TRV=Trivial |
| |   |   +-+
| |   |   | Date Posted |
| |   |   |  +--+
| |   |   |  | Description  |
| |   |   |  |  |
|55243|New|Enh|2013-07-11|Add special search string for nested roles|
|55470|New|Enh|2013-08-23|Help users for ClassNotFoundExceptions during star|
|55477|New|Enh|2013-08-23|Add a solution to map a realm name to a security r|
|55675|New|Enh|2013-10-18|Checking and handling invalid configuration option|
|55788|New|Enh|2013-11-16|TagPlugins should key on tag QName rather than imp|
|56148|New|Enh|2014-02-17|support (multiple) ocsp stapling  |
|56166|New|Enh|2014-02-20|Suggestions for exception handling (avoid potentia|
|56300|New|Enh|2014-03-22|[Tribes] No useful examples, lack of documentation|
|56398|New|Enh|2014-04-11|Support Arquillian-based unit testing |
|56402|New|Enh|2014-04-11|Add support for HTTP Upgrade to AJP components|
|56438|New|Enh|2014-04-21|If jar scan does not find context config or TLD co|
|56448|New|Enh|2014-04-23|Implement a robust solution for client initiated S|
|56522|Opn|Enh|2014-05-14|jasper-el 8 does not comply to EL Spec 3.0 regardi|
|56546|New|Enh|2014-05-19|Improve thread trace logging in WebappClassLoader.|
|56614|New|Enh|2014-06-12|Add a switch to ignore annotations detection on ta|
|56713|New|Enh|2014-07-12|Limit time that incoming request waits while webap|
|56787|New|Enh|2014-07-29|Simplified jndi name parsing  |
|57130|New|Enh|2014-10-22|Allow digest.sh to accept password from a file or |
|57367|New|Enh|2014-12-18|If JAR scan experiences a stack overflow, give the|
|57421|New|Enh|2015-01-07|Farming default directories   |
|57486|New|Enh|2015-01-23|Improve reuse of ProtectedFunctionMapper instances|
|57701|New|Enh|2015-03-13|Implement "[Redeploy]" button for a web applicatio|
|57827|New|Enh|2015-04-17|Enable adding/removing of members via jmx in a sta|
|57830|New|Enh|2015-04-18|Add support for ProxyProtocol |
|57872|New|Enh|2015-04-29|Do not auto-switch session cookie to version=1 due|
|58052|Opn|Enh|2015-06-19|RewriteValve: Implement additional RewriteRule dir|
|58072|New|Enh|2015-06-23|ECDH curve selection  |
|58935|Opn|Enh|2016-01-29|Re-deploy from war without deleting context   |
|59232|New|Enh|2016-03-24|Make the context name of an app available via JNDI|
|59758|New|Enh|2016-06-27|Add http proxy username-password credentials suppo|
|60597|New|Enh|2017-01-17|Add ability to set cipher suites for websocket cli|
|60849|New|Enh|2017-03-13|Tomcat NIO Connector not able to handle SSL renego|
|61877|New|Enh|2017-12-08|use web.xml from CATALINA_HOME by default |
|62214|New|Enh|2018-03-22|The "userSubtree=true" and "roleSubtree=true" in J|
|62245|New|Enh|2018-04-02|[Documentation] Mention contextXsltFile in Default|
|63080|New|Enh|2019-01-16|Support rfc7239 Forwarded header  |
|63167|New|Enh|2019-02-12|Network Requirements To Resolve No Members Active |
|63195|Inf|Enh|2019-02-21|Add easy way to test RemoteIpValve works properly |
+-+---+---+--+--+
| Total   38 bugs   |
+---+

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



Bug report for Tomcat 9 [2021/11/28]

2021-11-27 Thread bugzilla
+---+
| Bugzilla Bug ID   |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved)   |
| |   +-+
| |   | Severity: BLK=Blocker CRI=Critical  REG=Regression  MAJ=Major   |
| |   |   MIN=Minor   NOR=NormalENH=Enhancement TRV=Trivial |
| |   |   +-+
| |   |   | Date Posted |
| |   |   |  +--+
| |   |   |  | Description  |
| |   |   |  |  |
|53602|Ver|Enh|2012-07-25|Support for HTTP status code 451  |
|57505|New|Enh|2015-01-27|Add integration tests for JspC|
|58530|New|Enh|2015-10-23|Proposal for new Manager HTML GUI |
|58548|Inf|Enh|2015-10-26|support certifcate transparency   |
|58859|New|Enh|2016-01-14|Allow to limit charsets / encodings supported by T|
|59750|New|Enh|2016-06-24|Amend "authenticate" method with context by means |
|60997|New|Enh|2017-04-17|Enhance SemaphoreValve to support denied status an|
|61971|New|Enh|2018-01-06|documentation for using tomcat with systemd   |
|62048|New|Enh|2018-01-25|Missing logout function in Manager and Host-Manage|
|62072|New|Enh|2018-02-01|Add support for request compression   |
|62312|New|Enh|2018-04-18|Add Proxy Authentication support to websocket clie|
|62405|New|Enh|2018-05-23|Add Rereadable Request Filter |
|62488|New|Enh|2018-06-25|Obtain dependencies from Maven Central where possi|
|62611|Inf|Enh|2018-08-09|Compress log files after rotation |
|62723|New|Enh|2018-09-14|Clarify "channelSendOptions" value in cluster docu|
|62773|New|Enh|2018-09-28|Change DeltaManager to handle session deserializat|
|62814|New|Enh|2018-10-10|Use readable names for cluster channel/map options|
|62843|New|Enh|2018-10-22|Tomcat Russian localization   |
|62964|Inf|Enh|2018-11-29|Add RFC7807 conformant Problem Details for HTTP st|
|63023|New|Enh|2018-12-20|Provide a way to load SecurityProviders into the s|
|63049|New|Enh|2018-12-31|Add support in system properties override from com|
|63237|New|Enh|2019-03-06|Consider processing mbeans-descriptors.xml at comp|
|63389|New|Enh|2019-04-27|Enable Servlet Warmup for Containerization|
|63493|New|Enh|2019-06-10|enhancement - add JMX counters to monitor authenti|
|63505|New|Enh|2019-06-14|enhancement - support of stored procedures for Dat|
|63545|New|Enh|2019-07-06|enhancement - add a new pattern attribute for logg|
|63943|Opn|Enh|2019-11-20|Add possibility to overwrite remote port with info|
|63983|Ver|Cri|2019-12-03|Jasper builds-up open files until garbage collecti|
|64144|New|Enh|2020-02-14|Add an option for rejecting requests that have bot|
|64230|New|Enh|2020-03-15|Allow to configure session manager to skip expirin|
|64395|New|Enh|2020-04-30|Windows Installer should offer an option to select|
|65208|New|Enh|2021-03-29|Multi-threaded loading of servlets|
|65302|New|Enh|2021-05-12|Add support for setting com.sun.jndi.ldap.tls.cbty|
|65401|New|Enh|2021-06-28|do no silently fail on javax.net.ssl.SSLHandshakeE|
|65571|Inf|Nor|2021-09-14|ClientAbortException in Tomcat 9.0.50 and 9.0.52  |
+-+---+---+--+--+
| Total   35 bugs   |
+---+

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



Bug report for Tomcat Native [2021/11/28]

2021-11-27 Thread bugzilla
+---+
| Bugzilla Bug ID   |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved)   |
| |   +-+
| |   | Severity: BLK=Blocker CRI=Critical  REG=Regression  MAJ=Major   |
| |   |   MIN=Minor   NOR=NormalENH=Enhancement TRV=Trivial |
| |   |   +-+
| |   |   | Date Posted |
| |   |   |  +--+
| |   |   |  | Description  |
| |   |   |  |  |
|62911|New|Enh|2018-11-15|Add support for proxying ocsp  requests via ProxyH|
|64826|New|Maj|2020-10-19|libtcnative prompts for private key password in so|
|64862|New|Enh|2020-10-30|Improve LibreSSL support  |
|65344|New|Enh|2021-05-31|OpenSSL configuration |
+-+---+---+--+--+
| Total4 bugs   |
+---+

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



Bug report for Tomcat Connectors [2021/11/28]

2021-11-27 Thread bugzilla
+---+
| Bugzilla Bug ID   |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved)   |
| |   +-+
| |   | Severity: BLK=Blocker CRI=Critical  REG=Regression  MAJ=Major   |
| |   |   MIN=Minor   NOR=NormalENH=Enhancement TRV=Trivial |
| |   |   +-+
| |   |   | Date Posted |
| |   |   |  +--+
| |   |   |  | Description  |
| |   |   |  |  |
|46767|New|Enh|2009-02-25|mod_jk to send DECLINED in case no fail-over tomca|
|47327|New|Enh|2009-06-07|Return tomcat authenticated user back to mod_jk (A|
|47750|New|Maj|2009-08-27|ISAPI: Loss of worker settings when changing via j|
|48830|New|Nor|2010-03-01|IIS shutdown blocked in endpoint service when serv|
|49822|New|Enh|2010-08-25|Add hash lb worker method |
|49903|New|Enh|2010-09-09|Make workers file reloadable  |
|52483|New|Enh|2012-01-18|Print JkOptions's options in log file and jkstatus|
|54621|New|Enh|2013-02-28|[PATCH] custom mod_jk availability checks |
|56489|New|Enh|2014-05-05|Include a directory for configuration files   |
|56576|New|Enh|2014-05-29|Websocket support |
|57402|New|Enh|2014-12-30|Provide correlation ID between mod_jk log and acce|
|57403|New|Enh|2014-12-30|Persist configuration changes made via status work|
|57407|New|Enh|2014-12-31|Make session_cookie, session_path and session_cook|
|57790|New|Enh|2015-04-03|Check worker names for typos  |
|61476|New|Enh|2017-09-01|Allow reset of an individual worker stat value|
|61621|New|Enh|2017-10-15|Content-Type is forced to lowercase when it goes t|
|62093|New|Enh|2018-02-09|Allow use_server_errors to apply to specific statu|
|63808|Opn|Enh|2019-10-05|the fact that JkMount makes other directives ineff|
|64775|Inf|Nor|2020-09-28|mod_jk is sending both Content-Length and Transfer|
|65488|New|Nor|2021-08-08|Destroy method is not being called during Failover|
+-+---+---+--+--+
| Total   20 bugs   |
+---+

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



Bug report for Tomcat Modules [2021/11/28]

2021-11-27 Thread bugzilla
+---+
| Bugzilla Bug ID   |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved)   |
| |   +-+
| |   | Severity: BLK=Blocker CRI=Critical  REG=Regression  MAJ=Major   |
| |   |   MIN=Minor   NOR=NormalENH=Enhancement TRV=Trivial |
| |   |   +-+
| |   |   | Date Posted |
| |   |   |  +--+
| |   |   |  | Description  |
| |   |   |  |  |
|50571|Inf|Nor|2011-01-11|Tomcat 7 JDBC connection pool exception enhancemen|
|51595|Inf|Nor|2011-08-01|org.apache.tomcat.jdbc.pool.jmx.ConnectionPool sho|
|51879|Inf|Enh|2011-09-22|Improve access to Native Connection Methods   |
|52024|Inf|Enh|2011-10-13|Custom interceptor to support automatic failover o|
|53199|Inf|Enh|2012-05-07|Refactor ConnectionPool to use ScheduledExecutorSe|
|54437|New|Enh|2013-01-16|Update PoolProperties javadoc for ConnectState int|
|54929|Inf|Nor|2013-05-05|jdbc-pool cannot be used with Java 1.5, "java.lang|
|55078|New|Nor|2013-06-07|Configuring a DataSource Resource with dataSourceJ|
|55662|New|Enh|2013-10-17|Add a way to set an instance of java.sql.Driver di|
|56046|New|Enh|2014-01-21|org.apache.tomcat.jdbc.pool.XADataSource InitSQL p|
|56088|New|Maj|2014-01-29|AbstractQueryReport$StatementProxy throws exceptio|
|56310|Inf|Maj|2014-03-25|PooledConnection and XAConnection not handled corr|
|56586|New|Nor|2014-06-02|initSQL should be committed if defaultAutoCommit =|
|56775|New|Nor|2014-07-28|PoolCleanerTime schedule issue|
|56779|New|Nor|2014-07-28|Allow multiple connection initialization statement|
|56790|New|Nor|2014-07-29|Resizing pool.maxActive to a higher value at runti|
|56798|New|Nor|2014-07-31|Idle eviction strategy could perform better (and i|
|56804|New|Nor|2014-08-02|Use a default validationQueryTimeout other than "f|
|56805|New|Nor|2014-08-02|datasource.getConnection() may be unnecessarily bl|
|56837|New|Nor|2014-08-11|if validationQuery have error with timeBetweenEvic|
|56970|New|Nor|2014-09-11|MaxActive vs. MaxTotal for commons-dbcp and tomcat|
|57460|New|Nor|2015-01-19|[DB2]Connection broken after few hours but not rem|
|57729|New|Enh|2015-03-20|Add QueryExecutionReportInterceptor to log query e|
|58489|Opn|Maj|2015-10-08|QueryStatsComparator throws IllegalArgumentExcepti|
|59077|New|Nor|2016-02-26|DataSourceFactory creates a neutered data source  |
|59569|New|Nor|2016-05-18|isWrapperFor/unwrap implementations incorrect |
|59879|New|Nor|2016-07-18|StatementCache interceptor returns ResultSet objec|
|60195|New|Nor|2016-10-02|No javadoc in Maven Central   |
|60522|New|Nor|2016-12-27|An option for setting if the transaction should be|
|60524|Inf|Nor|2016-12-28|NPE in SlowQueryReport in tomcat-jdbc-7.0.68  |
|60645|New|Nor|2017-01-25|StatementFinalizer is not thread-safe |
|61032|New|Nor|2017-04-24|min pool size is not being respected  |
|61103|New|Nor|2017-05-18|StatementCache potentially caching non-functional |
|61302|New|Enh|2017-07-15|Refactoring of DataSourceProxy|
|61303|New|Enh|2017-07-15|Refactoring of ConnectionPool |
|62432|New|Nor|2018-06-06|Memory Leak in Statement Finalizer?   |
|62598|New|Enh|2018-08-04|support pool with multiple JDBC data sources  |
|62910|Inf|Nor|2018-11-15|tomcat-jdbc global pool transaction problem   |
|63612|Inf|Cri|2019-07-26|PooledConnection#connectUsingDriver, Thread.curren|
|63705|New|Nor|2019-08-29|The tomcat pool doesn't register all connection th|
|64083|New|Nor|2020-01-17|JDBC pool keeps closed connection as available|
|64107|New|Maj|2020-01-30|PreparedStatements correctly closed are not return|
|64231|New|Nor|2020-03-16|Tomcat jdbc pool behaviour|
|64570|New|Nor|2020-07-01|Transaction not rollbacked if autocommit is false |
|64809|New|Nor|2020-10-13|Connection properties not reset to defaults when C|
|65347|New|Nor|2021-06-02|The equals method from statements generated by the|
+-+---+---+--+--+
| Total   46 bugs   |
+---+

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

Bug report for Tomcat 10 [2021/11/28]

2021-11-27 Thread bugzilla
+---+
| Bugzilla Bug ID   |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved)   |
| |   +-+
| |   | Severity: BLK=Blocker CRI=Critical  REG=Regression  MAJ=Major   |
| |   |   MIN=Minor   NOR=NormalENH=Enhancement TRV=Trivial |
| |   |   +-+
| |   |   | Date Posted |
| |   |   |  +--+
| |   |   |  | Description  |
| |   |   |  |  |
|64353|New|Enh|2020-04-15|Add support for accessing server certificate from |
|64549|New|Enh|2020-06-23|create a project module to launch Tomcat in OSGi  |
|64550|New|Enh|2020-06-23|create a project module to launch Tomcat in JPMS  |
|64943|New|Enh|2020-11-29|[Patch] Add support for Unix Domain Sockets to org|
|65124|New|Enh|2021-02-03|Inefficient generated JSP code|
|65267|New|Enh|2021-04-27|Implement mod_headers like filter |
|65391|New|Enh|2021-06-19|Additional user attributes queried by (some) realm|
|65635|New|Enh|2021-10-15|Methods to return auth errors |
+-+---+---+--+--+
| Total8 bugs   |
+---+

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