project_key: EDG a NPE occurs on startup of 4 nodes {code} 16:13:15,731 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (pool-5-thread-44) ISPN000136: Execution error: java.lang.NullPointerException at org.infinispan.interceptors.CacheLoaderInterceptor.loadIfNeeded(CacheLoaderInterceptor.java:149) [infinispan-core-5.1.0-SNAPSHOT.jar:5.1.0-SNAPSHOT] at org.infinispan.interceptors.CacheLoaderInterceptor.loadIfNeededAndUpdateStats(CacheLoaderInterceptor.java:218) [infinispan-core-5.1.0-SNAPSHOT.jar:5.1.0-SNAPSHOT] at org.infinispan.interceptors.CacheLoaderInterceptor.visitGetKeyValueCommand(CacheLoaderInterceptor.java:90) [infinispan-core-5.1.0-SNAPSHOT.jar:5.1.0-SNAPSHOT] at org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:61) [infinispan-core-5.1.0-SNAPSHOT.jar:5.1.0-SNAPSHOT] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:119) [infinispan-core-5.1.0-SNAPSHOT.jar:5.1.0-SNAPSHOT] at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:133) [infinispan-core-5.1.0-SNAPSHOT.jar:5.1.0-SNAPSHOT] at org.infinispan.commands.AbstractVisitor.visitGetKeyValueCommand(AbstractVisitor.java:90) [infinispan-core-5.1.0-SNAPSHOT.jar:5.1.0-SNAPSHOT] at org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:61) [infinispan-core-5.1.0-SNAPSHOT.jar:5.1.0-SNAPSHOT] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:119) [infinispan-core-5.1.0-SNAPSHOT.jar:5.1.0-SNAPSHOT] at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:133) [infinispan-core-5.1.0-SNAPSHOT.jar:5.1.0-SNAPSHOT] at org.infinispan.commands.AbstractVisitor.visitGetKeyValueCommand(AbstractVisitor.java:90) [infinispan-core-5.1.0-SNAPSHOT.jar:5.1.0-SNAPSHOT] at org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:61) [infinispan-core-5.1.0-SNAPSHOT.jar:5.1.0-SNAPSHOT] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:119) [infinispan-core-5.1.0-SNAPSHOT.jar:5.1.0-SNAPSHOT] at org.infinispan.interceptors.TxInterceptor.enlistReadAndInvokeNext(TxInterceptor.java:201) [infinispan-core-5.1.0-SNAPSHOT.jar:5.1.0-SNAPSHOT] ... {code} this is because the initialisation code: {code} @Start(priority = 15) protected void startInterceptor() { loader = clm.getCacheLoader(); } {code} happens after the causing call... it's happening on test1 the tracelogs are quite big: http://www.qa.jboss.com/~mlinhard/run21.zip (I'll try to keep them on this location as long as this JIRA is relevant)
Link: Added: This issue relates to JBPAPP-6929
I just spotted the same thing in logs for JBPAPP-7021, but the solution there seems to be about something different.
versions: EDG 6.0.0-SNAPSHOT last commit 6d655c86ba05fe2f6a9aba5d77835dfbcb0aae4b Author: Galder Zamarreño <galderz> Date: Wed Aug 31 16:36:23 2011 +0000 Infinispan 5.1.0-SNAPSHOT last commit fc94449eec33469057614a13cbfe59e4f4e855fd Author: Michal Linhard <michal> Date: Wed Sep 7 13:42:32 2011 +0200 AS 7.0.1.Final
JBPAPP-7021 seems to be about a different NPE
config.zip - contains configuration of the instances and prepare.sh script I use to create the four servers
Attachment: Added: config.zip
Link: Added: This issue depends ISPN-1384
Docs QE Status: Removed: NEW
This should be solved in 5.1.0.ALPHA2, but state transfer code might not work fully right. Either build a snapshot from master or wait for BETA1 which should be out in Monday/Tuesday.
The technical_notes? flag indicates that this is a known issue. Please add summarized cause (what caused the issue) and consequence (how the issue manifests) information about this in the Technical Notes field.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: The startInterceptor method is called before it is initialized. Consequence: When four nodes are started, NullPointerException errors display. Fix: The startInterceptor method is now called after it is initialized. Result: When four nodes are started, they operate as expected with no errors.
Does this still happen?
No. And it hasn't for some time now. Sorry, I forgot about this one.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,4 +1 @@ -Cause: The startInterceptor method is called before it is initialized. +The startInterceptor method was called before it was initialized. When four nodes started, NullPointerException errors displayed. This is fixed so that the startInterceptor method is now called after it is initialized. As a result, when four nodes are now started, they operate as expected with no errors.-Consequence: When four nodes are started, NullPointerException errors display. -Fix: The startInterceptor method is now called after it is initialized. -Result: When four nodes are started, they operate as expected with no errors.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -The startInterceptor method was called before it was initialized. When four nodes started, NullPointerException errors displayed. This is fixed so that the startInterceptor method is now called after it is initialized. As a result, when four nodes are now started, they operate as expected with no errors.+The startInterceptor method was called before it was initialized. When four nodes started, <literal>NullPointerException</literal> errors displayed. This is fixed so that the startInterceptor method is now called after it is initialized. As a result, when four nodes are now started, they operate as expected with no errors.