[Bug 65037] Supports deploy Java EE web application to tomcat 10+

2020-12-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65037 Christopher Schultz changed: What|Removed |Added Resolution|--- |INVALID Status|NEW

[Bug 65037] New: Supports deploy Java EE web application to tomcat 10+

2020-12-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65037 Bug ID: 65037 Summary: Supports deploy Java EE web application to tomcat 10+ Product: Tomcat 10 Version: unspecified Hardware: PC OS: Mac OS X 10.4 Status: NEW

[GitHub] [tomcat-maven-plugin] hazendaz closed pull request #26: Allow easy myEclipse development

2020-12-28 Thread GitBox
hazendaz closed pull request #26: URL: https://github.com/apache/tomcat-maven-plugin/pull/26 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above

[GitHub] [tomcat] arjantijms commented on pull request #399: Add getRequest method to RequestFacade, to get the wrapped Request

2020-12-28 Thread GitBox
arjantijms commented on pull request #399: URL: https://github.com/apache/tomcat/pull/399#issuecomment-751867518 > @arjantijms why not using a valve as most integrators? You can't add a valve from your war, so that puts additional constraints on the user. For a simple integration wit

[GitHub] [tomcat] rmannibucau commented on pull request #399: Add getRequest method to RequestFacade, to get the wrapped Request

2020-12-28 Thread GitBox
rmannibucau commented on pull request #399: URL: https://github.com/apache/tomcat/pull/399#issuecomment-751862090 @arjantijms why not using a valve as most integrators? This is an automated message from the Apache Git Service

[GitHub] [tomcat] arjantijms opened a new pull request #399: Add getRequest method to RequestFacade, to get the wrapped Request

2020-12-28 Thread GitBox
arjantijms opened a new pull request #399: URL: https://github.com/apache/tomcat/pull/399 For consistency with Request, and practically for external code that needs to integrate with Tomcat and e.g. needs access to the notes. Signed-off-by: arjantijms -

[Bug 65033] Tomcat 8.5.60/61 User authentication with JNDIRealm failure

2020-12-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65033 --- Comment #7 from Remy Maucherat --- (In reply to Satya from comment #6) > Thanks for your quick responses. > > could you please let me know , which version of Tomcat contains the fix for > this issue. It is not fixed yet. (In reply to Sat

[Bug 65033] Tomcat 8.5.60/61 User authentication with JNDIRealm failure

2020-12-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65033 --- Comment #6 from Satya --- Thanks for your quick responses. could you please let me know , which version of Tomcat contains the fix for this issue. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 65033] Tomcat 8.5.60/61 User authentication with JNDIRealm failure

2020-12-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65033 --- Comment #5 from Satya --- could you please provide some information with sample example on how to configure connectionPoolSize(connectionPoolSize="2"). i will test and provide the results. -- You are receiving this mail because: You are t

[Bug 65033] Tomcat 8.5.60/61 User authentication with JNDIRealm failure

2020-12-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65033 --- Comment #4 from Remy Maucherat --- Thanks, that's what I thought. When using a single connection, then get() locks but never unlocks if there is an exception there. I should have a patch shortly, but I'm trying to verify with a test. As a w

[Bug 65033] Tomcat 8.5.60/61 User authentication with JNDIRealm failure

2020-12-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65033 --- Comment #3 from Satya --- Below is the stcktarce "https-jsse-nio-8443-exec-4" #70 daemon prio=5 os_prio=0 tid=0x7f6a784f4800 nid=0x1cc8b5 waiting on condition [0x7f6a541f] java.lang.Thread.State: WAITING (parking) a

[Bug 65033] Tomcat 8.5.60/61 User authentication with JNDIRealm failure

2020-12-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65033 --- Comment #2 from Satya --- Created attachment 37654 --> https://bz.apache.org/bugzilla/attachment.cgi?id=37654&action=edit Tomcat 8.5.60/61 User authentication with JNDIRealm failure stacktrace -- You are receiving this mail because: You

Re: Tomcat 10 startup time and JMX as an opt in fature?

2020-12-28 Thread Romain Manni-Bucau
Le lun. 28 déc. 2020 à 13:48, Rémy Maucherat a écrit : > On Sun, Dec 27, 2020 at 4:16 PM Romain Manni-Bucau > wrote: > > > Hi everyone, > > > > wonder if there is some work planned in tomcat 10 to 1. makes it start > > faster and 2. make jmx optional. > > > > I did some tests and locally a tomca

[Bug 65033] Tomcat 8.5.60/61 User authentication with JNDIRealm failure

2020-12-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65033 --- Comment #1 from Remy Maucherat --- This is caused by the refactoring which added connection pooling. I think I have an idea of what the problem is (bad cleanup if the error is when calling get() in authenticate, the connection object could

Re: Tomcat 10 startup time and JMX as an opt in fature?

2020-12-28 Thread Rémy Maucherat
On Sun, Dec 27, 2020 at 4:16 PM Romain Manni-Bucau wrote: > Hi everyone, > > wonder if there is some work planned in tomcat 10 to 1. makes it start > faster and 2. make jmx optional. > > I did some tests and locally a tomcat start is about 400ms. > I was surprised to see that Registry.disableRegi

[Bug 65033] Tomcat 8.5.60/61 User authentication with JNDIRealm failure

2020-12-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65033 Satya changed: What|Removed |Added Severity|critical|major -- You are receiving this mail because:

[tomcat] branch 9.0.x updated: [65022] Change tomcat access log attributes to be shown as code. (#397)

2020-12-28 Thread mgrigorov
This is an automated email from the ASF dual-hosted git repository. mgrigorov pushed a commit to branch 9.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/9.0.x by this push: new a8ff4d2 [65022] Change tomcat access log attri

[Bug 65022] [Enhancement] Use of font with distinct lowercase l , capital I (i) and one 1 tomcat access log pattern definition

2020-12-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65022 mgrigorov changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[tomcat] branch 8.5.x updated: [65022] Change tomcat access log attributes to be shown as code. (#397)

2020-12-28 Thread mgrigorov
This is an automated email from the ASF dual-hosted git repository. mgrigorov pushed a commit to branch 8.5.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/8.5.x by this push: new 5d3b5c9 [65022] Change tomcat access log attri

[tomcat] branch master updated: [65022] Change tomcat access log attributes to be shown as code. (#397)

2020-12-28 Thread mgrigorov
This is an automated email from the ASF dual-hosted git repository. mgrigorov pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/master by this push: new 6593fa7 [65022] Change tomcat access log att

[GitHub] [tomcat] martin-g merged pull request #397: [65022] Use of font with distinct lowercase l , capital I (i) and one 1 tomcat access log pattern definition

2020-12-28 Thread GitBox
martin-g merged pull request #397: URL: https://github.com/apache/tomcat/pull/397 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to th