[JBoss JIRA] (ISPN-2701) Spring ConfigurationOverridesTest fails
by Dan Berindei (JIRA)
Dan Berindei created ISPN-2701:
----------------------------------
Summary: Spring ConfigurationOverridesTest fails
Key: ISPN-2701
URL: https://issues.jboss.org/browse/ISPN-2701
Project: Infinispan
Issue Type: Bug
Components: Spring integration, Test Suite
Affects Versions: 5.2.0.Beta6
Reporter: Dan Berindei
Assignee: Mircea Markus
Priority: Critical
Fix For: 5.2.0.Final
ConfigurationOverridesTest wasn't running because it was missing the @Test annotation (see ISPN-2534). I added the annotation, but now many of its methods are failing because of configuration changes.
--
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, 12 months
[JBoss JIRA] (ISPN-2700) Solve the scala compilation warnings after upgrading to scala 2.10.0
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-2700?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-2700:
-----------------------------------
Description:
{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}
> 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
11 years, 12 months
[JBoss JIRA] (ISPN-2580) Do not request segments from all nodes at once
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2580?page=com.atlassian.jira.plugin.... ]
Mircea Markus resolved ISPN-2580.
---------------------------------
Resolution: Done
> Do not request segments from all nodes at once
> ----------------------------------------------
>
> Key: ISPN-2580
> URL: https://issues.jboss.org/browse/ISPN-2580
> Project: Infinispan
> Issue Type: Enhancement
> Components: State transfer
> Affects Versions: 5.2.0.Beta5
> Reporter: Radim Vansa
> Assignee: Adrian Nistor
> Priority: Blocker
> Fix For: 5.2.0.CR1
>
>
> When a new node joins large cluster filled with data, it gets the new CH and REBALANCE_START command, and requests data from all nodes at once (or almost all with even distribution of segments). It may be not able to handle this amount of transfers in parallel even at the JGroups level - this results in data sent to the node and discarded at the receiver, sent again and again. With a heavy congestion the node just buffers fragments of a message from one sender and never passes this up.
> The number of StateRequestCommands(START_STATE_TRANSFER) should be limited so that the node is not congested.
--
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, 12 months
[JBoss JIRA] (ISPN-2698) Some in-progress segment transfers are not cancelled properly during rehashing
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2698?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2698:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> 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, 12 months
[JBoss JIRA] (ISPN-2658) org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey fails constantly on all environments
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-2658?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-2658:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Integrated. Thanks!
> 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, 12 months
[JBoss JIRA] (ISPN-2699) Failed ping on startup can leave socket dirty
by Radim Vansa (JIRA)
Radim Vansa created ISPN-2699:
---------------------------------
Summary: Failed ping on startup can leave socket dirty
Key: ISPN-2699
URL: https://issues.jboss.org/browse/ISPN-2699
Project: Infinispan
Issue Type: Bug
Components: Remote protocols
Affects Versions: 5.2.0.Beta6
Reporter: Radim Vansa
Assignee: Galder Zamarreño
Ping on startup in TransportObjectFactory.makeObject does not check the return value of ping operation, neither the tcpTransport.isValid().
Therefore, if a HotRodClientException is thrown when the response header is read from socket, the socket is left in a dirty state.
In our case this resulted in reading response to previous request (the request was written but the response was not read due to some timeout and then, when another request was executed it read the response to the first request). This caused {{ISPN004004: Invalid message id. Expected 2930 and received 212}}
--
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, 12 months