[Bug 66680] [StandardSession] Misleading warning "Cannot serialize Principal object for session"

2023-07-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66680 --- Comment #4 from Christopher Schultz --- I can do the changelog if you do the PR. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscrib

[tomcat] branch main updated: Simplify code for allocation of blank arrays

2023-07-20 Thread remm
This is an automated email from the ASF dual-hosted git repository. remm 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 a903a28dd1 Simplify code for allocation of blank array

Re: JNDIRealm not retrying connections on NamingException

2023-07-20 Thread Rémy Maucherat
On Thu, Jul 20, 2023 at 12:30 PM Felix Schumacher wrote: > > > Am 20.07.23 um 11:40 schrieb Rémy Maucherat: > > On Thu, Jul 20, 2023 at 11:11 AM Felix Schumacher > wrote: > > Hi all, > > at work, we have seen the following stacktrace without a retrying log message. > > javax.naming.NamingExceptio

Re: JNDIRealm not retrying connections on NamingException

2023-07-20 Thread Felix Schumacher
Am 20.07.23 um 11:40 schrieb Rémy Maucherat: On Thu, Jul 20, 2023 at 11:11 AM Felix Schumacher wrote: Hi all, at work, we have seen the following stacktrace without a retrying log message. javax.naming.NamingException: LDAP connection has been closed at com.sun.jndi.ldap.LdapRequest.ge

[tomcat] branch main updated: Allocate API changes

2023-07-20 Thread remm
This is an automated email from the ASF dual-hosted git repository. remm 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 5f2bf30d66 Allocate API changes 5f2bf30d66 is describe

[GitHub] [tomcat] fmarco76 commented on pull request #639: Custom ssl engine parameters

2023-07-20 Thread via GitHub
fmarco76 commented on PR #639: URL: https://github.com/apache/tomcat/pull/639#issuecomment-1643630772 > but it would be an incompatible API change Yes, the API would be slightly different between version 9 and 11. -- This is an automated message from the Apache Git Service. To re

[Bug 66680] [StandardSession] Misleading warning "Cannot serialize Principal object for session"

2023-07-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66680 --- Comment #3 from Tseko --- Hi (In reply to Christopher Schultz from comment #1) > Seems reasonable. Would you like to prepare a patch/PR for this? > > Please include an entry in the changelog if you do so. I'm not sure how to include an en

[GitHub] [tomcat] rmaucher commented on pull request #639: Custom ssl engine parameters

2023-07-20 Thread via GitHub
rmaucher commented on PR #639: URL: https://github.com/apache/tomcat/pull/639#issuecomment-1643614685 > @rmaucher thanks for the merge. I have tested cherry-picking to tomcat 9 and it required a couple of minor fixes to work. Is there something I can do to facilitate the backport? Th

[GitHub] [tomcat] fmarco76 commented on pull request #639: Custom ssl engine parameters

2023-07-20 Thread via GitHub
fmarco76 commented on PR #639: URL: https://github.com/apache/tomcat/pull/639#issuecomment-1643609571 @rmaucher thanks for the merge. I have tested cherry-picking to tomcat 9 and it required a couple of minor fixes to work. Is there something I can do to facilitate the backport? -- Thi

Re: JNDIRealm not retrying connections on NamingException

2023-07-20 Thread Rémy Maucherat
On Thu, Jul 20, 2023 at 11:11 AM Felix Schumacher wrote: > > Hi all, > > at work, we have seen the following stacktrace without a retrying log message. > > javax.naming.NamingException: LDAP connection has been closed > at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:133) > ~[?:

[GitHub] [tomcat] rmaucher closed pull request #639: Custom ssl engine parameters

2023-07-20 Thread via GitHub
rmaucher closed pull request #639: Custom ssl engine parameters URL: https://github.com/apache/tomcat/pull/639 -- 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 the specific comment. To unsubscribe, e

[GitHub] [tomcat] rmaucher commented on pull request #639: Custom ssl engine parameters

2023-07-20 Thread via GitHub
rmaucher commented on PR #639: URL: https://github.com/apache/tomcat/pull/639#issuecomment-1643588616 I merged this change to Tomcat main branch (11). Backporting is not straightforward however as this is an API change stacked on top of a previous API change for Tomcat 11, so the code that

[tomcat] branch main updated (7e76d04f7d -> a5bcc5f525)

2023-07-20 Thread remm
This is an automated email from the ASF dual-hosted git repository. remm pushed a change to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git from 7e76d04f7d Fix failure trying to persist configuration add a5bcc5f525 Improve extensibility of endpoints No new revi

JNDIRealm not retrying connections on NamingException

2023-07-20 Thread Felix Schumacher
Hi all, at work, we have seen the following stacktrace without a retrying log message. javax.naming.NamingException: LDAP connection has been closed     at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:133) ~[?:1.8.0_342]     at com.sun.jndi.ldap.Connection.readReply(Connection.j

[GitHub] [tomcat] rmaucher commented on pull request #639: Custom ssl engine parameters

2023-07-20 Thread via GitHub
rmaucher commented on PR #639: URL: https://github.com/apache/tomcat/pull/639#issuecomment-1643431249 This proposed change looks good to me. -- 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 the sp