https://bz.apache.org/bugzilla/show_bug.cgi?id=58104
Ognjen Blagojevic changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #7 from Ognjen
https://bz.apache.org/bugzilla/show_bug.cgi?id=58104
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=58104
--- Comment #5 from Violeta Georgieva ---
The test case from bug 58103#c7 can be used for this issue also.
Once it is executed I can see the same exceptions that I posted earlier.
--
You are receiving this mail because:
You are the assignee f
https://bz.apache.org/bugzilla/show_bug.cgi?id=58104
Violeta Georgieva changed:
What|Removed |Added
OS||All
--- Comment #4 from Violeta Ge
https://bz.apache.org/bugzilla/show_bug.cgi?id=58104
--- Comment #3 from Ognjen Blagojevic ---
Created attachment 32885
--> https://bz.apache.org/bugzilla/attachment.cgi?id=32885&action=edit
Java class to reproduce the problem.
--
You are receiving this mail because:
You are the assignee for
https://bz.apache.org/bugzilla/show_bug.cgi?id=58104
Ognjen Blagojevic changed:
What|Removed |Added
OS|All |Windows 7
--- Comment #2 from Ognj
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
https://bz.apache.org/bugzilla/show_bug.cgi?id=58104
Ognjen Blagojevic changed:
What|Removed |Added
OS||All
Version|8.0.23
