[JBoss JIRA] (ISPN-6860) NPE in SSL failover scenario
by Bogdan Sikora (JIRA)
[ https://issues.jboss.org/browse/ISPN-6860?page=com.atlassian.jira.plugin.... ]
Bogdan Sikora updated ISPN-6860:
--------------------------------
Summary: NPE in SSL failover scenario (was: NPE in failover scenario)
> NPE in SSL failover scenario
> ----------------------------
>
> Key: ISPN-6860
> URL: https://issues.jboss.org/browse/ISPN-6860
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.4.Final
> Reporter: Bogdan Sikora
> Assignee: Radoslav Husar
>
> Scenario:
> * 2x Eaps as workers and 1xapache core as balancer
> * Connection request to balancer
> * Kill the one worker that handled request
> * Check that other worker handles the next request
> * Enable killed worker
> * Kill second worker (worker that stayed alive in first killing)
> * Send request (alive worker is not answering to that one )
> {noformat}
> 2016-07-15 06:46:11,404 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.infinispan.server: org.jboss.msc.service.StartException in service jboss.infinispan.server: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl
> at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:250)
> at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.start(CacheContainerBuilder.java:114)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> ... 3 more
> Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:172)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:887)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:656)
> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:645)
> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:548)
> at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:229)
> ... 6 more
> Caused by: java.lang.NullPointerException
> at org.infinispan.topology.ClusterTopologyManagerImpl.fetchRebalancingStatusFromCoordinator(ClusterTopologyManagerImpl.java:167)
> at org.infinispan.topology.ClusterTopologyManagerImpl.start(ClusterTopologyManagerImpl.java:136)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168)
> ... 11 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6860) NPE in SSL failover scenario
by Bogdan Sikora (JIRA)
[ https://issues.jboss.org/browse/ISPN-6860?page=com.atlassian.jira.plugin.... ]
Bogdan Sikora updated ISPN-6860:
--------------------------------
Description:
Scenario:
* 2x Eaps as workers and 1xapache core as balancer (SSL on)
* Connection request to balancer
* Kill the one worker that handled request
* Check that other worker handles the next request
* Enable killed worker
* Kill second worker (worker that stayed alive in first killing)
* Send request (alive worker is not answering to that one )
{noformat}
2016-07-15 06:46:11,404 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.infinispan.server: org.jboss.msc.service.StartException in service jboss.infinispan.server: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:250)
at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.start(CacheContainerBuilder.java:114)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
... 3 more
Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:172)
at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:887)
at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:656)
at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:645)
at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:548)
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:229)
... 6 more
Caused by: java.lang.NullPointerException
at org.infinispan.topology.ClusterTopologyManagerImpl.fetchRebalancingStatusFromCoordinator(ClusterTopologyManagerImpl.java:167)
at org.infinispan.topology.ClusterTopologyManagerImpl.start(ClusterTopologyManagerImpl.java:136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168)
... 11 more
{noformat}
was:
Scenario:
* 2x Eaps as workers and 1xapache core as balancer
* Connection request to balancer
* Kill the one worker that handled request
* Check that other worker handles the next request
* Enable killed worker
* Kill second worker (worker that stayed alive in first killing)
* Send request (alive worker is not answering to that one )
{noformat}
2016-07-15 06:46:11,404 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.infinispan.server: org.jboss.msc.service.StartException in service jboss.infinispan.server: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:250)
at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.start(CacheContainerBuilder.java:114)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
... 3 more
Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:172)
at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:887)
at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:656)
at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:645)
at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:548)
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:229)
... 6 more
Caused by: java.lang.NullPointerException
at org.infinispan.topology.ClusterTopologyManagerImpl.fetchRebalancingStatusFromCoordinator(ClusterTopologyManagerImpl.java:167)
at org.infinispan.topology.ClusterTopologyManagerImpl.start(ClusterTopologyManagerImpl.java:136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168)
... 11 more
{noformat}
> NPE in SSL failover scenario
> ----------------------------
>
> Key: ISPN-6860
> URL: https://issues.jboss.org/browse/ISPN-6860
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.4.Final
> Reporter: Bogdan Sikora
> Assignee: Radoslav Husar
>
> Scenario:
> * 2x Eaps as workers and 1xapache core as balancer (SSL on)
> * Connection request to balancer
> * Kill the one worker that handled request
> * Check that other worker handles the next request
> * Enable killed worker
> * Kill second worker (worker that stayed alive in first killing)
> * Send request (alive worker is not answering to that one )
> {noformat}
> 2016-07-15 06:46:11,404 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.infinispan.server: org.jboss.msc.service.StartException in service jboss.infinispan.server: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl
> at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:250)
> at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.start(CacheContainerBuilder.java:114)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> ... 3 more
> Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:172)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:887)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:656)
> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:645)
> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:548)
> at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:229)
> ... 6 more
> Caused by: java.lang.NullPointerException
> at org.infinispan.topology.ClusterTopologyManagerImpl.fetchRebalancingStatusFromCoordinator(ClusterTopologyManagerImpl.java:167)
> at org.infinispan.topology.ClusterTopologyManagerImpl.start(ClusterTopologyManagerImpl.java:136)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168)
> ... 11 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6861) NPE in failover scenario
by Bogdan Sikora (JIRA)
Bogdan Sikora created ISPN-6861:
-----------------------------------
Summary: NPE in failover scenario
Key: ISPN-6861
URL: https://issues.jboss.org/browse/ISPN-6861
Project: Infinispan
Issue Type: Bug
Affects Versions: 8.1.4.Final
Reporter: Bogdan Sikora
Assignee: Radoslav Husar
Scenario:
* 2x Eaps as workers and 1xapache core as balancer
* Connection request to balancer
* Kill the one worker that handled request
* Check that other worker handles the next request
* Enable killed worker
* Kill second worker (worker that stayed alive in first killing)
* Send request (alive worker is not answering to that one )
{noformat}
2016-07-15 06:46:11,404 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.infinispan.server: org.jboss.msc.service.StartException in service jboss.infinispan.server: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:250)
at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.start(CacheContainerBuilder.java:114)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
... 3 more
Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:172)
at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:887)
at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:656)
at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:645)
at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:548)
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:229)
... 6 more
Caused by: java.lang.NullPointerException
at org.infinispan.topology.ClusterTopologyManagerImpl.fetchRebalancingStatusFromCoordinator(ClusterTopologyManagerImpl.java:167)
at org.infinispan.topology.ClusterTopologyManagerImpl.start(ClusterTopologyManagerImpl.java:136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168)
... 11 more
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6860) NPE in failover scenario
by Bogdan Sikora (JIRA)
Bogdan Sikora created ISPN-6860:
-----------------------------------
Summary: NPE in failover scenario
Key: ISPN-6860
URL: https://issues.jboss.org/browse/ISPN-6860
Project: Infinispan
Issue Type: Bug
Affects Versions: 8.1.4.Final
Reporter: Bogdan Sikora
Assignee: Radoslav Husar
Scenario:
* 2x Eaps as workers and 1xapache core as balancer
* Connection request to balancer
* Kill the one worker that handled request
* Check that other worker handles the next request
* Enable killed worker
* Kill second worker (worker that stayed alive in first killing)
* Send request (alive worker is not answering to that one )
{noformat}
2016-07-15 06:46:11,404 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.infinispan.server: org.jboss.msc.service.StartException in service jboss.infinispan.server: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:250)
at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.start(CacheContainerBuilder.java:114)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
... 3 more
Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.topology.ClusterTopologyManagerImpl.start() on object of type ClusterTopologyManagerImpl
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:172)
at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:887)
at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:656)
at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:645)
at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:548)
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:229)
... 6 more
Caused by: java.lang.NullPointerException
at org.infinispan.topology.ClusterTopologyManagerImpl.fetchRebalancingStatusFromCoordinator(ClusterTopologyManagerImpl.java:167)
at org.infinispan.topology.ClusterTopologyManagerImpl.start(ClusterTopologyManagerImpl.java:136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168)
... 11 more
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6859) StateTransferLock should have non-blocking API
by Radim Vansa (JIRA)
Radim Vansa created ISPN-6859:
---------------------------------
Summary: StateTransferLock should have non-blocking API
Key: ISPN-6859
URL: https://issues.jboss.org/browse/ISPN-6859
Project: Infinispan
Issue Type: Enhancement
Components: Core
Affects Versions: 9.0.0.Alpha3
Reporter: Radim Vansa
Assignee: Radim Vansa
As Infinispan is moving towards asynchronous design, StateTransferLock shouldn't block threads either.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6858) Prepare a plan for refactoring server parser and writer part
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-6858?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec commented on ISPN-6858:
-------------------------------------------
Hey [~ryanemerson]! May I kindly ask you to have a look at this? You are probably the most knowledgeable in this area. Our area of interest is {{server/integration/endpoint}}.
> Prepare a plan for refactoring server parser and writer part
> ------------------------------------------------------------
>
> Key: ISPN-6858
> URL: https://issues.jboss.org/browse/ISPN-6858
> Project: Infinispan
> Issue Type: Task
> Reporter: Sebastian Łaskawiec
> Assignee: Ryan Emerson
> Priority: Optional
>
> Our Server Parser/Writer code doesn't look nice and has lots and lots of duplication. We should prepare a plan how to refactor it (and possibly distribute tasks all over the team).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6858) Prepare a plan for refactoring server parser and writer part
by Sebastian Łaskawiec (JIRA)
Sebastian Łaskawiec created ISPN-6858:
-----------------------------------------
Summary: Prepare a plan for refactoring server parser and writer part
Key: ISPN-6858
URL: https://issues.jboss.org/browse/ISPN-6858
Project: Infinispan
Issue Type: Task
Reporter: Sebastian Łaskawiec
Assignee: Ryan Emerson
Priority: Optional
Our Server Parser/Writer code doesn't look nice and has lots and lots of duplication. We should prepare a plan how to refactor it (and possibly distribute tasks all over the team).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6857) OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/ISPN-6857?page=com.atlassian.jira.plugin.... ]
Marek Posolda updated ISPN-6857:
--------------------------------
Description:
I have the following setup:
- 2 nodes in cluster with mode INVALIDATION_SYNC. No-transaction cache.
- Node1 is started
- Called "cache.remove" on some key on node1. At the same time, node2 is starting, which is causing topology change.
- The "cache.remove" call on node1 is throwing OutdatedTopologyException.
I found the cause is that StateTransferInterceptor is not added in InterceptorChain during INVALIDATION mode. It's just available during REPLICATION or DISTRIBUTED modes - https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o...
Indeed when I manually added StateTransferInterceptor to my invalidation cache:
{code}
invalidationConfigBuilder.customInterceptors()
.addInterceptor()
.before(NonTransactionalLockingInterceptor.class)
.interceptorClass(StateTransferInterceptor.class);
{code}
I can see that issue is gone as OutdatedTopologyException is catched and command is retried with new topology.
I am attaching the Java unit test for reproducing issue. On my laptop when I run it, I can almost always simulate the issue.
was:
I have the following setup:
- 2 nodes in cluster with mode INVALIDATION_SYNC. No-transaction cache.
- Node1 is started
- Called "cache.remove" on some key on node1. At the same time, node2 is starting, which is causing topology change.
- The "cache.remove" call on node1 is throwing OutdatedTopologyException.
I found the cause is that StateTransferInterceptor is not added in InterceptorChain during INVALIDATION mode. It's just available during REPLICATION or DISTRIBUTED modes - https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o...
Indeed when I manually added StateTransferInterceptor to my invalidation cache:
{code}
invalidationConfigBuilder.customInterceptors()
.addInterceptor()
.before(NonTransactionalLockingInterceptor.class)
.interceptorClass(StateTransferInterceptor.class);
{code}
I can see that issue is gone as OutdatedTopologyException is catched and command is retried with new topology.
> OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain
> -----------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6857
> URL: https://issues.jboss.org/browse/ISPN-6857
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.0.Final
> Reporter: Marek Posolda
> Attachments: OutdatedTopologyExceptionReproducerTest.java
>
>
> I have the following setup:
> - 2 nodes in cluster with mode INVALIDATION_SYNC. No-transaction cache.
> - Node1 is started
> - Called "cache.remove" on some key on node1. At the same time, node2 is starting, which is causing topology change.
> - The "cache.remove" call on node1 is throwing OutdatedTopologyException.
> I found the cause is that StateTransferInterceptor is not added in InterceptorChain during INVALIDATION mode. It's just available during REPLICATION or DISTRIBUTED modes - https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o...
> Indeed when I manually added StateTransferInterceptor to my invalidation cache:
> {code}
> invalidationConfigBuilder.customInterceptors()
> .addInterceptor()
> .before(NonTransactionalLockingInterceptor.class)
> .interceptorClass(StateTransferInterceptor.class);
> {code}
>
> I can see that issue is gone as OutdatedTopologyException is catched and command is retried with new topology.
> I am attaching the Java unit test for reproducing issue. On my laptop when I run it, I can almost always simulate the issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6857) OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/ISPN-6857?page=com.atlassian.jira.plugin.... ]
Marek Posolda updated ISPN-6857:
--------------------------------
Attachment: OutdatedTopologyExceptionReproducerTest.java
I am attaching the Java unit test for reproducing issue. On my laptop when I run it, I can almost always simulate the issue.
The stacktrace thrown on node1 ( looks like it's propagated from node2 where remote invalidation command failed):
{code}
org.infinispan.statetransfer.OutdatedTopologyException: Cache topology changed while the command was executing: expected 1, got 2
at org.infinispan.interceptors.EntryWrappingInterceptor.invokeNextAndApplyChanges(EntryWrappingInterceptor.java:522)
at org.infinispan.interceptors.EntryWrappingInterceptor.setSkipRemoteGetsAndInvokeNextForDataCommand(EntryWrappingInterceptor.java:560)
at org.infinispan.interceptors.EntryWrappingInterceptor.visitInvalidateCommand(EntryWrappingInterceptor.java:175)
at org.infinispan.commands.write.InvalidateCommand.acceptVisitor(InvalidateCommand.java:125)
at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
at org.infinispan.interceptors.locking.AbstractLockingInterceptor.visitInvalidateCommand(AbstractLockingInterceptor.java:109)
at org.infinispan.commands.write.InvalidateCommand.acceptVisitor(InvalidateCommand.java:125)
at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:113)
at org.infinispan.commands.AbstractVisitor.visitInvalidateCommand(AbstractVisitor.java:127)
at org.infinispan.commands.write.InvalidateCommand.acceptVisitor(InvalidateCommand.java:125)
at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:107)
at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:76)
at org.infinispan.commands.AbstractVisitor.visitInvalidateCommand(AbstractVisitor.java:127)
at org.infinispan.commands.write.InvalidateCommand.acceptVisitor(InvalidateCommand.java:125)
at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:336)
at org.infinispan.commands.remote.BaseRpcInvokingCommand.processVisitableCommand(BaseRpcInvokingCommand.java:43)
at org.infinispan.commands.remote.SingleRpcCommand.perform(SingleRpcCommand.java:48)
at org.infinispan.remoting.inboundhandler.BasePerCacheInboundInvocationHandler.invokePerform(BasePerCacheInboundInvocationHandler.java:92)
at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.run(BaseBlockingRunnable.java:34)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
> OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain
> -----------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6857
> URL: https://issues.jboss.org/browse/ISPN-6857
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.0.Final
> Reporter: Marek Posolda
> Attachments: OutdatedTopologyExceptionReproducerTest.java
>
>
> I have the following setup:
> - 2 nodes in cluster with mode INVALIDATION_SYNC. No-transaction cache.
> - Node1 is started
> - Called "cache.remove" on some key on node1. At the same time, node2 is starting, which is causing topology change.
> - The "cache.remove" call on node1 is throwing OutdatedTopologyException.
> I found the cause is that StateTransferInterceptor is not added in InterceptorChain during INVALIDATION mode. It's just available during REPLICATION or DISTRIBUTED modes - https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o...
> Indeed when I manually added StateTransferInterceptor to my invalidation cache:
> {code}
> invalidationConfigBuilder.customInterceptors()
> .addInterceptor()
> .before(NonTransactionalLockingInterceptor.class)
> .interceptorClass(StateTransferInterceptor.class);
> {code}
>
> I can see that issue is gone as OutdatedTopologyException is catched and command is retried with new topology.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6857) OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/ISPN-6857?page=com.atlassian.jira.plugin.... ]
Marek Posolda edited comment on ISPN-6857 at 7/15/16 4:09 AM:
--------------------------------------------------------------
The stacktrace thrown on node1 ( looks like it's propagated from node2 where remote invalidation command failed):
{code}
org.infinispan.statetransfer.OutdatedTopologyException: Cache topology changed while the command was executing: expected 1, got 2
at org.infinispan.interceptors.EntryWrappingInterceptor.invokeNextAndApplyChanges(EntryWrappingInterceptor.java:522)
at org.infinispan.interceptors.EntryWrappingInterceptor.setSkipRemoteGetsAndInvokeNextForDataCommand(EntryWrappingInterceptor.java:560)
at org.infinispan.interceptors.EntryWrappingInterceptor.visitInvalidateCommand(EntryWrappingInterceptor.java:175)
at org.infinispan.commands.write.InvalidateCommand.acceptVisitor(InvalidateCommand.java:125)
at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
at org.infinispan.interceptors.locking.AbstractLockingInterceptor.visitInvalidateCommand(AbstractLockingInterceptor.java:109)
at org.infinispan.commands.write.InvalidateCommand.acceptVisitor(InvalidateCommand.java:125)
at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:113)
at org.infinispan.commands.AbstractVisitor.visitInvalidateCommand(AbstractVisitor.java:127)
at org.infinispan.commands.write.InvalidateCommand.acceptVisitor(InvalidateCommand.java:125)
at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:107)
at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:76)
at org.infinispan.commands.AbstractVisitor.visitInvalidateCommand(AbstractVisitor.java:127)
at org.infinispan.commands.write.InvalidateCommand.acceptVisitor(InvalidateCommand.java:125)
at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:336)
at org.infinispan.commands.remote.BaseRpcInvokingCommand.processVisitableCommand(BaseRpcInvokingCommand.java:43)
at org.infinispan.commands.remote.SingleRpcCommand.perform(SingleRpcCommand.java:48)
at org.infinispan.remoting.inboundhandler.BasePerCacheInboundInvocationHandler.invokePerform(BasePerCacheInboundInvocationHandler.java:92)
at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.run(BaseBlockingRunnable.java:34)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
was (Author: mposolda):
I am attaching the Java unit test for reproducing issue. On my laptop when I run it, I can almost always simulate the issue.
The stacktrace thrown on node1 ( looks like it's propagated from node2 where remote invalidation command failed):
{code}
org.infinispan.statetransfer.OutdatedTopologyException: Cache topology changed while the command was executing: expected 1, got 2
at org.infinispan.interceptors.EntryWrappingInterceptor.invokeNextAndApplyChanges(EntryWrappingInterceptor.java:522)
at org.infinispan.interceptors.EntryWrappingInterceptor.setSkipRemoteGetsAndInvokeNextForDataCommand(EntryWrappingInterceptor.java:560)
at org.infinispan.interceptors.EntryWrappingInterceptor.visitInvalidateCommand(EntryWrappingInterceptor.java:175)
at org.infinispan.commands.write.InvalidateCommand.acceptVisitor(InvalidateCommand.java:125)
at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
at org.infinispan.interceptors.locking.AbstractLockingInterceptor.visitInvalidateCommand(AbstractLockingInterceptor.java:109)
at org.infinispan.commands.write.InvalidateCommand.acceptVisitor(InvalidateCommand.java:125)
at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:113)
at org.infinispan.commands.AbstractVisitor.visitInvalidateCommand(AbstractVisitor.java:127)
at org.infinispan.commands.write.InvalidateCommand.acceptVisitor(InvalidateCommand.java:125)
at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:107)
at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:76)
at org.infinispan.commands.AbstractVisitor.visitInvalidateCommand(AbstractVisitor.java:127)
at org.infinispan.commands.write.InvalidateCommand.acceptVisitor(InvalidateCommand.java:125)
at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:336)
at org.infinispan.commands.remote.BaseRpcInvokingCommand.processVisitableCommand(BaseRpcInvokingCommand.java:43)
at org.infinispan.commands.remote.SingleRpcCommand.perform(SingleRpcCommand.java:48)
at org.infinispan.remoting.inboundhandler.BasePerCacheInboundInvocationHandler.invokePerform(BasePerCacheInboundInvocationHandler.java:92)
at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.run(BaseBlockingRunnable.java:34)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
> OutdatedTopologyException in clustered invalidation cache because StateTransferInterceptor not in the chain
> -----------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6857
> URL: https://issues.jboss.org/browse/ISPN-6857
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.0.Final
> Reporter: Marek Posolda
> Attachments: OutdatedTopologyExceptionReproducerTest.java
>
>
> I have the following setup:
> - 2 nodes in cluster with mode INVALIDATION_SYNC. No-transaction cache.
> - Node1 is started
> - Called "cache.remove" on some key on node1. At the same time, node2 is starting, which is causing topology change.
> - The "cache.remove" call on node1 is throwing OutdatedTopologyException.
> I found the cause is that StateTransferInterceptor is not added in InterceptorChain during INVALIDATION mode. It's just available during REPLICATION or DISTRIBUTED modes - https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o...
> Indeed when I manually added StateTransferInterceptor to my invalidation cache:
> {code}
> invalidationConfigBuilder.customInterceptors()
> .addInterceptor()
> .before(NonTransactionalLockingInterceptor.class)
> .interceptorClass(StateTransferInterceptor.class);
> {code}
>
> I can see that issue is gone as OutdatedTopologyException is catched and command is retried with new topology.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months