[JBoss JIRA] (ISPN-6599) PutAll operation in the Hot Rod client only partially completed during topology changes
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6599?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes edited comment on ISPN-6599 at 5/12/16 12:02 PM:
-------------------------------------------------------------------
Tried running the reproducer using the PR linked and I am having issues starting the servers: very often they cannot start and hang with errors:
{noformat}
2016-05-12 14:33:14,598 ERROR [org.jgroups.protocols.UNICAST3] (OOB-20,server2) JGRP000039: server2: failed to deliver OOB message [dst: server2, src: server0 (4 headers), size=151 bytes, flags=OOB|DONT_BUNDLE|NO_TOTAL_ORDER]: java.lang.NullPointerException
...
2016-05-12 14:33:14,598 ERROR [org.jgroups.protocols.UNICAST3] (OOB-18,server2) JGRP000039: server2: failed to deliver OOB message [dst: server2, src: server1 (4 headers), size=151 bytes, flags=OOB|DONT_BUNDLE|NO_TOTAL_ORDER]: java.lang.NullPointerException
...
2016-05-12 14:33:20,598 ERROR [org.infinispan.CLUSTER] (transport-thread--p4-t1) ISPN000196: Failed to recover cluster state after the current node became the coordinator (or after merge): java.util.concurrent.ExecutionException: org.infinispan.util.concurrent.TimeoutException: Replication timeout for server0
at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1907)
at org.infinispan.util.concurrent.CompletableFutures.await(CompletableFutures.java:75)
at org.infinispan.topology.ClusterTopologyManagerImpl.executeOnClusterSync(ClusterTopologyManagerImpl.java:578)
at org.infinispan.topology.ClusterTopologyManagerImpl.recoverClusterStatus(ClusterTopologyManagerImpl.java:448)
at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:365)
at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener.lambda$handleViewChange$328(ClusterTopologyManagerImpl.java:717)
at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener$$Lambda$41/1877974992.call(Unknown Source)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.runInternal(SemaphoreCompletionService.java:172)
at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.run(SemaphoreCompletionService.java:151)
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)
2016-05-12 14:33:20,599 FATAL [org.infinispan.CLUSTER] (transport-thread--p4-t1) ISPN100004: After merge (or coordinator change), the coordinator failed to recover cluster. Cluster members are [server2, server1, server0].
{noformat}
Attached are the trace logs for all servers plus thread dump
[^start.zip]
was (Author: gustavonalle):
Tried running the reproducer using the PR linked and I am having issues starting the servers: very often they cannot start and hung with errors:
{noformat}
2016-05-12 14:33:14,598 ERROR [org.jgroups.protocols.UNICAST3] (OOB-20,server2) JGRP000039: server2: failed to deliver OOB message [dst: server2, src: server0 (4 headers), size=151 bytes, flags=OOB|DONT_BUNDLE|NO_TOTAL_ORDER]: java.lang.NullPointerException
...
2016-05-12 14:33:14,598 ERROR [org.jgroups.protocols.UNICAST3] (OOB-18,server2) JGRP000039: server2: failed to deliver OOB message [dst: server2, src: server1 (4 headers), size=151 bytes, flags=OOB|DONT_BUNDLE|NO_TOTAL_ORDER]: java.lang.NullPointerException
...
2016-05-12 14:33:20,598 ERROR [org.infinispan.CLUSTER] (transport-thread--p4-t1) ISPN000196: Failed to recover cluster state after the current node became the coordinator (or after merge): java.util.concurrent.ExecutionException: org.infinispan.util.concurrent.TimeoutException: Replication timeout for server0
at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1907)
at org.infinispan.util.concurrent.CompletableFutures.await(CompletableFutures.java:75)
at org.infinispan.topology.ClusterTopologyManagerImpl.executeOnClusterSync(ClusterTopologyManagerImpl.java:578)
at org.infinispan.topology.ClusterTopologyManagerImpl.recoverClusterStatus(ClusterTopologyManagerImpl.java:448)
at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:365)
at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener.lambda$handleViewChange$328(ClusterTopologyManagerImpl.java:717)
at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener$$Lambda$41/1877974992.call(Unknown Source)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.runInternal(SemaphoreCompletionService.java:172)
at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.run(SemaphoreCompletionService.java:151)
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)
2016-05-12 14:33:20,599 FATAL [org.infinispan.CLUSTER] (transport-thread--p4-t1) ISPN100004: After merge (or coordinator change), the coordinator failed to recover cluster. Cluster members are [server2, server1, server0].
{noformat}
Attached are the trace logs for all servers plus thread dump
[^start.zip]
> PutAll operation in the Hot Rod client only partially completed during topology changes
> ---------------------------------------------------------------------------------------
>
> Key: ISPN-6599
> URL: https://issues.jboss.org/browse/ISPN-6599
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 9.0.0.Alpha1
> Reporter: Gustavo Fernandes
> Assignee: Dan Berindei
> Attachments: reproducer.zip, start.zip, trace.zip
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-6599) PutAll operation in the Hot Rod client only partially completed during topology changes
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6599?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes edited comment on ISPN-6599 at 5/12/16 12:00 PM:
-------------------------------------------------------------------
Tried running the reproducer using the PR linked and I am having issues starting the servers: very often they cannot start and hung with errors:
{noformat}
2016-05-12 14:33:14,598 ERROR [org.jgroups.protocols.UNICAST3] (OOB-20,server2) JGRP000039: server2: failed to deliver OOB message [dst: server2, src: server0 (4 headers), size=151 bytes, flags=OOB|DONT_BUNDLE|NO_TOTAL_ORDER]: java.lang.NullPointerException
...
2016-05-12 14:33:14,598 ERROR [org.jgroups.protocols.UNICAST3] (OOB-18,server2) JGRP000039: server2: failed to deliver OOB message [dst: server2, src: server1 (4 headers), size=151 bytes, flags=OOB|DONT_BUNDLE|NO_TOTAL_ORDER]: java.lang.NullPointerException
...
2016-05-12 14:33:20,598 ERROR [org.infinispan.CLUSTER] (transport-thread--p4-t1) ISPN000196: Failed to recover cluster state after the current node became the coordinator (or after merge): java.util.concurrent.ExecutionException: org.infinispan.util.concurrent.TimeoutException: Replication timeout for server0
at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1907)
at org.infinispan.util.concurrent.CompletableFutures.await(CompletableFutures.java:75)
at org.infinispan.topology.ClusterTopologyManagerImpl.executeOnClusterSync(ClusterTopologyManagerImpl.java:578)
at org.infinispan.topology.ClusterTopologyManagerImpl.recoverClusterStatus(ClusterTopologyManagerImpl.java:448)
at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:365)
at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener.lambda$handleViewChange$328(ClusterTopologyManagerImpl.java:717)
at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener$$Lambda$41/1877974992.call(Unknown Source)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.runInternal(SemaphoreCompletionService.java:172)
at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.run(SemaphoreCompletionService.java:151)
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)
2016-05-12 14:33:20,599 FATAL [org.infinispan.CLUSTER] (transport-thread--p4-t1) ISPN100004: After merge (or coordinator change), the coordinator failed to recover cluster. Cluster members are [server2, server1, server0].
{noformat}
Attached are the trace logs for all servers plus thread dump
[^start.zip]
was (Author: gustavonalle):
Tried running the reproducer using the PR linked and I am having issues starting the servers: very often they cannot start and hung with errors:
{noformat}
2016-05-12 14:33:14,598 ERROR [org.jgroups.protocols.UNICAST3] (OOB-20,server2) JGRP000039: server2: failed to deliver OOB message [dst: server2, src: server0 (4 headers), size=151 bytes, flags=OOB|DONT_BUNDLE|NO_TOTAL_ORDER]: java.lang.NullPointerException
...
2016-05-12 14:33:14,598 ERROR [org.jgroups.protocols.UNICAST3] (OOB-18,server2) JGRP000039: server2: failed to deliver OOB message [dst: server2, src: server1 (4 headers), size=151 bytes, flags=OOB|DONT_BUNDLE|NO_TOTAL_ORDER]: java.lang.NullPointerException
...
2016-05-12 14:33:20,598 ERROR [org.infinispan.CLUSTER] (transport-thread--p4-t1) ISPN000196: Failed to recover cluster state after the current node became the coordinator (or after merge): java.util.concurrent.ExecutionException: org.infinispan.util.concurrent.TimeoutException: Replication timeout for server0
at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1907)
at org.infinispan.util.concurrent.CompletableFutures.await(CompletableFutures.java:75)
at org.infinispan.topology.ClusterTopologyManagerImpl.executeOnClusterSync(ClusterTopologyManagerImpl.java:578)
at org.infinispan.topology.ClusterTopologyManagerImpl.recoverClusterStatus(ClusterTopologyManagerImpl.java:448)
at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:365)
at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener.lambda$handleViewChange$328(ClusterTopologyManagerImpl.java:717)
at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener$$Lambda$41/1877974992.call(Unknown Source)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.runInternal(SemaphoreCompletionService.java:172)
at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.run(SemaphoreCompletionService.java:151)
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)
2016-05-12 14:33:20,599 FATAL [org.infinispan.CLUSTER] (transport-thread--p4-t1) ISPN100004: After merge (or coordinator change), the coordinator failed to recover cluster. Cluster members are [server2, server1, server0].
{noformat}
Attached are the trace logs for all servers plus thread dump
> PutAll operation in the Hot Rod client only partially completed during topology changes
> ---------------------------------------------------------------------------------------
>
> Key: ISPN-6599
> URL: https://issues.jboss.org/browse/ISPN-6599
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 9.0.0.Alpha1
> Reporter: Gustavo Fernandes
> Assignee: Dan Berindei
> Attachments: reproducer.zip, start.zip, trace.zip
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-6599) PutAll operation in the Hot Rod client only partially completed during topology changes
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6599?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes commented on ISPN-6599:
-----------------------------------------
Tried running the reproducer using the PR linked and I am having issues starting the servers: very often they cannot start and hung with errors:
{noformat}
2016-05-12 14:33:14,598 ERROR [org.jgroups.protocols.UNICAST3] (OOB-20,server2) JGRP000039: server2: failed to deliver OOB message [dst: server2, src: server0 (4 headers), size=151 bytes, flags=OOB|DONT_BUNDLE|NO_TOTAL_ORDER]: java.lang.NullPointerException
...
2016-05-12 14:33:14,598 ERROR [org.jgroups.protocols.UNICAST3] (OOB-18,server2) JGRP000039: server2: failed to deliver OOB message [dst: server2, src: server1 (4 headers), size=151 bytes, flags=OOB|DONT_BUNDLE|NO_TOTAL_ORDER]: java.lang.NullPointerException
...
2016-05-12 14:33:20,598 ERROR [org.infinispan.CLUSTER] (transport-thread--p4-t1) ISPN000196: Failed to recover cluster state after the current node became the coordinator (or after merge): java.util.concurrent.ExecutionException: org.infinispan.util.concurrent.TimeoutException: Replication timeout for server0
at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1907)
at org.infinispan.util.concurrent.CompletableFutures.await(CompletableFutures.java:75)
at org.infinispan.topology.ClusterTopologyManagerImpl.executeOnClusterSync(ClusterTopologyManagerImpl.java:578)
at org.infinispan.topology.ClusterTopologyManagerImpl.recoverClusterStatus(ClusterTopologyManagerImpl.java:448)
at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:365)
at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener.lambda$handleViewChange$328(ClusterTopologyManagerImpl.java:717)
at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener$$Lambda$41/1877974992.call(Unknown Source)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.runInternal(SemaphoreCompletionService.java:172)
at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.run(SemaphoreCompletionService.java:151)
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)
2016-05-12 14:33:20,599 FATAL [org.infinispan.CLUSTER] (transport-thread--p4-t1) ISPN100004: After merge (or coordinator change), the coordinator failed to recover cluster. Cluster members are [server2, server1, server0].
{noformat}
Attached are the trace logs for all servers plus thread dump
> PutAll operation in the Hot Rod client only partially completed during topology changes
> ---------------------------------------------------------------------------------------
>
> Key: ISPN-6599
> URL: https://issues.jboss.org/browse/ISPN-6599
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 9.0.0.Alpha1
> Reporter: Gustavo Fernandes
> Assignee: Dan Berindei
> Attachments: reproducer.zip, trace.zip
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-5883) Node can apply new topology after sending status response
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-5883?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5883:
----------------------------------
Fix Version/s: 9.0.0.Final
> Node can apply new topology after sending status response
> ---------------------------------------------------------
>
> Key: ISPN-5883
> URL: https://issues.jboss.org/browse/ISPN-5883
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Test Suite - Core
> Affects Versions: 8.0.1.Final, 7.2.5.Final, 8.1.0.Alpha2, 9.0.0.Alpha1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Critical
> Labels: testsuite_stability
> Fix For: 9.0.0.Alpha2, 8.1.5.Final, 8.2.2.Final, 9.0.0.Final
>
>
> {{LocalTopologyManagerImpl}} is responsible for sending the {{ClusterTopologyControlCommand(GET_STATUS)}} response, and when it sends the response it doesn't check the current view id against the new coordinator's view id. If the old coordinator already sent a topology update before the merge, that topology update might be processed after sending the status response. The new coordinator will send a topology update with a topology id of {{max(status response topology ids) + 1}}. The node will then process the topology update from the old coordinator, but it will ignore the topology update from the new coordinator with the same topology id.
> This is extra common in the partition handling tests, e.g. {{BasePessimisticTxPartitionAndMergeTest}} subclasses, because the test "injects" the JGroups view on each node serially, and often the 4th node sends the status response before it gets the new view.
> {noformat}
> 22:16:37,776 DEBUG (remote-thread-NodeD-p26-t6:[]) [LocalTopologyManagerImpl] Sending cluster status response for view 10
> // Topology from NodeC
> 22:16:37,778 DEBUG (transport-thread-NodeD-p28-t2:[]) [LocalTopologyManagerImpl] Updating local topology for cache pes-cache: CacheTopology{id=8, rebalanceId=3, currentCH=DefaultConsistentHash{ns=60, owners = (4)[NodeA-37631: 15+15, NodeB-47846: 15+15, NodeC-46467: 15+15, NodeD-30486: 15+15]}, pendingCH=null, unionCH=null, actualMembers=[NodeC-46467, NodeD-30486]}
> // Later, topology from NodeA
> 22:16:37,827 DEBUG (transport-thread-NodeD-p28-t1:[]) [LocalTopologyManagerImpl] Ignoring late consistent hash update for cache pes-cache, current topology is 8: CacheTopology{id=8, rebalanceId=3, currentCH=DefaultConsistentHash{ns=60, owners = (4)[NodeA-37631: 15+15, NodeB-47846: 15+15, NodeC-46467: 15+15, NodeD-30486: 15+15]}, pendingCH=null, unionCH=null, actualMembers=[NodeA-37631, NodeB-47846, NodeC-46467, NodeD-30486]}
> {noformat}
> As a solution, we can delay sending the status response until we have the same view as the coordinator (or a later one). We already check that the sender is the current coordinator before applying a topology update, so this will guarantee that the we don't apply other topology updates from the old coordinator. Since the status request is only sent after the new view was installed, this will not introduce any delays in the vast majority of cases.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-6601) can't edit cache configuration in cache configuration page if the cache has a xml <eviction> together with <file-store> or any jdbc-store
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-6601?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-6601:
-------------------------------
Status: Open (was: New)
> can't edit cache configuration in cache configuration page if the cache has a xml <eviction> together with <file-store> or any jdbc-store
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6601
> URL: https://issues.jboss.org/browse/ISPN-6601
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Reporter: Martin Vrabel
> Assignee: Ryan Emerson
> Attachments: Screenshot from 2016-05-06 14-46-13.png
>
>
> for example
> {code}
> <distributed-cache owners="2" name="DistributedCacheAsTamplate" mode="SYNC" remote-timeout="1000"
> segments="100" start="EAGER" l1-lifespan="50">
> <eviction type="MEMORY" strategy="LRU" size="100"/>
> <binary-keyed-jdbc-store datasource="java:jboss/datasources/JdbcDS"
> passivation="false"
> preload="false"
> purge="false">
> <binary-keyed-table prefix="JDG">
> <id-column name="id" type="int"/>
> <data-column name="datum" type="int"/>
> <timestamp-column name="version" type="$int"/>
> </binary-keyed-table>
> </binary-keyed-jdbc-store>
> </distributed-cache>
> {code}
> If I go to the configuration page of this cache, edit some value I get and click apply changes -> update I get
> Error
> WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:
> WFLYCTL0158: Operation handler failed: java.lang.NullPointerException
> SERVER stack strace:
> {code}
> [Server:server-one] 14:44:05,037 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 33) WFLYCTL0013: Operation ("write-attribute") failed - address: ([
> [Server:server-one] ("subsystem" => "datagrid-infinispan"),
> [Server:server-one] ("cache-container" => "clustered"),
> [Server:server-one] ("configurations" => "CONFIGURATIONS"),
> [Server:server-one] ("invalidation-cache-configuration" => "DistributedCacheAsTamplate"),
> [Server:server-one] ("eviction" => "EVICTION")
> [Server:server-one] ]): java.lang.NullPointerException
> [Server:server-one] at org.jboss.as.clustering.infinispan.subsystem.EvictionConfigurationResource.lambda$registerAttributes$0(EvictionConfigurationResource.java:89)
> [Server:server-one] at org.jboss.as.clustering.infinispan.subsystem.EvictionConfigurationResource$$Lambda$21/113375682.applyConfiguration(Unknown Source)
> [Server:server-one] at org.jboss.as.clustering.infinispan.subsystem.RuntimeCacheConfigurationWriteAttributeHandler.applyModelToRuntime(RuntimeCacheConfigurationWriteAttributeHandler.java:77)
> [Server:server-one] at org.jboss.as.clustering.infinispan.subsystem.RuntimeCacheConfigurationWriteAttributeHandler.applyUpdateToRuntime(RuntimeCacheConfigurationWriteAttributeHandler.java:62)
> [Server:server-one] at org.jboss.as.controller.AbstractWriteAttributeHandler$1.execute(AbstractWriteAttributeHandler.java:104)
> [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)
> [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)
> [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
> [Server:server-one] at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344)
> [Server:server-one] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
> [Server:server-one] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217)
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler.internalExecute(TransactionalProtocolOperationHandler.java:247)
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler.doExecute(TransactionalProtocolOperationHandler.java:185)
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$1.run(TransactionalProtocolOperationHandler.java:138)
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$1.run(TransactionalProtocolOperationHandler.java:134)
> [Server:server-one] at java.security.AccessController.doPrivileged(Native Method)
> [Server:server-one] at javax.security.auth.Subject.doAs(Subject.java:360)
> [Server:server-one] at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:81)
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$2$1.run(TransactionalProtocolOperationHandler.java:157)
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$2$1.run(TransactionalProtocolOperationHandler.java:153)
> [Server:server-one] at java.security.AccessController.doPrivileged(Native Method)
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$2.execute(TransactionalProtocolOperationHandler.java:153)
> [Server:server-one] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363)
> [Server:server-one] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:472)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:server-one] at java.lang.Thread.run(Thread.java:745)
> [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-6601) can't edit cache configuration in cache configuration page if the cache has a xml <eviction> together with <file-store> or any jdbc-store
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-6601?page=com.atlassian.jira.plugin.... ]
Ryan Emerson reassigned ISPN-6601:
----------------------------------
Assignee: Ryan Emerson (was: Vladimir Blagojevic)
> can't edit cache configuration in cache configuration page if the cache has a xml <eviction> together with <file-store> or any jdbc-store
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6601
> URL: https://issues.jboss.org/browse/ISPN-6601
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Reporter: Martin Vrabel
> Assignee: Ryan Emerson
> Attachments: Screenshot from 2016-05-06 14-46-13.png
>
>
> for example
> {code}
> <distributed-cache owners="2" name="DistributedCacheAsTamplate" mode="SYNC" remote-timeout="1000"
> segments="100" start="EAGER" l1-lifespan="50">
> <eviction type="MEMORY" strategy="LRU" size="100"/>
> <binary-keyed-jdbc-store datasource="java:jboss/datasources/JdbcDS"
> passivation="false"
> preload="false"
> purge="false">
> <binary-keyed-table prefix="JDG">
> <id-column name="id" type="int"/>
> <data-column name="datum" type="int"/>
> <timestamp-column name="version" type="$int"/>
> </binary-keyed-table>
> </binary-keyed-jdbc-store>
> </distributed-cache>
> {code}
> If I go to the configuration page of this cache, edit some value I get and click apply changes -> update I get
> Error
> WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:
> WFLYCTL0158: Operation handler failed: java.lang.NullPointerException
> SERVER stack strace:
> {code}
> [Server:server-one] 14:44:05,037 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 33) WFLYCTL0013: Operation ("write-attribute") failed - address: ([
> [Server:server-one] ("subsystem" => "datagrid-infinispan"),
> [Server:server-one] ("cache-container" => "clustered"),
> [Server:server-one] ("configurations" => "CONFIGURATIONS"),
> [Server:server-one] ("invalidation-cache-configuration" => "DistributedCacheAsTamplate"),
> [Server:server-one] ("eviction" => "EVICTION")
> [Server:server-one] ]): java.lang.NullPointerException
> [Server:server-one] at org.jboss.as.clustering.infinispan.subsystem.EvictionConfigurationResource.lambda$registerAttributes$0(EvictionConfigurationResource.java:89)
> [Server:server-one] at org.jboss.as.clustering.infinispan.subsystem.EvictionConfigurationResource$$Lambda$21/113375682.applyConfiguration(Unknown Source)
> [Server:server-one] at org.jboss.as.clustering.infinispan.subsystem.RuntimeCacheConfigurationWriteAttributeHandler.applyModelToRuntime(RuntimeCacheConfigurationWriteAttributeHandler.java:77)
> [Server:server-one] at org.jboss.as.clustering.infinispan.subsystem.RuntimeCacheConfigurationWriteAttributeHandler.applyUpdateToRuntime(RuntimeCacheConfigurationWriteAttributeHandler.java:62)
> [Server:server-one] at org.jboss.as.controller.AbstractWriteAttributeHandler$1.execute(AbstractWriteAttributeHandler.java:104)
> [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)
> [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)
> [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
> [Server:server-one] at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344)
> [Server:server-one] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
> [Server:server-one] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217)
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler.internalExecute(TransactionalProtocolOperationHandler.java:247)
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler.doExecute(TransactionalProtocolOperationHandler.java:185)
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$1.run(TransactionalProtocolOperationHandler.java:138)
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$1.run(TransactionalProtocolOperationHandler.java:134)
> [Server:server-one] at java.security.AccessController.doPrivileged(Native Method)
> [Server:server-one] at javax.security.auth.Subject.doAs(Subject.java:360)
> [Server:server-one] at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:81)
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$2$1.run(TransactionalProtocolOperationHandler.java:157)
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$2$1.run(TransactionalProtocolOperationHandler.java:153)
> [Server:server-one] at java.security.AccessController.doPrivileged(Native Method)
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$2.execute(TransactionalProtocolOperationHandler.java:153)
> [Server:server-one] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363)
> [Server:server-one] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:472)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:server-one] at java.lang.Thread.run(Thread.java:745)
> [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months