This is great stuff.
[link|http://www.eweek.com/article2/0,4149,1388643,00.asp|Survey Questions Java App Reliability ]

"Despite a strong commitment among enterprises that are developing applications around Java 2 Platform, Enterprise Edition, those organizations are only averaging about 88 percent availability for existing Java-based production applications
...
With an average availability of 88 percent, that is "the equivalent of having an application down one day a week
...
"On average only 42 percent of the time, the application performs as planned when it's deployed. Sixty percent of the time, it's not meeting user expectations," said Malloy.

"I would expect a bigger number [than 42 percent]," Garbani observed. "We're not designing applications for performance. Often, the developer has no idea of what will actually go on with the infrastructure. Today, the developer assembling pieces of applets and servlets has no idea what's going on inside the infrastructure, so the size of the machine is wrong, or configurations are wrong. I blame it on the fact that we have shielded the developer from reality without giving them a direct contact with the reality of the platform," he added.
...
Surprisingly, the actual code of an application caused problems only one out of eight times, the survey said. "

This is a perfect example of why wizard based development doesn't work. When the developers have no clue how things actually work they can't be expected to understand how the system will perform.

The most amazing thing is "the respondents indicated a strong commitment to continuing Java development. One third of the respondents indicated they intended to spend more than 75 percent of their application development budget on J2EE."

In other words, J2EE hasn't solved any of the problems that it was meant to solve, namely scalability, reliability and performance, but we are still going to continue investing in it. How stupid can you get?