January 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5971) Longer cache name overflows its div in mgmt console

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5971?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5971: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > Longer cache name overflows its div in mgmt console > --------------------------------------------------- > > Key: ISPN-5971 > URL: https://issues.jboss.org/browse/ISPN-5971 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Beta1 > Reporter: Jiří Holuša > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 8.2.0.CR1 > > > Page: Caches -> select cache container > When having cache with a longer name, e.g. replicatedCacheForStatisticsTesting, it overflows its tab. The tabs are probably fixed size. This might be an issue which requires more discussion what is correct solution, if increase the fixed size or make it flexible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5894) Move near cache demo from source to a separate repo

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5894?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5894: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > Move near cache demo from source to a separate repo > --------------------------------------------------- > > Key: ISPN-5894 > URL: https://issues.jboss.org/browse/ISPN-5894 > Project: Infinispan > Issue Type: Task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.2.0.CR1 > > > Move near cache demo from source to a separate repo. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5929) InfinispanQueryIT.testQueryOnFirstNode random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5929?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5929: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > InfinispanQueryIT.testQueryOnFirstNode random failures > ------------------------------------------------------ > > Key: ISPN-5929 > URL: https://issues.jboss.org/browse/ISPN-5929 > Project: Infinispan > Issue Type: Bug > Components: Integration , Test Suite - Query > Affects Versions: 8.1.0.Alpha2 > Reporter: Dan Berindei > Assignee: Adrian Nistor > Priority: Blocker > Fix For: 8.2.0.CR1 > > > {{InfinispanQueryIT.testQueryOnFirstNode()}} and {{InfinispanQueryIT.testQueryOnSecondNode()}} fail randomly in CI with this assertion: > {noformat} > java.lang.AssertionError: expected:<3> but was:<2> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.infinispan.test.integration.as.query.InfinispanQueryIT.testQueryOnFirstNode(InfinispanQueryIT.java:99) > {noformat} > Example: http://ci.infinispan.org/viewLog.html?buildId=31810&tab=buildResultsDiv&b... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5892) XML configuration should include number of segments for replicated caches

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5892?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5892: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > XML configuration should include number of segments for replicated caches > ------------------------------------------------------------------------- > > Key: ISPN-5892 > URL: https://issues.jboss.org/browse/ISPN-5892 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 8.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.CR1 > > > The primary owner of a key is determined based on the segment, so for remote caches it's good to increase the number of segments when there are many nodes in the cluster. Groups configuration may be useful as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5793) Expose massindexer status and progress over mbean/dmr

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5793?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5793: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > Expose massindexer status and progress over mbean/dmr > ----------------------------------------------------- > > Key: ISPN-5793 > URL: https://issues.jboss.org/browse/ISPN-5793 > Project: Infinispan > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > Fix For: 8.2.0.CR1 > > > It would be useful for the console/cli to expose the ongoing status/progress of any indexing happening on a cache. This would need to happen both on the massIndexer Mbean and on the server dmr > https://rawgit.com/infinispan/infinispan-console-mockup/master/cache-cont... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5853) Add Hawkular subsytem to server distribution

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5853?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5853: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > Add Hawkular subsytem to server distribution > -------------------------------------------- > > Key: ISPN-5853 > URL: https://issues.jboss.org/browse/ISPN-5853 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.2.0.CR1 > > > https://github.com/hawkular/hawkular-agent/blob/master/hawkular-wildfly-a... > <storage-adapter type="HAWKULAR" username="jdoe" password="password" url="http://${jboss.bind.address:127.0.0.1}:${jboss.http.port:8080}" /> > Use bindings. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5862) Add version number to deprecated comments

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5862?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5862: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > Add version number to deprecated comments > ----------------------------------------- > > Key: ISPN-5862 > URL: https://issues.jboss.org/browse/ISPN-5862 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Affects Versions: 8.1.0.Alpha1 > Reporter: Dan Berindei > Fix For: 8.2.0.CR1 > > > It should be possible to remove deprecated classes and methods after one major version cycle, but it's not always obvious when the API was deprecated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5849) AutoCloseable return from adding listeners can be clunky to use

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5849?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5849: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > AutoCloseable return from adding listeners can be clunky to use > --------------------------------------------------------------- > > Key: ISPN-5849 > URL: https://issues.jboss.org/browse/ISPN-5849 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.2.0.CR1 > > > On one side, to use it as a try-with-resource, you need to declare it right in the {{try()}}; > {code} > try(AutoCloseable handler = writeOnlyMap.listeners().onWrite(written -> > System.out.printf("Written (via onWrite): %s%n", written.get()))) { > Map<String, String> entries = new HashMap<>(); > entries.put("key1", "value1"); > entries.put("key2", "value2"); > writeOnlyMap.evalMany(entries, (v, writeView) -> writeView.set(v)) > .get(); // Wait for completable future > } > {code} > So it's usability is mostly designed for unit tests since listeners tend to be set and removed at a later stage. IOW, listeners are not generally a short-lived object. > The other aspect that is clunky to use is the fact that AutoCloseable's close() throws Exception, which again makes it ackward to use for example if lambdas. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5806) Add transaction support for Functional API

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5806?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5806: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > Add transaction support for Functional API > ------------------------------------------ > > Key: ISPN-5806 > URL: https://issues.jboss.org/browse/ISPN-5806 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.2.0.CR1 > > > A local cache with batching enabled produces this: > {code:java} > java.lang.IllegalArgumentException: Cannot create a transactional > context without a valid Transaction instance. > at org.infinispan.context.TransactionalInvocationContextFactory.createInvocationContext(TransactionalInvocationContextFactory.java:69) > at org.infinispan.context.TransactionalInvocationContextFactory.createInvocationContext(TransactionalInvocationContextFactory.java:63) > at org.infinispan.functional.impl.ReadWriteMapImpl.eval(ReadWriteMapImpl.java:56) > at org.infinispan.lucene.impl.FileListOperations.addFileName(FileListOperations.java:60) > (<-- experimental uncommitted code here) > {code} > For single operations that carry no transaction context, don't try to start a transaction and create a transactional context. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5757) Clustered statistics for transactions

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5757?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5757: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > Clustered statistics for transactions > ------------------------------------- > > Key: ISPN-5757 > URL: https://issues.jboss.org/browse/ISPN-5757 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management, Transactions > Affects Versions: 8.0.1.Final > Reporter: Tristan Tarrant > Assignee: Vladimir Blagojevic > Fix For: 8.2.0.CR1 > > > We want to return clustered statistics for transactions commits, rollbacks and prepares. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2016