Continuing: There was a timing issue when two requests for the same URL hit at the same time.  The result was that the thread that created the connection didn't end up grabbing the wait lock and, thus, the connection didn't exist for the one that did.
Continuing: There was a timing issue when two requests for the same URL hit at the same time.  The result was that the thread that created the connection didn't end up grabbing the wait lock and, thus, the connection didn't exist for the one that did.

That last fix wasn't good.

I don't believe that this fix is the right one either as it ignores the fact that the connection var is supposed to be global to the class (or something).

afilipovich/graphite-web,afilipovich/graphite-web,afilipovich/graphite-web,afilipovich/graphite-web,afilipovich/graphite-web