April 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3843) Remove broadcast/unicast optimization in JGroupsTransport

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3843?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3843: -------------------------------- Fix Version/s: 7.0.0.Alpha4 (was: 7.0.0.Alpha3) > Remove broadcast/unicast optimization in JGroupsTransport > --------------------------------------------------------- > > Key: ISPN-3843 > URL: https://issues.jboss.org/browse/ISPN-3843 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 7.0.0.Alpha4 > > > The broadcast/unicast optimization in JGroupsTransport can break the message ordering for regular messages, because NAKACK[2] and UNICAST[2|3] have their own ordering. > We should test if this optimization really brings any performance benefits and eliminate it, at least for asynchronous commands. -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-3851) Write tests for REST server using timeToLiveSeconds=0

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3851?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3851: -------------------------------- Fix Version/s: 7.0.0.Alpha4 (was: 7.0.0.Alpha3) > Write tests for REST server using timeToLiveSeconds=0 > ----------------------------------------------------- > > Key: ISPN-3851 > URL: https://issues.jboss.org/browse/ISPN-3851 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Fix For: 7.0.0.Alpha4, 7.0.0.Final > > > ISPN-3786 fixed an issue with timeToLiveSeconds=0 being treated inconsistently, but more tests are needed. -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-3840) Test suite should continue when a test hasn't closed its cache managers

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3840?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3840: -------------------------------- Fix Version/s: 7.0.0.Alpha4 (was: 7.0.0.Alpha3) > Test suite should continue when a test hasn't closed its cache managers > ----------------------------------------------------------------------- > > Key: ISPN-3840 > URL: https://issues.jboss.org/browse/ISPN-3840 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Core > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 7.0.0.Alpha4 > > > The test listener has access to the cache managers that are still open, so it could fail the test and still close the cache managers. > Especially now that the server tests are back into the main project, the server tests should run even if a test in another module failed to close its cache managers. -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-3984) CompatModeDistributedTwoNodesMapReduceTest.testInvokeMapReduceOnAllKeys random failures

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3984?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3984: -------------------------------- Fix Version/s: 7.0.0.Alpha4 (was: 7.0.0.Alpha3) > CompatModeDistributedTwoNodesMapReduceTest.testInvokeMapReduceOnAllKeys random failures > --------------------------------------------------------------------------------------- > > Key: ISPN-3984 > URL: https://issues.jboss.org/browse/ISPN-3984 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Vladimir Blagojevic > Labels: testsuite_stability > Fix For: 7.0.0.Alpha4 > > Attachments: cmdtnmrt.log.gz > > > The random failures in CompatModeDistributedTwoNodesMapReduceTest.testInvokeMapReduceOnAllKeys seem to be caused by state transfer being disabled in the test's caches. > {noformat} > 12:11:51,674 ERROR (testng-CompatModeDistributedTwoNodesMapReduceTest:) [UnitTestTestNGListener] Test testInvokeMapReduceOnAllKeys(org.infinispan.distexec.mapreduce.CompatModeDistributedTwoNodesMapReduceTest) failed. > java.lang.AssertionError: key 'well' does not have count 1 but 2 > at org.junit.Assert.fail(Assert.java:93) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.infinispan.distexec.mapreduce.BaseWordCountMapReduceTest.verifyResults(BaseWordCountMapReduceTest.java:224) > at org.infinispan.distexec.mapreduce.BaseWordCountMapReduceTest.verifyResults(BaseWordCountMapReduceTest.java:334) > at org.infinispan.distexec.mapreduce.BaseWordCountMapReduceTest.testInvokeMapReduceOnAllKeys(BaseWordCountMapReduceTest.java:162) > {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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3988) AsyncStoreTest.testPutClearPut fails randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3988?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3988: -------------------------------- Fix Version/s: 7.0.0.Alpha4 (was: 7.0.0.Alpha3) > AsyncStoreTest.testPutClearPut fails randomly > --------------------------------------------- > > Key: ISPN-3988 > URL: https://issues.jboss.org/browse/ISPN-3988 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 6.0.1.Final > Reporter: Pedro Ruivo > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 7.0.0.Alpha4, 7.0.0.Final > > > org.infinispan.persistence.support.AsyncStoreTest.testPutClearPut > http://ci.infinispan.org/viewLog.html?buildId=5946&tab=buildResultsDiv&bu... -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-3983) Remove some performance bottlenecks from ProtoStream

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3983?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3983: -------------------------------- Fix Version/s: 7.0.0.Alpha4 (was: 7.0.0.Alpha3) > Remove some performance bottlenecks from ProtoStream > ---------------------------------------------------- > > Key: ISPN-3983 > URL: https://issues.jboss.org/browse/ISPN-3983 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: 6.3remotequeries, 630 > Fix For: 7.0.0.Alpha4, 7.0.0.Final > > > Profiling has shown that there are many HashMaps created in MessageContext to help field lookup by name. > Normally this is a static piece of information that should be computed only once when a marshaller is registered and then it should become immutable and be reused. -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-3908) Security (Authentication, Authorization, Encryption)

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3908?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3908: -------------------------------- Fix Version/s: 7.0.0.Alpha4 (was: 7.0.0.Alpha3) > Security (Authentication, Authorization, Encryption) > ---------------------------------------------------- > > Key: ISPN-3908 > URL: https://issues.jboss.org/browse/ISPN-3908 > Project: Infinispan > Issue Type: Task > Components: Core, Remote Protocols, Security, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Critical > Labels: roadmap > Fix For: 7.0.0.Alpha4, 7.0.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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3941) Add pre-release stable version check for maven dependencies

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3941?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3941: -------------------------------- Fix Version/s: 7.0.0.Alpha4 (was: 7.0.0.Alpha3) > Add pre-release stable version check for maven dependencies > ----------------------------------------------------------- > > Key: ISPN-3941 > URL: https://issues.jboss.org/browse/ISPN-3941 > Project: Infinispan > Issue Type: Enhancement > Components: Build process > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Alpha4 > > > We need to enhance our maven build to perform the following dependecy checks before doing a release: > 1. no SNAPSHOT dependencies are used > 2. all dependencies are Final if the current build is a Final > Rule #2 might not be implementable for some external dependencies (some organizations use weird version schemes), so we might want to do this check only for org.jboss, org.infinispan artifact groups. -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-3907) Define a Protobuf custom option for defining numeric IDs for types

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3907?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3907: -------------------------------- Fix Version/s: 7.0.0.Alpha4 (was: 7.0.0.Alpha3) > Define a Protobuf custom option for defining numeric IDs for types > ------------------------------------------------------------------ > > Key: ISPN-3907 > URL: https://issues.jboss.org/browse/ISPN-3907 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Alpha4, 7.0.0.Final > > > Currently the wire format of all Protobuf encoded keys and values contains a header/envelope that has some metadata information, like the fully qualified type name (that is protobuf type name, not java) of the object encoded in the message. This information is needed so that the other end can decode the message. And we added it because the Protobuf spec assumes both ends are aware of the message type, which is not the case most of the time. > While this approach solves the problem nicely, it becomes very inefficient is the FQN is long, which is usually the case, as people tend to stick the domain name of their company + package app name into it. > Solution: provide alternative unique numeric IDs to all types. The IDs can be added to message type definitions in the protobuf schema and the user is in charge of guaranteeing their uniqueness while the system must check and enforce the uniqueness when a schema is registered ib the ProtobufMetadataManager. To do this we define a custom Protobuf Message type option that accepts a numeric value. If such a numeric ID was assigned to the type then when it is serialized in protobuf the system has to use this id in the header rather that the FQN string. > This option should not be mandatory. Existing apps should work without requiring source code changes or recompiling providing that the relevant jars are upgraded in both client and server to support the new header encoding. -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-3989) L1StateTransferRemovesValueTest.testStateTransferWithL1InvalidationAboutToBeCommitted fails randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3989?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3989: -------------------------------- Fix Version/s: 7.0.0.Alpha4 (was: 7.0.0.Alpha3) > L1StateTransferRemovesValueTest.testStateTransferWithL1InvalidationAboutToBeCommitted fails randomly > ---------------------------------------------------------------------------------------------------- > > Key: ISPN-3989 > URL: https://issues.jboss.org/browse/ISPN-3989 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 6.0.1.Final > Reporter: Pedro Ruivo > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 7.0.0.Alpha4, 7.0.0.Final > > > org.infinispan.distribution.rehash.L1StateTransferRemovesValueTest.testStateTransferWithL1InvalidationAboutToBeCommitted > http://ci.infinispan.org/viewLog.html?buildId=5946&tab=buildResultsDiv&bu... -- 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2014