Linked by Thom Holwerda on Fri 14th Sep 2012 02:30 UTC, submitted by MOS6510
Java "As a typical Java developer I never monitored the memory usage of my application apart from following typical best practices like closing the connections, streams etc. Recently we were struck with few issues in our JBoss servers that I had to dig in to the memory management."
Thread beginning with comment 535383
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Memory management
by WorknMan on Mon 17th Sep 2012 01:30 UTC in reply to "RE[4]: Memory management"
WorknMan
Member since:
2005-11-13

Is that the architects fault? Nope, not really. On the other hand, as an architect, you should know those things and take them into account when building systems. As an architect, you should really know how classloaders work and how they are linked together.


The problem is that the people that built this stuff have long since left the company, so the current guys are just doing damage control, I guess. Either way, it looks like shit's still going to crash, and I (along with those on my team who are unfortunate enough to get stuck with the pager) will continue to be woken up in the middle of the night. As long as that happens, I will continue to hate Java, whether it is justified or not ;)

Reply Parent Score: 1

RE[6]: Memory management
by JAlexoid on Mon 17th Sep 2012 18:58 in reply to "RE[5]: Memory management"
JAlexoid Member since:
2009-05-19

Until then you - are a troll.

Reply Parent Score: 2