[ https://issues.jboss.org/browse/ISPN-6309?page=com.atlassian.jira.plugin.... ] Goran Jaric updated ISPN-6309: ------------------------------ Steps to Reproduce: If there is some data in file-store and preload is used on invalidation cache, exception is thrown: {quote}... Caused by: java.lang.NullPointerException: null at org.infinispan.remoting.rpc.RpcManagerImpl.setTopologyId(RpcManagerImpl.java:300) ~[infinispan-core-8.1.0.Final.jar:8.1.0.Final] at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotelyAsync(RpcManagerImpl.java:136) ~[infinispan-core-8.1.0.Final.jar:8.1.0.Final] at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:203) ~[infinispan-core-8.1.0.Final.jar:8.1.0.Final] ...{quote} full stacktrace available in attachment. There is also configuration of infinispan and jgroup tcp attached as well. This is very similar to [https://issues.jboss.org/browse/ISPN-2723#comment-12749872], since this part is true ??Looks to me the NPE comes from stateTransferManager.getCacheTopology() returning null. That could potentially happen if preloading started before StateConsumerImpl.onTopologyUpdate() has executed.?? was: If there is some data in file-store and preload is used on invalidation cache, exception is thrown: ?? ... Caused by: java.lang.NullPointerException: null at org.infinispan.remoting.rpc.RpcManagerImpl.setTopologyId(RpcManagerImpl.java:300) ~[infinispan-core-8.1.0.Final.jar:8.1.0.Final] at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotelyAsync(RpcManagerImpl.java:136) ~[infinispan-core-8.1.0.Final.jar:8.1.0.Final] at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:203) ~[infinispan-core-8.1.0.Final.jar:8.1.0.Final] ... ?? full stacktrace available in attachment. There is also configuration of infinispan and jgroup tcp attached as well. This is very similar to [https://issues.jboss.org/browse/ISPN-2723#comment-12749872], since this part is true ??Looks to me the NPE comes from stateTransferManager.getCacheTopology() returning null. That could potentially happen if preloading started before StateConsumerImpl.onTopologyUpdate() has executed.?? -- This message was sent by Atlassian JIRA (v6.4.11#64026)