https://bz.apache.org/bugzilla/show_bug.cgi?id=63191
--- Comment #10 from Boris Petrov <boris_pet...@live.com> --- (In reply to Mark Thomas from comment #9) > It is not clear that Tomcat not calling the callback for Async.sendText() is > the cause of CometD failing to complete a Promise rather than the other way > around. I'm not sure I understand how the other way around is possible. Is "Async.sendText" somehow calling back to user code (before the response callback I mean)? How else could it be possible that someone calling "Async.sendText" is responsible for it not calling the callback? Perhaps we can start digging from there? > Until we know that any attempt to > fix this issue is going to be largely guess work. > > Knowing the sort of thing that is happening, we can do a code inspection and > try and find potential deadlocks but - if the issue is in Tomcat - finding > it that way is going to involve a large amount of luck. OK, please suggest what we do now. I'm not sure how to proceed. How can I help more? Do you have some sort of stress-tests that you can rewrite to use the async connectors/code? I think it should be fairly easy to reproduce the problem seeing how it happens all the time when I try it. -- 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
