| || |
Problematic code in J2EE
Does anyone have any metrics on what percentage (on average) of performance related issues in J2EE are actually code based (i.e. bugs in code, memory leaks, sychronization issues, resource pool issues, etc) as opposed to server/hardware configuration/tweaking requirements. I have heard that the majority of problems in J2EE actually lie deep in the code it would be nice to put a figure to this.
Any real life information anyone has on this would be very useful.
Re: Problematic code in J2EE
<font size="2" face="Verdana, Arial, Helvetica">An interesting article I found is here http://www.sys-con.com/story/print.cfm?storyid=37944
Originally posted by Neil Cameron: Any real life information anyone has on this would be very useful.