April 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5359) Drop old server parsers

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-5359: ------------------------------------- Summary: Drop old server parsers Key: ISPN-5359 URL: https://issues.jboss.org/browse/ISPN-5359 Project: Infinispan Issue Type: Task Components: Server Affects Versions: 7.2.0.Beta2 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 7.2.0.CR1 We should drop old server parsers (< 1.4) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4795) Warning message about forcing to return previous does not apply to Get operations

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4795?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4795: ----------------------------------------------- wfink(a)redhat.com changed the Status of [bug 1210335|https://bugzilla.redhat.com/show_bug.cgi?id=1210335] from NEW to ASSIGNED > Warning message about forcing to return previous does not apply to Get operations > --------------------------------------------------------------------------------- > > Key: ISPN-4795 > URL: https://issues.jboss.org/browse/ISPN-4795 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.1.0.Final > > > {code} > 'ISPN006010: Operation 'GetRequest' forced to return previous value should be used on transactional caches' in the log > {code} > That message should not appear. GetRequest does not force returning previous. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4795) Warning message about forcing to return previous does not apply to Get operations

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4795?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4795: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1210335 > Warning message about forcing to return previous does not apply to Get operations > --------------------------------------------------------------------------------- > > Key: ISPN-4795 > URL: https://issues.jboss.org/browse/ISPN-4795 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.1.0.Final > > > {code} > 'ISPN006010: Operation 'GetRequest' forced to return previous value should be used on transactional caches' in the log > {code} > That message should not appear. GetRequest does not force returning previous. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5321) StringBasedStoreMultinodeIT.testFetchState fails randomly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5321?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5321: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1210312|https://bugzilla.redhat.com/show_bug.cgi?id=1210312] from NEW to POST > StringBasedStoreMultinodeIT.testFetchState fails randomly > --------------------------------------------------------- > > Key: ISPN-5321 > URL: https://issues.jboss.org/browse/ISPN-5321 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 7.2.0.Beta2 > > > Fails as {{k1}} enrtyr is evicted instead of expected {{k2}}: > {noformat} > java.lang.AssertionError: expected null, but was:<[B@636e6f73> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotNull(Assert.java:664) > at org.junit.Assert.assertNull(Assert.java:646) > at org.junit.Assert.assertNull(Assert.java:656) > at org.infinispan.server.test.cs.jdbc.multinode.StringBasedStoreMultinodeIT.testFetchState(StringBasedStoreMultinodeIT.java:60) > {noformat} > see e.g. [this CI build|http://ci.infinispan.org/viewLog.html?buildId=24519&tab=buildResult...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5321) StringBasedStoreMultinodeIT.testFetchState fails randomly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5321?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5321: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1210312 > StringBasedStoreMultinodeIT.testFetchState fails randomly > --------------------------------------------------------- > > Key: ISPN-5321 > URL: https://issues.jboss.org/browse/ISPN-5321 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 7.2.0.Beta2 > > > Fails as {{k1}} enrtyr is evicted instead of expected {{k2}}: > {noformat} > java.lang.AssertionError: expected null, but was:<[B@636e6f73> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotNull(Assert.java:664) > at org.junit.Assert.assertNull(Assert.java:646) > at org.junit.Assert.assertNull(Assert.java:656) > at org.infinispan.server.test.cs.jdbc.multinode.StringBasedStoreMultinodeIT.testFetchState(StringBasedStoreMultinodeIT.java:60) > {noformat} > see e.g. [this CI build|http://ci.infinispan.org/viewLog.html?buildId=24519&tab=buildResult...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5147) Creation/configuration of caches using JON should not require a server restart

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-5147?page=com.atlassian.jira.plugin.... ] Tomas Sykora commented on ISPN-5147: ------------------------------------ When we configure a new cache under the cache manager in JON, the cache is automatically started immediatelly once the configuration is finished. Just FYI. What we are still missing however is the possibility of changing configuration "on-fly" without restarting the server. Is that ^ what we are trying to achieve in this JIRA? > Creation/configuration of caches using JON should not require a server restart > ------------------------------------------------------------------------------ > > Key: ISPN-5147 > URL: https://issues.jboss.org/browse/ISPN-5147 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management, Server > Reporter: Tristan Tarrant > Assignee: William Burns > Fix For: 7.2.0.Final > > > When creating a cache using the management interface, we want to be able to set all specific configuration and start the cache without requiring a server restart. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3826) CacheResultInterceptor has no InterceptorBindingType

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-3826?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec closed ISPN-3826. ------------------------------------- Fix Version/s: 7.2.0.CR1 Resolution: Won't Fix > CacheResultInterceptor has no InterceptorBindingType > ---------------------------------------------------- > > Key: ISPN-3826 > URL: https://issues.jboss.org/browse/ISPN-3826 > Project: Infinispan > Issue Type: Bug > Components: JCache > Affects Versions: 5.3.0.Final > Reporter: Nicolai Mainiero > Assignee: Sebastian Łaskawiec > Priority: Critical > Fix For: 7.2.0.CR1 > > > I'm migrating an enterprise application from JBoss AS 7 to WebSphere AS 8. We use Infinispan as Cache via the JCache API. On JBoss everything works fine. On WebSphere we get the following exception: > org.apache.webbeans.exception.WebBeansConfigurationException: WebBeans XML configuration defined in file infinispan-jcache-5.3.0.Final.jar!/META-INF/beans.xml is failed. Reason is : Interceptor class : org.infinispan.jcache.annotation.CacheResultInterceptor must have at least one @InterceptorBindingType > I think the cause is that there is no InterceptorBindingType in the CacheResultInterceptor as required by the specification (https://docs.jboss.org/cdi/spec/1.0/html/interceptors.html) and the CDI implementation of the WebSphere (OpenWebBeans) does not accept Interceptors without bindings. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3826) CacheResultInterceptor has no InterceptorBindingType

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-3826?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-3826: ------------------------------------------- Hey [~nicolai.mainiero.sidion]! I'm closing this issue, it looks like this is a WebSphere's issue. If this is still an issue to you I would recommend opening a ticket for WebSphere AS 8. Thanks! > CacheResultInterceptor has no InterceptorBindingType > ---------------------------------------------------- > > Key: ISPN-3826 > URL: https://issues.jboss.org/browse/ISPN-3826 > Project: Infinispan > Issue Type: Bug > Components: JCache > Affects Versions: 5.3.0.Final > Reporter: Nicolai Mainiero > Assignee: Sebastian Łaskawiec > Priority: Critical > > I'm migrating an enterprise application from JBoss AS 7 to WebSphere AS 8. We use Infinispan as Cache via the JCache API. On JBoss everything works fine. On WebSphere we get the following exception: > org.apache.webbeans.exception.WebBeansConfigurationException: WebBeans XML configuration defined in file infinispan-jcache-5.3.0.Final.jar!/META-INF/beans.xml is failed. Reason is : Interceptor class : org.infinispan.jcache.annotation.CacheResultInterceptor must have at least one @InterceptorBindingType > I think the cause is that there is no InterceptorBindingType in the CacheResultInterceptor as required by the specification (https://docs.jboss.org/cdi/spec/1.0/html/interceptors.html) and the CDI implementation of the WebSphere (OpenWebBeans) does not accept Interceptors without bindings. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5358) FuturesTest.testCombineWithCompletionErrors random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5358?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-5358. -------------------------------- Resolution: Duplicate Issue Duplicate of ISPN-5198 > FuturesTest.testCombineWithCompletionErrors random failures > ----------------------------------------------------------- > > Key: ISPN-5358 > URL: https://issues.jboss.org/browse/ISPN-5358 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite - Core > Affects Versions: 7.2.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Blocker > Fix For: 7.2.0.Final > > > {noformat} > [pri:0, instance:org.infinispan.commons.util.concurrent.FuturesTest@241ecdba] should have thrown an exception of class java.util.concurrent.ExecutionException > at org.testng.internal.Invoker.handleInvocationResults(Invoker.java:1512) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:754) > {noformat} > http://ci.infinispan.org/viewLog.html?buildId=24682&buildTypeId=bt9&guest=1 > I believe this can happen because {{NotifyingFutureImpl}}'s {{actualReturnValue}} and {{exceptionThrown}} fields are not {{volatile}}. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5306) Eviction should allow for long size configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5306?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5306: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.2.0.Final Resolution: Done > Eviction should allow for long size configuration > ------------------------------------------------- > > Key: ISPN-5306 > URL: https://issues.jboss.org/browse/ISPN-5306 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Eviction > Reporter: William Burns > Assignee: William Burns > Fix For: 7.2.0.CR1, 7.2.0.Final > > > We added the new EquivalentBoundedConcurrentHashMapv8 in ISPN-3023. This new implementation allows for long size instead of int. However there is no way to configure these at this time. We need to change both the xsd schema and the programmatic configuration to support long. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2015