I've noticed the following NPE in the server.log on a clustered instance
in one of the failed tests (the test failed because resource hasn't been
registered properly, and I don't know if this is the cause or not):
[2013-04-26T06:21:18.390-0700] [glassfish 4.0] [SEVERE] []
[javax.enterprise.system.core] [tid: _ThreadID=655
_ThreadName=pool-100-thread-1] [timeMillis: 1366982478390] [levelValue:
1000] [[
Exception while processing config bean changes :
java.lang.NullPointerException
at java.lang.reflect.Proxy.getInvocationHandler(Proxy.java:656)
at
org.jvnet.hk2.config.ConfigSupport.getImpl(ConfigSupport.java:246)
at
com.sun.enterprise.v3.admin.listener.CombinedJavaConfigSystemPropertyListener$1.changed(CombinedJavaConfigSystemPropertyListener.java:249)
at
org.jvnet.hk2.config.ConfigSupport.sortAndDispatch(ConfigSupport.java:288)
at
com.sun.enterprise.v3.admin.listener.CombinedJavaConfigSystemPropertyListener.changed(CombinedJavaConfigSystemPropertyListener.java:195)
at
org.jvnet.hk2.config.Transactions$ConfigListenerJob.process(Transactions.java:400)
at
org.jvnet.hk2.config.Transactions$ConfigListenerJob.process(Transactions.java:390)
at
org.jvnet.hk2.config.Transactions$ConfigListenerNotifier$1$1.call(Transactions.java:280)
at
org.jvnet.hk2.config.Transactions$ConfigListenerNotifier$1$1.call(Transactions.java:278)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
-marina