January 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3730) Revisit Infinsipan's transactions

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3730?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3730: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > Revisit Infinsipan's transactions > --------------------------------- > > Key: ISPN-3730 > URL: https://issues.jboss.org/browse/ISPN-3730 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 7.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3711) Add more tests and documentation over Map.putAll with manual eviction with activation

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3711?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3711: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > Add more tests and documentation over Map.putAll with manual eviction with activation > ------------------------------------------------------------------------------------- > > Key: ISPN-3711 > URL: https://issues.jboss.org/browse/ISPN-3711 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.0.CR1 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.1.0.CR1 > > > Map.putAll should now work properly with manual eviction with activation in that there shouldn't be a gap when no entry is seen, but we should confirm with more tests and add some additional explanation since it is different than the other write operations. > https://github.com/infinispan/infinispan/pull/2217#issuecomment-28469310 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3707) I tried to access mbeans on a remotely running Jboss AS7 infinispan server using the jconsole.bat from the infinispan Jboss AS7 installation and i am gettign the following error:

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3707?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3707: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > I tried to access mbeans on a remotely running Jboss AS7 infinispan server using the jconsole.bat from the infinispan Jboss AS7 installation and i am gettign the following error: > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-3707 > URL: https://issues.jboss.org/browse/ISPN-3707 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 6.0.0.CR1 > Reporter: Pra remo > Assignee: Galder Zamarreño > Labels: jboss > Fix For: 7.1.0.CR1 > > > I tried to access mbeans on a remotely running Jboss AS7 infinispan server using the jconsole.bat from the infinispan Jboss AS7 installation and i am gettign the following error: > xception in thread "VMPanel.connect" java.lang.NoClassDefFoundError: org/jboss/logging/Logger > at org.jboss.remotingjmx.RemotingConnectorProvider.<clinit>(RemotingConnectorProvider.java:42) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:247) > at com.sun.jmx.remote.util.Service$LazyIterator.next(Service.java:270) > at javax.management.remote.JMXConnectorFactory.getConnectorAsService(JMXConnectorFactory.java:425) > at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:310) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:207) > at sun.tools.jconsole.ProxyClient.tryConnect(ProxyClient.java:336) > at sun.tools.jconsole.ProxyClient.connect(ProxyClient.java:296) > at sun.tools.jconsole.VMPanel$2.run(VMPanel.java:280) > Caused by: java.lang.ClassNotFoundException: org.jboss.logging.Logger > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:247) > ... 11 more > I used both url's : service:jmx:remoting-jmx://:9999 service:jmx:remoting-jmx://:4447 > C:\Developer\JDK\Java\jdk1.6.0_34\lib\jconsole.jar;C:\Developer\JDK\Java\jdk1.6.0_34\lib\tools.jar;C:\Users\<user>\Downloads\infinispan-server-6.0.0.CR1-bin\infini > span-server-6.0.0.CR1\jboss-modules.jar;C:\Users\<user>\Downloads\infinispan-server-6.0.0.CR1-bin\infinispan-server-6.0.0.CR1\modules\system\layers\base\org\jboss\ > remoting-jmx\main\remoting-jmx-1.1.0.Final.jar;C:\Users\<user>\Downloads\infinispan-server-6.0.0.CR1-bin\infinispan-server-6.0.0.CR1\modules\system\layers\base\org > \jboss\staxmapper\main\staxmapper-1.1.0.Final.jar;C:\Users\<user>\Downloads\infinispan-server-6.0.0.CR1-bin\infinispan-server-6.0.0.CR1\modules\system\layers\base\ > org\jboss\as\protocol\main\jboss-as-protocol-7.2.0.Final.jar;C:\Users\<user>\Downloads\infinispan-server-6.0.0.CR1-bin\infinispan-server-6.0.0.CR1\modules\system\l > ayers\base\org\jboss\dmr\main\jboss-dmr-1.1.6.Final.jar;C:\Users\<user>\Downloads\infinispan-server-6.0.0.CR1-bin\infinispan-server-6.0.0.CR1\modules\system\layers > \base\org\jboss\as\controller-client\main\jboss-as-controller-client-7.2.0.Final.jar;C:\Users\<user>\Downloads\infinispan-server-6.0.0.CR1-bin\infinispan-server-6. > 0.0.CR1\modules\system\layers\base\org\jboss\threads\main\jboss-threads-2.1.0.Fin -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3716) Shareability of Configuration and ConfigurationBuilder instances (and global versions)

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3716?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3716: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > Shareability of Configuration and ConfigurationBuilder instances (and global versions) > -------------------------------------------------------------------------------------- > > Key: ISPN-3716 > URL: https://issues.jboss.org/browse/ISPN-3716 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Reporter: Galder Zamarreño > Assignee: Mircea Markus > Fix For: 7.1.0.CR1 > > > Widlfly is using Configuration/GlobalConfiguration instances of one cache/cachemanager to create other cache managers. > Configuration/GlobalConfiguration are probably not designed to be shareable at this point in time. The builder classes should be sharable but sharing them would not have resolved the issue in ISPN-3698. > It probably makes sense to change marshaller to be a factory or lookup configuration to be able to create instances of marshaller when configuration is created. > ConfigurationBuilder/GlobalConfigurationBuilder classes are expected to be shareable. > Tests and verifications should be added. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3854) Tests from org.infinispan.eviction package fail randomly with Oracle JDK and constantly with IBM JDK6

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3854?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3854: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > Tests from org.infinispan.eviction package fail randomly with Oracle JDK and constantly with IBM JDK6 > ------------------------------------------------------------------------------------------------------ > > Key: ISPN-3854 > URL: https://issues.jboss.org/browse/ISPN-3854 > Project: Infinispan > Issue Type: Bug > Components: Eviction > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1, 7.0.0.Alpha2, 7.0.0.Alpha3, 7.0.0.Alpha4 > Reporter: Vitalii Chepeliuk > Assignee: Pedro Ruivo > Priority: Critical > Labels: testsuite_stability > Fix For: 7.0.0.Alpha1, 7.1.0.CR1 > > Attachments: EvictionWithPassivationAndConcurrentOperationsTest.log.zip, ManualEvictionWithPassivationAndConcurrentOperationsInPrimaryOwnerTest.log.zip > > > Following tests fail randomly on JDK7 > org.infinispan.eviction.ManualEvictionWithPassivationAndConcurrentOperationsInPrimaryOwnerTest.testScenario6 > org.infinispan.eviction.EvictionWithPassivationAndConcurrentOperationsTest.testScenario6 > OracleJDK7 > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > IBM7 > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > OpenJDK7 > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > And bunch of tests fail on IBM6 > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > and here > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > Add windows runs > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3843) Remove broadcast/unicast optimization in JGroupsTransport

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3843?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3843: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > Remove broadcast/unicast optimization in JGroupsTransport > --------------------------------------------------------- > > Key: ISPN-3843 > URL: https://issues.jboss.org/browse/ISPN-3843 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Fix For: 7.1.0.CR1 > > > The broadcast/unicast optimization in JGroupsTransport can break the message ordering for regular messages, because NAKACK[2] and UNICAST[2|3] have their own ordering. > We should test if this optimization really brings any performance benefits and eliminate it, at least for asynchronous commands. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3835) Index Update command is processed before the registry listener is triggered

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3835?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3835: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > Index Update command is processed before the registry listener is triggered > --------------------------------------------------------------------------- > > Key: ISPN-3835 > URL: https://issues.jboss.org/browse/ISPN-3835 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Priority: Critical > Labels: 64QueryBlockers > Fix For: 7.1.0.CR1 > > > When using the InfinispanIndexManager backend the master node might receive an index update command about an index which it hasn't defined yet. > Index definitions are triggered by the type registry, which in turn is driven by the ClusterRegistry and an event listener on the ClusterRegistry. It looks like slaves are sending update requests before the master has processed the configuration event. > This leads to index update commands to be lost (with a stacktrace logged) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

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

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3824?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3824: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > Upgrade to JBoss Transactions 4.17.20 > ------------------------------------- > > 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: 7.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3823) Migrators should not pollute each other with their "global" key entries

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3823?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3823: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > Migrators should not pollute each other with their "global" key entries > ----------------------------------------------------------------------- > > Key: ISPN-3823 > URL: https://issues.jboss.org/browse/ISPN-3823 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.0.Final > Reporter: Tristan Tarrant > Fix For: 7.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3795) QueryInterceptor incorrectly relies on the return value of a RemoveCommand

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3795?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3795: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > QueryInterceptor incorrectly relies on the return value of a RemoveCommand > -------------------------------------------------------------------------- > > Key: ISPN-3795 > URL: https://issues.jboss.org/browse/ISPN-3795 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Fix For: 7.1.0.CR1 > > > QueryInterceptor uses the return value from RemoveCommand/ReplaceCommand to remove the value from the index. > But both RemoveCommand and ReplaceCommand have a variant with an expected value parameter, and this variant return a boolean value instead of the removed/replaced value. In that case, the previous value won't be removed from the index. > QueryInterceptor should probably use the previous value from the context entries to update the index instead. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 January 2015