[Bug 61183] Deadlock occurs while sending to a closing session

2017-06-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61183

--- Comment #5 from Mark Thomas  ---
I'm building the 9.0.0.M22 release now. 8.5.x will follow shortly. Releases
take 4-5 days, mainly because of the minimum 72 hour voting period and allowing
24 hours for the mirrors to sync.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



[Bug 61183] Deadlock occurs while sending to a closing session

2017-06-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61183

--- Comment #4 from Lorcan O'Toole  ---
Thanks Mark,
I assume the refactoring of registerFuture involved avoiding stateLock. I would
imagine this problem should be reproducible with the right test harness. 

Have you any view to when these patches will be made available?
regards,
Lorcan

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



[Bug 61183] Deadlock occurs while sending to a closing session

2017-06-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61183

Mark Thomas  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Mark Thomas  ---
I spent a lot of time trying to avoid calling the callbacks with the lock held.
In the end, I opted to refactor registerFuture().

Fixed in:
- trunk for 9.0.0.M22 onwards
- 8.5.x for 8.5.16 onwards
- 8.0.x for 8.0.45 onwards
- 7.0.x for 7.0.79 onwards

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



[Bug 61183] Deadlock occurs while sending to a closing session

2017-06-18 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61183

Mark Thomas  changed:

   What|Removed |Added

 OS||All

--- Comment #2 from Mark Thomas  ---
The analysis looks to be spot on. The tricky part is likely to be fixing this
without re-introducing the bugs those locks were put in place to fix.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



[Bug 61183] Deadlock occurs while sending to a closing session

2017-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61183

--- Comment #1 from Lorcan O'Toole  ---
Created attachment 35050
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=35050=edit
Description in txt

Call stacks and comments might be easier to read with .txt

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org