May 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6603) 'passivation' attribute should be removed from 'store' schema

by Pedro Ruivo (JIRA)

Pedro Ruivo created ISPN-6603: --------------------------------- Summary: 'passivation' attribute should be removed from 'store' schema Key: ISPN-6603 URL: https://issues.jboss.org/browse/ISPN-6603 Project: Infinispan Issue Type: Feature Request Components: Configuration Reporter: Pedro Ruivo Assignee: Pedro Ruivo The 'passivation' attribute belongs to the 'persistence' element and not to each configured 'store'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6602) ParallelHotRodOperation fail-over not working

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-6602: --------------------------------------- Summary: ParallelHotRodOperation fail-over not working Key: ISPN-6602 URL: https://issues.jboss.org/browse/ISPN-6602 Project: Infinispan Issue Type: Bug Reporter: Gustavo Fernandes When doing a {{putAll}} and a server goes down, the Hot Rod client aborts with the exception: {code} 15:53:10,741 ERROR (HotRod-client-async-pool-5) [RetryOnFailureOperation] ISPN004007: Exception encountered. Retry 10 out of 10 org.infinispan.client.hotrod.exceptions.TransportException:: Could not fetch transport at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.borrowTransportFromPool(TcpTransportFactory.java:400) at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.getTransport(TcpTransportFactory.java:278) at org.infinispan.client.hotrod.impl.operations.PutAllOperation.getTransport(PutAllOperation.java:65) at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:53) at org.infinispan.client.hotrod.impl.operations.ParallelHotRodOperation.lambda$executeParallel$15(ParallelHotRodOperation.java:63) at org.infinispan.client.hotrod.impl.operations.ParallelHotRodOperation$$Lambda$38/973833666.call(Unknown Source) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266)Exception in thread "main" java.util.concurrent.CompletionException: org.infinispan.client.hotrod.exceptions.ParallelOperationException:: java.util.concurrent.ExecutionException: org.infinispan.client.hotrod.exceptions.TransportException:: Could not fetch transport at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273) at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280) at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1584) at java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1574) at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1689) at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) Caused by: org.infinispan.client.hotrod.exceptions.ParallelOperationException:: java.util.concurrent.ExecutionException: org.infinispan.client.hotrod.exceptions.TransportException:: Could not fetch transport at org.infinispan.client.hotrod.impl.operations.ParallelHotRodOperation.executeParallel(ParallelHotRodOperation.java:79) at org.infinispan.client.hotrod.impl.operations.ParallelHotRodOperation.execute(ParallelHotRodOperation.java:50) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.putAll(RemoteCacheImpl.java:223) at {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6531) when editing security roles in cache configuration page I have to manually add [ ] brackets before updating

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6531?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-6531: ------------------------------------------- I agree [~mvrabel] - great idea. We can read all roles defined in that cache container and list them as checkboxes. A user would then select particular roles for the cache/template he is configuring. By default, no roles are selected and security is not enabled. > when editing security roles in cache configuration page I have to manually add [ ] brackets before updating > ----------------------------------------------------------------------------------------------------------- > > Key: ISPN-6531 > URL: https://issues.jboss.org/browse/ISPN-6531 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.0.Final > Reporter: Martin Vrabel > Assignee: Vladimir Blagojevic > > If there are for example 2 roles in the "roles" filed the cache configuration page shows it as "admin,reader" but if I want to add/remove a role I have to add all role in a [ ]. > e.g. adding [admin,reader,writer] removing [admin]. > Otherwise it throws: > Error > domain-failure-description > WFLYCTL0097: Wrong type for roles. Expected [LIST] but was STRING -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[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 Martin Vrabel (JIRA)

[ https://issues.jboss.org/browse/ISPN-6601?page=com.atlassian.jira.plugin.... ] Martin Vrabel updated ISPN-6601: -------------------------------- Attachment: Screenshot from 2016-05-06 14-46-13.png > 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: Vladimir Blagojevic > 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

1
0
0 / 0

[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 Martin Vrabel (JIRA)

Martin Vrabel created ISPN-6601: ----------------------------------- Summary: 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: Vladimir Blagojevic 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

1
0
0 / 0

[JBoss JIRA] (ISPN-6316) Expiration data (lifespan, max-idle, interval) is empty in cachce configuration

by Martin Vrabel (JIRA)

[ https://issues.jboss.org/browse/ISPN-6316?page=com.atlassian.jira.plugin.... ] Martin Vrabel resolved ISPN-6316. --------------------------------- Resolution: Done > Expiration data (lifespan,max-idle,interval) is empty in cachce configuration > ----------------------------------------------------------------------------- > > Key: ISPN-6316 > URL: https://issues.jboss.org/browse/ISPN-6316 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Martin Vrabel > Assignee: Martin Vrabel > > <cluster> -> <cache> -> "actions" -> "View configuration" -> "expiration" tab. > lifespan max-idle interval is empty. > It worked 1-2 weeks ago. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6316) Expiration data (lifespan, max-idle, interval) is empty in cachce configuration

by Martin Vrabel (JIRA)

[ https://issues.jboss.org/browse/ISPN-6316?page=com.atlassian.jira.plugin.... ] Work on ISPN-6316 started by Martin Vrabel. ------------------------------------------- > Expiration data (lifespan,max-idle,interval) is empty in cachce configuration > ----------------------------------------------------------------------------- > > Key: ISPN-6316 > URL: https://issues.jboss.org/browse/ISPN-6316 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Martin Vrabel > Assignee: Martin Vrabel > > <cluster> -> <cache> -> "actions" -> "View configuration" -> "expiration" tab. > lifespan max-idle interval is empty. > It worked 1-2 weeks ago. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6316) Expiration data (lifespan, max-idle, interval) is empty in cachce configuration

by Martin Vrabel (JIRA)

[ https://issues.jboss.org/browse/ISPN-6316?page=com.atlassian.jira.plugin.... ] Work on ISPN-6316 stopped by Martin Vrabel. ------------------------------------------- > Expiration data (lifespan,max-idle,interval) is empty in cachce configuration > ----------------------------------------------------------------------------- > > Key: ISPN-6316 > URL: https://issues.jboss.org/browse/ISPN-6316 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Martin Vrabel > Assignee: Martin Vrabel > > <cluster> -> <cache> -> "actions" -> "View configuration" -> "expiration" tab. > lifespan max-idle interval is empty. > It worked 1-2 weeks ago. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6316) Expiration data (lifespan, max-idle, interval) is empty in cachce configuration

by Martin Vrabel (JIRA)

[ https://issues.jboss.org/browse/ISPN-6316?page=com.atlassian.jira.plugin.... ] Work on ISPN-6316 started by Martin Vrabel. ------------------------------------------- > Expiration data (lifespan,max-idle,interval) is empty in cachce configuration > ----------------------------------------------------------------------------- > > Key: ISPN-6316 > URL: https://issues.jboss.org/browse/ISPN-6316 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Martin Vrabel > Assignee: Martin Vrabel > > <cluster> -> <cache> -> "actions" -> "View configuration" -> "expiration" tab. > lifespan max-idle interval is empty. > It worked 1-2 weeks ago. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6316) Expiration data (lifespan, max-idle, interval) is empty in cachce configuration

by Martin Vrabel (JIRA)

[ https://issues.jboss.org/browse/ISPN-6316?page=com.atlassian.jira.plugin.... ] Martin Vrabel commented on ISPN-6316: ------------------------------------- [~vblagojevic] everything works, marking it as "Done" > Expiration data (lifespan,max-idle,interval) is empty in cachce configuration > ----------------------------------------------------------------------------- > > Key: ISPN-6316 > URL: https://issues.jboss.org/browse/ISPN-6316 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Martin Vrabel > Assignee: Vladimir Blagojevic > > <cluster> -> <cache> -> "actions" -> "View configuration" -> "expiration" tab. > lifespan max-idle interval is empty. > It worked 1-2 weeks ago. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2016