March 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11448) Upgrade to SB 2.2.5.RELEASE

by Katia Aresti (Jira)

Katia Aresti created ISPN-11448: ----------------------------------- Summary: Upgrade to SB 2.2.5.RELEASE Key: ISPN-11448 URL: https://issues.redhat.com/browse/ISPN-11448 Project: Infinispan Issue Type: Component Upgrade Components: Spring Integration Affects Versions: 10.1.3.Final, 9.4.18.Final Reporter: Katia Aresti Assignee: Katia Aresti Upgrade starters with Infinispan 10 and 9.4 to Spring-Boot 2.2.5.RELEASE -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11447) Docs: REST API get cache config templates

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11447?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11447: ------------------------------- Summary: Docs: REST API get cache config templates (was: Docs: Enabling statistics, microprofile metrics, jmx) > Docs: REST API get cache config templates > ----------------------------------------- > > Key: ISPN-11447 > URL: https://issues.redhat.com/browse/ISPN-11447 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Enable statistics on cache manager and cache levels. Enable gauges and histograms. Enable JMX. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11447) Docs: Enabling statistics, microprofile metrics, jmx

by Donald Naro (Jira)

Donald Naro created ISPN-11447: ---------------------------------- Summary: Docs: Enabling statistics, microprofile metrics, jmx Key: ISPN-11447 URL: https://issues.redhat.com/browse/ISPN-11447 Project: Infinispan Issue Type: Enhancement Components: Documentation Reporter: Donald Naro Assignee: Donald Naro Enable statistics on cache manager and cache levels. Enable gauges and histograms. Enable JMX. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11447) Docs: REST API get cache config templates

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11447?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11447: ------------------------------- Description: /v2/cache-managers/{name}/cache-configs/templates (was: Enable statistics on cache manager and cache levels. Enable gauges and histograms. Enable JMX.) > Docs: REST API get cache config templates > ----------------------------------------- > > Key: ISPN-11447 > URL: https://issues.redhat.com/browse/ISPN-11447 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > /v2/cache-managers/{name}/cache-configs/templates -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11447) Docs: REST API get cache config templates

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11447?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11447: ------------------------------- Git Pull Request: (was: https://github.com/infinispan/infinispan/pull/7979) > Docs: REST API get cache config templates > ----------------------------------------- > > Key: ISPN-11447 > URL: https://issues.redhat.com/browse/ISPN-11447 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > /v2/cache-managers/{name}/cache-configs/templates -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11444) Server Driver Support for JUnit5

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11444?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11444: -------------------------------- Description: Junit5 extension for testing > Server Driver Support for JUnit5 > -------------------------------- > > Key: ISPN-11444 > URL: https://issues.redhat.com/browse/ISPN-11444 > Project: Infinispan > Issue Type: Task > Components: Test Suite > Affects Versions: 10.1.3.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Labels: test > > Junit5 extension for testing -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11428) Docs: JGroups Config Updates

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11428?page=com.atlassian.jira.plugi... ] Donald Naro commented on ISPN-11428: ------------------------------------ Review draft at: http://file.rdu.redhat.com/dnaro/ISPN-11428/titles/configuring/configurin... [~wfink] fyi ^ > Docs: JGroups Config Updates > ---------------------------- > > Key: ISPN-11428 > URL: https://issues.redhat.com/browse/ISPN-11428 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > From Wolf: > ISPN docs > https://infinispan.org/docs/dev/titles/configuring/configuring.html#clust... > show information about improve performance and mention jgroups-default.xml .... > but no idea where to find it > name is confusing should be clarified > there is no jgroups-defaults for the server it is default-configs/default-jgroups-<stack>.xml > there is no infinispan-jgroups.xml as well in core.jar > so the (i) box is just confusion > 5. Setting up Cluster Transport > 5.1.2 Default stack > Confusing as the default-jgroups-[tcp|udp].xml show something more specific and more attributes. > What is the purpose of this simplified stack? If the default xmls are used I would not include the example here, just point to the ispn-core.jar/default-configs which are listed in 5.1.1 > The (i) box is confusing as there is no heint where to find it. > Also the ispn-core.jar does not include a jgroups-default.xml or infinspan-jgroups.xml. The embedded stuff seems to point to the same defaults as 5.1.1. > If there are no real properties which are the default I would remove the box > 5.2 inline stack > The hint box “Use inheritance …” should point to 5.3 and here it should mention that this is a fully created stack with the complete configuration. > 5.3 Adjusting > For 2. You should mention that this can be “udp” or “tcp” used by default, not only a self created one > Note that <VERIFY_SUSPECT> is replaced, which means all attributes are back to defaults. > Example might include RELAY as it can be used without any position to be appended at the end. This is most useful for XSite replication (example is infnispan-xsite.xml) > Explain that the stack.position is the name of any protocol. > Not sure what happen if it is not found! > 5.5.1 system properties default jgroups > UDP > Jgroups.udp.* → no udp ! > Missing > Address → jgroups.bind.address,jgroups.udp.address defaults to SITE_LOCAL > Port → jgroups.bind.port,jgroups.udp.port defaults to “0” automatically > TCP > Address can use jgroups.bind.address and the default is SITE_LOCAL not 127.0.0.1 > Port can use jgroups.bind.port > Jgroups.udp.* → no udp ! > EC2, kubernetes > Same here for address and port > 6 Discovery > Should we list FILE_PING as well as this is the simple base for discovery and already shared with customers? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11393) Docs: Enabling statistics, microprofile metrics, jmx

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11393?page=com.atlassian.jira.plugi... ] Donald Naro commented on ISPN-11393: ------------------------------------ Review drafts: http://file.rdu.redhat.com/dnaro/ISPN-11393/titles/configuring/configurin... http://file.rdu.redhat.com/dnaro/ISPN-11393/titles/server/server.html#sta... > Docs: Enabling statistics, microprofile metrics, jmx > ---------------------------------------------------- > > Key: ISPN-11393 > URL: https://issues.redhat.com/browse/ISPN-11393 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Enable statistics on cache manager and cache levels. Enable gauges and histograms. Enable JMX. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10835) Docs: Cross-Site Repl with IRAC

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10835?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-10835: ------------------------------- Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38, DataGrid Sprint #39, DataGrid Sprint #41) > Docs: Cross-Site Repl with IRAC > ------------------------------- > > Key: ISPN-10835 > URL: https://issues.redhat.com/browse/ISPN-10835 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Update cross-site replication docs for IRAC conflict resolution. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11446) Always set a default request MediaType for caches

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11446?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11446: ------------------------------------- Description: *Background*: when a cache is created, it does not have a default request type inside its internal Key/Value DataConversion objects, so no transcoding will be attempted during its operations. When decorated with _{{.withMediaType(MediaType key, MediaType value)}}_, a new cache instance is produced setting the request type internally, and all operations will be converted from the storage media type to this request media type (when reading), or from the request media type to storage media type (when writing). *Drawback*: When a cache is used through any remote endpoint, it is always decorated since remote clients are able to communicate the request format, but when a cache is used directly in the same JVM the request type is _null_, so no transcoding is done, unless the cache is decorated with the required type. *Change*: This issue will change the default request type for all caches to _{{application/x-java-object}}_, so transcoding can be done in embedded caches without the need to decorate, it's enough to set the storage type in the configuration. was: *Background*: when a cache is created, it does not have a default request type inside its internal Key/Value DataConversion objects, so no transcoding will be attempted during its operations. When decorated with _{{.withMediaType(MediaType key, MediaType value)}}_, a new cache instance is produced setting the request type internally, and all operations will be converted from the storage media type to this request media type (when reading), or from the request media type to storage media type (when writing). *Drawback*: When a cache is used through any remote endpoint, it is always decorated since remote clients are able to communicate the request format, but when a cache is used directly in the same JVM the request type is _null_, so no transcoding is done, unless the cache is decorated with the required type. *Change*: This issue will change the default request type for all caches to _{{application/x-java-object}}_, so transcoding can be done in embedded caches as well, without the need to decorate: it's enough to set the storage type in the configuration. > Always set a default request MediaType for caches > ------------------------------------------------- > > Key: ISPN-11446 > URL: https://issues.redhat.com/browse/ISPN-11446 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 11.0.0.Alpha2 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > *Background*: when a cache is created, it does not have a default request type inside its internal Key/Value DataConversion objects, so no transcoding will be attempted during its operations. > When decorated with _{{.withMediaType(MediaType key, MediaType value)}}_, a new cache instance is produced setting the request type internally, and all operations will be converted from the storage media type to this request media type (when reading), or from the request media type to storage media type (when writing). > *Drawback*: When a cache is used through any remote endpoint, it is always decorated since remote clients are able to communicate the request format, but when a cache is used directly in the same JVM the request type is _null_, so no transcoding is done, unless the cache is decorated with the required type. > *Change*: This issue will change the default request type for all caches to _{{application/x-java-object}}_, so transcoding can be done in embedded caches without the need to decorate, it's enough to set the storage type in the configuration. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2020