January 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2684) Upgrade to Netty 3.6.1.Final

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2684?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2684: ---------------------------------- Assignee: Norman Maurer (was: Tristan Tarrant) > Upgrade to Netty 3.6.1.Final > ---------------------------- > > Key: ISPN-2684 > URL: https://issues.jboss.org/browse/ISPN-2684 > Project: Infinispan > Issue Type: Enhancement > Reporter: Norman Maurer > Assignee: Norman Maurer > Fix For: 5.2.0.CR1, 5.2.0.Final > > > We should upgrade to Netty 3.6.1.Final as this allows us to fix ISPN-1954 and also fix some issues with SSL. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1954) Wrong ServerWorker thread name in Hot rod server

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1954?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-1954: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Wrong ServerWorker thread name in Hot rod server > ------------------------------------------------ > > Key: ISPN-1954 > URL: https://issues.jboss.org/browse/ISPN-1954 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.1.3.CR1 > Reporter: Michal Linhard > Assignee: Norman Maurer > Priority: Minor > Fix For: 5.2.0.CR1, 5.2.0.Final > > > When debugging/profiling JDG, we're seeing HotRod server calls being executed by MemcachedServerWorker threads. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2684) Upgrade to Netty 3.6.1.Final

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2684?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2684: ---------------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Tristan Tarrant (was: Mircea Markus) Fix Version/s: 5.2.0.CR1 5.2.0.Final Resolution: Done > Upgrade to Netty 3.6.1.Final > ---------------------------- > > Key: ISPN-2684 > URL: https://issues.jboss.org/browse/ISPN-2684 > Project: Infinispan > Issue Type: Enhancement > Reporter: Norman Maurer > Assignee: Tristan Tarrant > Fix For: 5.2.0.CR1, 5.2.0.Final > > > We should upgrade to Netty 3.6.1.Final as this allows us to fix ISPN-1954 and also fix some issues with SSL. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2686) Enhance Mapper API with lazy loaded value

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2686: ---------------------------------- Summary: Enhance Mapper API with lazy loaded value Key: ISPN-2686 URL: https://issues.jboss.org/browse/ISPN-2686 Project: Infinispan Issue Type: Enhancement Components: Distributed Execution and Map/Reduce Affects Versions: 5.2.0.Beta6 Reporter: Thomas Fromm Assignee: Vladimir Blagojevic In situations where Map/Reduce is used and the value is not (always) needed at the Mapper, the value could be loaded lazy, when the map(..) interface is slightly changed: map(Entry<KIn, VIn> entry, Collector<Entry<KIn, VIn>> collector) When entry.getValue() is called, the value should be loaded from store or maybe remote node. Maybe this change to Entry would be also useful for event api ISPN-1802 -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2560) Distribution ZIP file polluted

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2560?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2560: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Distribution ZIP file polluted > ------------------------------ > > Key: ISPN-2560 > URL: https://issues.jboss.org/browse/ISPN-2560 > Project: Infinispan > Issue Type: Bug > Components: Build process > Affects Versions: 5.2.0.Beta4 > Reporter: Manik Surtani > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 5.2.0.CR1, 5.2.0.Final > > > There appear to be a lot of files packaged up and archived in various (incorrect and superfluous) places in the ZIP archives. > 1. Looking at 5.2.0.Beta4-all.zip, I see: > {code} > Multiverse:infinispan-5.2.0.Beta4-all manik $ jar tf infinispan-core.jar | grep "\.sh" > functions.sh > importConfig.sh > Multiverse:infinispan-5.2.0.Beta4-all manik $ > {code} > Why are these shell scripts in the JAR file? > 2. Also, I see similar things in other JAR files: > {code} > Multiverse:infinispan-5.2.0.Beta4-all manik $ jar tf modules/demos/ec2/infinispan-ec2-demo.jar | grep "\.sh" > runEC2Demo-all.sh > runEC2Demo-influenza.sh > runEC2Demo-nucleotide.sh > runEC2Demo-protein.sh > runEC2Demo-query.sh > runEC2Demo-reader.sh > Multiverse:infinispan-5.2.0.Beta4-all manik $ > {code} > {code} > Multiverse:infinispan-5.2.0.Beta4-all manik $ jar tf modules/cli-client/infinispan-cli-client.jar | grep "\.sh" > ispn-cli.sh > Multiverse:infinispan-5.2.0.Beta4-all manik $ > {code} > 3. I see these in {{/etc/}} which, if I now put {{/etc/}} in my classpath, causes things to break in spectacular ways due to the service loaded picking up incorrect metadata. > {code} > Multiverse:infinispan-5.2.0.Beta4-all manik $ ls etc/META-INF/services/ > org.infinispan.cli.commands.Command > org.infinispan.cli.connection.Connector > org.infinispan.commands.module.ModuleCommandExtensions > org.infinispan.configuration.parsing.ConfigurationParser > org.infinispan.distexec.mapreduce.spi.MapReduceTaskLifecycle > org.infinispan.distexec.spi.DistributedTaskLifecycle > org.infinispan.factories.components.ModuleMetadataFileFinder > org.infinispan.lifecycle.ModuleLifecycle > Multiverse:infinispan-5.2.0.Beta4-all manik $ > {code} > 4. Why do we package {{etc/infinispan-query-component-metadata.dat}}? That should be a part of infinispan-query.jar, and not in etc. > 5. What is in {{/etc/help}}? Looks like resource files for the CLI, which should really be in one of the CLI jars. > Marking this as critical, since this is messy and confusing for users, and can cause breakage when running some demos and makes things very confusing to debug. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2685) TopologyAwareTwoNodesMapReduceTest.testCombinerDoesNotChangeResult fails randomly

by Dan Berindei (JIRA)

Dan Berindei created ISPN-2685: ---------------------------------- Summary: TopologyAwareTwoNodesMapReduceTest.testCombinerDoesNotChangeResult fails randomly Key: ISPN-2685 URL: https://issues.jboss.org/browse/ISPN-2685 Project: Infinispan Issue Type: Feature Request Components: Distributed Execution and Map/Reduce, Test Suite Affects Versions: 5.2.0.Beta6 Reporter: Dan Berindei Assignee: Vladimir Blagojevic Fix For: 6.0.0.Final TopologyAwareTwoNodesMapReduceTest.testCombinerDoesNotChangeResult fails randomly on my machine, with this stacktrace: {noformat} java.lang.AssertionError at org.infinispan.distexec.mapreduce.BaseWordCountMapReduceTest.testCombinerDoesNotChangeResult(BaseWordCountMapReduceTest.java:217) {noformat} I think it's because it's comparing {{Integer}} objects with {{==}} instead of {{equals()}}. Actually it would be best to use {{Assert.assertEquals()}}, I tried to find the expected and actual values in the log but I wasn't able to. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2560) Distribution ZIP file polluted

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2560?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2560: -------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/1546, https://github.com/infinispan/infinispan/pull/1553 (was: https://github.com/infinispan/infinispan/pull/1546) > Distribution ZIP file polluted > ------------------------------ > > Key: ISPN-2560 > URL: https://issues.jboss.org/browse/ISPN-2560 > Project: Infinispan > Issue Type: Bug > Components: Build process > Affects Versions: 5.2.0.Beta4 > Reporter: Manik Surtani > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 5.2.0.CR1, 5.2.0.Final > > > There appear to be a lot of files packaged up and archived in various (incorrect and superfluous) places in the ZIP archives. > 1. Looking at 5.2.0.Beta4-all.zip, I see: > {code} > Multiverse:infinispan-5.2.0.Beta4-all manik $ jar tf infinispan-core.jar | grep "\.sh" > functions.sh > importConfig.sh > Multiverse:infinispan-5.2.0.Beta4-all manik $ > {code} > Why are these shell scripts in the JAR file? > 2. Also, I see similar things in other JAR files: > {code} > Multiverse:infinispan-5.2.0.Beta4-all manik $ jar tf modules/demos/ec2/infinispan-ec2-demo.jar | grep "\.sh" > runEC2Demo-all.sh > runEC2Demo-influenza.sh > runEC2Demo-nucleotide.sh > runEC2Demo-protein.sh > runEC2Demo-query.sh > runEC2Demo-reader.sh > Multiverse:infinispan-5.2.0.Beta4-all manik $ > {code} > {code} > Multiverse:infinispan-5.2.0.Beta4-all manik $ jar tf modules/cli-client/infinispan-cli-client.jar | grep "\.sh" > ispn-cli.sh > Multiverse:infinispan-5.2.0.Beta4-all manik $ > {code} > 3. I see these in {{/etc/}} which, if I now put {{/etc/}} in my classpath, causes things to break in spectacular ways due to the service loaded picking up incorrect metadata. > {code} > Multiverse:infinispan-5.2.0.Beta4-all manik $ ls etc/META-INF/services/ > org.infinispan.cli.commands.Command > org.infinispan.cli.connection.Connector > org.infinispan.commands.module.ModuleCommandExtensions > org.infinispan.configuration.parsing.ConfigurationParser > org.infinispan.distexec.mapreduce.spi.MapReduceTaskLifecycle > org.infinispan.distexec.spi.DistributedTaskLifecycle > org.infinispan.factories.components.ModuleMetadataFileFinder > org.infinispan.lifecycle.ModuleLifecycle > Multiverse:infinispan-5.2.0.Beta4-all manik $ > {code} > 4. Why do we package {{etc/infinispan-query-component-metadata.dat}}? That should be a part of infinispan-query.jar, and not in etc. > 5. What is in {{/etc/help}}? Looks like resource files for the CLI, which should really be in one of the CLI jars. > Marking this as critical, since this is messy and confusing for users, and can cause breakage when running some demos and makes things very confusing to debug. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2560) Distribution ZIP file polluted

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2560?page=com.atlassian.jira.plugin.... ] Adrian Nistor reopened ISPN-2560: --------------------------------- Reopening because SampleConfigFilesCorrectnessTest was broken. > Distribution ZIP file polluted > ------------------------------ > > Key: ISPN-2560 > URL: https://issues.jboss.org/browse/ISPN-2560 > Project: Infinispan > Issue Type: Bug > Components: Build process > Affects Versions: 5.2.0.Beta4 > Reporter: Manik Surtani > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 5.2.0.CR1, 5.2.0.Final > > > There appear to be a lot of files packaged up and archived in various (incorrect and superfluous) places in the ZIP archives. > 1. Looking at 5.2.0.Beta4-all.zip, I see: > {code} > Multiverse:infinispan-5.2.0.Beta4-all manik $ jar tf infinispan-core.jar | grep "\.sh" > functions.sh > importConfig.sh > Multiverse:infinispan-5.2.0.Beta4-all manik $ > {code} > Why are these shell scripts in the JAR file? > 2. Also, I see similar things in other JAR files: > {code} > Multiverse:infinispan-5.2.0.Beta4-all manik $ jar tf modules/demos/ec2/infinispan-ec2-demo.jar | grep "\.sh" > runEC2Demo-all.sh > runEC2Demo-influenza.sh > runEC2Demo-nucleotide.sh > runEC2Demo-protein.sh > runEC2Demo-query.sh > runEC2Demo-reader.sh > Multiverse:infinispan-5.2.0.Beta4-all manik $ > {code} > {code} > Multiverse:infinispan-5.2.0.Beta4-all manik $ jar tf modules/cli-client/infinispan-cli-client.jar | grep "\.sh" > ispn-cli.sh > Multiverse:infinispan-5.2.0.Beta4-all manik $ > {code} > 3. I see these in {{/etc/}} which, if I now put {{/etc/}} in my classpath, causes things to break in spectacular ways due to the service loaded picking up incorrect metadata. > {code} > Multiverse:infinispan-5.2.0.Beta4-all manik $ ls etc/META-INF/services/ > org.infinispan.cli.commands.Command > org.infinispan.cli.connection.Connector > org.infinispan.commands.module.ModuleCommandExtensions > org.infinispan.configuration.parsing.ConfigurationParser > org.infinispan.distexec.mapreduce.spi.MapReduceTaskLifecycle > org.infinispan.distexec.spi.DistributedTaskLifecycle > org.infinispan.factories.components.ModuleMetadataFileFinder > org.infinispan.lifecycle.ModuleLifecycle > Multiverse:infinispan-5.2.0.Beta4-all manik $ > {code} > 4. Why do we package {{etc/infinispan-query-component-metadata.dat}}? That should be a part of infinispan-query.jar, and not in etc. > 5. What is in {{/etc/help}}? Looks like resource files for the CLI, which should really be in one of the CLI jars. > Marking this as critical, since this is messy and confusing for users, and can cause breakage when running some demos and makes things very confusing to debug. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2684) Upgrade to Netty 3.6.1.Final

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2684?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2684: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1552 > Upgrade to Netty 3.6.1.Final > ---------------------------- > > Key: ISPN-2684 > URL: https://issues.jboss.org/browse/ISPN-2684 > Project: Infinispan > Issue Type: Enhancement > Reporter: Norman Maurer > Assignee: Mircea Markus > > We should upgrade to Netty 3.6.1.Final as this allows us to fix ISPN-1954 and also fix some issues with SSL. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1954) Wrong ServerWorker thread name in Hot rod server

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1954?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-1954: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1552 > Wrong ServerWorker thread name in Hot rod server > ------------------------------------------------ > > Key: ISPN-1954 > URL: https://issues.jboss.org/browse/ISPN-1954 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.1.3.CR1 > Reporter: Michal Linhard > Assignee: Norman Maurer > Priority: Minor > Fix For: 5.2.0.CR1, 5.2.0.Final > > > When debugging/profiling JDG, we're seeing HotRod server calls being executed by MemcachedServerWorker threads. -- 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, 4 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