A couple of the questions that I've asked have attracted close votes - I think unfairly:
Most recently, I asked a question about Tomcat been very slow at certain times to serve some static files. Because at first glance this skirts near to the "Apache HTTPD Vs. Tomcat HTTP Throughput Debate" it got a close vote and someone telling me the question "had already been discussed". My issue was occaisionally a small (<2 KiB) file may take 90+ seconds to start downloading. Even if it were related, where's the explanation of what's happening?
Edit: Fairly moved to Serverfault. Would be nice if there was a notification of the close reason, but I understand this may already be happening?
One question I asked got closed - this time because it got pounced on because it was assumed I was asking why Java didn't support multiple-inheritence. I wasn't (I understand the diamond problem etc etc). Instead, the actual question gets completely ignored. :(
Edit: This one is still an issue for me. I'm trying to ask why inheriting from multiple interfaces is seen as the solution to multiple inheritence. As stated in my comments, the method may guarantee a given return type, but it doesn't guarantee the same process / calculation 'under the covers'. The linked questions don't answer that.
It seems many mods/users who can cast close votes are a bit 'trigger happy'. It seems that many don't read the question they want to close - or attempt to help the user explain or expand on their question.
I understand that many questions get asked over and over, but I'd like to find a why to encourage a more 'helpful' approach than just closing questions sometimes. Any ideas, comments or suggestions?