June 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6777) Improve Cache Stores configuration screen

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6777?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-6777: ------------------------------- Status: Open (was: New) > Improve Cache Stores configuration screen > ----------------------------------------- > > Key: ISPN-6777 > URL: https://issues.jboss.org/browse/ISPN-6777 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Reporter: Pedro Zapata > Assignee: Ryan Emerson > Fix For: 9.0.0.Beta2 > > > Infinispan administrators should be able to select and configure any cache store easily, without having to enter class names and other free-form properties. > Only one tab ‘Cache store’ will be displayed in the cache configuration options > The user will have the option to select a type of store from the list (Single File, LevelDB, …) + the option ‘NONE’ > When the option is changed, all the generic + specific properties will be shown below. > Properties should be presented as combos, if they are enumerable. For example, class (if there’s a way of filtering all implementing classes in classpath). > Sensible defaults should be set. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6811) The deadlock-detection-spin attribute is not allowed in Client-Server configuration.

by Christian Huffman (JIRA)

[ https://issues.jboss.org/browse/ISPN-6811?page=com.atlassian.jira.plugin.... ] Christian Huffman updated ISPN-6811: ------------------------------------ Affects Version/s: 8.2.2.Final > The deadlock-detection-spin attribute is not allowed in Client-Server configuration. > ------------------------------------------------------------------------------------ > > Key: ISPN-6811 > URL: https://issues.jboss.org/browse/ISPN-6811 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 8.2.2.Final > Reporter: Christian Huffman > > When attempting to define the `deadlock-detection-spin` attribute in Client-Server mode an error is thrown: > Standalone.xml: > {code} > <local-cache name="default" start="EAGER" deadlock-detection-spin="1000" > > <locking acquire-timeout="30000" concurrency-level="1000" striping="false"/> > <transaction mode="NON_XA"/> > </local-cache> > {code} > The following error is thrown: > {code} > 16:16:13,674 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:131) > at org.jboss.as.server.ServerService.boot(ServerService.java:356) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299) > at java.lang.Thread.run(Thread.java:745) > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[172,17] > Message: WFLYCTL0197: Unexpected attribute 'deadlock-detection-spin' encountered > at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:117) > at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.parseCacheAttribute(InfinispanSubsystemXMLReader.java:649) > at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.parseLocalCache(InfinispanSubsystemXMLReader.java:715) > at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.parseContainer(InfinispanSubsystemXMLReader.java:244) > at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.readElement(InfinispanSubsystemXMLReader.java:94) > at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.readElement(InfinispanSubsystemXMLReader.java:67) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) > at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) > at org.jboss.as.server.parsing.StandaloneXml_4.parseServerProfile(StandaloneXml_4.java:546) > at org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:242) > at org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:141) > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:103) > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) > ... 3 more > 16:16:13,675 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6811) The deadlock-detection-spin attribute is not allowed in Client-Server configuration.

by Christian Huffman (JIRA)

Christian Huffman created ISPN-6811: --------------------------------------- Summary: The deadlock-detection-spin attribute is not allowed in Client-Server configuration. Key: ISPN-6811 URL: https://issues.jboss.org/browse/ISPN-6811 Project: Infinispan Issue Type: Bug Components: Configuration Reporter: Christian Huffman When attempting to define the `deadlock-detection-spin` attribute in Client-Server mode an error is thrown: Standalone.xml: {code} <local-cache name="default" start="EAGER" deadlock-detection-spin="1000" > <locking acquire-timeout="30000" concurrency-level="1000" striping="false"/> <transaction mode="NON_XA"/> </local-cache> {code} The following error is thrown: {code} 16:16:13,674 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:131) at org.jboss.as.server.ServerService.boot(ServerService.java:356) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299) at java.lang.Thread.run(Thread.java:745) Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[172,17] Message: WFLYCTL0197: Unexpected attribute 'deadlock-detection-spin' encountered at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:117) at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.parseCacheAttribute(InfinispanSubsystemXMLReader.java:649) at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.parseLocalCache(InfinispanSubsystemXMLReader.java:715) at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.parseContainer(InfinispanSubsystemXMLReader.java:244) at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.readElement(InfinispanSubsystemXMLReader.java:94) at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.readElement(InfinispanSubsystemXMLReader.java:67) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) at org.jboss.as.server.parsing.StandaloneXml_4.parseServerProfile(StandaloneXml_4.java:546) at org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:242) at org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:141) at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:103) at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) ... 3 more 16:16:13,675 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-3) Add support for map data type

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-3?page=com.atlassian.jira.plugin.s... ] Adrian Nistor updated IPROTO-3: ------------------------------- Fix Version/s: 4.0.0.Final > Add support for map data type > ----------------------------- > > Key: IPROTO-3 > URL: https://issues.jboss.org/browse/IPROTO-3 > Project: Infinispan ProtoStream > Issue Type: Feature Request > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 4.0.0.Alpha1, 4.0.0.Final > > > See https://developers.google.com/protocol-buffers/docs/proto3#maps -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-8) Default value for enums should not accept strings

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-8?page=com.atlassian.jira.plugin.s... ] Adrian Nistor updated IPROTO-8: ------------------------------- Fix Version/s: 4.0.0.Final > Default value for enums should not accept strings > ------------------------------------------------- > > Key: IPROTO-8 > URL: https://issues.jboss.org/browse/IPROTO-8 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 3.0.5.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 4.0.0.Final > > > The only acceptable default value should be an identifier (no quotes) which is one of the possible values of the enum. Currently we also accept a string literal, but this is due to a bug in protoparser lib. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-5) Add support for 'Any'

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-5?page=com.atlassian.jira.plugin.s... ] Adrian Nistor updated IPROTO-5: ------------------------------- Status: Open (was: New) > Add support for 'Any' > --------------------- > > Key: IPROTO-5 > URL: https://issues.jboss.org/browse/IPROTO-5 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Adrian Nistor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-4) Nested message type definitions should not be allowed in 'extend' declarations

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-4?page=com.atlassian.jira.plugin.s... ] Adrian Nistor updated IPROTO-4: ------------------------------- Status: Open (was: New) > Nested message type definitions should not be allowed in 'extend' declarations > ------------------------------------------------------------------------------ > > Key: IPROTO-4 > URL: https://issues.jboss.org/browse/IPROTO-4 > Project: Infinispan ProtoStream > Issue Type: Bug > Reporter: Adrian Nistor > > The test DescriptorsTest.testNestedMessageInExtend demonstrates these declarations are ignored. But the correct way to handle this is to throw a parsing error similar to protoc. > In proto3 we should ban extend declarations completely. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-4) Nested message type definitions should not be allowed in 'extend' declarations

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-4?page=com.atlassian.jira.plugin.s... ] Adrian Nistor reassigned IPROTO-4: ---------------------------------- Assignee: Adrian Nistor > Nested message type definitions should not be allowed in 'extend' declarations > ------------------------------------------------------------------------------ > > Key: IPROTO-4 > URL: https://issues.jboss.org/browse/IPROTO-4 > Project: Infinispan ProtoStream > Issue Type: Bug > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > The test DescriptorsTest.testNestedMessageInExtend demonstrates these declarations are ignored. But the correct way to handle this is to throw a parsing error similar to protoc. > In proto3 we should ban extend declarations completely. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-2) Add support for packed fields

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-2?page=com.atlassian.jira.plugin.s... ] Adrian Nistor reassigned IPROTO-2: ---------------------------------- Assignee: Adrian Nistor > Add support for packed fields > ----------------------------- > > Key: IPROTO-2 > URL: https://issues.jboss.org/browse/IPROTO-2 > Project: Infinispan ProtoStream > Issue Type: Feature Request > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > See https://developers.google.com/protocol-buffers/docs/encoding#packed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-2) Add support for packed fields

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-2?page=com.atlassian.jira.plugin.s... ] Adrian Nistor updated IPROTO-2: ------------------------------- Status: Open (was: New) > Add support for packed fields > ----------------------------- > > Key: IPROTO-2 > URL: https://issues.jboss.org/browse/IPROTO-2 > Project: Infinispan ProtoStream > Issue Type: Feature Request > Reporter: Adrian Nistor > > See https://developers.google.com/protocol-buffers/docs/encoding#packed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2016