November 2019 - infinispan-issues

[JBoss JIRA] (ISPN-11007) State Transfer hangs on org.infinispan.CONFIG cache

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-11007?page=com.atlassian.jira.plugin... ] Dan Berindei reassigned ISPN-11007: ----------------------------------- Assignee: Dan Berindei > State Transfer hangs on org.infinispan.CONFIG cache > --------------------------------------------------- > > Key: ISPN-11007 > URL: https://issues.jboss.org/browse/ISPN-11007 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.0.Beta1 > Reporter: Gustavo Fernandes > Assignee: Dan Berindei > Priority: Major > Attachments: log.trace, log.txt, stack > > > Observed when running the tests from integrationtests/elasticsearch-indexmanager-it > Attached the stack stack trace and debug log. > When running with -Dinfinispan.cluster.stack=tcp it works -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11007) State Transfer hangs on org.infinispan.CONFIG cache

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-11007?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-11007: -------------------------------- Status: Open (was: New) > State Transfer hangs on org.infinispan.CONFIG cache > --------------------------------------------------- > > Key: ISPN-11007 > URL: https://issues.jboss.org/browse/ISPN-11007 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.0.Beta1 > Reporter: Gustavo Fernandes > Assignee: Dan Berindei > Priority: Major > Attachments: log.trace, log.txt, stack > > > Observed when running the tests from integrationtests/elasticsearch-indexmanager-it > Attached the stack stack trace and debug log. > When running with -Dinfinispan.cluster.stack=tcp it works -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11008) Remove context-path for the rest connector

by Donald Naro (Jira)

Donald Naro created ISPN-11008: ---------------------------------- Summary: Remove context-path for the rest connector Key: ISPN-11008 URL: https://issues.jboss.org/browse/ISPN-11008 Project: Infinispan Issue Type: Bug Reporter: Donald Naro Assignee: Gustavo Fernandes context-path should not be configurable for REST connectors -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11007) State Transfer hangs on org.infinispan.CONFIG cache

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-11007?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-11007: ------------------------------------- Attachment: log.trace > State Transfer hangs on org.infinispan.CONFIG cache > --------------------------------------------------- > > Key: ISPN-11007 > URL: https://issues.jboss.org/browse/ISPN-11007 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.0.Beta1 > Reporter: Gustavo Fernandes > Priority: Major > Attachments: log.trace, log.txt, stack > > > Observed when running the tests from integrationtests/elasticsearch-indexmanager-it > Attached the stack stack trace and debug log. > When running with -Dinfinispan.cluster.stack=tcp it works -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11007) State Transfer hangs on org.infinispan.CONFIG cache

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-11007?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-11007: ------------------------------------- Attachment: log.txt stack > State Transfer hangs on org.infinispan.CONFIG cache > --------------------------------------------------- > > Key: ISPN-11007 > URL: https://issues.jboss.org/browse/ISPN-11007 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.0.Beta1 > Reporter: Gustavo Fernandes > Priority: Major > Attachments: log.txt, stack > > > Observed when running the tests from integrationtests/elasticsearch-indexmanager-it > Attached the stack stack trace and debug log. > When running with -Dinfinispan.cluster.stack=tcp it works -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11007) State Transfer hangs on org.infinispan.CONFIG cache

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-11007: ---------------------------------------- Summary: State Transfer hangs on org.infinispan.CONFIG cache Key: ISPN-11007 URL: https://issues.jboss.org/browse/ISPN-11007 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 10.1.0.Beta1 Reporter: Gustavo Fernandes Observed when running the tests from integrationtests/elasticsearch-indexmanager-it Attached the stack stack trace and debug log. When running with -Dinfinispan.cluster.stack=tcp it works -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10563) Unable to start blueprint container for bundle org.infinispan.multimap/9.4.1.Final org.osgi.service.blueprint.container.Component Definition Exception: Unable to validate xml

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10563?page=com.atlassian.jira.plugin... ] Tristan Tarrant reassigned ISPN-10563: -------------------------------------- Assignee: Dan Berindei > Unable to start blueprint container for bundle org.infinispan.multimap/9.4.1.Final org.osgi.service.blueprint.container.Component Definition Exception: Unable to validate xml > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-10563 > URL: https://issues.jboss.org/browse/ISPN-10563 > Project: Infinispan > Issue Type: Bug > Components: Multimap > Affects Versions: 9.4.1.Final > Environment: java 1.8.0_191 > org.eclipse.osgi 3.14.0.v20190517-1309 > org.apache.felix.scr 2.1.14.v20190123-1619 > infinispan-core 9.4.1.Final > infinispan-commons 9.4.1.Final > infinispan-multimap 9.4.1.Final > infinispan-persistence-soft-index 9.4.1.Final > Reporter: NHUT THAI LE > Assignee: Dan Berindei > Priority: Major > > Using infinispan-multimap in equinox, when starting server i got this error: > 14:52:24.059 [Blueprint Extender: 3] ERROR o.a.a.b.c.BlueprintContainerImpl - Unable to start blueprint container for bundle org.infinispan.multimap/9.4.1.Final > org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to validate xml > at org.apache.aries.blueprint.parser.Parser.validate(Parser.java:349) ~[org.apache.aries.blueprint.core_1.9.0.jar:1.9.0] > at org.apache.aries.blueprint.parser.Parser.validate(Parser.java:336) ~[org.apache.aries.blueprint.core_1.9.0.jar:1.9.0] > at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:345) [org.apache.aries.blueprint.core_1.9.0.jar:1.9.0] > at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:278) [org.apache.aries.blueprint.core_1.9.0.jar:1.9.0] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_45] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_45] > at org.apache.aries.blueprint.container.ExecutorServiceWrapper.run(ExecutorServiceWrapper.java:106) [org.apache.aries.blueprint.core_1.9.0.jar:1.9.0] > at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:45) [org.apache.aries.blueprint.core_1.9.0.jar:1.9.0] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_45] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_45] > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_45] > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_45] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_45] > at java.lang.Thread.run(Thread.java:745) [na:1.8.0_45] > Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.3: Element 'blueprint' cannot have character [children], because the type's content type is element-only. > at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203) ~[na:1.8.0_45] > at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:134) ~[na:1.8.0_45] > at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:437) ~[na:1.8.0_45] > at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368) ~[na:1.8.0_45] > at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:325) ~[na:1.8.0_45] > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:458) ~[na:1.8.0_45] > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3237) ~[na:1.8.0_45] > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.elementLocallyValidComplexType(XMLSchemaValidator.java:3200) ~[na:1.8.0_45] > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.elementLocallyValidType(XMLSchemaValidator.java:3160) ~[na:1.8.0_45] > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.processElementContent(XMLSchemaValidator.java:3062) ~[na:1.8.0_45] > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleEndElement(XMLSchemaValidator.java:2140) ~[na:1.8.0_45] > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.endElement(XMLSchemaValidator.java:859) ~[na:1.8.0_45] > at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.finishNode(DOMValidatorHelper.java:342) ~[na:1.8.0_45] > at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(DOMValidatorHelper.java:247) ~[na:1.8.0_45] > at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(DOMValidatorHelper.java:190) ~[na:1.8.0_45] > at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.validate(ValidatorImpl.java:109) ~[na:1.8.0_45] > at javax.xml.validation.Validator.validate(Validator.java:124) ~[na:1.8.0_45] > at org.apache.aries.blueprint.parser.Parser.validate(Parser.java:346) ~[org.apache.aries.blueprint.core_1.9.0.jar:1.9.0] > ... 14 common frames omitted > Looking at the org.infinispan.multimap_9.4.1.Final.jar\OSGI-INF\blueprint\blueprint.xml i found that it contains ${services}. Look like some pre-processing need to run when packaging this bundle to replace that place holder with <service> tag > Also noticed that the bundle contain service file to be loaded by ServiceLoader which is not available in an OSGI env, if this is the only way to load service then perhaps, the manifest of the bundle also need to specify that it require a service mediator -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10966) StateTransferLockImpl.topologyFuture should complete exceptionally after stop

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10966?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10966: -------------------------------- Status: Open (was: New) > StateTransferLockImpl.topologyFuture should complete exceptionally after stop > ----------------------------------------------------------------------------- > > Key: ISPN-10966 > URL: https://issues.jboss.org/browse/ISPN-10966 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.0.CR1 > > > When a cache is shutting down, the topology id is increased to {{Integer.MAX_VALUE}}. > If a component uses {{StateTransferLock.topologyUpdate()}} to retry in the next topology and doesn't explicitly check if the cache is running, it could retry 2^^31 times before giving up. > This causes {{StreamDistPartitionHandlingTest.clearContent}} to hang randomly: > {noformat} > 11:58:14,655 TRACE (testng-Test:[]) [StateTransferLockImpl] Signalling topology 2147483647 is installed > 11:58:14,655 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} not completed - retrying > 11:58:14,655 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Retrying segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} after 16 is installed for Test-NodeA-12596#7046 > ... > 12:03:16,127 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} not completed - retrying > 12:03:16,127 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Retrying segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} after 16 is installed for Test-NodeA-12596#7046 > ... > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10966) StateTransferLockImpl.topologyFuture should complete exceptionally after stop

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10966?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10966: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7631 > StateTransferLockImpl.topologyFuture should complete exceptionally after stop > ----------------------------------------------------------------------------- > > Key: ISPN-10966 > URL: https://issues.jboss.org/browse/ISPN-10966 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.0.CR1 > > > When a cache is shutting down, the topology id is increased to {{Integer.MAX_VALUE}}. > If a component uses {{StateTransferLock.topologyUpdate()}} to retry in the next topology and doesn't explicitly check if the cache is running, it could retry 2^^31 times before giving up. > This causes {{StreamDistPartitionHandlingTest.clearContent}} to hang randomly: > {noformat} > 11:58:14,655 TRACE (testng-Test:[]) [StateTransferLockImpl] Signalling topology 2147483647 is installed > 11:58:14,655 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} not completed - retrying > 11:58:14,655 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Retrying segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} after 16 is installed for Test-NodeA-12596#7046 > ... > 12:03:16,127 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} not completed - retrying > 12:03:16,127 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Retrying segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} after 16 is installed for Test-NodeA-12596#7046 > ... > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11006) Remove REST v1 API

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-11006?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-11006: ------------------------------------- Status: Open (was: New) > Remove REST v1 API > ------------------ > > Key: ISPN-11006 > URL: https://issues.jboss.org/browse/ISPN-11006 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 10.0.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 11.0.0.Final > > > The legacy API was deprecated on 10.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2019