[JBoss JIRA] (ISPN-3959) JdbcBinaryStore's expiration locks buckets indefinitely
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3959?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3959:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1176265|https://bugzilla.redhat.com/show_bug.cgi?id=1176265] from MODIFIED to ON_QA
> JdbcBinaryStore's expiration locks buckets indefinitely
> -------------------------------------------------------
>
> Key: ISPN-3959
> URL: https://issues.jboss.org/browse/ISPN-3959
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 6.0.2.Final, 7.0.0.Alpha4
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Fix For: 7.0.0.Alpha5, 7.0.0.Final
>
>
> The buckets are locked in eviction thread (in the main purge method), while unlocked in BucketPurger.call() which is executed in persistence thread. The unlock fails and the buckets stay locked indefinitely.
> Another error is that the Bucket class is not serializable.
> This is also a bug in BaseStoreTest as this uses WithinThreadExecutor as the executor for purging while usually this is done in different thread. Moreover, as the purge method is actually not obliged to purge anything, the test does not test the purging itself, but rather a check for expired entry when it is loaded (contains operation). The purging should be enforced by purge listener (calling the purge method until all entries are purged).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (ISPN-5112) SpringEmbeddedCacheManagerFactoryBeanTest and InfinispanEmbeddedCacheManagerFactoryBeanTest tests fail with FileNotFoundException exception
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5112?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5112:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1178649|https://bugzilla.redhat.com/show_bug.cgi?id=1178649] from MODIFIED to ON_QA
> SpringEmbeddedCacheManagerFactoryBeanTest and InfinispanEmbeddedCacheManagerFactoryBeanTest tests fail with FileNotFoundException exception
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-5112
> URL: https://issues.jboss.org/browse/ISPN-5112
> Project: Infinispan
> Issue Type: Bug
> Components: Spring Integration
> Affects Versions: 7.0.1.Final, 7.0.2.Final
> Reporter: Vitalii Chepeliuk
> Assignee: Vitalii Chepeliuk
> Labels: testsuite_stability
>
> {noformat}
> org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheConfigurationException: configurationFile property specifies value jgroups-tcp.xml that could not be read!
> at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:254)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:570)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:536)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:414)
> at org.infinispan.spring.support.embedded.InfinispanEmbeddedCacheManagerFactoryBeanTest$2.call(InfinispanEmbeddedCacheManagerFactoryBeanTest.java:82)
> at org.infinispan.test.TestingUtil.withCacheManager(TestingUtil.java:1277)
> at org.infinispan.spring.support.embedded.InfinispanEmbeddedCacheManagerFactoryBeanTest.infinispanEmbeddedCacheManagerFactoryBeanShouldCreateACustomizedCacheManagerIfGivenADefaultConfigurationLocation(InfinispanEmbeddedCacheManagerFactoryBeanTest.java:75)
> 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:606)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
> at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
> at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.infinispan.commons.CacheConfigurationException: configurationFile property specifies value jgroups-tcp.xml that could not be read!
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.buildChannel(JGroupsTransport.java:398)
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.initChannel(JGroupsTransport.java:310)
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.initChannelAndRPCDispatcher(JGroupsTransport.java:354)
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.start(JGroupsTransport.java:190)
> 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:606)
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638)
> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:627)
> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530)
> at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:232)
> ... 26 more
> Caused by: java.io.FileNotFoundException: jgroups-tcp.xml
> ... 40 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (ISPN-2145) No descriptions for invalid jgroups configuration files
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-2145?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-2145:
----------------------------------
Fix Version/s: 7.1.0.CR1
(was: 7.1.0.Beta1)
> No descriptions for invalid jgroups configuration files
> -------------------------------------------------------
>
> Key: ISPN-2145
> URL: https://issues.jboss.org/browse/ISPN-2145
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 5.1.2.FINAL, 7.0.0.CR1
> Environment: Any
> Reporter: Dmitry Udalov
> Assignee: Tristan Tarrant
> Fix For: 7.1.0.CR1
>
>
> Can't find error's description for invalid jgroups configuration files. Shuffling elements of the file (why not!) makes it invalid, but log-files only report the existence of the error and you have to debug it to figure out the problem. It would be easier if the class JGroupsTransport also reports the exception, not just a generic message in blocks like
> } catch (Exception e) {
> log.errorCreatingChannelFromConfigFile(cfg);
> throw new CacheException(e);
> }
> As a result log-file contains a lot of generic messages without explaining the problem, which in my case was quite helpful:
> java.lang.Exception: events [GET_DIGEST SET_DIGEST FIND_INITIAL_MBRS FIND_ALL_VIEWS ] are required by GMS, but not provided by any of the protocols below it
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (ISPN-3199) API to manipulate multiple versions of an entry
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-3199?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-3199:
----------------------------------
Fix Version/s: 7.1.0.CR1
(was: 7.1.0.Beta1)
> API to manipulate multiple versions of an entry
> -----------------------------------------------
>
> Key: ISPN-3199
> URL: https://issues.jboss.org/browse/ISPN-3199
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 5.3.0.Final
> Reporter: Manik Surtani
> Assignee: Mircea Markus
> Labels: leads
> Fix For: 7.1.0.CR1
>
>
> In addition to the existing API, the following will be needed to allow user applications to directly control versioning. E.g.,
> {code}
> put(K key, EntryVersion version);
> get(K key, EntryVersion version);
> getLatest(K key, EntryVersion upperBound);
> evict(K key, EntryVersion upTo);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months