From: Minoru Nitta <minoru.nitta_at_jp.fujitsu.com>
Date: Thu, 21 Jan 2010 10:47:16 +0900

Hi all,


I encountered a strange problem. I am using grizzly 1.9.18-i and running it
on RHEL4 with JDK5. I exexuted a stress test and found out that NullPointerException
occurred in Grizzly.

java.lang.NullPointerException
   at com.sun.grizzly.NIOContext.configureOpType(NIOContext.java:431)
   at com.sun.grizzly.connectioncache.client.CacheableConnectorHandler.notifyCallbackHandlerPseudoConnect(CacheableConnectorHandler.java:221)
   at com.sun.grizzly.connectioncache.client.CacheableConnectorHandler.doConnect(CacheableConnectorHandler.java:168)
   at com.sun.grizzly.connectioncache.client.CacheableConnectorHandler.connect(CacheableConnectorHandler.java:116)


I understood that key argument to NIOContext.configureOpType was null.
I executed the test with no -ea option (to java command), so assertion at
CacheableConnectorHandler.notifyCallbackHandlerPseudoConnect was not executed.
I checked and foud out that CacheableConnectorHandler.notifyCallbackHandlerPseudoConnect
was modified because of spinning problem on Linux.

So, should I run the test with -ea option or is this another spinning problem of
Linux?


Minoru Nitta