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

2015-08-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 Ognjen Blagojevic ognjen.d.blagoje...@gmail.com changed: What|Removed |Added Status|RESOLVED

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

2015-07-29 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 --- Comment #14 from Remy Maucherat r...@apache.org --- Thanks for the fix, and +1 for restoring maxConnections now that it works properly. I was way too certain this was a NIO2 issue only I guess. -- You are receiving this mail because: You

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

2015-07-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 Mark Thomas ma...@apache.org changed: What|Removed |Added Status|NEW |RESOLVED

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

2015-07-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 --- Comment #12 from Mark Thomas ma...@apache.org --- *** Bug 58104 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

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

2015-07-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 --- Comment #13 from Mark Thomas ma...@apache.org --- *** Bug 58105 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

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

2015-07-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 --- Comment #8 from Mark Thomas ma...@apache.org --- I'll take a look at this. I think we do need to restore maxConnections support for NIO2 (probably with the limit disabled by default). While I am confident that NIO2 can scale to as many

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

2015-07-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 --- Comment #9 from Mark Thomas ma...@apache.org --- Quick question. Do you see this on trunk or just 8.0.x? -- You are receiving this mail because: You are the assignee for the bug.

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

2015-07-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 --- Comment #10 from Mark Thomas ma...@apache.org --- I've just answered my own question. Running this test case once on Windows triggers the warning message once a second (roughly). Given how easy it is to reproduce, a fix should be (fairly)

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

2015-07-23 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 --- Comment #7 from Ognjen Blagojevic ognjen.d.blagoje...@gmail.com --- Here is a minimal test case: public static void main(String[] argv) throws Exception { URL url = new

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

2015-07-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 --- Comment #5 from Ognjen Blagojevic ognjen.d.blagoje...@gmail.com --- I narrowed the problem to one single problematic example: /examples/servlets/nonblocking/numberwriter. It is example to demonstrate Servlet 3.1 Non-blocking IO. Crawling

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

2015-07-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 --- Comment #6 from Ognjen Blagojevic ognjen.d.blagoje...@gmail.com --- (In reply to Ognjen Blagojevic from comment #5) Crawling that single URL from Java using java.net.URL / URLConnection classes causes reported log messages.

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

2015-07-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 --- Comment #3 from Ognjen Blagojevic ognjen.d.blagoje...@gmail.com --- Can I help somehow to get to the root cause of the problem? For instance, to print stack trace and connection count every time AbstractEndpoint.countUpOrAwaitConnection

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

2015-07-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 --- Comment #4 from Remy Maucherat r...@apache.org --- Feel free to debug it, but as far I am concerned I am probably done with this feature at the moment. -- You are receiving this mail because: You are the assignee for the bug.

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

2015-07-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 --- Comment #2 from Remy Maucherat r...@apache.org --- This would happen occasionally for me. Now this doesn't but it still does rarely in the CI runs. I cannot figure out why it still fails after my fixes. Since it doesn't look like a very

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

2015-07-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 Ognjen Blagojevic ognjen.d.blagoje...@gmail.com changed: What|Removed |Added Version|8.0.23 |trunk

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

2015-07-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58103 Ognjen Blagojevic ognjen.d.blagoje...@gmail.com changed: What|Removed |Added OS||All