[GitHub] [tomcat] aooohan commented on pull request #642: clean up code - formating

aooohan commented on PR #642: URL: https://github.com/apache/tomcat/pull/642#issuecomment-1657826941 Those files were generated by [JavaCC](https://github.com/javacc/javacc), so this change is meaningless. -- This is an automated message from the Apache Git Service. To respond to the mess

[GitHub] [tomcat] aooohan closed pull request #642: clean up code - formating

aooohan closed pull request #642: clean up code - formating URL: https://github.com/apache/tomcat/pull/642 -- 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-mai

[Bug 66669] JVM crash in APR mode

https://bz.apache.org/bugzilla/show_bug.cgi?id=9 Mark Thomas changed: What|Removed |Added Component|Catalina|Library Target Milestone|-

[Bug 66669] JVM crash in APR mode

https://bz.apache.org/bugzilla/show_bug.cgi?id=9 --- Comment #15 from Mark Thomas --- Note 2.0.x is also affected -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsub

Need Tomcat Native release before August Tomcat releases

Hi all, I have been working on BZ 9 [1] and have confirmed a small memory leak when using Tomcat Native. I have a fix and will be committing it shortly. I plan to start the release process for Tomcat Native 1.2.x and 2.0.x shortly afterwards. I'd like to delay the August Tomcat releases u

Re: Need Tomcat Native release before August Tomcat releases

There are OpenSSL releases due tomorrow with security fixes. Given the timing, I'm going to delay the Tomcat Native tags to pick up those releases. Mark On 31/07/2023 09:12, Mark Thomas wrote: Hi all, I have been working on BZ 9 [1] and have confirmed a small memory leak when using Tomc

Re: Need Tomcat Native release before August Tomcat releases

On Mon, Jul 31, 2023 at 10:54 AM Mark Thomas wrote: > > There are OpenSSL releases due tomorrow with security fixes. Given the > timing, I'm going to delay the Tomcat Native tags to pick up those releases. Makes sense. Rémy > Mark > > > On 31/07/2023 09:12, Mark Thomas wrote: > > Hi all, > > >

[tomcat-native] branch 1.2.x updated: Fix BZ 66669 - memory leak in SNI processing

This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 1.2.x in repository https://gitbox.apache.org/repos/asf/tomcat-native.git The following commit(s) were added to refs/heads/1.2.x by this push: new ac050ed07 Fix BZ 9 - memory leak in SNI

[tomcat-native] branch main updated: Fix BZ 66669 - memory leak in SNI processing

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-native.git The following commit(s) were added to refs/heads/main by this push: new f64a8a4b0 Fix BZ 9 - memory leak in SNI pr

[Bug 66669] JVM crash in APR mode

https://bz.apache.org/bugzilla/show_bug.cgi?id=9 Mark Thomas changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug 66822] New: "BindException: Address already in use" - pls say which ip/port is causing the problem

https://bz.apache.org/bugzilla/show_bug.cgi?id=66822 Bug ID: 66822 Summary: "BindException: Address already in use" - pls say which ip/port is causing the problem Product: Tomcat 9 Version: 9.0.43 Hardware: Other

[Bug 66822] "BindException: Address already in use" - pls say which ip/port is causing the problem

https://bz.apache.org/bugzilla/show_bug.cgi?id=66822 Mark Thomas changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW

[Bug 66822] "BindException: Address already in use" - pls say which ip/port is causing the problem

https://bz.apache.org/bugzilla/show_bug.cgi?id=66822 --- Comment #2 from Graham Leggett --- +1 to fixing the error message. There is no obvious link between log lines on different lines, just because a port appears on previous line, it means nothing. Please fix this. -- You are receiving this

[Bug 66822] "BindException: Address already in use" - pls say which ip/port is causing the problem

https://bz.apache.org/bugzilla/show_bug.cgi?id=66822 Antonio Ancona changed: What|Removed |Added CC||cont...@antonioancona.it -- You are

[Bug 66822] "BindException: Address already in use" - pls say which ip/port is causing the problem

https://bz.apache.org/bugzilla/show_bug.cgi?id=66822 Antonio Ancona changed: What|Removed |Added Resolution|WONTFIX |--- Ever confirmed|1

[Bug 66822] "BindException: Address already in use" - pls say which ip/port is causing the problem

https://bz.apache.org/bugzilla/show_bug.cgi?id=66822 --- Comment #4 from Antonio Ancona --- We have multiple connectors listening on port 8443 in our server.xml, each of them with a different "address" field. As Ralf Hauser suggested, it would be beneficial to cite this address verbatimely, the

[Bug 66822] "BindException: Address already in use" - pls say which ip/port is causing the problem

https://bz.apache.org/bugzilla/show_bug.cgi?id=66822 --- Comment #5 from Ralf Hauser --- also, it would be useful to be clearer on the protocol: The current error message says "HTTP/1.1". In reality it is most likely "https" as the connector has the attributes scheme="https" secure="true" SSL

[tomcat] branch main updated (5cd6da7dca -> 6e3aa49334)

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 5cd6da7dca Additional debug logging after CI test failure add 6e3aa49334 Remove preview flag No new revisions were a