title: Why is the Glassfish admin console so slow?
body: <p>I'm running GlassFish Server Open Source Edition 3.0.1 (build 22). Both in my dev environment (Mac OSX, 4 cores and 8GB RAM) and production (Linux, 2 cores, 4GB) the console is painfully slow to start up. </p>
  
  <p>The machine is largely idle. What is glassfish doing? Is there anything that to be tweaked to make it start up faster?</p>
  
  <p><strong>Update 1</strong>:</p>
  
  <p>Example- I've been trying to replicate some JDBC configuration that I have implemented and tested locally up to my server. I've just wasted an HOUR trying to copy the configuration over because I can't get both the dev and prod glassfish consoles to open simultaneously without one of them timing out.</p>
  
  <p>I'd get the dev console to open, then finally the prod one, but when I click back in my dev window it has already timed out, and now tries to restart itself.  </p>
  
  <p>This is insane.  An hour to replicate a simple JDBC connection? Does anyone really manage to use this in production successfully?</p>
  
  <p><strong>Update: 2</strong></p>
  
  <p>I found two things that made a huge difference: </p>
  
  <ol>
  <li><p>The Ajax aspects of the glassfish UI seem very fragile. I had two browser tabs open, one to <code>localhost:4848</code>, and another to <code>localhost:9000</code>. The first tab was to a glassfish server actually running on localhost. The second was a remote server, port-forwarded to appear as a local server via ssh. Normally this is not an issue, but I suspect that it confuses the session-handling in glassfish to see two servers on the same "host", even if they are on different ports.</p></li>
  <li><p>I updated my 3.0 to 3.1. This seems to have removed a lot of the start-up delay.</p></li>
  </ol>
  
  <p>I hope this post helps someone else not suffer this trauma.  Thanks everyone for your suggestions.</p>