January 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2694) Fix Spring build caused by HotRod Client changes

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2694?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2694: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Fix Spring build caused by HotRod Client changes > ------------------------------------------------ > > Key: ISPN-2694 > URL: https://issues.jboss.org/browse/ISPN-2694 > Project: Infinispan > Issue Type: Bug > Components: Spring integration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Blocker > Fix For: 5.2.0.CR1 > > -- 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, 11 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2696?page=com.atlassian.jira.plugin.... ] Work on ISPN-2696 started by Galder Zamarreño. > 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, 11 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2542?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2542: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/1562 > AsyncStoreTest.testRestrictionOnAddingToAsyncQueue fails randomly > ----------------------------------------------------------------- > > Key: ISPN-2542 > URL: https://issues.jboss.org/browse/ISPN-2542 > 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.Final > > Attachments: testRestrictionOnAddingToAsyncQueue-2.log.zip > > > {code}testRestrictionOnAddingToAsyncQueue(org.infinispan.loaders.decorators.AsyncStoreTest): > Method org.testng.internal.TestNGMethod.testRestrictionOnAddingToAsyncQueue() didn't finish within the time-out 10000{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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2698) Some in-progress segment transfers are not cancelled properly during rehashing

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2698?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2698: -------------------------------- Description: If segments are re-assigned to another node due to rehashing and these segments happen to be in-progress on current node then these transfers should be cancelled. This is handled in method StateConsumerImpl.cancelTransfers(..). The code contains an error: the currently iterated segment is not included into the cancelled set and this means it does not get cancelled, possibly causing the rehashing to never complete. was: If segments are re-assigned to another node due to rehashing and these segments happen to be in-progress on current node then these transfers should be cancelled. This is handled in method StateConsumerImpl.cancelTransfers(..). The code contains an error: the currently iterated segment is not included into the cancelled set. > Some in-progress segment transfers are not cancelled properly during rehashing > ------------------------------------------------------------------------------ > > Key: ISPN-2698 > URL: https://issues.jboss.org/browse/ISPN-2698 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.ALPHA1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 5.2.0.CR1 > > > If segments are re-assigned to another node due to rehashing and these segments happen to be in-progress on current node then these transfers should be cancelled. This is handled in method StateConsumerImpl.cancelTransfers(..). > The code contains an error: the currently iterated segment is not included into the cancelled set and this means it does not get cancelled, possibly causing the rehashing to never complete. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2698) Some in-progress segment transfers are not cancelled properly during rehashing

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2698?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2698: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1555 > Some in-progress segment transfers are not cancelled properly during rehashing > ------------------------------------------------------------------------------ > > Key: ISPN-2698 > URL: https://issues.jboss.org/browse/ISPN-2698 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.ALPHA1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 5.2.0.CR1 > > > If segments are re-assigned to another node due to rehashing and these segments happen to be in-progress on current node then these transfers should be cancelled. This is handled in method StateConsumerImpl.cancelTransfers(..). > The code contains an error: the currently iterated segment is not included into the cancelled set. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2698) Some in-progress segment transfers are not cancelled properly during rehashing

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-2698: ----------------------------------- Summary: Some in-progress segment transfers are not cancelled properly during rehashing Key: ISPN-2698 URL: https://issues.jboss.org/browse/ISPN-2698 Project: Infinispan Issue Type: Bug Components: State transfer Affects Versions: 5.2.0.ALPHA1 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 5.2.0.CR1 If segments are re-assigned to another node due to rehashing and these segments happen to be in-progress on current node then these transfers should be cancelled. This is handled in method StateConsumerImpl.cancelTransfers(..). The code contains an error: the currently iterated segment is not included into the cancelled set. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2535) AsyncStoreTest fails every time (with TRACE logs enabled)

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2535?page=com.atlassian.jira.plugin.... ] Galder Zamarreño resolved ISPN-2535. ------------------------------------ Labels: testsuite_stability (was: ) Fix Version/s: (was: 6.0.0.Final) Resolution: Duplicate Issue > AsyncStoreTest fails every time (with TRACE logs enabled) > --------------------------------------------------------- > > Key: ISPN-2535 > URL: https://issues.jboss.org/browse/ISPN-2535 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.0.Beta4 > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Labels: testsuite_stability > Attachments: ast.log.gz > > > I have TRACE enabled for org.infinispan (except for org.infinispan.marshall) and AsyncStoreTest fails for me every time with this stack trace: > {noformat} > 11:56:27,576 ERROR (testng-AsyncStoreTest:) [UnitTestTestNGListener] Test testRestrictionOnAddingToAsyncQueue(org.infinispan.loaders.decorators.AsyncStoreTest) failed. > org.testng.internal.thread.ThreadTimeoutException: Method org.testng.internal.TestNGMethod.testRestrictionOnAddingToAsyncQueue() didn't finish within the time-out 10000 > at java.lang.Throwable.getStackTraceElement(Native Method) > at java.lang.Throwable.getOurStackTrace(Throwable.java:826) > at java.lang.Throwable.printStackTrace(Throwable.java:655) > at java.lang.Throwable.printStackTrace(Throwable.java:720) > at org.apache.log4j.DefaultThrowableRenderer.render(DefaultThrowableRenderer.java:60) > at org.apache.log4j.spi.ThrowableInformation.getThrowableStrRep(ThrowableInformation.java:87) > at org.apache.log4j.pattern.ThrowableInformationPatternConverter.format(ThrowableInformationPatternConverter.java:84) > at org.apache.log4j.pattern.BridgePatternConverter.format(BridgePatternConverter.java:119) > at org.apache.log4j.EnhancedPatternLayout.format(EnhancedPatternLayout.java:546) > at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:310) > at org.apache.log4j.WriterAppender.append(WriterAppender.java:162) > at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251) > at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66) > at org.apache.log4j.Category.callAppenders(Category.java:206) > at org.apache.log4j.Category.forcedLog(Category.java:391) > at org.apache.log4j.Category.log(Category.java:856) > at org.jboss.logging.Log4jLogger.doLogf(Log4jLogger.java:53) > at org.jboss.logging.Logger.logf(Logger.java:2143) > at org.infinispan.util.logging.Log_$logger.interruptedWaitingAsyncStorePush(Log_$logger.java:246) > at org.infinispan.loaders.decorators.AsyncStore.stop(AsyncStore.java:326) > at org.infinispan.loaders.decorators.AsyncStoreTest.testRestrictionOnAddingToAsyncQueue(AsyncStoreTest.java:136) > 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.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:46) > at org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:37) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > 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) > {noformat} -- 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, 11 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2542?page=com.atlassian.jira.plugin.... ] Work on ISPN-2542 started by Galder Zamarreño. > AsyncStoreTest.testRestrictionOnAddingToAsyncQueue fails randomly > ----------------------------------------------------------------- > > Key: ISPN-2542 > URL: https://issues.jboss.org/browse/ISPN-2542 > 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.Final > > Attachments: testRestrictionOnAddingToAsyncQueue-2.log.zip > > > {code}testRestrictionOnAddingToAsyncQueue(org.infinispan.loaders.decorators.AsyncStoreTest): > Method org.testng.internal.TestNGMethod.testRestrictionOnAddingToAsyncQueue() didn't finish within the time-out 10000{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, 11 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2542?page=com.atlassian.jira.plugin.... ] Galder Zamarreño reassigned ISPN-2542: -------------------------------------- Assignee: Galder Zamarreño (was: Mircea Markus) > AsyncStoreTest.testRestrictionOnAddingToAsyncQueue fails randomly > ----------------------------------------------------------------- > > Key: ISPN-2542 > URL: https://issues.jboss.org/browse/ISPN-2542 > 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.Final > > Attachments: testRestrictionOnAddingToAsyncQueue-2.log.zip > > > {code}testRestrictionOnAddingToAsyncQueue(org.infinispan.loaders.decorators.AsyncStoreTest): > Method org.testng.internal.TestNGMethod.testRestrictionOnAddingToAsyncQueue() didn't finish within the time-out 10000{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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2693) ByteArrayKey should print out its hashCode

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-2693?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-2693: ------------------------------ Affects Version/s: 5.2.0.Beta6 > ByteArrayKey should print out its hashCode > ------------------------------------------ > > Key: ISPN-2693 > URL: https://issues.jboss.org/browse/ISPN-2693 > Project: Infinispan > Issue Type: Bug > Components: Marshalling > Affects Versions: 5.2.0.Beta6 > Reporter: Radim Vansa > Assignee: Galder Zamarreño > Priority: Minor > > When a ByteArrayKey is printed out, the format is {{ByteArrayKey{data=ByteArray{size=..., hashCode=..., array=...}}}} > However, ByteArray computes hashCode using array.hashCode() instead of Arrays.hashCode(array) and, therefore, two equal ByteArrayKeys have different hashCode when printed out. > Another way to fix that could be using Arrays.hashCode(array) in Util.printArray() (although I am not sure whether this could break anything). > As the result is pretty unexpected, I consider this a bug rather than a feature request. -- 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, 11 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