January 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2697) HotRodServer startup fails when its record cannot be inserted into topology cache

by Radim Vansa (JIRA)

Radim Vansa created ISPN-2697: --------------------------------- Summary: HotRodServer startup fails when its record cannot be inserted into topology cache Key: ISPN-2697 URL: https://issues.jboss.org/browse/ISPN-2697 Project: Infinispan Issue Type: Bug Components: Remote protocols Affects Versions: 5.2.0.Beta6 Reporter: Radim Vansa Assignee: Galder Zamarreño When the HotRodServer starts it inserts its record to __hotRodTopologyCache ({{HotRodServer.addSelfToTopologyView(...)}}). However, this put may very easily fail - as the command is broadcasted using NAKACK2 protocol, if the message gets lost and there's no following broadcasted message, the message will be not retransmitted and the put operation times out (Replication timeout), which fails the whole HotRodServer startup, all because of one lost UDP message. -- 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, 4 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2624?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2624: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2658) org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey fails constantly on all environments

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2658?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2658: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/1561 > org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey fails constantly on all environments > ------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-2658 > URL: https://issues.jboss.org/browse/ISPN-2658 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.0.Beta6 > Reporter: Anna Manukyan > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 5.2.0.CR1 > > Attachments: testModificationsOnSameCustomKey-2.log > > > org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey test fails on all environments (RHEL, Windows, Solaris - JDK7, Open JDK7, IBM JDK7). > The error message is: > {code} > Error Message > Serialization count: expected 4 but was 5 > Stacktrace > java.lang.AssertionError: Serialization count: expected 4 but was 5 > at org.infinispan.marshall.MarshalledValueTest.assertSerializationCounts(MarshalledValueTest.java:135) > at org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey(MarshalledValueTest.java:452) > 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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:715) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237) > 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$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) > {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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2696) Upgrade to Scala 2.10

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2696: -------------------------------------- Summary: Upgrade to Scala 2.10 Key: ISPN-2696 URL: https://issues.jboss.org/browse/ISPN-2696 Project: Infinispan Issue Type: Component Upgrade Components: Remote protocols Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.2.0.CR1, 5.2.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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2689) Support storage of indexes of Apache Lucene 4

by James Aley (JIRA)

[ https://issues.jboss.org/browse/ISPN-2689?page=com.atlassian.jira.plugin.... ] James Aley updated ISPN-2689: ----------------------------- Attachment: ISPN-2689-hack-main.diff ISPN-2689-hack-test.diff I've attached a very hacky proof of concept. I basically just forked the module and patched the code to build with Lucene 4, then everything magically worked! So it seems some very trivial changes can in fact make what we have now at least work with Lucene 4.0 - though not in a backwards compatible way. Question now is, what's the best way to make both a Lucene 3 and 4 compatible version (or version) available to users? > Support storage of indexes of Apache Lucene 4 > --------------------------------------------- > > Key: ISPN-2689 > URL: https://issues.jboss.org/browse/ISPN-2689 > Project: Infinispan > Issue Type: Feature Request > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 6.0.0.Beta1, 6.0.0.Final > > Attachments: ISPN-2689-hack-main.diff, ISPN-2689-hack-test.diff > > > The current Lucene Directory supports Lucene version from 2.9 to 3.6, > but Lucene 4 made consistent changes which might need a new 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2689) Support storage of indexes of Apache Lucene 4

by James Aley (JIRA)

[ https://issues.jboss.org/browse/ISPN-2689?page=com.atlassian.jira.plugin.... ] James Aley edited comment on ISPN-2689 at 1/8/13 7:24 AM: ---------------------------------------------------------- I've attached a very hacky proof of concept. I basically just forked the module and patched the code to build with Lucene 4, then everything magically worked! So it seems some very trivial changes can in fact make what we have now at least work with Lucene 4.0 - though not in a backwards compatible way. Question now is, what's the best way to make both a Lucene 3 and 4 compatible version (or versions) available to users? was (Author: jaley): I've attached a very hacky proof of concept. I basically just forked the module and patched the code to build with Lucene 4, then everything magically worked! So it seems some very trivial changes can in fact make what we have now at least work with Lucene 4.0 - though not in a backwards compatible way. Question now is, what's the best way to make both a Lucene 3 and 4 compatible version (or version) available to users? > Support storage of indexes of Apache Lucene 4 > --------------------------------------------- > > Key: ISPN-2689 > URL: https://issues.jboss.org/browse/ISPN-2689 > Project: Infinispan > Issue Type: Feature Request > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 6.0.0.Beta1, 6.0.0.Final > > Attachments: ISPN-2689-hack-main.diff, ISPN-2689-hack-test.diff > > > The current Lucene Directory supports Lucene version from 2.9 to 3.6, > but Lucene 4 made consistent changes which might need a new 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2658) org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey fails constantly on all environments

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2658?page=com.atlassian.jira.plugin.... ] Work on ISPN-2658 started by Galder Zamarreño. > org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey fails constantly on all environments > ------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-2658 > URL: https://issues.jboss.org/browse/ISPN-2658 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.0.Beta6 > Reporter: Anna Manukyan > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 5.2.0.CR1 > > Attachments: testModificationsOnSameCustomKey-2.log > > > org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey test fails on all environments (RHEL, Windows, Solaris - JDK7, Open JDK7, IBM JDK7). > The error message is: > {code} > Error Message > Serialization count: expected 4 but was 5 > Stacktrace > java.lang.AssertionError: Serialization count: expected 4 but was 5 > at org.infinispan.marshall.MarshalledValueTest.assertSerializationCounts(MarshalledValueTest.java:135) > at org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey(MarshalledValueTest.java:452) > 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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:715) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237) > 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$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) > {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, 4 months

1
0
0 / 0

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

by Michal Linhard (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] Michal Linhard commented on ISPN-2632: -------------------------------------- the run http://www.qa.jboss.com/~mlinhard/hyperion3/run0013/report/stats-throughp... that contains this issue, was done with JDG 6.1.0.ER5 patched with dan's fixes for ISPN-2550, see my last comments in ISPN-2550. > Uneven request balancing after node restore > -------------------------------------------- > > Key: ISPN-2632 > URL: https://issues.jboss.org/browse/ISPN-2632 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.Beta5 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Fix For: 5.2.0.CR1 > > > 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

11 years, 4 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-2632: ---------------------------------------- @Michal, is the issue still present once an Infinispan version containing a fix for ISPN-2550 is used? You wanna wait to test CR1 and then we see if the issue is still present? > Uneven request balancing after node restore > -------------------------------------------- > > Key: ISPN-2632 > URL: https://issues.jboss.org/browse/ISPN-2632 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.Beta5 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Fix For: 5.2.0.CR1 > > > 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1220) Add classloader hooks to cache listener events

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-1220?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-1220: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add classloader hooks to cache listener events > ---------------------------------------------- > > Key: ISPN-1220 > URL: https://issues.jboss.org/browse/ISPN-1220 > Project: Infinispan > Issue Type: Enhancement > Components: Listeners > Affects Versions: 5.0.0.CR7 > Reporter: Paul Ferraro > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 5.2.0.CR1, 5.2.0.Final > > > This issue seeks to extend the classloading api changes made in ISPN-1096 to the Event API. Currently, cache listener events do not allow a classloader to be specified to perform any necessary deserialization triggered by the getKey(), getValue() methods. Can the event api be enhanced such that calls to getKey(), getValue() use a specific classloader? -- 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, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2013