July 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6734) XML serializer serializes the singleFile location property in different way

by Anna Manukyan (JIRA)

[ https://issues.jboss.org/browse/ISPN-6734?page=com.atlassian.jira.plugin.... ] Anna Manukyan updated ISPN-6734: -------------------------------- Status: Open (was: New) > XML serializer serializes the singleFile location property in different way > --------------------------------------------------------------------------- > > Key: ISPN-6734 > URL: https://issues.jboss.org/browse/ISPN-6734 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Reporter: Anna Manukyan > > In case when {{persistence}} is configured with {{SingleFileStore}} class and the location is provided with properties, the generated xml contains both the {{path}} attribute and the property with the same value. > This code: > {code} > <infinispan> > <namedCache name="withLoaderDefaults"> > <persistence> > <store class="org.infinispan.persistence.file.SingleFileStore"> > <properties> > <property name="location" value="/tmp/Another-FileCacheStore-Location" /> > </properties> > </store> > </persistence> > </namedCache> > </infinispan> > {code} > is converted to: > {code} > <infinispan> > <threads/> > <cache-container name="DefaultCacheManager"> > <jmx/> > <local-cache name="withLoaderDefaults"> > <transaction mode="NONE"/> > <persistence> > <file-store path="/tmp/Another-FileCacheStore-Location"> > <property name="location"> > /tmp/Another-FileCacheStore-Location > </property> > </file-store> > </persistence> > </local-cache> > </cache-container> > </infinispan> > {code} > Also, if the value of location {{property}} is set to e.g. > {noformat} > ${java.io.tmpdir} > {noformat} > , then the evaluated value is placed in the generated xml. > So the following xml: > {code} > <infinispan> > <namedCache name="withLoaderDefaults"> > <persistence> > <store class="org.infinispan.persistence.file.SingleFileStore"> > <properties> > <property name="location" value="${java.io.tmpdir}" /> > </properties> > </store> > </persistence> > </namedCache> > </infinispan> > {code} > is converted to: > {code} > <infinispan> > <threads/> > <cache-container name="DefaultCacheManager"> > <jmx/> > <local-cache name="withLoaderDefaults"> > <transaction mode="NONE"/> > <persistence> > <file-store path="/tmp"> > <property name="location"> > /tmp > </property> > </file-store> > </persistence> > </local-cache> > </cache-container> > </infinispan> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6734) XML serializer serializes the singleFile location property in different way

by Anna Manukyan (JIRA)

[ https://issues.jboss.org/browse/ISPN-6734?page=com.atlassian.jira.plugin.... ] Anna Manukyan reassigned ISPN-6734: ----------------------------------- Assignee: Anna Manukyan > XML serializer serializes the singleFile location property in different way > --------------------------------------------------------------------------- > > Key: ISPN-6734 > URL: https://issues.jboss.org/browse/ISPN-6734 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Reporter: Anna Manukyan > Assignee: Anna Manukyan > > In case when {{persistence}} is configured with {{SingleFileStore}} class and the location is provided with properties, the generated xml contains both the {{path}} attribute and the property with the same value. > This code: > {code} > <infinispan> > <namedCache name="withLoaderDefaults"> > <persistence> > <store class="org.infinispan.persistence.file.SingleFileStore"> > <properties> > <property name="location" value="/tmp/Another-FileCacheStore-Location" /> > </properties> > </store> > </persistence> > </namedCache> > </infinispan> > {code} > is converted to: > {code} > <infinispan> > <threads/> > <cache-container name="DefaultCacheManager"> > <jmx/> > <local-cache name="withLoaderDefaults"> > <transaction mode="NONE"/> > <persistence> > <file-store path="/tmp/Another-FileCacheStore-Location"> > <property name="location"> > /tmp/Another-FileCacheStore-Location > </property> > </file-store> > </persistence> > </local-cache> > </cache-container> > </infinispan> > {code} > Also, if the value of location {{property}} is set to e.g. > {noformat} > ${java.io.tmpdir} > {noformat} > , then the evaluated value is placed in the generated xml. > So the following xml: > {code} > <infinispan> > <namedCache name="withLoaderDefaults"> > <persistence> > <store class="org.infinispan.persistence.file.SingleFileStore"> > <properties> > <property name="location" value="${java.io.tmpdir}" /> > </properties> > </store> > </persistence> > </namedCache> > </infinispan> > {code} > is converted to: > {code} > <infinispan> > <threads/> > <cache-container name="DefaultCacheManager"> > <jmx/> > <local-cache name="withLoaderDefaults"> > <transaction mode="NONE"/> > <persistence> > <file-store path="/tmp"> > <property name="location"> > /tmp > </property> > </file-store> > </persistence> > </local-cache> > </cache-container> > </infinispan> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6736) XML Serializer does not serialize jpaStoreType element

by Anna Manukyan (JIRA)

[ https://issues.jboss.org/browse/ISPN-6736?page=com.atlassian.jira.plugin.... ] Anna Manukyan reassigned ISPN-6736: ----------------------------------- Assignee: Anna Manukyan > XML Serializer does not serialize jpaStoreType element > ------------------------------------------------------ > > Key: ISPN-6736 > URL: https://issues.jboss.org/browse/ISPN-6736 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Reporter: Anna Manukyan > Assignee: Anna Manukyan > > There is no configuration parser available for {{jpaStoreType}} element (http://infinispan.org/schemas/infinispan-cachestore-jpa-config-6.0.xsd ). > When trying to parse the following xml: > {code} > <namedCache name="withJpaStore"> > <persistence passivation="true"> > <jpaStoreType xmlns="urn:infinispan:config:jpa:6.0" persistenceUnitName="TestPersistentName" entityClassName="org.infinispan.tools.customs.CustomDataContainer" > batchSize="80" storeMetadata="false"/> > </persistence> > </namedCache> > {code} > getting the following exception: > {code} > org.infinispan.commons.CacheConfigurationException: ISPN000327: Cannot find a parser for element 'jpaStoreType' in namespace 'urn:infinispan:config:jpa:6.0'. Check that your configuration is up-to date for this version of Infinispan. > at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:157) > at org.infinispan.configuration.parsing.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:37) > at org.infinispan.tools.config.v6.Parser60.parsePersistence(Parser60.java:570) > at org.infinispan.tools.config.v6.Parser60.parseCache(Parser60.java:162) > at org.infinispan.tools.config.v6.Parser60.parseNamedCache(Parser60.java:121) > at org.infinispan.tools.config.v6.Parser60.readElement(Parser60.java:88) > at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:161) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:141) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:128) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:115) > at org.infinispan.tools.config.ConfigurationConverter.convert(ConfigurationConverter.java:27) > at org.infinispan.tools.ConfigurationConverterTest.testConversionAndSerializationFrom60(ConfigurationConverterTest.java:55) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) > at org.testng.SuiteRunner.run(SuiteRunner.java:254) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) > at org.testng.TestNG.run(TestNG.java:1057) > at org.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:72) > at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:122) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6736) XML Serializer does not serialize jpaStoreType element

by Anna Manukyan (JIRA)

[ https://issues.jboss.org/browse/ISPN-6736?page=com.atlassian.jira.plugin.... ] Anna Manukyan updated ISPN-6736: -------------------------------- Status: Open (was: New) > XML Serializer does not serialize jpaStoreType element > ------------------------------------------------------ > > Key: ISPN-6736 > URL: https://issues.jboss.org/browse/ISPN-6736 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Reporter: Anna Manukyan > Assignee: Anna Manukyan > > There is no configuration parser available for {{jpaStoreType}} element (http://infinispan.org/schemas/infinispan-cachestore-jpa-config-6.0.xsd ). > When trying to parse the following xml: > {code} > <namedCache name="withJpaStore"> > <persistence passivation="true"> > <jpaStoreType xmlns="urn:infinispan:config:jpa:6.0" persistenceUnitName="TestPersistentName" entityClassName="org.infinispan.tools.customs.CustomDataContainer" > batchSize="80" storeMetadata="false"/> > </persistence> > </namedCache> > {code} > getting the following exception: > {code} > org.infinispan.commons.CacheConfigurationException: ISPN000327: Cannot find a parser for element 'jpaStoreType' in namespace 'urn:infinispan:config:jpa:6.0'. Check that your configuration is up-to date for this version of Infinispan. > at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:157) > at org.infinispan.configuration.parsing.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:37) > at org.infinispan.tools.config.v6.Parser60.parsePersistence(Parser60.java:570) > at org.infinispan.tools.config.v6.Parser60.parseCache(Parser60.java:162) > at org.infinispan.tools.config.v6.Parser60.parseNamedCache(Parser60.java:121) > at org.infinispan.tools.config.v6.Parser60.readElement(Parser60.java:88) > at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:161) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:141) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:128) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:115) > at org.infinispan.tools.config.ConfigurationConverter.convert(ConfigurationConverter.java:27) > at org.infinispan.tools.ConfigurationConverterTest.testConversionAndSerializationFrom60(ConfigurationConverterTest.java:55) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) > at org.testng.SuiteRunner.run(SuiteRunner.java:254) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) > at org.testng.TestNG.run(TestNG.java:1057) > at org.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:72) > at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:122) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6846) Script filter_failed_logs.sh doesn't work with the new test suite listeners

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-6846?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-6846: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Script filter_failed_logs.sh doesn't work with the new test suite listeners > --------------------------------------------------------------------------- > > Key: ISPN-6846 > URL: https://issues.jboss.org/browse/ISPN-6846 > Project: Infinispan > Issue Type: Bug > Components: Build process > Affects Versions: 9.0.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.0.0.Alpha4 > > > CI uses {{filter_failed_logs.sh}} to find and filter the logs of failed tests in the Trace build. Unfortunately the script wasn't updated by ISPN-6364 (or ISPN-6609), so it doesn't find any failures. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6848) HotRod client testsuite crashes with trace logging enabled

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-6848?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-6848: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > HotRod client testsuite crashes with trace logging enabled > ---------------------------------------------------------- > > Key: ISPN-6848 > URL: https://issues.jboss.org/browse/ISPN-6848 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.0.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 9.0.0.Alpha4 > > > {{HotRodEncoder}} logs the entire contents of the buffer before writing it to the socket, and the allocations cause an OOME. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-14) Allow aliases for enum constants if option 'allow_alias' is true

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-14?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on IPROTO-14: ------------------------------------- The current version of the square proto parser makes it hard to implement right now. We'll have to see if we can upgrade. > Allow aliases for enum constants if option 'allow_alias' is true > ---------------------------------------------------------------- > > Key: IPROTO-14 > URL: https://issues.jboss.org/browse/IPROTO-14 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 3.0.6.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 4.0.0.Alpha1, 4.0.0.Final > > > Duplicate constant numbers are not usually allowed, but the the following should be allowed (based on the presence of 'allow_alias' option. > {code} > enum EnumAllowingAlias { > option allow_alias = true; > UNKNOWN = 0; > STARTED = 1; > RUNNING = 1; > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-14) Allow aliases for enum constants if option 'allow_alias' is true

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-14?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-14: -------------------------------- Fix Version/s: 4.0.0.Alpha1 4.0.0.Final > Allow aliases for enum constants if option 'allow_alias' is true > ---------------------------------------------------------------- > > Key: IPROTO-14 > URL: https://issues.jboss.org/browse/IPROTO-14 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 3.0.6.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 4.0.0.Alpha1, 4.0.0.Final > > > Duplicate constant numbers are not usually allowed, but the the following should be allowed (based on the presence of 'allow_alias' option. > {code} > enum EnumAllowingAlias { > option allow_alias = true; > UNKNOWN = 0; > STARTED = 1; > RUNNING = 1; > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-14) Allow aliases for enum constants if option 'allow_alias' is true

by Adrian Nistor (JIRA)

Adrian Nistor created IPROTO-14: ----------------------------------- Summary: Allow aliases for enum constants if option 'allow_alias' is true Key: IPROTO-14 URL: https://issues.jboss.org/browse/IPROTO-14 Project: Infinispan ProtoStream Issue Type: Bug Affects Versions: 3.0.6.Final Reporter: Adrian Nistor Duplicate constant numbers are not usually allowed, but the the following should be allowed (based on the presence of 'allow_alias' option. {code} enum EnumAllowingAlias { option allow_alias = true; UNKNOWN = 0; STARTED = 1; RUNNING = 1; } {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-14) Allow aliases for enum constants if option 'allow_alias' is true

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-14?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-14: -------------------------------- Status: Open (was: New) > Allow aliases for enum constants if option 'allow_alias' is true > ---------------------------------------------------------------- > > Key: IPROTO-14 > URL: https://issues.jboss.org/browse/IPROTO-14 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 3.0.6.Final > Reporter: Adrian Nistor > > Duplicate constant numbers are not usually allowed, but the the following should be allowed (based on the presence of 'allow_alias' option. > {code} > enum EnumAllowingAlias { > option allow_alias = true; > UNKNOWN = 0; > STARTED = 1; > RUNNING = 1; > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 July 2016