But in fairness, the J2EE implementation was anything BUT optimized. Many basic architectural mistakes were made, and for the sake of credibility, this whole set of results should be thrown out.
It doesnt benefit Microsoft to show an optimized solution against one who's coders didnt know what they were doing.
A couple of points: 1. This version of the MS implementation has been somewhat de-optimized because of feedback from Java people. 2. I don't think the claim is that the J2EE implementation is optimized -- only that it's per community norms and recommendations. The fact is that best practices in the MS part of the world are already geared towards performance, but best practices in the Java world are geared towards ideology and groupthink.
The problem with this kind of statement is that it implies that there is some way to make a J2EE box perform as well as a .NET box. I don't think there's any way to do this! If it's so obvious, where is such a rewrite posted and benchmarked? Show us.