November 2016 - infinispan-issues

[JBoss JIRA] (ISPN-7227) SearchNewEntityJmsMasterSlaveUsingInfinispanAndModulesIT fails

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-7227?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-7227: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4680 > SearchNewEntityJmsMasterSlaveUsingInfinispanAndModulesIT fails > -------------------------------------------------------------- > > Key: ISPN-7227 > URL: https://issues.jboss.org/browse/ISPN-7227 > Project: Infinispan > Issue Type: Bug > Components: Integration > Affects Versions: 9.0.0.Alpha4 > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > {{SearchNewEntityJmsMasterSlaveUsingInfinispanAndModulesIT}} fails with > {noformat} > Caused by: java.lang.Exception: {"WFLYCTL0080: Failed services" => {"jboss.persistenceunit.\"master.war#pu-master\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"master.war#pu-master\": javax.persistence.PersistenceException: [PersistenceUnit: pu-master] Unable to build Hibernate SessionFactory > Caused by: javax.persistence.PersistenceException: [PersistenceUnit: pu-master] Unable to build Hibernate SessionFactory > Caused by: org.hibernate.search.exception.SearchException: HSEARCH000103: Unable to initialize IndexManager named 'org.infinispan.test.integration.as.jms.model.RegisteredMember' > Caused by: org.hibernate.search.exception.SearchException: HSEARCH000252: Unable to initialize directory provider org.infinispan.hibernate.search.spi.InfinispanDirectoryProvider for index org.infinispan.test.integration.as.jms.model.RegisteredMember > Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheConfigurationException: ISPN000085: Error while trying to create a channel using the specified configuration file: default-configs/default-jgroups-udp.xml > Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000085: Error while trying to create a channel using the specified configuration file: default-configs/default-jgroups-udp.xml > Caused by: java.lang.IllegalArgumentException: JGRP000001: configuration error: the following properties in UDP are not recognized: {oob_thread_pool.max_threads=200, internal_thread_pool.max_threads=20, internal_thread_pool.keep_alive_time=60000, thread_pool.queue_enabled=false, internal_thread_pool.min_threads=5, oob_thread_pool.keep_alive_time=60000, oob_thread_pool.min_threads=20, oob_thread_pool.queue_enabled=false, internal_thread_pool.queue_max_size=500, internal_thread_pool.queue_enabled=true}"}} > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7227) SearchNewEntityJmsMasterSlaveUsingInfinispanAndModulesIT fails

by Vojtech Juranek (JIRA)

Vojtech Juranek created ISPN-7227: ------------------------------------- Summary: SearchNewEntityJmsMasterSlaveUsingInfinispanAndModulesIT fails Key: ISPN-7227 URL: https://issues.jboss.org/browse/ISPN-7227 Project: Infinispan Issue Type: Bug Components: Integration Affects Versions: 9.0.0.Alpha4 Reporter: Vojtech Juranek Assignee: Vojtech Juranek {{SearchNewEntityJmsMasterSlaveUsingInfinispanAndModulesIT}} fails with {noformat} Caused by: java.lang.Exception: {"WFLYCTL0080: Failed services" => {"jboss.persistenceunit.\"master.war#pu-master\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"master.war#pu-master\": javax.persistence.PersistenceException: [PersistenceUnit: pu-master] Unable to build Hibernate SessionFactory Caused by: javax.persistence.PersistenceException: [PersistenceUnit: pu-master] Unable to build Hibernate SessionFactory Caused by: org.hibernate.search.exception.SearchException: HSEARCH000103: Unable to initialize IndexManager named 'org.infinispan.test.integration.as.jms.model.RegisteredMember' Caused by: org.hibernate.search.exception.SearchException: HSEARCH000252: Unable to initialize directory provider org.infinispan.hibernate.search.spi.InfinispanDirectoryProvider for index org.infinispan.test.integration.as.jms.model.RegisteredMember Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheConfigurationException: ISPN000085: Error while trying to create a channel using the specified configuration file: default-configs/default-jgroups-udp.xml Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000085: Error while trying to create a channel using the specified configuration file: default-configs/default-jgroups-udp.xml Caused by: java.lang.IllegalArgumentException: JGRP000001: configuration error: the following properties in UDP are not recognized: {oob_thread_pool.max_threads=200, internal_thread_pool.max_threads=20, internal_thread_pool.keep_alive_time=60000, thread_pool.queue_enabled=false, internal_thread_pool.min_threads=5, oob_thread_pool.keep_alive_time=60000, oob_thread_pool.min_threads=20, oob_thread_pool.queue_enabled=false, internal_thread_pool.queue_max_size=500, internal_thread_pool.queue_enabled=true}"}} {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7158) EmbeddedApplicationPublishedBridgeTest.testEventBridge random failures

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7158?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7158: -------------------------------------- Status: Open (was: New) > EmbeddedApplicationPublishedBridgeTest.testEventBridge random failures > ---------------------------------------------------------------------- > > Key: ISPN-7158 > URL: https://issues.jboss.org/browse/ISPN-7158 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Reporter: Dan Berindei > Assignee: Sebastian Łaskawiec > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.Beta1 > > > {{TimeUnit.SECONDS.sleep(1)}} doesn't guarantee that the thread actually sleeps for a full second. And if it wakes up a millisecond too early, the entry is not expired by the time of the check: > {noformat} > java.lang.AssertionError: expected [null] but found [org.springframework.cache.support.SimpleValueWrapper@7bbbe232] > at org.testng.Assert.fail(Assert.java:94) > at org.testng.Assert.failNotSame(Assert.java:490) > at org.testng.Assert.assertNull(Assert.java:426) > at org.testng.Assert.assertNull(Assert.java:415) > at org.infinispan.spring.session.InfinispanApplicationPublishedBridgeTCK.testEventBridge(InfinispanApplicationPublishedBridgeTCK.java:58) > at org.infinispan.spring.session.EmbeddedApplicationPublishedBridgeTest.testEventBridge(EmbeddedApplicationPublishedBridgeTest.java:59) > {noformat} > The test should use a {{TimeService}} to guarantee that the entry expires without having to wait so long. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7158) EmbeddedApplicationPublishedBridgeTest.testEventBridge random failures

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7158?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7158: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4679 > EmbeddedApplicationPublishedBridgeTest.testEventBridge random failures > ---------------------------------------------------------------------- > > Key: ISPN-7158 > URL: https://issues.jboss.org/browse/ISPN-7158 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Reporter: Dan Berindei > Assignee: Sebastian Łaskawiec > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.Beta1 > > > {{TimeUnit.SECONDS.sleep(1)}} doesn't guarantee that the thread actually sleeps for a full second. And if it wakes up a millisecond too early, the entry is not expired by the time of the check: > {noformat} > java.lang.AssertionError: expected [null] but found [org.springframework.cache.support.SimpleValueWrapper@7bbbe232] > at org.testng.Assert.fail(Assert.java:94) > at org.testng.Assert.failNotSame(Assert.java:490) > at org.testng.Assert.assertNull(Assert.java:426) > at org.testng.Assert.assertNull(Assert.java:415) > at org.infinispan.spring.session.InfinispanApplicationPublishedBridgeTCK.testEventBridge(InfinispanApplicationPublishedBridgeTCK.java:58) > at org.infinispan.spring.session.EmbeddedApplicationPublishedBridgeTest.testEventBridge(EmbeddedApplicationPublishedBridgeTest.java:59) > {noformat} > The test should use a {{TimeService}} to guarantee that the entry expires without having to wait so long. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7160) RemoteSpringSessionTest random failures

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7160?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7160: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4679 > RemoteSpringSessionTest random failures > --------------------------------------- > > Key: ISPN-7160 > URL: https://issues.jboss.org/browse/ISPN-7160 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Reporter: Dan Berindei > Assignee: Sebastian Łaskawiec > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.Beta1 > > > {{RemoteSpringSessionTest}} and {{EmbeddedSpringSessionTest}} use the default cache jmx configuration, so they try to register the same JMX object names. If they run in parallel, one of them will fail to start the cache manager: > {noformat} > org.infinispan.jmx.JmxDomainConflictException: ISPN000034: There's already a JMX MBean instance type=CacheManager,name="DefaultCacheManager" already registered under 'org.infinispan' JMX domain. If you want to allow multiple instances configured with same JMX domain enable 'allowDuplicateDomains' attribute in 'globalJmxStatistics' config element > at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:53) > at org.infinispan.jmx.CacheManagerJmxRegistration.updateDomain(CacheManagerJmxRegistration.java:79) > at org.infinispan.jmx.CacheManagerJmxRegistration.buildRegistrar(CacheManagerJmxRegistration.java:73) > at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:37) > at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:41) > at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:661) > at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:235) > at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:147) > at org.infinispan.integrationtests.spring.boot.session.remote.RemoteSpringSessionTest.beforeclass(RemoteSpringSessionTest.java:29) > {noformat} > If the cache manager was not created, teardown also fails with a NPE: > {noformat} > java.lang.NullPointerException > at org.infinispan.integrationtests.spring.boot.session.remote.RemoteSpringSessionTest.afterClass(RemoteSpringSessionTest.java:41) > {noformat} > The test should use the {{TestCacheManagerFactory}} methods to create the cache manager, which will set a unique JMX domain name for each instance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7226) Compatibility only adds version on replace

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7226?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7226: -------------------------------- Description: Compatibility would add a version if the replace command was used and no version was set. This may be needed for other commands as well, need to confirm. https://github.com/infinispan/infinispan/blob/f9945e7707ca107c9ce0bfaf880... https://github.com/infinispan/infinispan/pull/4578/files/11b100b5b0d42b2d... was: Compatibility would add a version if the replace command was used and no version was set. This may be needed for other commands as well, need to confirm. https://github.com/infinispan/infinispan/blob/f9945e7707ca107c9ce0bfaf880... > Compatibility only adds version on replace > ------------------------------------------ > > Key: ISPN-7226 > URL: https://issues.jboss.org/browse/ISPN-7226 > Project: Infinispan > Issue Type: Task > Components: Server > Reporter: William Burns > > Compatibility would add a version if the replace command was used and no version was set. This may be needed for other commands as well, need to confirm. > https://github.com/infinispan/infinispan/blob/f9945e7707ca107c9ce0bfaf880... > https://github.com/infinispan/infinispan/pull/4578/files/11b100b5b0d42b2d... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7226) Compatibility only adds version on replace

by William Burns (JIRA)

William Burns created ISPN-7226: ----------------------------------- Summary: Compatibility only adds version on replace Key: ISPN-7226 URL: https://issues.jboss.org/browse/ISPN-7226 Project: Infinispan Issue Type: Task Components: Server Reporter: William Burns Compatibility would add a version if the replace command was used and no version was set. This may be needed for other commands as well, need to confirm. https://github.com/infinispan/infinispan/blob/f9945e7707ca107c9ce0bfaf880... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7224) Support synchronous get in Spring's cache abstraction

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7224?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7224: -------------------------------------- Priority: Critical (was: Major) > Support synchronous get in Spring's cache abstraction > ----------------------------------------------------- > > Key: ISPN-7224 > URL: https://issues.jboss.org/browse/ISPN-7224 > Project: Infinispan > Issue Type: Feature Request > Components: Spring Integration > Reporter: Stéphane Nicoll > Assignee: Sebastian Łaskawiec > Priority: Critical > > Spring Framework 4.3 has introduced a read-through option See https://jira.spring.io/browse/SPR-9254 for more details. In practice this would require you to compile against 4.3 and implement the additional method. > The code is meant to be backward compatible with previous version, as long as you're guarding the new exception in an inner class, see [this implementation for an example|https://github.com/hazelcast/hazelcast/blob/37ba79c4a8d35617c5f6a...] > Let me know if I can help. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7225) Move Cache MBean to be separate

by William Burns (JIRA)

William Burns created ISPN-7225: ----------------------------------- Summary: Move Cache MBean to be separate Key: ISPN-7225 URL: https://issues.jboss.org/browse/ISPN-7225 Project: Infinispan Issue Type: Enhancement Reporter: William Burns Currently the MBean is directly defined on the Cache implementation. This makes it cumbersome if we added or used different implementations based on configuration. We should instead separate this to allow for different implementations to be used. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6742) Console shows cache available and disabled at the same time

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6742?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-6742: ------------------------------------------- [~rmacor] [~jholusa] Please see related discussion on https://github.com/infinispan/infinispan-management-console/pull/142 e propose to keep things as they are for now and revisit them later! > Console shows cache available and disabled at the same time > ----------------------------------------------------------- > > Key: ISPN-6742 > URL: https://issues.jboss.org/browse/ISPN-6742 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.2.Final > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Alpha3 > > Attachments: attachment.png > > > Page: go to cache detail and click "Actions" -> "Disable". > After confirmation, the cache status is still "Available", but new red box appears with text "Disabled", see the attachment. This doesn't seem to me very intuitive, if the cache is disabled, it should be IMO unavailable and this should be also reflected in the caches list. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2016