Oracle Glassfish Server 3.0 Stops Responding After NullPointerException (Doc ID 1381780.1)

Last updated on NOVEMBER 05, 2016

In this Document
  Symptoms
  Cause
  Solution
  References


Symptoms

GlassFish Server v3 (build 74.2) stops responding to http connections after this Java exception

[#|2011-11-28T19:45:56.365+0530|SEVERE|glassfishv3.0|grizzly|_ThreadID=18;_ThreadName=Thread-1;|doSelect exception
java.lang.NullPointerException
at com.sun.enterprise.v3.services.impl.monitor.MonitorableSelectorHandler.acceptWithoutRegistration(MonitorableSelectorHandler.java:96)
at com.sun.grizzly.http.SelectorThreadHandler.onAcceptInterest(SelectorThreadHandler.java:91)
at com.sun.grizzly.SelectorHandlerRunner.handleSelectedKey(SelectorHandlerRunner.java:295)
at com.sun.grizzly.SelectorHandlerRunner.handleSelectedKeys(SelectorHandlerRunner.java:258)
at com.sun.grizzly.SelectorHandlerRunner.doSelect(SelectorHandlerRunner.java:195)
at com.sun.grizzly.SelectorHandlerRunner.run(SelectorHandlerRunner.java:130)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

This is the last message that has been observed in the server.log.

Even though the Java thread dumps of the JVM indicate that the GlassFish application server is healthy, nothing gets logged after this NullPointerException.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms