March 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11511) Custom branding creates ambiguous logs on server startup

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11511?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11511: ----------------------------------- Status: Open (was: New) > Custom branding creates ambiguous logs on server startup > -------------------------------------------------------- > > Key: ISPN-11511 > URL: https://issues.redhat.com/browse/ISPN-11511 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.1.5.Final, 11.0.0.Dev03 > Reporter: Pavel Drobek > Assignee: Tristan Tarrant > Priority: Major > > Server starts up with following message in the logs: > {code} > INFO (main) [org.infinispan.SERVER] ISPN080001: Red Hat Data Grid Server 10.1.5.Final-redhat-00001 started in 4708ms > {code} > Expected message: > {code} > INFO (main) [org.infinispan.SERVER] ISPN080001: Red Hat Data Grid Server 8.0.0.GA started in 4708ms > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11511) Custom branding creates ambiguous logs on server startup

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11511?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11511: ----------------------------------- Security: (was: Red Hat Internal) > Custom branding creates ambiguous logs on server startup > -------------------------------------------------------- > > Key: ISPN-11511 > URL: https://issues.redhat.com/browse/ISPN-11511 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.1.5.Final, 11.0.0.Dev03 > Reporter: Pavel Drobek > Assignee: Tristan Tarrant > Priority: Major > > Server starts up with following message in the logs: > {code} > INFO (main) [org.infinispan.SERVER] ISPN080001: Red Hat Data Grid Server 10.1.5.Final-redhat-00001 started in 4708ms > {code} > Expected message: > {code} > INFO (main) [org.infinispan.SERVER] ISPN080001: Red Hat Data Grid Server 8.0.0.GA started in 4708ms > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11474) RecoveryManager API should be non blocking

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11474?page=com.atlassian.jira.plugi... ] Will Burns resolved ISPN-11474. ------------------------------- Resolution: Done > RecoveryManager API should be non blocking > ------------------------------------------ > > Key: ISPN-11474 > URL: https://issues.redhat.com/browse/ISPN-11474 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev03 > > > RecoverManager, which is internal only, has a blocking API which can pass a sync parameter. Instead we should change the API to be non blocking and let callers decide if they want to wait or not on it. This allows us to clean up callers who may be able to use this in a non blocking fashion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11474) RecoveryManager API should be non blocking

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11474?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11474: ------------------------------ Fix Version/s: 11.0.0.Dev03 (was: 11.0.0.Dev04) > RecoveryManager API should be non blocking > ------------------------------------------ > > Key: ISPN-11474 > URL: https://issues.redhat.com/browse/ISPN-11474 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev03 > > > RecoverManager, which is internal only, has a blocking API which can pass a sync parameter. Instead we should change the API to be non blocking and let callers decide if they want to wait or not on it. This allows us to clean up callers who may be able to use this in a non blocking fashion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11510) Convert detection of blocking or non blocking threads

by Will Burns (Jira)

Will Burns created ISPN-11510: --------------------------------- Summary: Convert detection of blocking or non blocking threads Key: ISPN-11510 URL: https://issues.redhat.com/browse/ISPN-11510 Project: Infinispan Issue Type: Sub-task Reporter: Will Burns Assignee: Will Burns Unfortunately detecting a blocking thread by name is very fragile as a user can change the name of the threads. Also a non blocking thread is detected by checking the implementation of the thread. This will not work for Java 15 with loom as we may not have a thread but rather a fiber. We should detect these instead by using a thread group which will work for both and be more explicit. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11509) Support JDK fibers

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-11509: -------------------------------------- Summary: Support JDK fibers Key: ISPN-11509 URL: https://issues.redhat.com/browse/ISPN-11509 Project: Infinispan Issue Type: Enhancement Components: Build, Core Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 11.0.0.Dev04 Project Loom adds support for lightweight/virtual threads. We should have a cross-version way to create threads which can support this. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11489) TransactionCoordinator updated for non blocking

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11489?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11489: ------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/7997, https://github.com/infinispan/infinispan/pull/8080 (was: https://github.com/infinispan/infinispan/pull/7997) > TransactionCoordinator updated for non blocking > ----------------------------------------------- > > Key: ISPN-11489 > URL: https://issues.redhat.com/browse/ISPN-11489 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev04 > > > TransactionCoordinator is utilized when working with transactions. Unfortunately due to transaction API being inherently blocking, we need to make some exceptions to how this is handled. > # TransactionCoordinator should only be invokable by a blocking method, the inverse of the PersistenceManagerImpl > # We should invoke all the non blocking code of TransactionCoordinator in a non blocking thread and then block on its completion in the blocking thread. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11482) Provide way for ClusterExecutor to use non blocking thread

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11482?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11482: ------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/8080 > Provide way for ClusterExecutor to use non blocking thread > ---------------------------------------------------------- > > Key: ISPN-11482 > URL: https://issues.redhat.com/browse/ISPN-11482 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > > https://github.com/infinispan/infinispan/pull/7997#discussion_r394122227 changes cluster executor to run tasks on the blocking executor. Unfortunately since a user can run any arbitrary code we don't know if it will block or not. We should provide some way to run non blocking code more easily. Maybe add a new API method that is non blocking? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11443) PersistenceManagerImpl thread checks need to be updated

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11443?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11443: ------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/8022, https://github.com/infinispan/infinispan/pull/8080 (was: https://github.com/infinispan/infinispan/pull/8022) > PersistenceManagerImpl thread checks need to be updated > ------------------------------------------------------- > > Key: ISPN-11443 > URL: https://issues.redhat.com/browse/ISPN-11443 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Priority: Major > Fix For: 11.0.0.Dev04 > > > We added a NonBlockingThread interface that a non blocking thread implements in Infinispan. The checks need to be updated to the new thread pools. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11508) JDK-specific way to obtain process info

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-11508: -------------------------------------- Summary: JDK-specific way to obtain process info Key: ISPN-11508 URL: https://issues.redhat.com/browse/ISPN-11508 Project: Infinispan Issue Type: Enhancement Reporter: Tristan Tarrant Assignee: Tristan Tarrant JDK 9 has introduced ProcessHandle as a way to obtain process info (PID, etc). We should use that instead of hacks based on the RuntimeMXBean -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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