was #renderContentOn: called on dblClick? Did it return something?
Did you check the HTTP communication for reasons of the empty page (I use Firebug for such things)?
This may be a browser issue rather than a server side problem. What Browser are you using? To my knowledge, there is not actually a standard behaviour for double clicks on Links in HTML...
Let me give you an example for why I suspect this:
I sometimes get bitten by my boredom of repeating click sequences several dozens of times a day. I move the mouse too fast after clicking a link, and then the browser marks the link as visited/active, but no request is sent to the server. So I often look for reasons why I get no response, until I realize there never was a request
Ok, the situation is a little more complicated as I thought. The main problem seems to be to get this error for the first time. I can get this error for the first time, when I do silly and stupids clicks on a web-page in a very fast way of clicking. In the worst case I get a socket exception - but more normally I get empty white pages.
After I've reached this state I can reproduce this problem very easily - every normal double click produces an empty page.
To get a more robust system again I have to stop the WASstServerAdaptor and restart it again. Then I'm in the situation where it is hard to get the error for the first time.
And yes: it happens with IE, Firefox and Safari (others are not tested).
And yes: the renderContentOn: method is executed (one - for the first click ?). But the empty page "shows" the content of the second click (perhaps a different link - because I made a very fast click on different links). When I do a refresh I get the content of the second click !