November 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3670) Any commands received before the initial topology is installed should block

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3670?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3670: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > Any commands received before the initial topology is installed should block > --------------------------------------------------------------------------- > > Key: ISPN-3670 > URL: https://issues.jboss.org/browse/ISPN-3670 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 6.0.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 6.1.0.Final > > > Because the initial cache topology is installed in a single phase, it's possible to receive a StateRequestCommand from another node before receiving the JOIN response from the coordinator and installing the initial cache topology. As such, commands received before we have a cache topology should block instead of being ignored. > This bug is especially visible in the Map/Reduce tests (e.g. ReplicatedTwoNodesMapReduceTest) because the M/R task sends the CreateCacheCommand to the other nodes before it's executed on the originator. Since the originator happens to be the coordinator, it's possible for the coordinator to start the rebalance before the first member installed the initial topology. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3614) Add remote query quick start/demo

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3614?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3614: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > Add remote query quick start/demo > --------------------------------- > > Key: ISPN-3614 > URL: https://issues.jboss.org/browse/ISPN-3614 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Adrian Nistor > Fix For: 6.1.0.Final > > > Should describe how the users: > - download the servers > - configure it (indexing ...) > - with sample domain model, how to write the marshallers, define the indexes using the RHQ plugin > - some code that connects to the server, adds and queries the data (mvn module?) -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3354) Multiple events on the local node with Infinispan 5.3.0-final

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3354?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3354: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > Multiple events on the local node with Infinispan 5.3.0-final > ------------------------------------------------------------- > > Key: ISPN-3354 > URL: https://issues.jboss.org/browse/ISPN-3354 > Project: Infinispan > Issue Type: Bug > Components: Listeners > Affects Versions: 5.3.0.Final > Reporter: Luca Zenti > Assignee: Pedro Ruivo > Priority: Critical > Labels: 620 > Fix For: 6.1.0.Final > > Attachments: TestInfinispanDuplicatedEvents.java > > > After upgrading to Infinispan 5.3.0-final I found a strange "intermittent" problem in my application. Digging a bit deeper, I found out it is due to CacheEntry events raised twice for some keys on the local node (the node where the cache operation is invoked). > I was able to reproduce the problem and I wrote the attached test case. > The problem happens regardless of the cluster mode, but only with non-transactional caches. I think this is due to the fact that with transactional caches the events are raised on commit. > Also, my application used to work with an interceptor rather than an event listener, so I actually found the problem when I saw my interceptor being occasionally executed 3 times with 2 nodes. > I'm not sure whether the command and the chain of interceptor is really meant to be executed twice on the local node, but the consequent behaviour on the events sounds like a bug. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3336) Extended Statistics check list

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3336?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3336: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > Extended Statistics check list > ------------------------------ > > Key: ISPN-3336 > URL: https://issues.jboss.org/browse/ISPN-3336 > Project: Infinispan > Issue Type: Task > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 6.1.0.Final > > > * add documentation > * check for duplicate stats; > * check for not exposed statistics > * try to improve the code (reduce the number of access to the CHM) > * add tests to check if they are exported via JMX correctly > * failing test: OptimisticLockingTxClusterExtendedStatisticLogicTest.testWriteSkewOnNonOwner > * failing test: PessimisticLockingTxClusterExtendedStatisticLogicTest.testDeadlockOnNonOwnerWithRemoteTx -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3624) Rewrite documentation on load testing Infinispan Servers

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3624?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3624: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > Rewrite documentation on load testing Infinispan Servers > -------------------------------------------------------- > > Key: ISPN-3624 > URL: https://issues.jboss.org/browse/ISPN-3624 > Project: Infinispan > Issue Type: Task > Components: Documentation > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 6.1.0.Final > > > The current documentation in http://infinispan.org/docs/6.0.x/user_guide/user_guide.html#sid-68355066 is outdated. -- 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

11 years, 2 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 Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3707?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3707: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > 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 > Affects Versions: 6.0.0.CR1 > Reporter: Pra remo > Assignee: Mircea Markus > Labels: jboss > Fix For: 6.1.0.Final > > > 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 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2324) Add user documentation for NSBT

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2324?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2324: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > Add user documentation for NSBT > -------------------------------- > > Key: ISPN-2324 > URL: https://issues.jboss.org/browse/ISPN-2324 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 5.2.0.Alpha3 > Reporter: Mircea Markus > Assignee: Dan Berindei > Labels: documentation > Fix For: 6.1.0.Final > > > To be linked from the user guide page:https://docs.jboss.org/author/display/ISPN/User+Guide -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3608) HotRod client cannot be configured to connect to servers running on IPv6 through hotrod-client.properties

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3608?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3608: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > HotRod client cannot be configured to connect to servers running on IPv6 through hotrod-client.properties > --------------------------------------------------------------------------------------------------------- > > Key: ISPN-3608 > URL: https://issues.jboss.org/browse/ISPN-3608 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.CR1 > Reporter: Martin Gencur > Assignee: Galder Zamarreño > Priority: Critical > Labels: 620 > Fix For: 6.1.0.Final > > > HotRod client's RemoteCacheManager still has a constructor that internally reads hotrod-client.properties (public RemoteCacheManager(boolean start)) and this constructor is not deprecated. > This call leads to parsing "server_list" property by ConfigurationBuilder.addServers(String servers)). > However, IPv6 addresses usually contain colons and so this parsing fails (enable to differentiate the host and port as these are separated by colon too) -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3422) In non-tx caches, write operations may not be atomic during rebalance

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3422?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3422: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > In non-tx caches, write operations may not be atomic during rebalance > --------------------------------------------------------------------- > > Key: ISPN-3422 > URL: https://issues.jboss.org/browse/ISPN-3422 > Project: Infinispan > Issue Type: Bug > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: 620 > Fix For: 6.1.0.Final > > > If the cache topology changes while a write command is running and before it has actually committed the entry to the data container, we retry the command (see ISPN-3366 and ISPN-3357). But before we detect the topology change, one or more of the backup owners may have already applied the modification. > Retrying the command re-acquires the key lock on the primary owner (even if the primary owner didn't change). That means another command could have modified the same key in the meantime, but the retried command is going to ignore any changes and is going to return the value before the first attempt. Obviously, the command is not retried if the first attempt is not successful, but scenarios like this are possible: > {code} > thread 1: putIfAbsent(k, v1) -> null > thread 2: putIfAbsent(k, v2) -> null > {code} -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3626) Add tests for JGroups AUTH and ENCRYPT protocols to server

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3626?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3626: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > Add tests for JGroups AUTH and ENCRYPT protocols to server > ---------------------------------------------------------- > > Key: ISPN-3626 > URL: https://issues.jboss.org/browse/ISPN-3626 > Project: Infinispan > Issue Type: Task > Components: Server > Affects Versions: 6.0.0.CR1 > Reporter: Martin Gencur > Assignee: Martin Gencur > Fix For: 6.1.0.Final > > > Usage: > https://community.jboss.org/wiki/JGroupsAUTH > https://community.jboss.org/wiki/JGroupsENCRYPT -- 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

11 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2013