December 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3450) Jon plugin - failing RebuildIndex operation on [MassIndexer] component

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3450?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-3450: ------------------------------------- This definitelly does not work because in CacheComponent.queryBean method there is a check that ensure the MBean name has a type=Cache attribute. This is true for all cache components but not for the mass indexing mbean which has type=Query. For this one the method returns null, leading to the observer NPE. An easy fix would be to add a type parameter to the method in question. > Jon plugin - failing RebuildIndex operation on [MassIndexer] component > ---------------------------------------------------------------------- > > Key: ISPN-3450 > URL: https://issues.jboss.org/browse/ISPN-3450 > Project: Infinispan > Issue Type: Bug > Reporter: Tomas Sykora > Assignee: Mircea Markus > > RebuildIndex operation on [MassIndexer] component is failing while issuing in JON with this error: > java.lang.NullPointerException > at org.infinispan.rhq.CacheComponent.invokeOperation(CacheComponent.java:157) > 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:601) > at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:634) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > I reused configuration from ISPN test suite + I was able to issue this operation successfully via jconsole tool. That's why I suspect that problems are somewhere in JON-ISPN interaction or plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3364) Tests from org.infinispan.atomic package fail with AssertionError

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3364?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3364: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Tests from org.infinispan.atomic package fail with AssertionError > ----------------------------------------------------------------- > > Key: ISPN-3364 > URL: https://issues.jboss.org/browse/ISPN-3364 > Project: Infinispan > Issue Type: Bug > Components: Core API > Affects Versions: 6.0.0.Alpha1 > Environment: RHEL5_x86, RHEL5_x86_64, RHEL6_x86, RHEL5_x86_64 with IBM JDK7 > Reporter: Vitalii Chepeliuk > Assignee: William Burns > Labels: 620 > Fix For: 6.1.0.Final > > Attachments: LocalDeltaAwarePassivationTest.log.zip, ReplDeltaAwarePassivationTest.log.zip > > > Following tests fail from org.infinispan.atomic package > org.infinispan.atomic.LocalDeltaAwarePassivationTest.testAtomicMap > org.infinispan.atomic.LocalDeltaAwarePassivationTest.testDeltaAware > org.infinispan.atomic.LocalDeltaAwarePassivationTest.testFineGrainedAtomicMap > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testAtomicMap > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testAtomicMap2 > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testDeltaAware > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testDeltaAware2 > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testFineGrainedAtomicMap > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testFineGrainedAtomicMap2 > Add link on jenkins job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3821) Server distribution missing some client dependencies

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3821?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-3821: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Server distribution missing some client dependencies > ---------------------------------------------------- > > Key: ISPN-3821 > URL: https://issues.jboss.org/browse/ISPN-3821 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 6.0.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.1.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3659) Cache stop should clear thread-local ExtendedRiverMarshaller or their instance caches

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3659?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3659: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) > Cache stop should clear thread-local ExtendedRiverMarshaller or their instance caches > ------------------------------------------------------------------------------------- > > Key: ISPN-3659 > URL: https://issues.jboss.org/browse/ISPN-3659 > Project: Infinispan > Issue Type: Bug > Components: Marshalling > Affects Versions: 5.3.0.Final, 6.0.0.CR1 > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Priority: Critical > Labels: 620 > Fix For: 6.1.0.Final > > > The fix for ISPN-2372 was incomplete. We now clear the references from the thread-local marshallers to the cache itself, so it can be garbage-collected, but we don't clear the marshallers or their instance caches. If the cache values' object graph is very large, the cached marshallers will use up a lot of memory that could be garbage-collected (assuming the cache was indeed restarted and only one cache instance is running now). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3805) Extended statistics test failures caused by ISPN-3422

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3805?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3805: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Extended statistics test failures caused by ISPN-3422 > ----------------------------------------------------- > > Key: ISPN-3805 > URL: https://issues.jboss.org/browse/ISPN-3805 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Labels: testsuite_stability > Fix For: 7.0.0.Alpha1 > > > The ISPN-3422 fix caused a lot of failures in the extended statistics module's test suite. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3822) Server configuration should allow disabling statistics

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3822?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-3822: --------------------------------------- {quote} For the 7.x stream we should disable them by default instead.{quote} +1 !! created ISPN-3822 > Server configuration should allow disabling statistics > ------------------------------------------------------ > > Key: ISPN-3822 > URL: https://issues.jboss.org/browse/ISPN-3822 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 6.0.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.1.0.Final > > > Statistics collection has an adverse performance impact. > Add a statistics boolean attribute to both caches and containers. For backwards compatibility, maintain stats enabled by default. For the 7.x stream we should disable them by default instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3825) Have statistics collection disabled by default

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-3825: ------------------------------------- Summary: Have statistics collection disabled by default Key: ISPN-3825 URL: https://issues.jboss.org/browse/ISPN-3825 Project: Infinispan Issue Type: Enhancement Components: Server Reporter: Sanne Grinovero Assignee: Tristan Tarrant Fix For: 7.0.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3724) REST RollUps -- Unsupported protocol version 60 throws annoying ERROR and WARN

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3724?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3724: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1031660|https://bugzilla.redhat.com/show_bug.cgi?id=1031660] from NEW to ASSIGNED > REST RollUps -- Unsupported protocol version 60 throws annoying ERROR and WARN > ------------------------------------------------------------------------------ > > Key: ISPN-3724 > URL: https://issues.jboss.org/browse/ISPN-3724 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.CR1 > Reporter: Tomas Sykora > Assignee: Mircea Markus > Labels: 620 > Attachments: restRollups6dot0to6dot0tryingToGetHRkey, RestRollUpsUnsupportedProtocol60 > > > Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and the same server as a source node. > Run Infinispan-server testsuite test for REST Rolling Upgrades. > mvn clean verify -P suite.examples -Dtest=ExampleConfigsTest#testRestRollingUpgrades -DfailIfNoTests=false > See new attached file with current stacktrace. REST rolling upgrades from 5.2.x to 6.0 will probably _not_ be supported. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3824) Upgrade to JBoss Transactions 4.17.17

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-3824: ------------------------------------- Summary: Upgrade to JBoss Transactions 4.17.17 Key: ISPN-3824 URL: https://issues.jboss.org/browse/ISPN-3824 Project: Infinispan Issue Type: Component Upgrade Components: Transactions Reporter: Sanne Grinovero Assignee: Mircea Markus Fix For: 6.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3724) REST RollUps -- Unsupported protocol version 60 throws annoying ERROR and WARN

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3724?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3724: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2278 > REST RollUps -- Unsupported protocol version 60 throws annoying ERROR and WARN > ------------------------------------------------------------------------------ > > Key: ISPN-3724 > URL: https://issues.jboss.org/browse/ISPN-3724 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.CR1 > Reporter: Tomas Sykora > Assignee: Mircea Markus > Labels: 620 > Attachments: restRollups6dot0to6dot0tryingToGetHRkey, RestRollUpsUnsupportedProtocol60 > > > Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and the same server as a source node. > Run Infinispan-server testsuite test for REST Rolling Upgrades. > mvn clean verify -P suite.examples -Dtest=ExampleConfigsTest#testRestRollingUpgrades -DfailIfNoTests=false > See new attached file with current stacktrace. REST rolling upgrades from 5.2.x to 6.0 will probably _not_ be supported. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 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 December 2013