June 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4291) Poor REPL state transfer performance with cache stores

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4291?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4291: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1111188 > Poor REPL state transfer performance with cache stores > ------------------------------------------------------ > > Key: ISPN-4291 > URL: https://issues.jboss.org/browse/ISPN-4291 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: State Transfer > Affects Versions: 6.0.2.Final > Reporter: Dennis Reed > Assignee: Dan Berindei > > During a state transfer every single key is loaded from the cache store to determine whether it's still owned by the local node. > This is an extremely slow operation, and doesn't even make sense for a REPL cache. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4421) Migration from jboss-as to wildfly arquillian-container-managed broke RollingUpgrades tests

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4421?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4421: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1111186 > Migration from jboss-as to wildfly arquillian-container-managed broke RollingUpgrades tests > ------------------------------------------------------------------------------------------- > > Key: ISPN-4421 > URL: https://issues.jboss.org/browse/ISPN-4421 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite - Server > Affects Versions: 7.0.0.Alpha4 > Reporter: Tomas Sykora > Assignee: Mircea Markus > Labels: test_suite, testsuite_stability > > Server was rebased to Wildfly. > For Arquillian, jboss-as-arquillian-container-managed was changed to wildfly-arquillian-container-managed in order to reflect respective changes. > The problem for Rolling Upgrade tests ( -Psuite.rolling.upgrades ) is that there are used also old server instances in those tests. > Due to new changes in infinispan-arquillian-container old Infinispan servers are not properly managed during their startup phase. > Observation: > Switching port to 10099 (wildfly is using 10090 for mgmt ops) does not help. Strange message is continuously showing until timeout: > 13:41:57,691 ERROR [org.jboss.remoting.remote.connection] (Remoting "node1:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856 > "Experiment" with setting up <property name="managementProtocol">remoting-jmx</property> for OLD server in arquillian.xml didn't help either, however, ERROR message ^ disappeared. > But the server can't start properly, better to say, it starts, but Arquillian is not able to handle it properly and communicate: > testHotRodRollingUpgradesDiffVersions(org.infinispan.server.test.rollingupgrades.HotRodRollingUpgradesIT) Time elapsed: 60.389 sec <<< ERROR! > org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container > at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:204) > at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:112) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:93) > at org.infinispan.server.test.rollingupgrades.HotRodRollingUpgradesIT.testHotRodRollingUpgradesDiffVersions(HotRodRollingUpgradesIT.java:68) > It looks like we need to somehow create a "bridge" or "switch" which will allow operations for both old and new servers in one test. > Or maybe I'm missing something important. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4421) Migration from jboss-as to wildfly arquillian-container-managed broke RollingUpgrades tests

by Tomas Sykora (JIRA)

Tomas Sykora created ISPN-4421: ---------------------------------- Summary: Migration from jboss-as to wildfly arquillian-container-managed broke RollingUpgrades tests Key: ISPN-4421 URL: https://issues.jboss.org/browse/ISPN-4421 Project: Infinispan Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite - Server Affects Versions: 7.0.0.Alpha4 Reporter: Tomas Sykora Assignee: Mircea Markus Server was rebased to Wildfly. For Arquillian, jboss-as-arquillian-container-managed was changed to wildfly-arquillian-container-managed in order to reflect respective changes. The problem for Rolling Upgrade tests ( -Psuite.rolling.upgrades ) is that there are used also old server instances in those tests. Due to new changes in infinispan-arquillian-container old Infinispan servers are not properly managed during their startup phase. Observation: Switching port to 10099 (wildfly is using 10090 for mgmt ops) does not help. Strange message is continuously showing until timeout: 13:41:57,691 ERROR [org.jboss.remoting.remote.connection] (Remoting "node1:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856 "Experiment" with setting up <property name="managementProtocol">remoting-jmx</property> for OLD server in arquillian.xml didn't help either, however, ERROR message ^ disappeared. But the server can't start properly, better to say, it starts, but Arquillian is not able to handle it properly and communicate: testHotRodRollingUpgradesDiffVersions(org.infinispan.server.test.rollingupgrades.HotRodRollingUpgradesIT) Time elapsed: 60.389 sec <<< ERROR! org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:204) at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:112) at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:93) at org.infinispan.server.test.rollingupgrades.HotRodRollingUpgradesIT.testHotRodRollingUpgradesDiffVersions(HotRodRollingUpgradesIT.java:68) It looks like we need to somehow create a "bridge" or "switch" which will allow operations for both old and new servers in one test. Or maybe I'm missing something important. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3917) Filter objects using the query DSL (without using an index)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3917?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3917: ----------------------------------------------- Radim Vansa <rvansa(a)redhat.com> changed the Status of [bug 1102791|https://bugzilla.redhat.com/show_bug.cgi?id=1102791] from ON_QA to VERIFIED > Filter objects using the query DSL (without using an index) > ----------------------------------------------------------- > > Key: ISPN-3917 > URL: https://issues.jboss.org/browse/ISPN-3917 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Embedded Querying > Reporter: William Burns > Assignee: Adrian Nistor > Labels: 630, roadmap > Fix For: 7.0.0.Alpha4, 7.0.0.Final > > > The cluster listeners will want to use the Query DSL for filtering and projection views. We don't want to have to tie ourselves to Lucene to do this. It was discussed to implement this using reflection. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4047) Use the sort criteria provided by hql-parser (after fixing HQLPARSER-24)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4047?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4047: ----------------------------------------------- Radim Vansa <rvansa(a)redhat.com> changed the Status of [bug 1102791|https://bugzilla.redhat.com/show_bug.cgi?id=1102791] from ON_QA to VERIFIED > Use the sort criteria provided by hql-parser (after fixing HQLPARSER-24) > ------------------------------------------------------------------------ > > Key: ISPN-4047 > URL: https://issues.jboss.org/browse/ISPN-4047 > Project: Infinispan > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Embedded Querying, Remote Querying > Affects Versions: 6.0.1.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: 630 > Fix For: 7.0.0.Beta1, 7.0.0.Final > > > Currently we have separate handling of the sort criteria in Infinispan because the JPQL parser skips it. See https://hibernate.atlassian.net/browse/HQLPARSER-24. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2109) OData for Infinispan

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-2109?page=com.atlassian.jira.plugin.... ] Tomas Sykora commented on ISPN-2109: ------------------------------------ Code in upstream -- branch odata4j-based at: https://github.com/infinispan/infinispan-odata-server Currently migrating to Apache Olingo. > OData for Infinispan > -------------------- > > Key: ISPN-2109 > URL: https://issues.jboss.org/browse/ISPN-2109 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Tomas Sykora > Assignee: Tomas Sykora > > Infinispan allows clients to connect to the data grid over a RESTful protocol, as described here: https://docs.jboss.org/author/display/ISPN/Infinispan+REST+Server. However, the http://www.odata.org/ specification and API is an ideal, open, RESTful API for interacting with data stores. This student idea is to implement an alternative REST endpoint - similar to Infinispan's existing REST endpoint - that speaks ODATA, and to benchmark and test this endpoint using one or more ODATA clients publicly available on http://www.odata.org/libraries. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3717) Add support for index-less queries using the EntryRetriever

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3717?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3717: ----------------------------------------------- Radim Vansa <rvansa(a)redhat.com> changed the Status of [bug 1104667|https://bugzilla.redhat.com/show_bug.cgi?id=1104667] from ON_QA to MODIFIED > Add support for index-less queries using the EntryRetriever > ----------------------------------------------------------- > > Key: ISPN-3717 > URL: https://issues.jboss.org/browse/ISPN-3717 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: 6.3remotequeries, 630, roadmap > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > > The current Lucene-based search implementation requires indexes for all fields that are referenced in queries. > Need to be able to query also for non-indexed fields. M/R is a potential implementation idea. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4420) Allow configuring keepalive for hotrod connections

by Mircea Markus (JIRA)

Mircea Markus created ISPN-4420: ----------------------------------- Summary: Allow configuring keepalive for hotrod connections Key: ISPN-4420 URL: https://issues.jboss.org/browse/ISPN-4420 Project: Infinispan Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mircea Markus Assignee: Mircea Markus Also consider making the Tcp connections pluggable. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4419) Upgrade to netty 4.0.20

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4419?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4419: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2636 > Upgrade to netty 4.0.20 > ----------------------- > > Key: ISPN-4419 > URL: https://issues.jboss.org/browse/ISPN-4419 > Project: Infinispan > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Server > Reporter: Tristan Tarrant > Assignee: Norman Maurer > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4419) Upgrade to netty 4.0.20

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4419?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4419: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade to netty 4.0.20 > ----------------------- > > Key: ISPN-4419 > URL: https://issues.jboss.org/browse/ISPN-4419 > Project: Infinispan > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Server > Reporter: Tristan Tarrant > Assignee: Norman Maurer > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 June 2014