October 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4544) BaseWordCountMapReduceTest#testCombinerForDistributedReductionWithException doesn't actually test reduce exception

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4544?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4544: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.CR2 Resolution: Done > BaseWordCountMapReduceTest#testCombinerForDistributedReductionWithException doesn't actually test reduce exception > ------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-4544 > URL: https://issues.jboss.org/browse/ISPN-4544 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Affects Versions: 7.0.0.Alpha5 > Reporter: William Burns > Assignee: Vladimir Blagojevic > Fix For: 7.0.0.CR2 > > > When looking into serialization issues I found that many map reduce failures occur due to not serializable exceptions. Looking closer it appears this was caused by the testCombinerForDistributedReductionWithException method because the anonymous inner class cannot be serialized and throws a CacheException causing the test to pass. However if I pass in a serializable class the test fails because the Divide By Zero exception is swallowed incorrectly. > {code} > @Test(expectedExceptions = CacheException.class) > public void testCombinerForDistributedReductionWithException() throws Exception { > MapReduceTask<String, String, String, Integer> task = invokeMapReduce(null); > task.combinedWith(new DivideByZeroReducer()); > task.execute(); > } > private static class DivideByZeroReducer implements Reducer<String, Integer>, Serializable { > @Override > public Integer reduce(String reducedKey, Iterator<Integer> iter) { > //simulating exception > int a = 4 / 0; > return null; > } > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4544) BaseWordCountMapReduceTest#testCombinerForDistributedReductionWithException doesn't actually test reduce exception

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4544?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4544: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2750 > BaseWordCountMapReduceTest#testCombinerForDistributedReductionWithException doesn't actually test reduce exception > ------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-4544 > URL: https://issues.jboss.org/browse/ISPN-4544 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Affects Versions: 7.0.0.Alpha5 > Reporter: William Burns > Assignee: Vladimir Blagojevic > > When looking into serialization issues I found that many map reduce failures occur due to not serializable exceptions. Looking closer it appears this was caused by the testCombinerForDistributedReductionWithException method because the anonymous inner class cannot be serialized and throws a CacheException causing the test to pass. However if I pass in a serializable class the test fails because the Divide By Zero exception is swallowed incorrectly. > {code} > @Test(expectedExceptions = CacheException.class) > public void testCombinerForDistributedReductionWithException() throws Exception { > MapReduceTask<String, String, String, Integer> task = invokeMapReduce(null); > task.combinedWith(new DivideByZeroReducer()); > task.execute(); > } > private static class DivideByZeroReducer implements Reducer<String, Integer>, Serializable { > @Override > public Integer reduce(String reducedKey, Iterator<Integer> iter) { > //simulating exception > int a = 4 / 0; > return null; > } > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4685) Lucene Directory Externalizers not used on server deployment

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4685?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4685: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1139652|https://bugzilla.redhat.com/show_bug.cgi?id=1139652] from ON_QA to VERIFIED > Lucene Directory Externalizers not used on server deployment > ------------------------------------------------------------ > > Key: ISPN-4685 > URL: https://issues.jboss.org/browse/ISPN-4685 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 7.0.0.Beta1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 7.0.0.Beta2 > > > Infinispan server module does not import services from lucene directory module, and java serialization is used since all Lucene cache objets (wrongly) implements Serializable -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4807) NPE under high load when using async metadata writes for the Lucene Directory

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4807?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4807: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > NPE under high load when using async metadata writes for the Lucene Directory > ----------------------------------------------------------------------------- > > Key: ISPN-4807 > URL: https://issues.jboss.org/browse/ISPN-4807 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Fix For: 7.0.0.CR2 > > > Method > org.infinispan.lucene.readlocks.DistributedSegmentReadLocker.deleteOrReleaseReadLock(String) > might hit a NPE under high load as the fileMetadata retrieved from the Cache might be null when it's written asynchronously. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4105) Optimize Cluster Listener performance for Replicated Caches

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4105?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4105: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1150501 > Optimize Cluster Listener performance for Replicated Caches > ----------------------------------------------------------- > > Key: ISPN-4105 > URL: https://issues.jboss.org/browse/ISPN-4105 > Project: Infinispan > Issue Type: Enhancement > Components: Listeners > Affects Versions: 7.0.0.Alpha1 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Beta2, 7.0.0.Final > > > Currently cluster listeners behave the same way for replicated caches as distributed caches. We should enhance this so the replicated cache only uses a local listener to improve write performance when they are installed. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4704) Cluster Listener REPL may not notify properly based on owner

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4704?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4704: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1150501 > Cluster Listener REPL may not notify properly based on owner > ------------------------------------------------------------ > > Key: ISPN-4704 > URL: https://issues.jboss.org/browse/ISPN-4704 > Project: Infinispan > Issue Type: Bug > Affects Versions: 7.0.0.Beta2 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Beta2 > > > The new optimization for cluster listeners with replication has a slight bug that an event may not be raised if the event comes from a non owner. > http://ci.infinispan.org/viewLog.html?buildId=11468&buildTypeId=bt8&tab=b... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4813) JMX returns wrong number of cache entries

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-4813?page=com.atlassian.jira.plugin.... ] Vojtech Juranek commented on ISPN-4813: --------------------------------------- This is caused by HotRod {{clear}} request, which actually doesn't call {{clear()}} method on data container and thus some entries survive there. JMX then reports actual number of entries in data container. > JMX returns wrong number of cache entries > ----------------------------------------- > > Key: ISPN-4813 > URL: https://issues.jboss.org/browse/ISPN-4813 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Reporter: Vojtech Juranek > Assignee: Mircea Markus > > Number of cache entries ({{numberOfEntries}}) provided by JMX is wrong. {{HotRodRemoteCacheIT#testPutAsyc}} fails with assert error (see bellow), because JMX returns wrong number of entries in the cache. When debugging the test, number of entries in the cache is correct (100 - obrained e.g. by {{cache.getBulk().size()}}), but JMX return wrong number (100). Even on cleared cache JMX return that it contains 3 entries. When the {{clear}} operation is called via JMX, JMX show correct number (0). > {noformat} > java.lang.AssertionError: expected:<100> but was:<103> > 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.server.test.client.hotrod.AbstractRemoteCacheIT.testPutAsync(AbstractRemoteCacheIT.java:574) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4011) Make it possible to use 'remote-jmx' protocol inside Karaf

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4011?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-4011: ------------------------------------- [~mgencur] This issue has now become pretty much obsolete since the introduction of a proper mechanism to define protobuf schemas in a much nicer and friendlier way that does not require the use of JMX (see ISPN-4357). JMX support is still there but I think we should deprecate it in 7 and eventually remove it. Wdyt? > Make it possible to use 'remote-jmx' protocol inside Karaf > ---------------------------------------------------------- > > Key: ISPN-4011 > URL: https://issues.jboss.org/browse/ISPN-4011 > Project: Infinispan > Issue Type: Feature Request > Reporter: Adrian Nistor > Assignee: Martin Gencur > Labels: 630 > Fix For: 7.0.0.Final > > > This is needed so remote-query clients can register protobuf schemas via jmx. Currently this was circumvented by creating a separate stand-alone app (ProtofileRegistrar) that runs outside Karaf before the actual test. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4814) Publishing the site via awestruct doesn't work

by Dan Berindei (JIRA)

Dan Berindei created ISPN-4814: ---------------------------------- Summary: Publishing the site via awestruct doesn't work Key: ISPN-4814 URL: https://issues.jboss.org/browse/ISPN-4814 Project: Infinispan Issue Type: Bug Components: Build process Affects Versions: 7.0.0.CR1 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 7.0.0.CR2 The {{publish_production.sh}} script uses {{awestruct --deploy}} to publish the site. Normally it should do something like this: {noformat} git checkout master cp -r _site/* . git commit -a -m "Published master to GitHub pages." git push origin master {noformat} Instead, it deletes everything on the master branch and pushes that, taking the site down (because GitHub relies on a CNAME file to find the domain name). The solution is to revert the commit (since some files are not generated) and publish the site manually. This could be caused by an incompatibility between the version of git on the CI machine and the 'git' gem used by awestruct. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4811) Add Cross-Site state transfer operations and metrics to CLI

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4811?page=com.atlassian.jira.plugin.... ] Work on ISPN-4811 started by Pedro Ruivo. ----------------------------------------- > Add Cross-Site state transfer operations and metrics to CLI > ----------------------------------------------------------- > > Key: ISPN-4811 > URL: https://issues.jboss.org/browse/ISPN-4811 > Project: Infinispan > Issue Type: Sub-task > Components: Cross-Site Replication > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 7.0.0.CR2 > > > Add the operations to control the cross-site state transfer and the metrics to check the state of running state transfer to CLI. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 October 2014