February 2018 - infinispan-issues

[JBoss JIRA] (ISPN-8873) Remove all references to DistributedExecutorService from Infinispan codebase

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-8873: ----------------------------------------- Summary: Remove all references to DistributedExecutorService from Infinispan codebase Key: ISPN-8873 URL: https://issues.jboss.org/browse/ISPN-8873 Project: Infinispan Issue Type: Enhancement Reporter: Sebastian Łaskawiec -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8535) Rest API redesign

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8535?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-8535: ------------------------------------------- That could work. We could also use a query param called version (see https://apigee.com/about/blog/technology/restful-api-design-tips-versioning). > Rest API redesign > ----------------- > > Key: ISPN-8535 > URL: https://issues.jboss.org/browse/ISPN-8535 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 9.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 10.0.0.Final > > > Infinispan REST API deals with only one resource, (the cache) and maps all operations on the cache using HTTP verbs and request parameters. The API assumes the URI is related to the cache making it hard to add new kinds of resources without causing ambiguous references. > Since we now have other types of entities, such as counters, scripts, templates, etc, and each one of them can involve different operations, we should make the API more "Restful" by using more than one resource and collections of resources, plus HTTP verbs and operations on them. Examples: > * Create a cache: POST /rest/caches > * Delete a cache: DELETE /rest/caches/myCache > * Create a template: POST /rest/templates > * Delete a template: DELETE /rest/templates/myTemplate > * Create an entry: POST /rest/caches/myCache/1 > * Create a counter: POST /rest/counters > * Get a counter value: GET /rest/counters/mycounter > * Increment a counter: GET /rest/counters/mycounter?action=increment > * Search a cache: GET /rest/caches/myCache?action=search > * Create a script: POST /rest/scripts/ > * Get a script source: GET /rest/scritps/myScript > * Execute a script: GET /rest/scripts/myScript?action=execute&param1=foo > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

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

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7100?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-7100: ------------------------------------------- Yes [~rhusar], the cause (and the fix) seems to be the same. However my fix was for 9.0.0. Would you like to have backport? > 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)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8840) Upgrade WildFly Build Tools to 1.2.6.Final and pull plugin version in the parent pom

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8840?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-8840. -------------------------------- Fix Version/s: 9.2.0.CR3 (was: 9.2.0.Final) Resolution: Done > Upgrade WildFly Build Tools to 1.2.6.Final and pull plugin version in the parent pom > ------------------------------------------------------------------------------------ > > Key: ISPN-8840 > URL: https://issues.jboss.org/browse/ISPN-8840 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Optional > Fix For: 9.2.0.CR3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8780) WildFly modules no longer provide support for the Lucene Directory Provider for WildFly's Hibernate Search

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-8780?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-8780: --------------------------------------- Situation changed after https://github.com/infinispan/infinispan/pull/5766 was merged in 9.2 The Hibernate Search version used by Infinispan Query now matches the latest upstream, so the test coverage is now complete - however that's just happening to be the case as the versions happen to match. So this issue is no longer a blocker for 9.2 (in fact there's nothing left to do for 9.2) but we should still make sure that future versions clearly check all required combinations. Moving this to 9.3 as a blocker, and not going it now as 9.3 is also moving to feature packs so it will be easier to do this after the move is complete. > WildFly modules no longer provide support for the Lucene Directory Provider for WildFly's Hibernate Search > ---------------------------------------------------------------------------------------------------------- > > Key: ISPN-8780 > URL: https://issues.jboss.org/browse/ISPN-8780 > Project: Infinispan > Issue Type: Bug > Components: Build > Reporter: Sanne Grinovero > Priority: Blocker > Fix For: 9.3.0.Final > > > The structure of the modules has been "reorganized" but while doing so the strict separation of the modules meant to support the Hibernate Search version of WildFly - separate from the one included in Infinispan - has been confused. > I consider this a critical regression as we have many users relying on this feature. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8780) WildFly modules no longer provide support for the Lucene Directory Provider for WildFly's Hibernate Search

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-8780?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-8780: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > WildFly modules no longer provide support for the Lucene Directory Provider for WildFly's Hibernate Search > ---------------------------------------------------------------------------------------------------------- > > Key: ISPN-8780 > URL: https://issues.jboss.org/browse/ISPN-8780 > Project: Infinispan > Issue Type: Bug > Components: Build > Reporter: Sanne Grinovero > Priority: Blocker > Fix For: 9.3.0.Final > > > The structure of the modules has been "reorganized" but while doing so the strict separation of the modules meant to support the Hibernate Search version of WildFly - separate from the one included in Infinispan - has been confused. > I consider this a critical regression as we have many users relying on this feature. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8796) Jolokia must be secured by default

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8796?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-8796: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5788 > Jolokia must be secured by default > ---------------------------------- > > Key: ISPN-8796 > URL: https://issues.jboss.org/browse/ISPN-8796 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Reporter: Diego Lovison > Assignee: Diego Lovison > Fix For: 9.2.0.Final > > > After [ISPN-7599|https://issues.jboss.org/browse/ISPN-7599] we can read and change JMX attributes via rest. > Jolokia is allowing to change the MBean attribute using the GET HTTP verb like: > http://localhost:8778/jolokia/write/java.lang:type=Memory/Verbose/true > http://127.0.0.1:8778/jolokia/write/jboss.datagrid-infinispan:component=C..."local",name="namedCache(local)",type=Cache/evictionSize/10 > And also, all other attributes that are writable. > Our intention here is block this behavior by default. > Allow only request that comes from localhost, using POST HTTP verb and blocking all commands by default. > Jolokia has a XML security policy that can be created to handle this. > More info [here|https://jolokia.org/reference/html/security.html] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8796) Jolokia must be secured by default

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8796?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-8796: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.2.0.Final Resolution: Done > Jolokia must be secured by default > ---------------------------------- > > Key: ISPN-8796 > URL: https://issues.jboss.org/browse/ISPN-8796 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Reporter: Diego Lovison > Assignee: Diego Lovison > Fix For: 9.2.0.Final > > > After [ISPN-7599|https://issues.jboss.org/browse/ISPN-7599] we can read and change JMX attributes via rest. > Jolokia is allowing to change the MBean attribute using the GET HTTP verb like: > http://localhost:8778/jolokia/write/java.lang:type=Memory/Verbose/true > http://127.0.0.1:8778/jolokia/write/jboss.datagrid-infinispan:component=C..."local",name="namedCache(local)",type=Cache/evictionSize/10 > And also, all other attributes that are writable. > Our intention here is block this behavior by default. > Allow only request that comes from localhost, using POST HTTP verb and blocking all commands by default. > Jolokia has a XML security policy that can be created to handle this. > More info [here|https://jolokia.org/reference/html/security.html] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8621) Share connection for events

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-8621?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-8621: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5787 > Share connection for events > --------------------------- > > Key: ISPN-8621 > URL: https://issues.jboss.org/browse/ISPN-8621 > Project: Infinispan > Issue Type: Sub-task > Components: Remote Protocols > Reporter: Radim Vansa > Assignee: Radim Vansa > > Right now the event listeners require separate connection. With ISPN-8620 in place we can send the events along with responses and route them to listeners. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8796) Jolokia must be secured by default

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8796?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-8796: -------------------------------------- Status: Open (was: New) > Jolokia must be secured by default > ---------------------------------- > > Key: ISPN-8796 > URL: https://issues.jboss.org/browse/ISPN-8796 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Reporter: Diego Lovison > Assignee: Diego Lovison > > After [ISPN-7599|https://issues.jboss.org/browse/ISPN-7599] we can read and change JMX attributes via rest. > Jolokia is allowing to change the MBean attribute using the GET HTTP verb like: > http://localhost:8778/jolokia/write/java.lang:type=Memory/Verbose/true > http://127.0.0.1:8778/jolokia/write/jboss.datagrid-infinispan:component=C..."local",name="namedCache(local)",type=Cache/evictionSize/10 > And also, all other attributes that are writable. > Our intention here is block this behavior by default. > Allow only request that comes from localhost, using POST HTTP verb and blocking all commands by default. > Jolokia has a XML security policy that can be created to handle this. > More info [here|https://jolokia.org/reference/html/security.html] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2018