February 2018 - infinispan-issues

[JBoss JIRA] (ISPN-8837) CompatModeClusteredCacheTest failing with ClassCastException

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-8837: ------------------------------------- Summary: CompatModeClusteredCacheTest failing with ClassCastException Key: ISPN-8837 URL: https://issues.jboss.org/browse/ISPN-8837 Project: Infinispan Issue Type: Task Components: Test Suite - Query Reporter: Sanne Grinovero Assignee: Adrian Nistor Fix For: 9.2.0.Final This test is failing consistently; someone please investigate? http://ci.infinispan.org/job/Infinispan/job/master/lastCompletedBuild/tes... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8837) CompatModeClusteredCacheTest failing with ClassCastException

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-8837?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-8837: ---------------------------------- Status: Open (was: New) > CompatModeClusteredCacheTest failing with ClassCastException > ------------------------------------------------------------ > > Key: ISPN-8837 > URL: https://issues.jboss.org/browse/ISPN-8837 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Query > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > Fix For: 9.2.0.Final > > > This test is failing consistently; someone please investigate? > http://ci.infinispan.org/job/Infinispan/job/master/lastCompletedBuild/tes... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7011) @AfterClass cleanup doesn't work with @InTransactionMode or @InCacheMode

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7011?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-7011: ------------------------------------ Should be fixed in TestNG [6.9.5+|https://github.com/cbeust/testng/pull/525/commits/5f8941a053222c26...]. > @AfterClass cleanup doesn't work with @InTransactionMode or @InCacheMode > ------------------------------------------------------------------------ > > Key: ISPN-7011 > URL: https://issues.jboss.org/browse/ISPN-7011 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Labels: testsuite_stability > Fix For: 9.2.0.Final > > > Very much like ISPN-7003, TestNG's {{TestMethodWorker.invokeAfterClassMethods}} never sees an empty list of methods in {{m_classMethodMap}}. That happens because {{m_classMethodMap}} is populated before our {{ChainMethodInterceptor}} had a chance to filter the methods (e.g. when a test method has an {{@InTransactionMode}} annotation). > Normally this is not a problem because each test has a different name, and the test suite tolerates some leaked managers. But when you run a test like {{PutForExternalReadTest}} with {{-Dtest.infinispan.shortTestName=true}}, you get this failure: > {noformat} > java.lang.IllegalStateException: Two tests with the same name running in parallel: test > at org.infinispan.test.fwk.TestResourceTracker.testStarted(TestResourceTracker.java:88) > at org.infinispan.test.AbstractInfinispanTest.testClassStarted(AbstractInfinispanTest.java:115) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138) > at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:175) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:107) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7011) @AfterClass cleanup doesn't work with @InTransactionMode or @InCacheMode

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7011?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7011: ------------------------------- Summary: @AfterClass cleanup doesn't work with @InTransactionMode or @InCacheMode (was: @AfterClass cleanup doesn't work with @InTransactionMode) > @AfterClass cleanup doesn't work with @InTransactionMode or @InCacheMode > ------------------------------------------------------------------------ > > Key: ISPN-7011 > URL: https://issues.jboss.org/browse/ISPN-7011 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Labels: testsuite_stability > Fix For: 9.2.0.Final > > > Very much like ISPN-7003, TestNG's {{TestMethodWorker.invokeAfterClassMethods}} never sees an empty list of methods in {{m_classMethodMap}}. That happens because {{m_classMethodMap}} is populated before our {{ChainMethodInterceptor}} had a chance to filter the methods (e.g. when a test method has an {{@InTransactionMode}} annotation). > Normally this is not a problem because each test has a different name, and the test suite tolerates some leaked managers. But when you run a test like {{PutForExternalReadTest}} with {{-Dtest.infinispan.shortTestName=true}}, you get this failure: > {noformat} > java.lang.IllegalStateException: Two tests with the same name running in parallel: test > at org.infinispan.test.fwk.TestResourceTracker.testStarted(TestResourceTracker.java:88) > at org.infinispan.test.AbstractInfinispanTest.testClassStarted(AbstractInfinispanTest.java:115) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138) > at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:175) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:107) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (IPROTO-47) A new declarative API using entity field bindings with lambdas

by Adrian Nistor (JIRA)

Adrian Nistor created IPROTO-47: ----------------------------------- Summary: A new declarative API using entity field bindings with lambdas Key: IPROTO-47 URL: https://issues.jboss.org/browse/IPROTO-47 Project: Infinispan ProtoStream Issue Type: Feature Request Reporter: Adrian Nistor -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (IPROTO-44) Native support for BigInteger, BigDecimal

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-44?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned IPROTO-44: ----------------------------------- Assignee: Adrian Nistor > Native support for BigInteger, BigDecimal > ----------------------------------------- > > Key: IPROTO-44 > URL: https://issues.jboss.org/browse/IPROTO-44 > Project: Infinispan ProtoStream > Issue Type: Feature Request > Reporter: Adrian Nistor > Assignee: Adrian Nistor > -- 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 Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8780?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-8780: ----------------------------------------- Well spotted, the test against the "main" slot seems to be missing > 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.2.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-8836) Custom region definition causes ISPN000453

by Anton Zalesky (JIRA)

Anton Zalesky created ISPN-8836: ----------------------------------- Summary: Custom region definition causes ISPN000453 Key: ISPN-8836 URL: https://issues.jboss.org/browse/ISPN-8836 Project: Infinispan Issue Type: Bug Components: Hibernate Cache Affects Versions: 9.2.0.CR2 Environment: Hibernate 5.2.13 SpringFramework 5.0.2.RELEASE Reporter: Anton Zalesky Priority: Critical I have entity with defined region @Entity @Table(name = "Dashboard") @Cache(usage = CacheConcurrencyStrategy.READ_WRITE, region = "dashboard") public class Dashboard {..} And I have infinispan.xml with custom configuration for region <local-cache name="dashboard" simple-cache="true" statistics="true" statistics-available="true"> <transaction mode="NONE" /> <expiration max-idle="14400000" /> <memory> <object size="10000"/> </memory> </local-cache> On start I get the following exception org.infinispan.commons.CacheConfigurationException: ISPN000453: Attempt to define configuration for cache dashboard which already exists at org.infinispan.manager.DefaultCacheManager.doDefineConfiguration(DefaultCacheManager.java:370) at org.infinispan.manager.DefaultCacheManager.defineConfiguration(DefaultCacheManager.java:342) at org.infinispan.hibernate.cache.commons.InfinispanRegionFactory.getCache(InfinispanRegionFactory.java:692) at org.infinispan.hibernate.cache.commons.InfinispanRegionFactory.buildEntityRegion(InfinispanRegionFactory.java:332) at org.hibernate.cache.spi.RegionFactory.buildEntityRegion(RegionFactory.java:132) at org.hibernate.internal.CacheImpl.determineEntityRegionAccessStrategy(CacheImpl.java:439) at org.hibernate.metamodel.internal.MetamodelImpl.initialize(MetamodelImpl.java:120) at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:300) at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:460) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:710) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:726) at org.springframework.orm.hibernate5.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:535) at org.springframework.orm.hibernate5.LocalSessionFactoryBean.afterPropertiesSet(LocalSessionFactoryBean.java:519) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1769) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1706) ... 97 more -- 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: --------------------------------------- Finally gettting back on this, sorry for the delay. The most notable thing missing is that the integration tests covering compatibility with the latest "upstream" version of Hibernate Search are not actually testing with the latest. e.g. see {{InfinispanModuleMemberRegistrationIT}} is being injected module identifiers, these ids are now pointing to the "one and only" property version of Hibernate Search in the project. Several of these integration tests had different purposes and were explicitly - as mentioned in their comments - targeting other versions. I'll try to cleanup. > 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.2.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-8794) Simplify Hot Rod client security configuration

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8794?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-8794. -------------------------------- Fix Version/s: 9.2.0.CR3 Resolution: Done > Simplify Hot Rod client security configuration > ---------------------------------------------- > > Key: ISPN-8794 > URL: https://issues.jboss.org/browse/ISPN-8794 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration, Hot Rod > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.2.0.CR3 > > > Configuring a Hot Rod client for authentication can be greatly simplified: > * default to DIGEST-MD5 mech > * use ApplicationRealm as default realm name > * implicitly enable security when setting one of the properties instead of invoking enable() > * add a way to specify a trust cert chain stored in a single PEM file without requiring a full-blown java KeyStore. -- 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