Forum Post: RE: Analysing Java Memory Usage (AppServer Brokers)

  • Thread starter Thread starter TheMadDBA
  • Start date Start date
Status
Not open for further replies.
T

TheMadDBA

Guest
Tweaking java is always a pain and I am sad to say that some of the java versions required by more recent OE versions take up even more memory than previously. Most of the fault lies with java itself (server vs client concepts). I assume you have already used JConsole to take a peak at your java processes? I didn't get much out of it but it does let you get a few details and allows you to run garbage collection. To me the real solution is to make sure you are using name server load balancing to spread the load between a larger number of brokers. In the past I have set up to 50 appserver different brokers to respond to the same logical broker name. When you are running 4000+ users it indeed sucks for a broker to hang or crash. But having only a small fraction of the users impacted for a brief amount of time is certainly better than locking everyone out.

Continue reading...
 
Status
Not open for further replies.
Back
Top