This little IM conversation impressed me - a Client was doing some heavy testing on one of their servers (new plugins and stuff) and inadvertently crashed it...
(16:33:29) Guy Fraser: *********.com - site has crashed after trying to export a page as pdf - got ******* on the phone
(16:33:35) Guy Fraser: apparently she can't ping it
(16:33:45) Dan Hardiker: logging in
(16:34:15) Dan Hardiker: conf is still running, not doing much
(16:34:41) Guy Fraser: she can't access it :s or even ping it - maybe it's something on their network changed preventing them access to that ip?
(16:34:52) Dan Hardiker: looking at the logs
(16:35:15) Dan Hardiker: java.lang.OutOfMemoryError: PermGen space
(16:35:16) Guy Fraser: she was exporting to pdf when it chimped
(16:35:22) Dan Hardiker: to be expected with lots of reloading of plugins
(16:35:27) Guy Fraser: yup
(16:40:58) Dan Hardiker: increase perm gen and its on its way up
(16:41:00) Dan Hardiker: its now 256
(16:44:10) Dan Hardiker: *** (********) is back up and running
That's why our Confluence Support and Remote Hosting services are sold out! Within 30 seconds of the client phoning our SLA (Service Level Agreement) support desk, Dan was logging in and within 10 minutes the fault was diagnosed, resolved and the server back up and running.
Admittedly, it was a simple fault to fix, but starting diagnosis within 15 seconds of the client calling is why our SLA clients love us 
Note: This sort of speedy resolution is obviously only possible if we have remote access to the server - without that we have to start asking questions, wait for the client to check things and answer, etc. It takes much longer (sometimes days) if we don't have remote access to the server.
And yes, "chimped" is a technical term here at Adaptavist
Added by