January 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (IPROTO-82) Useless warnings regarding undefined proto schema annotations

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-82?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-82: -------------------------------- Fix Version/s: 4.3.0.Alpha1 4.2.3.Final > Useless warnings regarding undefined proto schema annotations > ------------------------------------------------------------- > > Key: IPROTO-82 > URL: https://issues.jboss.org/browse/IPROTO-82 > Project: Infinispan ProtoStream > Issue Type: Bug > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 4.3.0.Alpha1, 4.2.3.Final > > > Protostream emits the warning "Encountered and ignored and unknown annotation..." whenever it parses the documentation text of a definition which contains (pseudo)annotations that were not defined. These warnings do not always make sense for all use cases of a certain schema. For example a user might have some indexing related annotations that are used by the server, but those same anontations will also be seen by the client when parsing the schema and the client does not need to know or care about them. This means the client does not define them in the Protostream configuration to be parsed, so the parser will complain about them later saying they are unknown. > This issue is benign, as the log message in question is just a WARNing and no exception is thrown, so there is no functional impact on the user app, but it is very noisy and it clogs the log. > The proposed fix is to not emit any such warnings if there are no custom defined annotations in config. If there is at least one custom annotation, then the old behaviour will continue to exist. > An new config flag (AnnotationsConfig.logUndefinedAnnotations - default _true_) is introduced to be able to turn this warning off completely if needed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9880) Docs: Hot Rod Transaction Support Feedback

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9880?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-9880. -------------------------------- Fix Version/s: 10.0.0.Beta1 9.4.7.Final Resolution: Done > Docs: Hot Rod Transaction Support Feedback > ------------------------------------------ > > Key: ISPN-9880 > URL: https://issues.jboss.org/browse/ISPN-9880 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Affects Versions: 10.0.0.Beta1, 9.4.6.Final > Reporter: Don Naro > Assignee: Don Naro > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.7.Final > > > https://access.qa.redhat.com/documentation/en-us/red_hat_data_grid/7.3/ht... > Feedback for on Hot Rod Transaction docs: > Server Guide > - 6.2.6 Transactions > Remove: While it is possible to configure server caches to be transactional, none of the available protocols offer transaction capabilities. > User Guide > - 20.7.21.2.2 Transaction Modes > "The transaction mode names are the same for server configuration and for client settings. > To prevent from confusion it should be clarified here that this is the client setting > and the server will not work correctly if the client use Tx but the server has no Tx setting. > This should fail at runtime if the client request a Tx for a non-tx-cache (but I did not tested this yet)" > - 20.7.21 > "The introducing paragraph and the tip mention that the client side Tx is quasi optimistic. > But there is no highlighted node that the consistence is possibly affected by that. > There should be a warning and a link to the detailed description 20.7.21.4 to makes this as clear as possible." > Additionally: > "to make it simple for the user if you don't highlight to implement a custom TxManager, this is only needed to integrate other implementations. > If not needed, the GenericTxM is the best choice as it will use our TxM inside EAP or the RemoteTxM if there is nothing found. > So this will be 99% of the use cases (or more)" -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9906) Add clustered lock to wildfly modules

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9906?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9906: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6627 > Add clustered lock to wildfly modules > ------------------------------------- > > Key: ISPN-9906 > URL: https://issues.jboss.org/browse/ISPN-9906 > Project: Infinispan > Issue Type: Bug > Components: Clustered Locks > Affects Versions: 9.4.6.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Fix For: 9.4.7.Final > > > Wildfly modules don't include clustered locks jar to be used in embedded mode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9906) Add clustered lock to wildfly modules

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9906?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9906: ------------------------------- Status: Open (was: New) > Add clustered lock to wildfly modules > ------------------------------------- > > Key: ISPN-9906 > URL: https://issues.jboss.org/browse/ISPN-9906 > Project: Infinispan > Issue Type: Bug > Components: Clustered Locks > Affects Versions: 9.4.6.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Fix For: 9.4.7.Final > > > Wildfly modules don't include clustered locks jar to be used in embedded mode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9906) Add clustered lock to wildfly modules

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9906?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9906: ------------------------------- Fix Version/s: 9.4.7.Final > Add clustered lock to wildfly modules > ------------------------------------- > > Key: ISPN-9906 > URL: https://issues.jboss.org/browse/ISPN-9906 > Project: Infinispan > Issue Type: Bug > Components: Clustered Locks > Affects Versions: 9.4.6.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Fix For: 9.4.7.Final > > > Wildfly modules don't include clustered locks jar to be used in embedded mode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9906) Add clustered lock to wildfly modules

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9906?page=com.atlassian.jira.plugin.... ] Katia Aresti reassigned ISPN-9906: ---------------------------------- Assignee: Katia Aresti > Add clustered lock to wildfly modules > ------------------------------------- > > Key: ISPN-9906 > URL: https://issues.jboss.org/browse/ISPN-9906 > Project: Infinispan > Issue Type: Bug > Components: Clustered Locks > Affects Versions: 9.4.6.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Fix For: 9.4.7.Final > > > Wildfly modules don't include clustered locks jar to be used in embedded mode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9906) Add clustered lock to wildfly modules

by Katia Aresti (Jira)

Katia Aresti created ISPN-9906: ---------------------------------- Summary: Add clustered lock to wildfly modules Key: ISPN-9906 URL: https://issues.jboss.org/browse/ISPN-9906 Project: Infinispan Issue Type: Bug Components: Clustered Locks Affects Versions: 9.4.6.Final Reporter: Katia Aresti Wildfly modules don't include clustered locks jar to be used in embedded mode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8772) Update Server Licenses

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-8772?page=com.atlassian.jira.plugin.... ] Ryan Emerson closed ISPN-8772. ------------------------------ Fix Version/s: (was: 9.4.7.Final) Resolution: Out of Date > Update Server Licenses > ---------------------- > > Key: ISPN-8772 > URL: https://issues.jboss.org/browse/ISPN-8772 > Project: Infinispan > Issue Type: Task > Components: Build > Affects Versions: 9.2.0.CR2 > Reporter: Ryan Emerson > Priority: Major > > After upgrading the server to wildfly 11, the server license files have become outdated and should be updated. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9883) Control cluster configuration

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-9883?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes deleted ISPN-9883: ------------------------------------ > Control cluster configuration > ------------------------------ > > Key: ISPN-9883 > URL: https://issues.jboss.org/browse/ISPN-9883 > Project: Infinispan > Issue Type: Feature Request > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > The operator assumes a config map is populated with the configuration to be used. We should support other types of configuration. Proposal: > * type=Custom: the user provides a configmap where the config is located > * type=Statefull: it will start a cluster backed by a stateful set: the data/ directory will be the stable storage > * type=Stateless: it will start a cluster with cloud.xml without stable persistence > * type=Default: no configuration provided, will start a type=Stateless cluster -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-82) Useless warnings regarding undefined proto schema annotations

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-82?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned IPROTO-82: ----------------------------------- Assignee: Adrian Nistor > Useless warnings regarding undefined proto schema annotations > ------------------------------------------------------------- > > Key: IPROTO-82 > URL: https://issues.jboss.org/browse/IPROTO-82 > Project: Infinispan ProtoStream > Issue Type: Bug > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > > Protostream emits the warning "Encountered and ignored and unknown annotation..." whenever it parses the documentation text of a definition which contains (pseudo)annotations that were not defined. These warnings do not always make sense for all use cases of a certain schema. For example a user might have some indexing related annotations that are used by the server, but those same anontations will also be seen by the client when parsing the schema and the client does not need to know or care about them. This means the client does not define them in the Protostream configuration to be parsed, so the parser will complain about them later saying they are unknown. > This issue is benign, as the log message in question is just a WARNing and no exception is thrown, so there is no functional impact on the user app, but it is very noisy and it clogs the log. > The proposed fix is to not emit any such warnings if there are no custom defined annotations in config. If there is at least one custom annotation, then the old behaviour will continue to exist. > An new config flag (AnnotationsConfig.logUndefinedAnnotations - default _true_) is introduced to be able to turn this warning off completely if needed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2019