This manifest itself as a 500 error with a Java Heap size error.  I followed instructions to change the configuration of the Heap Size and raised it from 128/256 (Start/Max) to 256/768.  The Heap Size error went away and now we can just not close a log. 

 

It spins its wheels and eventually stops loading and stays on the log with no closure.   During this, Java.exe on the server is pegging the processor to 95 to 100%.

 

I have restarted the server as well as the service with no affect.

 

Thanks

 

Jason Meyers