February 2018 - infinispan-issues

[JBoss JIRA] (ISPN-8853) Registering interposed synchronization fails in async operation with implicit transaction

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-8853?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-8853: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5785 > Registering interposed synchronization fails in async operation with implicit transaction > ----------------------------------------------------------------------------------------- > > Key: ISPN-8853 > URL: https://issues.jboss.org/browse/ISPN-8853 > Project: Infinispan > Issue Type: Bug > Components: Core, Transactions > Affects Versions: 9.2.0.CR2 > Reporter: Radim Vansa > > {{TransactionTable.enlist}} calls {{transactionSynchronizationRegistry.registerInterposedSynchronization(sync);}} but when an async operation is invoked with implicit transaction, the thread-local transaction is suspended. That can result in > {code} > java.lang.NullPointerException > at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936) > at org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.registerInterposedSynchronization(TransactionSynchronizationRegistryWrapper.java:69) > {code} > I guess that since {{TransactionSynchronizationRegistry}} does not offer a variant that would accept the transaction as parameter we need to wrap the call with resume & suspend. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8853) Registering interposed synchronization fails in async operation with implicit transaction

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-8853?page=com.atlassian.jira.plugin.... ] Radim Vansa reassigned ISPN-8853: --------------------------------- Assignee: Radim Vansa > Registering interposed synchronization fails in async operation with implicit transaction > ----------------------------------------------------------------------------------------- > > Key: ISPN-8853 > URL: https://issues.jboss.org/browse/ISPN-8853 > Project: Infinispan > Issue Type: Bug > Components: Core, Transactions > Affects Versions: 9.2.0.CR2 > Reporter: Radim Vansa > Assignee: Radim Vansa > > {{TransactionTable.enlist}} calls {{transactionSynchronizationRegistry.registerInterposedSynchronization(sync);}} but when an async operation is invoked with implicit transaction, the thread-local transaction is suspended. That can result in > {code} > java.lang.NullPointerException > at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936) > at org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.registerInterposedSynchronization(TransactionSynchronizationRegistryWrapper.java:69) > {code} > I guess that since {{TransactionSynchronizationRegistry}} does not offer a variant that would accept the transaction as parameter we need to wrap the call with resume & suspend. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7100) IllegalLifecycleStateException: Trying to register a component after stopping

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-7100?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on ISPN-7100: -------------------------------------- Hey [~altanis] could you confirm ^ and close if that's the case? > IllegalLifecycleStateException: Trying to register a component after stopping > ----------------------------------------------------------------------------- > > Key: ISPN-7100 > URL: https://issues.jboss.org/browse/ISPN-7100 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.4.Final > Reporter: Radoslav Husar > Priority: Minor > Labels: infinispan_clean_shutdown > > Occured on server. Scenarios affected: > eap-7x-failover-ejb-ejbremote-shutdown-dist-async > eap-7x-failover-ejb-ejbremote-shutdown-dist-sync > eap-7x-failover-ejb-ejbremote-shutdown-dist-sync-3owners > eap-7x-failover-ejb-ejbremote-shutdown-dist-sync-tcpStack > eap-7x-failover-ejb-ejbremote-shutdown-repl-sync > eap-7x-failover-ejb-ejbservlet-shutdown-dist-async > eap-7x-failover-ejb-ejbservlet-shutdown-repl-async > eap-7x-failover-ejb-ejbservlet-shutdown-repl-sync > eap-7x-failover-http-session-shutdown-dist-async > eap-7x-failover-http-session-shutdown-dist-sync > eap-7x-failover-http-session-shutdown-repl-async-haproxy > Occurs after "ISPN000082: Stopping the RpcDispatcher for channel ejb" or "WFLYSRV0028: Stopped deployment clusterbench-ee7.ear": > {code} > 21:58:55,724 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 91) WFLYCLINF0003: Stopped client-mappings cache from ejb container > [JBossINF] 21:58:55,726 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0208: Stopped subdeployment (runtime-name: clusterbench-ee7-web-passivating.war) in 259ms > [JBossINF] 21:58:55,726 INFO [org.infinispan.CLUSTER] (remote-thread--p5-t43) [Context=client-mappings][Scope=dev213]ISPN100003: Finished local rebalance > [JBossINF] 21:58:55,727 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000080: Disconnecting JGroups channel ejb > [JBossINF] 21:58:55,727 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000082: Stopping the RpcDispatcher for channel ejb > [JBossINF] 21:58:55,734 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0208: Stopped subdeployment (runtime-name: clusterbench-ee7-web-granular.war) in 267ms > [JBossINF] 21:58:55,735 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0208: Stopped subdeployment (runtime-name: clusterbench-ee7-web-default.war) in 268ms > [JBossINF] 21:58:55,735 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Stopped deployment clusterbench-ee7.ear (runtime-name: clusterbench-ee7.ear) in 269ms > [JBossINF] 21:58:55,736 WARN [org.infinispan.remoting.inboundhandler.GlobalInboundInvocationHandler] (remote-thread--p5-t9) ISPN000071: Caught exception when handling command CacheTopologyControlCommand{cache=client-mappings, type=REBALANCE_CONFIRM, sender=dev215, joinInfo=null, topologyId=29, rebalanceId=0, currentCH=null, pendingCH=null, availabilityMode=null, actualMembers=null, throwable=null, viewId=11}: org.infinispan.commons.CacheConfigurationException: Unable to configure component (type: class org.infinispan.topology.CacheTopologyControlCommand, instance CacheTopologyControlCommand{cache=client-mappings, type=REBALANCE_CONFIRM, sender=dev215, joinInfo=null, topologyId=29, rebalanceId=0, currentCH=null, pendingCH=null, availabilityMode=null, actualMembers=null, throwable=null, viewId=11}) > [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.wireDependencies(AbstractComponentRegistry.java:151) > [JBossINF] at org.infinispan.remoting.inboundhandler.GlobalInboundInvocationHandler$2.run(GlobalInboundInvocationHandler.java:157) > [JBossINF] at org.infinispan.util.concurrent.BlockingTaskAwareExecutorServiceImpl$RunnableWrapper.run(BlockingTaskAwareExecutorServiceImpl.java:199) > [JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [JBossINF] at org.jboss.as.clustering.infinispan.ClassLoaderThreadFactory.lambda$newThread$0(ClassLoaderThreadFactory.java:48) > [JBossINF] at java.lang.Thread.run(Thread.java:745) > [JBossINF] Caused by: org.infinispan.IllegalLifecycleStateException: Trying to register a component after stopping: org.infinispan.topology.LocalTopologyManagerFactory > [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:184) > [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:171) > [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:167) > [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.createComponentFactoryInternal(AbstractComponentRegistry.java:348) > [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.getFactory(AbstractComponentRegistry.java:327) > [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:293) > [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:246) > [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.wireDependencies(AbstractComponentRegistry.java:147) > [JBossINF] ... 6 more > {code} > Server logs: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-e... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8871) AuthorizationHelper should not enable the ACL cache if authz is disabled

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8871?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8871: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5784 > AuthorizationHelper should not enable the ACL cache if authz is disabled > ------------------------------------------------------------------------ > > Key: ISPN-8871 > URL: https://issues.jboss.org/browse/ISPN-8871 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > The authorizationhelper initializes a bounded ACL cache even when authz is disabled. This initializes the caffeine classes even though we might not need them (true for unbounded caches and for off-heap). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8871) AuthorizationHelper should not enable the ACL cache if authz is disabled

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8871?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8871: ---------------------------------- Status: Open (was: New) > AuthorizationHelper should not enable the ACL cache if authz is disabled > ------------------------------------------------------------------------ > > Key: ISPN-8871 > URL: https://issues.jboss.org/browse/ISPN-8871 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > The authorizationhelper initializes a bounded ACL cache even when authz is disabled. This initializes the caffeine classes even though we might not need them (true for unbounded caches and for off-heap). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8871) AuthorizationHelper should not enable the ACL cache if authz is disabled

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-8871: ------------------------------------- Summary: AuthorizationHelper should not enable the ACL cache if authz is disabled Key: ISPN-8871 URL: https://issues.jboss.org/browse/ISPN-8871 Project: Infinispan Issue Type: Bug Components: Core Reporter: Tristan Tarrant Assignee: Tristan Tarrant The authorizationhelper initializes a bounded ACL cache even when authz is disabled. This initializes the caffeine classes even though we might not need them (true for unbounded caches and for off-heap). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8870) Loggers should not inherit from the Core logger

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8870?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8870: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5783 > Loggers should not inherit from the Core logger > ----------------------------------------------- > > Key: ISPN-8870 > URL: https://issues.jboss.org/browse/ISPN-8870 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > JBoss Logging generates a lot of methods. Using inheritance for the loggers just to reuse one or two methods from the parent logger generates a lot of waste in class metadata. We should drop inheritance and duplicate methods instead -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8870) Loggers should not inherit from the Core logger

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8870?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8870: ---------------------------------- Status: Open (was: New) > Loggers should not inherit from the Core logger > ----------------------------------------------- > > Key: ISPN-8870 > URL: https://issues.jboss.org/browse/ISPN-8870 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > JBoss Logging generates a lot of methods. Using inheritance for the loggers just to reuse one or two methods from the parent logger generates a lot of waste in class metadata. We should drop inheritance and duplicate methods instead -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8863) Initial Infinispan subsystem cannot be created via CLI

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8863?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8863: ------------------------------- Affects Version/s: 9.2.0.CR3 (was: 9.2.0.CR2) > Initial Infinispan subsystem cannot be created via CLI > ------------------------------------------------------ > > Key: ISPN-8863 > URL: https://issues.jboss.org/browse/ISPN-8863 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.2.0.CR3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.0.Final > > Attachments: no-ispn.xml > > > If the infinispan server is created with a .xml file that does not contain a {code}<subsystem xmlns="urn:infinispan:server:core:9.2"><cache-container>...</cache-container></subsystem{code} entry, then it's not possible to initialise the subsystem via CLI DMR operations. > Executing {code}/subsystem=datagrid-infinispan:add(){code} results in the following server error: > {code} > 16:46:18,701 INFO [org.jboss.as.clustering.infinispan] (management-handler-thread - 2) Activating Infinispan subsystem. > 16:46:18,705 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "datagrid-infinispan")]): java.lang.IllegalStateException > at org.jboss.as.server.AbstractDeploymentChainStep.execute(AbstractDeploymentChainStep.java:74) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:980) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1402) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:418) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:217) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:137) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:161) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:157) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > 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) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8869) Infinispan Subsystem Code Cleanup

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8869?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8869: ------------------------------- Status: Open (was: New) > Infinispan Subsystem Code Cleanup > --------------------------------- > > Key: ISPN-8869 > URL: https://issues.jboss.org/browse/ISPN-8869 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 9.2.0.CR3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.0.Final > > > The infinispan server subsystem has been neglected for a while resulting in old java code, use of various deprecated jboss apis as well as numerous redundant method/variable declarations. While some of the deprecated apis are harder to replace than others, we should replace the ones that are easy wins sooner rather than later. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2018