March 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11435) The server sometimes doesn't start all the caches

by Dan Berindei (Jira)

Dan Berindei created ISPN-11435: ----------------------------------- Summary: The server sometimes doesn't start all the caches Key: ISPN-11435 URL: https://issues.redhat.com/browse/ISPN-11435 Project: Infinispan Issue Type: Bug Components: Server Affects Versions: 11.0.0.Alpha2, 10.1.3.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 10.1.4.Final, 11.0.0.Dev03 Our regression tests are reporting throughput variations between builds with no significant differences, and we tracked it down to some servers not starting all the caches. {{HotRodServer}} is currently responsible for starting all the defined caches in the {{preStartCaches()}} method. We might want to move this functionality to the generic server or to {{DefaultCacheManager}} itself. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11430) Align microprofile metrics and config artifact versions with latest Wildfly

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11430?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11430: --------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8011 (was: https://github.com/infinispan/infinispan/pull/7963) > Align microprofile metrics and config artifact versions with latest Wildfly > --------------------------------------------------------------------------- > > Key: ISPN-11430 > URL: https://issues.redhat.com/browse/ISPN-11430 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management > Affects Versions: 11.0.0.Alpha2 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Dev03 > > > Need to use the same versions used by Wildlfy latest for smooth integration: > microprofile-config-api: 1.4 > microprofile-metrics-api: 2.3 > smallrye-config: 1.6.2 > smallrye-metrics: 2.4.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11434) Counter creation should be non blocking

by Will Burns (Jira)

Will Burns created ISPN-11434: --------------------------------- Summary: Counter creation should be non blocking Key: ISPN-11434 URL: https://issues.redhat.com/browse/ISPN-11434 Project: Infinispan Issue Type: Sub-task Reporter: Will Burns Assignee: Will Burns Retrieval of a counter can block when it is first created. Counters are created at runtime very often and we need a non blocking solution to handle this. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11433) DB2TableManager is missing segmentColumnName parameter

by Gustavo Lira e Silva (Jira)

[ https://issues.redhat.com/browse/ISPN-11433?page=com.atlassian.jira.plugi... ] Gustavo Lira e Silva updated ISPN-11433: ---------------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8009, https://github.com/infinispan/infinispan/pull/8010 (was: https://github.com/infinispan/infinispan/pull/8009) > DB2TableManager is missing segmentColumnName parameter > ------------------------------------------------------ > > Key: ISPN-11433 > URL: https://issues.redhat.com/browse/ISPN-11433 > Project: Infinispan > Issue Type: Bug > Affects Versions: 11.0.0.Alpha2 > Reporter: Gustavo Lira e Silva > Assignee: Gustavo Lira e Silva > Priority: Major > > https://github.com/infinispan/infinispan/blob/master/persistence/jdbc/src... line has 5 {{$s}} and only 4 parameters, because of that we are receiving MissingFormatArgumentException: Format specifier '%s' -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11433) DB2TableManager is missing segmentColumnName parameter

by Gustavo Lira e Silva (Jira)

[ https://issues.redhat.com/browse/ISPN-11433?page=com.atlassian.jira.plugi... ] Gustavo Lira e Silva updated ISPN-11433: ---------------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8009 > DB2TableManager is missing segmentColumnName parameter > ------------------------------------------------------ > > Key: ISPN-11433 > URL: https://issues.redhat.com/browse/ISPN-11433 > Project: Infinispan > Issue Type: Bug > Affects Versions: 11.0.0.Alpha2 > Reporter: Gustavo Lira e Silva > Assignee: Gustavo Lira e Silva > Priority: Major > > https://github.com/infinispan/infinispan/blob/master/persistence/jdbc/src... line has 5 {{$s}} and only 4 parameters, because of that we are receiving MissingFormatArgumentException: Format specifier '%s' -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11433) DB2TableManager throwing MissingFormatArgumentException: Format specifier '%s'

by Gustavo Lira e Silva (Jira)

Gustavo Lira e Silva created ISPN-11433: ------------------------------------------- Summary: DB2TableManager throwing MissingFormatArgumentException: Format specifier '%s' Key: ISPN-11433 URL: https://issues.redhat.com/browse/ISPN-11433 Project: Infinispan Issue Type: Bug Affects Versions: 11.0.0.Alpha2 Reporter: Gustavo Lira e Silva Assignee: Gustavo Lira e Silva https://github.com/infinispan/infinispan/blob/master/persistence/jdbc/src... line has 5 {{$s}} and only 4 parameters, because of that we are receiving MissingFormatArgumentException: Format specifier '%s' -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11433) DB2TableManager is missing segmentColumnName parameter

by Gustavo Lira e Silva (Jira)

[ https://issues.redhat.com/browse/ISPN-11433?page=com.atlassian.jira.plugi... ] Gustavo Lira e Silva updated ISPN-11433: ---------------------------------------- Summary: DB2TableManager is missing segmentColumnName parameter (was: DB2TableManager throwing MissingFormatArgumentException: Format specifier '%s') > DB2TableManager is missing segmentColumnName parameter > ------------------------------------------------------ > > Key: ISPN-11433 > URL: https://issues.redhat.com/browse/ISPN-11433 > Project: Infinispan > Issue Type: Bug > Affects Versions: 11.0.0.Alpha2 > Reporter: Gustavo Lira e Silva > Assignee: Gustavo Lira e Silva > Priority: Major > > https://github.com/infinispan/infinispan/blob/master/persistence/jdbc/src... line has 5 {{$s}} and only 4 parameters, because of that we are receiving MissingFormatArgumentException: Format specifier '%s' -- 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 updated ISPN-11428: ------------------------------- Status: Open (was: New) > 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-11428) Docs: JGroups Config Updates

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11428?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11428: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8008 > 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-11205) DataSource support in the Server

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11205?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11205: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8007 > DataSource support in the Server > -------------------------------- > > Key: ISPN-11205 > URL: https://issues.redhat.com/browse/ISPN-11205 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Affects Versions: 10.1.1.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Dev03, 11.0.0.Final > > > The server needs to have the ability to manage datasources/connection pools to databases so that they can be shared by multiple cache stores/loaders. > We should use Agroal for this. -- 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