January 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2624) JDG: Storage-only example: HotRodDecoder: NSEE: key not found: node1/clustered

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2624?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2624: ----------------------------------------------- Tomas Sykora <tsykora(a)redhat.com> changed the Status of [bug 875151|https://bugzilla.redhat.com/show_bug.cgi?id=875151] from ON_QA to VERIFIED > JDG: Storage-only example: HotRodDecoder: NSEE: key not found: node1/clustered > ------------------------------------------------------------------------------ > > Key: ISPN-2624 > URL: https://issues.jboss.org/browse/ISPN-2624 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Reporter: Tomas Sykora > Assignee: Galder Zamarreño > Fix For: 5.2.0.CR1 > > Attachments: standalone-ha.xml, standalone-storage-only.xml, storageOnlyTraceMainNode.txt, storageOnlyTraceStorageOnlyNode.txt > > > This is issue to distinguish from https://issues.jboss.org/browse/ISPN-2550. > For logs and more info see related BZ: https://bugzilla.redhat.com/show_bug.cgi?id=875151 > This issue was found during running JDG functional test suite for configuration examples provided with JDG. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2159) startServer.sh should provide an option to start a node without a server endpoint

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2159?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2159: ---------------------------------- Labels: (was: jdg jdg6) > startServer.sh should provide an option to start a node without a server endpoint > --------------------------------------------------------------------------------- > > Key: ISPN-2159 > URL: https://issues.jboss.org/browse/ISPN-2159 > Project: Infinispan > Issue Type: Enhancement > Components: Remote protocols > Affects Versions: 5.2.0.ALPHA1 > Reporter: Jeffrey Jia > Assignee: Galder Zamarreño > Priority: Minor > Fix For: 6.0.0.Final > > Attachments: 0001-add-node-server-entry-point.patch > > > Sometimes we will start infinispan as a storage node, not binding any IP or Port for client communications (only p2p communications) -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2551) HotRod Client testsuite leaves many dangling threads

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2551?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2551: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done This was actually integrated a while ago > HotRod Client testsuite leaves many dangling threads > ---------------------------------------------------- > > Key: ISPN-2551 > URL: https://issues.jboss.org/browse/ISPN-2551 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols, Test Suite > Affects Versions: 5.2.0.Beta4 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Labels: testsuite_stability > Fix For: 5.2.0.Final > > > Some of the HotRod client tests don't kill some of the RemoteCacheManagers and/or HotRodServers they create -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2657) Support for LevelDB CacheStore

by Ray Tsang (JIRA)

[ https://issues.jboss.org/browse/ISPN-2657?page=com.atlassian.jira.plugin.... ] Ray Tsang commented on ISPN-2657: --------------------------------- Mircea, I'm looking at the Java implementation: https://github.com/dain/leveldb, and the JNI implementation: https://github.com/fusesource/leveldbjni It's possible to iterate through all of the entries in leveldb. I've put together something for fun. I wonder if it's worth having yet another store though. > Support for LevelDB CacheStore > ------------------------------ > > Key: ISPN-2657 > URL: https://issues.jboss.org/browse/ISPN-2657 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Ray Tsang > Assignee: Mircea Markus > Fix For: 7.0.0.Final > > > Support for LevelDB, a fast key-value persistence storage. > There is a pure java implementation and a jni by fuse -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2632) Uneven request balancing after node crash

by Michal Linhard (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] Michal Linhard commented on ISPN-2632: -------------------------------------- The behaviour is the same with protocol version 1.1 http://www.qa.jboss.com/~mlinhard/hyperion3/run0027/report/stats-throughp... > Uneven request balancing after node crash > ----------------------------------------- > > Key: ISPN-2632 > URL: https://issues.jboss.org/browse/ISPN-2632 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.CR1 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 5.2.0.CR2, 5.2.0.Final > > > This is a new manifestation of ISPN-1995, but in this case this happens after killing only one node: the hot rod requests aren't very well balanced. > these runs still manifest also ISPN-2550 and it may be cause of this bug. > The uneven balancing of requests can be seen here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2632) Uneven request balancing after node crash

by Michal Linhard (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] Michal Linhard commented on ISPN-2632: -------------------------------------- in this test there were 50 driver threads distributed over 11 driver nodes, RCM per thread > Uneven request balancing after node crash > ----------------------------------------- > > Key: ISPN-2632 > URL: https://issues.jboss.org/browse/ISPN-2632 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.CR1 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 5.2.0.CR2, 5.2.0.Final > > > This is a new manifestation of ISPN-1995, but in this case this happens after killing only one node: the hot rod requests aren't very well balanced. > these runs still manifest also ISPN-2550 and it may be cause of this bug. > The uneven balancing of requests can be seen here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2632) Uneven request balancing after node crash

by Michal Linhard (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] Michal Linhard commented on ISPN-2632: -------------------------------------- for server logs see: report/serverlogs.zip > Uneven request balancing after node crash > ----------------------------------------- > > Key: ISPN-2632 > URL: https://issues.jboss.org/browse/ISPN-2632 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.CR1 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 5.2.0.CR2, 5.2.0.Final > > > This is a new manifestation of ISPN-1995, but in this case this happens after killing only one node: the hot rod requests aren't very well balanced. > these runs still manifest also ISPN-2550 and it may be cause of this bug. > The uneven balancing of requests can be seen here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2704) AsyncStoreTest.testRestrictionOnAddingToAsyncQueue still fails randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2704?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2704: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > AsyncStoreTest.testRestrictionOnAddingToAsyncQueue still fails randomly > ----------------------------------------------------------------------- > > Key: ISPN-2704 > URL: https://issues.jboss.org/browse/ISPN-2704 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 5.2.0.CR2 > > > {code}testRestrictionOnAddingToAsyncQueue(org.infinispan.loaders.decorators.AsyncStoreTest) Time elapsed: 0.05 sec <<< FAILURE! > org.infinispan.CacheException: AsyncStore stopped; no longer accepting more entries. > at org.infinispan.loaders.decorators.AsyncStore$State.put(AsyncStore.java:401) > at org.infinispan.loaders.decorators.AsyncStore.put(AsyncStore.java:140) > at org.infinispan.loaders.decorators.AsyncStore.remove(AsyncStore.java:243) > at org.infinispan.loaders.decorators.AsyncStoreTest.doTestRemove(AsyncStoreTest.java:421) > at org.infinispan.loaders.decorators.AsyncStoreTest.testRestrictionOnAddingToAsyncQueue(AsyncStoreTest.java:147) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:46) > at org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:37) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:680){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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2300) Versioned Transactional Cache issues

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2300?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-2300: ------------------------------------- {quote}In the current code base, when a versioned entry fails to update due to conditional operation not fulfilling the condition, the previous value entry is added to the context with isChanged=true (if present in the cache, as a result of marking RepeatableReadEntry.copyForUpdate), and then EntryWrappingInterceptor loops through all the entries in the context, and if "changed", it will try commit them.{quote} A better fix would be for the previous value to have its isChanged flag set to false rather than true. The flag being set to true is incorrect, as the entry is not actually changed and might cause problems in other scenarios as well. The value of the flag can be set in the conditional command perform() method. > Versioned Transactional Cache issues > ------------------------------------ > > Key: ISPN-2300 > URL: https://issues.jboss.org/browse/ISPN-2300 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 5.2.0.Alpha3 > Reporter: Pedro Ruivo > Assignee: Galder Zamarreño > Priority: Critical > Labels: Commands, Conditional, Transactions, Version > Fix For: 5.2.0.CR2, 5.2.0.Final > > > Description from http://lists.jboss.org/pipermail/infinispan-dev/2012-September/011205.html > 1) testPutIfAbsent, testRemoveIfPresent, testReplaceWithOldVal (methods > the test cases) > In this tests, it was updating the cache entry with a null version. This > originates later a IllegalStateException when it tries to perform the > write skew check and the version is null. > I have fixed this problem in this way: if the command fails (PutCommand, > RemoveCommand, ReplaceCommand), I unset the flag CHANGED in the > MvccEntry to avoid to update the entry in the DataContainer. > 2) testClear in distributed mode > I have no clear idea how to solve this problem but it looks like the > PrepareCommand (with the ClearCommand) is not sent to all the nodes in > the cluster. Then, when I do a get, a remote get is performed and the > key is still there. I think that it is not the desired behavior. > 3) testRemoveUnexistingEntry > In this test, it tries to remove a key that does not exists but it does > not success due to a NullPointerException. I have looked deeper and I > check that the transaction's lookup entries map has an entry with [key > => null] and when it tries to perform the write skew check in that key, > a NullPointerException is thrown in here [2] (line 80, WriteSkewHelper) > [1] https://github.com/pruivo/infinispan/tree/t_replace_fix > [2] https://github.com/pruivo/infinispan/blob/t_replace_fix/core/src/main/jav... -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2700) Solve the scala compilation warnings after upgrading to scala 2.10.0

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2700?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2700: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Solve the scala compilation warnings after upgrading to scala 2.10.0 > -------------------------------------------------------------------- > > Key: ISPN-2700 > URL: https://issues.jboss.org/browse/ISPN-2700 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Affects Versions: 5.2.0.CR1 > Reporter: Mircea Markus > Assignee: Galder Zamarreño > Fix For: 5.2.0.Final > > > {code}[WARNING] /Users/g/Go/test/infinispan.git/server/core/src/main/scala/org/infinispan/server/core/AbstractProtocolDecoder.scala:176: warning: non-variable type argument org.jboss.netty.buffer.ChannelBuffer in type pattern List[org.jboss.netty.buffer.ChannelBuffer] is unchecked since it is eliminated by erasure > [INFO] case l: List[ChannelBuffer] => l.foreach(ch.write(_)) > [INFO]{code} > {code}[WARNING] /Users/g/Go/test/infinispan.git/server/hotrod/src/test/scala/org/infinispan/server/hotrod/HotRodStatsTest.scala:48: warning: Option[String] and Int are unrelated: they will most likely always compare unequal > [INFO] assertTrue(s.get("timeSinceStart") != 0) > [INFO] ^ > [WARNING] /Users/g/Go/test/infinispan.git/server/hotrod/src/test/scala/org/infinispan/server/hotrod/HotRodStatsTest.scala:69: warning: Option[String] and Int are unrelated: they will most likely always compare unequal > [INFO] assertTrue(s.get("totalBytesRead") != 0) > [INFO] ^ > [WARNING] /Users/g/Go/test/infinispan.git/server/hotrod/src/test/scala/org/infinispan/server/hotrod/HotRodStatsTest.scala:70: warning: Option[String] and Int are unrelated: they will most likely always compare unequal > [INFO] assertTrue(s.get("totalBytesWritten") != 0) > [INFO] {code} > {code}[WARNING] /Users/g/Go/test/infinispan.git/server/memcached/src/test/scala/org/infinispan/server/memcached/test/MemcachedTestingUtil.scala:92: warning: a pure expression does nothing in statement position; you may be omitting necessary parentheses > [INFO] null > [INFO] {code} > {code}[WARNING] /Users/g/Go/test/infinispan.git/server/rest/src/main/scala/org/infinispan/rest/Server.scala:88: warning: unreachable code > [INFO] case _ => throw new Exception > [INFO] {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

13 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 2013