To view parent comment, click here.
To read all comments associated with this story, please click here.
Agreed. I've had Tomcat applications run for 6 months without a restart - while in moderate usage. I am a Java developer, so I'm biased, of course.
You may want to look at the application itself. The biggest reason I've seen that any Java web application eats up memory/resources is not closing connections to external resources (i.e. databases).
Replacing your architects is a good start here. Anyone called an "architect" should be able to figure out your issues in 2 days, tops. But I guess it's easier to bash Java itself.
I use Jboss for all my java and java/flex applications at work. We do not have these problems when the applications are coded properly, and on proper hardware.
So ... it's either a coder issue, a tomcat issue or hardware issue. Nothing to do with Java.
Replace those developers, they are a waste of time. Or .. it could be one of those management "decisions". In that case, replace those managers ...
Edited 2011-07-11 18:16 UTC





Member since:
2005-11-13
Well, given how bad Flash performance is on most mobile/tablet devices (and even some desktops), comparing Java and Flash performance is like comparing the shit I took last night with the shit I took this morning. Either way, it's still shit.
At work, we have Java apps running on servers inside of tomcat/resin instances, and we're constantly having to restart them because of OutOfMemory errors and cpu spikes. For some of them, we have to restart them once or twice a day via crontab, because the architects can't figure out WTF is causing them to wig out and swallow up RAM/CPU resources like a Hoover. Of course, I did not write these apps, so who knows how well written they are, but it seems like Java is a hog no matter what environment it runs in.
Edited 2011-07-11 02:50 UTC