(eg: Jetty 7/8/9.0 vs Jetty 9.1)ĭepending on your specific installation technique of Jetty, your startup can be different. 'Removing all JVM options' can also have no effect, depending on how you have your Jetty configured, which you have not specified in your question.ĭepending on your specific version of Jetty, the startup is different. Switching Jetty or JVM versions will have no effect for a OutOfMemoryError. You could have a scenario where the server attempted to allocate a new Thread, but the OS prevented it, that would also cause an OutOfMemoryError: Failed to Create Thread You could have had a single action that attempted to allocate 4GB, that wouldn't show up on GC, but still cause the OutOfMemoryError. The GC event logs provide far too little of a view as to what is going on. Without the extra information from the OutOfMemoryError error message advising you on what path to look at is nigh impossible. It can occur from insufficient heap, or permgen, or threads, or file descriptors, etc. (You didn't paste the full error message and stacktrace to narrow down the cause). OutOfMemoryError can occur for various reasons. If you want to see the server and handler tree dump, without stopping the server, then you can use either the startup property =true or enable JMX and access the :type=server,id=0 MBean and use the dump() operation. It has nothing to do with server memory or server crashes. If you are meaning the startup property =true then that is for dumping the state of the server + handler tree during a formal / graceful shutdown. The dumpBeforeStop=TRUE you mention is not a known configuration of Jetty. First, what version of Jetty 9? (be specific! edit your question with these details)

Jetty server