Details
Description
Since servlets are singletons, synchronizing on the actual servlet is probably a
bit too course. As we've seen from Since servlets are singletons, synchronizing on the actual servlet is probably a
bit too course. As we've seen from bug 1010, when something deadlocks,
everybody coming in will jam up waiting for the lock to be released. This can
be mitigated to some extent by synchronizing on something a bit less broad., when something deadlocks,
everybody coming in will jam up waiting for the lock to be released. This can
be mitigated to some extent by synchronizing on something a bit less broad.
bit too course. As we've seen from Since servlets are singletons, synchronizing on the actual servlet is probably a
bit too course. As we've seen from bug 1010, when something deadlocks,
everybody coming in will jam up waiting for the lock to be released. This can
be mitigated to some extent by synchronizing on something a bit less broad., when something deadlocks,
everybody coming in will jam up waiting for the lock to be released. This can
be mitigated to some extent by synchronizing on something a bit less broad.
BlockingServlet no longer uses synchronized(this) in the head or 1.5 branch; however, the general area of
this bug (deadlock under load) needs further investigation. Marking this as verified with the intent that
future specific bugs in the general area will be opened as necessary.