Bug report for Tomcat 9 [2015/07/05]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat 8 [2015/07/05]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat Modules [2015/07/05]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat Native [2015/07/05]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat 7 [2015/07/05]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat 6 [2015/07/05]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Taglibs [2015/07/05]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat Connectors [2015/07/05]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 58103] New: NIO2 warning: Incorrect connection count, multiple socket.close called on the same socket.

https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 Bug ID: 58103 Summary: NIO2 warning: Incorrect connection count, multiple socket.close called on the same socket. Product: Tomcat 8 Version: 8.0.23 Hardware: PC

[Bug 58103] NIO2 warning: Incorrect connection count, multiple socket.close called on the same socket.

https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 Ognjen Blagojevic changed: What|Removed |Added OS||All --- Comment #1 from Ognjen Bla

[Bug 58104] New: APR log error: org.apache.tomcat.jni.Error: 20005: An invalid socket was returned

https://bz.apache.org/bugzilla/show_bug.cgi?id=58104 Bug ID: 58104 Summary: APR log error: org.apache.tomcat.jni.Error: 20005: An invalid socket was returned Product: Tomcat 8 Version: 8.0.23 Hardware: PC Status

[Bug 58105] New: Incorrect access log messages

https://bz.apache.org/bugzilla/show_bug.cgi?id=58105 Bug ID: 58105 Summary: Incorrect access log messages Product: Tomcat 8 Version: 8.0.23 Hardware: PC Status: NEW Severity: minor Priority: P2 Componen

[Bug 58105] Incorrect access log messages

https://bz.apache.org/bugzilla/show_bug.cgi?id=58105 Ognjen Blagojevic changed: What|Removed |Added Version|8.0.23 |trunk OS|

[Bug 58104] APR log error: org.apache.tomcat.jni.Error: 20005: An invalid socket was returned

https://bz.apache.org/bugzilla/show_bug.cgi?id=58104 Ognjen Blagojevic changed: What|Removed |Added OS||All Version|8.0.23

[Bug 58103] NIO2 warning: Incorrect connection count, multiple socket.close called on the same socket.

https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 Ognjen Blagojevic changed: What|Removed |Added Version|8.0.23 |trunk -- You are receiving this m

Re: [VOTE] Release Apache Tomcat 8.0.24

Mark, On 1.7.2015 22:56, Mark Thomas wrote: The proposed 8.0.24 release is: [ ] Broken - do not release [X] Stable - go ahead and release as 8.0.24 Tested .zip distribution on Windows 7 64-bit, Oracle JDK 1.7.0_79 and APR/native 1.1.33: - Crawled all links (except /manager, /host-manager an

[Bug 58104] APR log error: org.apache.tomcat.jni.Error: 20005: An invalid socket was returned

https://bz.apache.org/bugzilla/show_bug.cgi?id=58104 --- Comment #1 from Christopher Schultz --- I'm glad those native checks are starting to catch some errors and stop the JVM from crashing. Any chance this is reproducible? I'd love to get some of these socket errors in the APR connector found a

Re: JASPIC configuration

Hi! I would start with some experiments based on given information in order to figure out the better approach. If I have some questions/problems I'll write to this thread shortly. There are also your comments on github, I'll review them and prepare fixes. P.S. Thank you for your confidence in me.