Linked by theuserbl on Sun 10th Jul 2011 18:48 UTC
Java "After an initial round of testing we've declared build 147 to be the first Release Candidate of JDK 7. There are only thirteen changes in this build. Over half of them are administrivial updates that don't affect the actual code; the remainder are true showstoppers, including several hard VM crashes and a JIT correctness bug identified by an Eclipse unit test. If no new showstopper issues are reported, and if JSR 336 and the component JSRs pass their Final Approval Ballots in the JCP, then this will be the GA build for release later this month per the schedule posted back in January."
Permalink for comment 480238
To read all comments associated with this story, please click here.
RE[4]: great
by noisedeli on Mon 11th Jul 2011 04:36 UTC in reply to "RE[3]: great"
Member since:

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.

Reply Parent Score: 2