Linked by theuserbl on Sun 10th Jul 2011 18:48 UTC
Thread beginning with comment 480237
To view parent comment, click here.
To read all comments associated with this story, please click here.
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.
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.
Well, we've got perl apps that run side-by-side along with the java ones, and never have any trouble with those. It's only once the 'legacy' perl code gets rewritten to java (I assume because of java's multi-threading capabilities) does the trouble begin.
But who knows, you guys may be right. I don't work on the dev team - I'm just the grunt that gets paged at 3am every time one of those f**king apps decides to go on strike. So, I just call 'em like I see 'em. I've seen so many badly written apps in java, both on the server and desktop, yet it always seems to be the developers' fault every time this happens. Maybe other languages make it just as incredibly easy as java to write apps that run like dogshit. *shrug*
Edited 2011-07-11 05:31 UTC





Member since:
2006-05-09
Instead of bashing Java... have you thought about replacing your architects?