February 2018 - infinispan-issues

[JBoss JIRA] (ISPN-8811) JavaDocs should only include major.minor versions (no micro and no qualfiier)

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8811?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8811: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.2.0.CR3 Resolution: Done > JavaDocs should only include major.minor versions (no micro and no qualfiier) > ----------------------------------------------------------------------------- > > Key: ISPN-8811 > URL: https://issues.jboss.org/browse/ISPN-8811 > Project: Infinispan > Issue Type: Feature Request > Components: Documentation-Core > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.2.0.CR3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8817) build[.sh|.bat] should set clean install as default maven goals

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8817?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8817: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > build[.sh|.bat] should set clean install as default maven goals > --------------------------------------------------------------- > > Key: ISPN-8817 > URL: https://issues.jboss.org/browse/ISPN-8817 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Affects Versions: 9.2.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.2.0.CR3 > > > The build scripts default to the "install" maven goal, but this can lead to broken builds. The default should be "clean install" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8790) Distributed iterator performance degradation

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8790?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8790: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Distributed iterator performance degradation > --------------------------------------------- > > Key: ISPN-8790 > URL: https://issues.jboss.org/browse/ISPN-8790 > Project: Infinispan > Issue Type: Bug > Components: Streams > Affects Versions: 9.2.0.CR2 > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.CR3 > > > While testing out DistributedStreamRehashStressTest the number of invocations is not as high as it should be when testing out iteration. Something has regressed since it was originally written. > I have found https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... which helped immensely, however there is still some other issue causing performance loss. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8806) ClusterStreamManagerImpl Subscription can request too many remote entries

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8806?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8806: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ClusterStreamManagerImpl Subscription can request too many remote entries > ------------------------------------------------------------------------- > > Key: ISPN-8806 > URL: https://issues.jboss.org/browse/ISPN-8806 > Project: Infinispan > Issue Type: Bug > Components: Streams > Affects Versions: 9.2.0.CR2 > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.CR3 > > > The ClusterStreamManagerImpl.ClusterStreamSubscription stores a requestedAmount variable to ensure that only the correct number of entries are requested. It also ensures that only a single request per node can be done at at time by protecting calls via pendingRequest variable. Unfortunately there is an interleaving of code that allows for a request to possibly send 2 batches worth. This can cause the downstream queues that rely on only a specific number of entries to fail sometimes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8775) Encoder documentation

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8775?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8775: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.2.0.CR3 (was: 9.2.0.Final) Resolution: Done > Encoder documentation > --------------------- > > Key: ISPN-8775 > URL: https://issues.jboss.org/browse/ISPN-8775 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.2.0.CR3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8634) Wildfly 11 fails to start with Infinispan 9.x modules installed

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8634?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8634: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.2.0.CR3 (was: 9.2.0.Final) Resolution: Done > Wildfly 11 fails to start with Infinispan 9.x modules installed > --------------------------------------------------------------- > > Key: ISPN-8634 > URL: https://issues.jboss.org/browse/ISPN-8634 > Project: Infinispan > Issue Type: Bug > Components: Integration > Affects Versions: 9.2.0.Beta1, 9.1.3.Final > Reporter: Alan Field > Assignee: Ryan Emerson > Fix For: 9.2.0.CR3 > > > A user on the forums reported that he got the following errors starting up Wildfly 11 with the Infinispan 9.1 modules installed and the extensions added to the {{standalone.xml}} file: > {noformat} > 14:25:14,340 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143) > at org.jboss.as.server.ServerService.boot(ServerService.java:387) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:370) > at java.lang.Thread.run(Thread.java:748) > Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module org.infinispan.server.endpoint:ispn-9.2 > at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:154) > at org.jboss.as.server.parsing.StandaloneXml$DefaultExtensionHandler.parseExtensions(StandaloneXml.java:131) > at org.jboss.as.server.parsing.StandaloneXml_5.readServerElement(StandaloneXml_5.java:219) > at org.jboss.as.server.parsing.StandaloneXml_5.readElement(StandaloneXml_5.java:142) > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76) > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:126) > ... 3 more > Caused by: java.util.concurrent.ExecutionException: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:192) > at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:146) > ... 11 more > Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module > at org.jboss.as.controller.parsing.ExtensionXml.loadModule(ExtensionXml.java:195) > at org.jboss.as.controller.parsing.ExtensionXml.access$000(ExtensionXml.java:68) > at org.jboss.as.controller.parsing.ExtensionXml$1.call(ExtensionXml.java:126) > at org.jboss.as.controller.parsing.ExtensionXml$1.call(ExtensionXml.java:123) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > Caused by: org.jboss.modules.ModuleNotFoundException: org.jboss.sasl > at org.jboss.modules.Module.addPaths(Module.java:1217) > at org.jboss.modules.Module.link(Module.java:1573) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1601) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:287) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:271) > at org.jboss.as.controller.parsing.ExtensionXml.loadModule(ExtensionXml.java:177) > ... 8 more > {noformat} > This also happens with the 9.2.0.Beta1 modules. Wildfly 11 includes a {{bin/client/README-EJB-JMS.txt}} file that states: > {noformat} > jboss-client.jar is a combined client jar for WildFly, for use in non-maven environments. This jar should be used > with standalone clients only, not with deployments are that deployed to a WildFly instance. > This jar contains the classes required for remote JMS and EJB usage, and consists of the following shaded artifacts: > org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec > org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec > org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec > com.google.guava:guava > commons-beanutils:commons-beanutils > commons-collections:commons-collections > io.netty:netty-all > org.apache.activemq:artemis-commons > org.apache.activemq:artemis-core-client > org.apache.activemq:artemis-hqclient-protocol > org.apache.activemq:artemis-jms-client > org.jboss:jboss-ejb-client > org.jboss:jboss-remote-naming > org.jboss.logging:jboss-logging > org.jboss.marshalling:jboss-marshalling > org.jboss.marshalling:jboss-marshalling-river > org.jboss.remoting:jboss-remoting > org.jboss.remotingjmx:remoting-jmx > org.jboss.sasl:jboss-sasl > org.jboss.xnio:xnio-api > org.jboss.xnio:xnio-nio > org.jgroups:jgroups > org.slf4j:slf4j-api > org.slf4j:jcl-over-slf4j > Maven users should not use this jar, but should use the following BOM dependencies instead > <dependencies> > <dependency> > <groupId>org.wildfly</groupId> > <artifactId>wildfly-ejb-client-bom</artifactId> > <type>pom</type> > </dependency> > <dependency> > <groupId>org.wildfly</groupId> > <artifactId>wildfly-jms-client-bom</artifactId> > <type>pom</type> > </dependency> > </dependencies> > This is because using maven with a shaded jar has a very high chance of causing class version conflicts, which is why > we do not publish this jar to the maven repository. > {noformat} > The modules will need to modified to deal with this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8829) LockedStream doesn't override BaseCacheStream methods

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8829?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8829: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > LockedStream doesn't override BaseCacheStream methods > ----------------------------------------------------- > > Key: ISPN-8829 > URL: https://issues.jboss.org/browse/ISPN-8829 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.2.0.CR2 > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.CR3 > > > LockedStream extends BaseCacheStream to get its methods. Unfortunately it doesn't override these methods, so the compiler only has the return type as BaseCacheStream instead of LockedStream which prevents chaining methods together properly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8822) Major performance hit when running Spark jobs

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8822?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-8822: ----------------------------------------- Taking a single test from the suite and looking at the metrics at http://localhost:4040: {{./sbt "test:run-main org.scalatest.tools.Runner -o -s org.infinispan.spark.suites.SQLSuite"}} ||Stage ID || Before ||After|| |60| 67 ms | 2s | |62| 50 ms | 2s | |64| 41 ms | 2s | Curiously some other stages are faster, but the overall job time is 1 order slower > Major performance hit when running Spark jobs > --------------------------------------------- > > Key: ISPN-8822 > URL: https://issues.jboss.org/browse/ISPN-8822 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod > Affects Versions: 9.2.0.CR2 > Reporter: Gustavo Fernandes > Priority: Critical > > When trying to upgrade the [Spark connector |https://github.com/infinispan/infinispan-spark/] to use Infinispan 9.2.0.CR2, the test suite runs about 10x slower. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8778) Create HeartBeatCommand

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8778?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8778: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.2.0.CR3 Resolution: Done > Create HeartBeatCommand > ----------------------- > > Key: ISPN-8778 > URL: https://issues.jboss.org/browse/ISPN-8778 > Project: Infinispan > Issue Type: Enhancement > Components: Core, State Transfer > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.2.0.CR3 > > > Create a hear-beat command to replace in {{confirmMembersAvailable()}} method. > If a node is joining the cluster while the coordinator is sending the command, the joiner can receive the heart-beat command and delays the reply since its GCR hasn't start yet. > A new hear-beat command would reply immediately. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8828) Cannot locate SessionAccess implementation in modular classloading environment

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8828?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8828: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Cannot locate SessionAccess implementation in modular classloading environment > ------------------------------------------------------------------------------ > > Key: ISPN-8828 > URL: https://issues.jboss.org/browse/ISPN-8828 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.2.0.CR2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 9.2.0.CR3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2018