[JBoss JIRA] (ISPN-6309) Preload does not work with invalidation cache [file-store]
by Goran Jaric (JIRA)
[ 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]
at org.infinispan.interceptors.InvalidationInterceptor.invalidateAcrossCluster(InvalidationInterceptor.java:249) ~[infinispan-core-8.1.0.Final.jar:8.1.0.Final]
at org.infinispan.interceptors.InvalidationInterceptor.visitCommitCommand(InvalidationInterceptor.java:138) ~[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:
{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.??
> Preload does not work with invalidation cache [file-store]
> ----------------------------------------------------------
>
> Key: ISPN-6309
> URL: https://issues.jboss.org/browse/ISPN-6309
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 8.1.0.Final
> Reporter: Goran Jaric
> Priority: Critical
> Attachments: CacheException.log, infinispan.xml, jgroups-tcp.xml
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6309) Preload does not work with invalidation cache [file-store]
by Goran Jaric (JIRA)
[ 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.??
> Preload does not work with invalidation cache [file-store]
> ----------------------------------------------------------
>
> Key: ISPN-6309
> URL: https://issues.jboss.org/browse/ISPN-6309
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 8.1.0.Final
> Reporter: Goran Jaric
> Priority: Critical
> Attachments: CacheException.log, infinispan.xml, jgroups-tcp.xml
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6309) Preload does not work with invalidation cache [file-store]
by Goran Jaric (JIRA)
[ 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:
??
...
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.??
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.??
> Preload does not work with invalidation cache [file-store]
> ----------------------------------------------------------
>
> Key: ISPN-6309
> URL: https://issues.jboss.org/browse/ISPN-6309
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 8.1.0.Final
> Reporter: Goran Jaric
> Priority: Critical
> Attachments: CacheException.log, infinispan.xml, jgroups-tcp.xml
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6309) Preload does not work with invalidation cache [file-store]
by Goran Jaric (JIRA)
[ 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:
??...
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.??
was:
If there is some data in file-store and preload is used on invalidation cache, exception is thrown 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.??
> Preload does not work with invalidation cache [file-store]
> ----------------------------------------------------------
>
> Key: ISPN-6309
> URL: https://issues.jboss.org/browse/ISPN-6309
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 8.1.0.Final
> Reporter: Goran Jaric
> Priority: Critical
> Attachments: CacheException.log, infinispan.xml, jgroups-tcp.xml
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6291) Send REST queries to coordinator instead of first server in the cluster
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-6291?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-6291:
--------------------------------------
Status: Open (was: New)
> Send REST queries to coordinator instead of first server in the cluster
> -----------------------------------------------------------------------
>
> Key: ISPN-6291
> URL: https://issues.jboss.org/browse/ISPN-6291
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.1.0.Final, 8.2.0.Beta2
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Priority: Blocker
>
> Whenever we have to send a query to a cluster server directly (not the domain controller) we currently pick the first server. However, we should pick coordinator instead of the first server as the coordinator is guaranteed to have the specific information needed for a valid reply (e.g. cluster events). Throughout the codebase we need to replace all calls to first server with a call to the coordinator.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6308) Stream iterator method can fail sometimes with a node failure
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-6308?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-6308:
--------------------------------
Status: Open (was: New)
> Stream iterator method can fail sometimes with a node failure
> -------------------------------------------------------------
>
> Key: ISPN-6308
> URL: https://issues.jboss.org/browse/ISPN-6308
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Execution and Map/Reduce
> Affects Versions: 8.1.2.Final
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 8.2.0.Final
>
>
> While adding some additional changes for replication using distributed streams I ran the stress test. I found that iterator could fail somehow. Need to patch this issue.
> Using following settings:
> {code}
> protected final static int CACHE_COUNT = 5;
> protected final static int THREAD_MULTIPLIER = 15;
> protected final static long CACHE_ENTRY_COUNT = 5000;
> {code}
> {code}
> 15:25:29,655 FATAL (ForkThread-17,DistributedStreamRehashStressTest) [DistributedStreamRehashStressTest] Exception encountered:
> java.lang.IllegalArgumentException: Thread[ForkThread-17,DistributedStreamRehashStressTest,5,main]-Found incorrect amount 6 of entries, expected 10 for segment 39 missing entries [ImmortalCacheEntry{key=1922, value=1922}, ImmortalCacheEntry{key=2107, value=2107}, ImmortalCacheEntry{key=2265, value=2265}, ImmortalCacheEntry{key=2412, value=2412}, ImmortalCacheEntry{key=2446, value=2446}, ImmortalCacheEntry{key=2575, value=2575}, ImmortalCacheEntry{key=3315, value=3315}, ImmortalCacheEntry{key=3324, value=3324}, ImmortalCacheEntry{key=3349, value=3349}, ImmortalCacheEntry{key=3675, value=3675}] on iteration 3
> at org.infinispan.stream.stress.DistributedStreamRehashStressTest.lambda$testStressNodesLeavingWhileMultipleIterators$4(DistributedStreamRehashStressTest.java:139)
> at org.infinispan.stream.stress.DistributedStreamRehashStressTest.lambda$testStressNodesLeavingWhilePerformingCallable$5(DistributedStreamRehashStressTest.java:173)
> at org.infinispan.test.AbstractInfinispanTest$LoggingCallable.call(AbstractInfinispanTest.java:478)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month