November 2014 - infinispan-issues

[JBoss JIRA] (ISPN-4965) Upgrade to protostream-2.0.2.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4965?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4965: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1162536|https://bugzilla.redhat.com/show_bug.cgi?id=1162536] from MODIFIED to ON_QA > Upgrade to protostream-2.0.2.Final > ---------------------------------- > > Key: ISPN-4965 > URL: https://issues.jboss.org/browse/ISPN-4965 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 7.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.1.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4933) Protostream annotation parser throws ArrayIndexOutOfBoundsException if the last annotation identifier is not followed by at least one other token

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4933?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4933: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1162536|https://bugzilla.redhat.com/show_bug.cgi?id=1162536] from MODIFIED to ON_QA > Protostream annotation parser throws ArrayIndexOutOfBoundsException if the last annotation identifier is not followed by at least one other token > ------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-4933 > URL: https://issues.jboss.org/browse/ISPN-4933 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 7.0.0.CR2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.1.Final > > > The following example results in ArrayIndexOutOfBoundsException: > {code} > /** > * @Indexed > */ > {code} > and this one works: > {code} > /** > * @Indexed() > */ > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4821) RHQ operation 'Upload Proto Schemas' no longer works due to changes introduced by ISPN-4357

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4821?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4821: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1151218|https://bugzilla.redhat.com/show_bug.cgi?id=1151218] from MODIFIED to ON_QA > RHQ operation 'Upload Proto Schemas' no longer works due to changes introduced by ISPN-4357 > ------------------------------------------------------------------------------------------- > > Key: ISPN-4821 > URL: https://issues.jboss.org/browse/ISPN-4821 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 7.0.0.CR1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.CR2 > > > UploadProtoFileOperationHandler cannot correctly guess the file path from the given URL, so it would be better to add an another parameter for the name, similar to the way RegisterProtoSchemasOperationHandler works. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4694) Apply ASYNC backend indexing options to the RemoteIndexingBackend

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4694?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4694: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1161659|https://bugzilla.redhat.com/show_bug.cgi?id=1161659] from MODIFIED to ON_QA > Apply ASYNC backend indexing options to the RemoteIndexingBackend > ----------------------------------------------------------------- > > Key: ISPN-4694 > URL: https://issues.jboss.org/browse/ISPN-4694 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 7.0.0.CR1, 7.0.0.Final > > > The {{RemoteIndexingBackend}} in Infinispan Query generates synchronous RPCs. > There is an option in Hibernate Search to enable the "async" worker, which decouples the indexing queue processing from the invoker by using a separate executor. > If this option is enabled, we should transparently apply it to the {{RemoteIndexingBackend}} too by making RPCs non blocking as well. > {code}rpcManager.getDefaultRpcOptions(sync){code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4969) Stopping a cache will stop all KeyAffinityServices created for other caches in the cache manager

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/ISPN-4969?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated ISPN-4969: ------------------------------- Description: We've had several reports in the WildFly forums of application runtime failures following undeployment of a separate application. WF creates a cache instance for each web application within the same cache container. However, KeyAffinityServiceImpl registers a cache manager listener that calls stop() on a @CacheStoppedEvent. However, this event can be triggered by any cache stop, not necessarily the cache with to which the KeyAffinityService is associated. The KeyAffinityServiceImpl.handleCacheStopped(CacheStoppedEvent) should only call stop() if the event.getCacheName() equals the name of the cache to which the affinity service is associated. was: We've had several reports in the WildFly forums of application runtime failures following undeployment of a separate application. WF creates a cache instance for each web application within the same cache container. However, KeyAffinityServiceImpl registers a cache manager listener that calls stop() on a @CacheStoppedEvent. However, this event is triggered by any cache stop, not necessarily the cache with to which the KeyAffinityService is associated. The KeyAffinityServiceImpl.handleCacheStopped(CacheStoppedEvent) should only call stop() if the event.getCacheName() equals the name of the cache to which the affinity service is associated. > Stopping a cache will stop all KeyAffinityServices created for other caches in the cache manager > ------------------------------------------------------------------------------------------------ > > Key: ISPN-4969 > URL: https://issues.jboss.org/browse/ISPN-4969 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 5.2.8.Final, 6.0.2.Final, 7.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > > We've had several reports in the WildFly forums of application runtime failures following undeployment of a separate application. > WF creates a cache instance for each web application within the same cache container. However, KeyAffinityServiceImpl registers a cache manager listener that calls stop() on a @CacheStoppedEvent. However, this event can be triggered by any cache stop, not necessarily the cache with to which the KeyAffinityService is associated. > The KeyAffinityServiceImpl.handleCacheStopped(CacheStoppedEvent) should only call stop() if the event.getCacheName() equals the name of the cache to which the affinity service is associated. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4969) Stopping a cache will stop all KeyAffinityServices created for other caches in the cache manager

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/ISPN-4969?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated ISPN-4969: ------------------------------- Description: We've had several reports in the WildFly forums of application runtime failures following undeployment of a separate application. WF creates a cache instance for each web application within the same cache container. However, KeyAffinityServiceImpl registers a cache manager listener that calls stop() on a @CacheStoppedEvent. However, this event might be triggered by any cache, not necessarily the cache with to which the KeyAffinityService is associated. The KeyAffinityServiceImpl.handleCacheStopped(CacheStoppedEvent) should only call stop() if the event.getCacheName() equals the name of the cache to which the affinity service is associated. was: We've had several reports in the WildFly forums of application runtime failures following undeployment of a separate application. WF creates a cache instance for each web application within the same cache container. However, KeyAffinityServiceImpl registers a cache manager listener that calls stop() on a @CacheStoppedEvent. However, this event can be triggered by any cache stop, not necessarily the cache with to which the KeyAffinityService is associated. The KeyAffinityServiceImpl.handleCacheStopped(CacheStoppedEvent) should only call stop() if the event.getCacheName() equals the name of the cache to which the affinity service is associated. > Stopping a cache will stop all KeyAffinityServices created for other caches in the cache manager > ------------------------------------------------------------------------------------------------ > > Key: ISPN-4969 > URL: https://issues.jboss.org/browse/ISPN-4969 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 5.2.8.Final, 6.0.2.Final, 7.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > > We've had several reports in the WildFly forums of application runtime failures following undeployment of a separate application. > WF creates a cache instance for each web application within the same cache container. However, KeyAffinityServiceImpl registers a cache manager listener that calls stop() on a @CacheStoppedEvent. However, this event might be triggered by any cache, not necessarily the cache with to which the KeyAffinityService is associated. > The KeyAffinityServiceImpl.handleCacheStopped(CacheStoppedEvent) should only call stop() if the event.getCacheName() equals the name of the cache to which the affinity service is associated. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4957) Rebalancing "Finished cluster wide rebalance" message is not logged in INFO

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4957?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4957: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1146786|https://bugzilla.redhat.com/show_bug.cgi?id=1146786] from MODIFIED to ON_QA > Rebalancing "Finished cluster wide rebalance" message is not logged in INFO > ---------------------------------------------------------------------------- > > Key: ISPN-4957 > URL: https://issues.jboss.org/browse/ISPN-4957 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Final > Reporter: Suzumura Keishi > Assignee: Ion Savin > Fix For: 7.0.1.Final > > > Rebalancing "Finished cluster wide rebalance" message is not logged in INFO. I can get the log (started/enabled/suspended) messages, but can't get the finished message. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4969) Stopping a cache will stop all KeyAffinityServices created for other caches in the cache manager

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/ISPN-4969?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated ISPN-4969: ------------------------------- Priority: Critical (was: Blocker) > Stopping a cache will stop all KeyAffinityServices created for other caches in the cache manager > ------------------------------------------------------------------------------------------------ > > Key: ISPN-4969 > URL: https://issues.jboss.org/browse/ISPN-4969 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 5.2.8.Final, 6.0.2.Final, 7.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > > We've had several reports in the WildFly forums of application runtime failures following undeployment of a separate application. > WF creates a cache instance for each web application within the same cache container. However, KeyAffinityServiceImpl registers a cache manager listener that calls stop() on a @CacheStoppedEvent. However, this event is triggered by any cache stop, not necessarily the cache with to which the KeyAffinityService is associated. > The KeyAffinityServiceImpl.handleCacheStopped(CacheStoppedEvent) should only call stop() if the event.getCacheName() equals the name of the cache to which the affinity service is associated. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4957) Rebalancing "Finished cluster wide rebalance" message is not logged in INFO

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4957?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4957: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1146786|https://bugzilla.redhat.com/show_bug.cgi?id=1146786] from POST to MODIFIED > Rebalancing "Finished cluster wide rebalance" message is not logged in INFO > ---------------------------------------------------------------------------- > > Key: ISPN-4957 > URL: https://issues.jboss.org/browse/ISPN-4957 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Final > Reporter: Suzumura Keishi > Assignee: Ion Savin > Fix For: 7.0.1.Final > > > Rebalancing "Finished cluster wide rebalance" message is not logged in INFO. I can get the log (started/enabled/suspended) messages, but can't get the finished message. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4969) Stopping a cache will stop all KeyAffinityServices created for other caches in the cache manager

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/ISPN-4969?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on ISPN-4969: ------------------------------------ This requires fixes for the following branches: * 7.0.x, for WildFly 9 * 6.0.x, for WildFly 8.2 * 5.2.x, for EAP 6.4 > Stopping a cache will stop all KeyAffinityServices created for other caches in the cache manager > ------------------------------------------------------------------------------------------------ > > Key: ISPN-4969 > URL: https://issues.jboss.org/browse/ISPN-4969 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 5.2.8.Final, 6.0.2.Final, 7.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 7.0.1.Final > > > We've had several reports in the WildFly forums of application runtime failures following undeployment of a separate application. > WF creates a cache instance for each web application within the same cache container. However, KeyAffinityServiceImpl registers a cache manager listener that calls stop() on a @CacheStoppedEvent. However, this event is triggered by any cache stop, not necessarily the cache with to which the KeyAffinityService is associated. > The KeyAffinityServiceImpl.handleCacheStopped(CacheStoppedEvent) should only call stop() if the event.getCacheName() equals the name of the cache to which the affinity service is associated. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 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 November 2014