June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8770) Allow remote clients to hint for optimal node when running Server Task

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8770?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8770: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.3.0.Final Resolution: Done > Allow remote clients to hint for optimal node when running Server Task > ---------------------------------------------------------------------- > > Key: ISPN-8770 > URL: https://issues.jboss.org/browse/ISPN-8770 > Project: Infinispan > Issue Type: Feature Request > Components: Hot Rod, Tasks > Reporter: Sanne Grinovero > Assignee: Radim Vansa > Fix For: 9.3.0.Final > > > As suggested by Radim on the Hibernate mailing list, for OGM: > - http://lists.jboss.org/pipermail/hibernate-dev/2018-February/017177.html > See also follow ups. We'll likely want to be able to have the task definition on the Hot Rod client hint that it's going to operate on one specific key (simple case) or a group of keys (more complex but still beneficial). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9286) WriteBehindFaultToleranceTest Failures

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9286?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9286: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > WriteBehindFaultToleranceTest Failures > -------------------------------------- > > Key: ISPN-9286 > URL: https://issues.jboss.org/browse/ISPN-9286 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 9.3.0.CR1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Final > > > #testBlockingOnStoreAvailabilityChange failure due to the async write not completing before store.size is called. > {code:java} > java.lang.AssertionError: expected:<1> but was:<0> > at org.infinispan.persistence.WriteBehindFaultToleranceTest.testBlockingOnStoreAvailabilityChange(WriteBehindFaultToleranceTest.java:55) > at org.infinispan.commons.test.TestNGLongTestsHook.run(TestNGLongTestsHook.java:24) > 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) > ... Removed 23 stack frames > {code} > #testWritesFailSilentlyWhenConfigured failure due to the async write not being executed on the store before the entry is loaded from the store. > {code:java} > java.lang.NullPointerException > at org.infinispan.persistence.WriteBehindFaultToleranceTest.testWritesFailSilentlyWhenConfigured(WriteBehindFaultToleranceTest.java:110) > at org.infinispan.commons.test.TestNGLongTestsHook.run(TestNGLongTestsHook.java:24) > 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) > ... Removed 18 stack frames > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9016) Component metadata serialization format changes depending on compiler

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-9016?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-9016: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated in master. Thanks [~dan.berindei]! > Component metadata serialization format changes depending on compiler > --------------------------------------------------------------------- > > Key: ISPN-9016 > URL: https://issues.jboss.org/browse/ISPN-9016 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.3.0.Final > > > The field and method metadata classes have a {{serialVersionUUID}}, but {{ComponentMetadata}} itself doesn't have it, so it can change at any time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9295) Server fails to start if maven repo does not have Xerces

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9295?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9295: ----------------------------------- Priority: Minor (was: Blocker) > Server fails to start if maven repo does not have Xerces > -------------------------------------------------------- > > Key: ISPN-9295 > URL: https://issues.jboss.org/browse/ISPN-9295 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.3.0.CR1 > Reporter: Galder Zamarreño > Priority: Minor > Fix For: 9.3.0.Final > > > If XercesImpl is not present in maven repo, there doesn't seem to be an attempt to download and instead you get: > {code} > [Host Controller] Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to resolve artifact 'xerces:xercesImpl:2.11.0.SP5' (position: END_TAG seen ...resources>\n <artifact name="xerces:xercesImpl:2.11.0.SP5"/>... @26:56) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseArtifact(ModuleXmlParser.java:981) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleXmlParser.java:869) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:659) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXmlParser.java:426) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:302) > [Host Controller] ... 15 more > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9224) Reduce ExceptionEvictionTest runtime

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9224?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9224: -------------------------------- Summary: Reduce ExceptionEvictionTest runtime (was: Reduce ExceptionEvictionTest combinations) > Reduce ExceptionEvictionTest runtime > ------------------------------------ > > Key: ISPN-9224 > URL: https://issues.jboss.org/browse/ISPN-9224 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Core > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.Final > > > The ExceptionEvictionTest tests all possible permutations. This is a bit wasteful as the multiple node ones should behave the same irrespective of the storage type. The local mode should be sufficient to test different storage type calculations. > We can comment out quite a few of the tests, which should allow for quicker test runs -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9295) Server fails to start if maven repo does not have Xerces

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9295?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-9295: ---------------------------------------- Ah, this only happens if you download the server from: https://repository.jboss.org/nexus/content/groups/public-jboss/org/infini... > Server fails to start if maven repo does not have Xerces > -------------------------------------------------------- > > Key: ISPN-9295 > URL: https://issues.jboss.org/browse/ISPN-9295 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.3.0.CR1 > Reporter: Galder Zamarreño > Priority: Blocker > Fix For: 9.3.0.Final > > > If XercesImpl is not present in maven repo, there doesn't seem to be an attempt to download and instead you get: > {code} > [Host Controller] Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to resolve artifact 'xerces:xercesImpl:2.11.0.SP5' (position: END_TAG seen ...resources>\n <artifact name="xerces:xercesImpl:2.11.0.SP5"/>... @26:56) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseArtifact(ModuleXmlParser.java:981) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleXmlParser.java:869) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:659) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXmlParser.java:426) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:302) > [Host Controller] ... 15 more > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9295) Server fails to start if maven repo does not have Xerces

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9295?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9295: ----------------------------------- Workaround Description: Seems like for this to work, Maven settings need to point to JBoss Nexus repo. Although a workaround, this is not a valid solution long term: {code} <settings> <profiles> <profile> <id>jboss</id> <repositories> <repository> <id>jboss-public-repository-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> <layout>default</layout> <releases> <enabled>true</enabled> <updatePolicy>always</updatePolicy> </releases> <snapshots> <enabled>false</enabled> <updatePolicy>never</updatePolicy> </snapshots> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>jboss-public-repository-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>true</enabled> </snapshots> </pluginRepository> </pluginRepositories> </profile> </profiles> <activeProfiles> <activeProfile>jboss</activeProfile> </activeProfiles> </settings> {code} Workaround: Workaround Exists > Server fails to start if maven repo does not have Xerces > -------------------------------------------------------- > > Key: ISPN-9295 > URL: https://issues.jboss.org/browse/ISPN-9295 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.3.0.CR1 > Reporter: Galder Zamarreño > Priority: Blocker > Fix For: 9.3.0.Final > > > If XercesImpl is not present in maven repo, there doesn't seem to be an attempt to download and instead you get: > {code} > [Host Controller] Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to resolve artifact 'xerces:xercesImpl:2.11.0.SP5' (position: END_TAG seen ...resources>\n <artifact name="xerces:xercesImpl:2.11.0.SP5"/>... @26:56) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseArtifact(ModuleXmlParser.java:981) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleXmlParser.java:869) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:659) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXmlParser.java:426) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:302) > [Host Controller] ... 15 more > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9294) It is not possible override enable_diagnostics

by Diego Lovison (JIRA)

[ https://issues.jboss.org/browse/ISPN-9294?page=com.atlassian.jira.plugin.... ] Diego Lovison closed ISPN-9294. ------------------------------- Resolution: Rejected This is not a bug. You need to configure as the following: {code:xml} <transport type="UDP" socket-binding="jgroups-udp" diagnostics-socket-binding="diag-socket-binding" /> <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"> ........ <socket-binding name="diag-socket-binding" interface="public" multicast-address="224.0.75.75" multicast-port="7500" fixed-port="true"/> {code} For more details check: https://github.com/belaban/jdg-client/blob/e2d72b1c1881e9ab21ea42a6c17a52... > It is not possible override enable_diagnostics > ---------------------------------------------- > > Key: ISPN-9294 > URL: https://issues.jboss.org/browse/ISPN-9294 > Project: Infinispan > Issue Type: Bug > Reporter: Diego Lovison > Attachments: pasted_image.png > > > I would like to set enable_diagnostics=true but the following configuration is not working. > Edit standalone/configuration/clustered.xml file adding the new property > {code:xml} > <transport type="UDP" socket-binding="jgroups-udp"> > <property name="enable_diagnostics">true</property> > </transport> > {code} > Start the server ./standalone.sh -c clustered.xml > Open jcm and check the property. It is still false. See the attachment. > The desirable solution could be a change in the following files to: > - default-configs/default-jgroups-udp.xml > - default-configs/default-jgroups-tcp.xml > {noformat} > enable_diagnostics="${jgroups.udp.enable_diagnostics:false}" > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9295) Server fails to start if maven repo does not have Xerces

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-9295: -------------------------------------- Summary: Server fails to start if maven repo does not have Xerces Key: ISPN-9295 URL: https://issues.jboss.org/browse/ISPN-9295 Project: Infinispan Issue Type: Bug Components: Server Affects Versions: 9.3.0.CR1 Reporter: Galder Zamarreño Priority: Blocker Fix For: 9.3.0.Final If XercesImpl is not present in maven repo, there doesn't seem to be an attempt to download and instead you get: {code} [Host Controller] Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to resolve artifact 'xerces:xercesImpl:2.11.0.SP5' (position: END_TAG seen ...resources>\n <artifact name="xerces:xercesImpl:2.11.0.SP5"/>... @26:56) [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseArtifact(ModuleXmlParser.java:981) [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleXmlParser.java:869) [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:659) [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXmlParser.java:426) [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:302) [Host Controller] ... 15 more {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9020) Remote query: disabling indexing for a type with @Indexed(false) still creates empty documents in index

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-9020?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-9020: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/6041, https://github.com/infinispan/infinispan/pull/6062, https://github.com/infinispan/infinispan/pull/6067 (was: https://github.com/infinispan/infinispan/pull/6041, https://github.com/infinispan/infinispan/pull/6062) > Remote query: disabling indexing for a type with @Indexed(false) still creates empty documents in index > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-9020 > URL: https://issues.jboss.org/browse/ISPN-9020 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 7.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.3.0.Final > > > When adding to cache protobuf encoded entries of types that are specifically annotated as @Indexed(false) we would expect that nothing is added to the index. But a document with no fields is added instead, cluttering the index. This does not impact the correctness of query results but it impacts performance because every put operation touches the index even if not required. This bug is a consequence of some limitations of the integration point between infinispan and hibernate search: the FieldBridge api. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 June 2018