[JBoss JIRA] (ISPN-12030) BlockHound is not active on JDK 13/14
by Dan Berindei (Jira)
Dan Berindei created ISPN-12030:
-----------------------------------
Summary: BlockHound is not active on JDK 13/14
Key: ISPN-12030
URL: https://issues.redhat.com/browse/ISPN-12030
Project: Infinispan
Issue Type: Bug
Components: Build, Test Suite
Affects Versions: 11.0.0.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 11.0.1.Final
BlockHound cannot instrument native methods on JDK 13+
{noformat}
15:04:47,001 FATAL (Thread-0) [Infinispan-TEST] Throwable was not caught in thread Thread[Thread-0,5,main] - exception is: java.lang.IllegalStateException: The instrumentation have failed.
It looks like you're running on JDK 13+.
You need to add '-XX:+AllowRedefinitionToAddDeleteMethods' JVM flag.
See https://github.com/reactor/BlockHound/issues/33 for more info.
{noformat}
Maven profile {{java13-test}} is supposed to add flag -XX:+AllowRedefinitionToAddDeleteMethods to the fork JVM, but it doesn't work because the activation condition is incomplete (missing a {{)}} after the comma).
The profile also tries to add the flag when the {{java8-test}} profile is selected from the command line, so adding the missing {{)}} is not enough.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-12029) Replace Blocking Executor with an EnhancedQueueExecutor
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-12029?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-12029:
------------------------------
Status: Open (was: New)
> Replace Blocking Executor with an EnhancedQueueExecutor
> -------------------------------------------------------
>
> Key: ISPN-12029
> URL: https://issues.redhat.com/browse/ISPN-12029
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 12.0.0.Final, 11.0.1.Final
>
>
> The blocking executor today uses a simple ThreadPoolExecutor. Unfortunately, this means that we will eventually start all configured threads (since core = max and we require a queue). Setting core size to less than max is not desirable as well as it will enqueue additional tasks rather than spawn a thread.
>
> The EnhancedQueueExecutor does exactly what we want and also has some additional features. We should utilize this which will keep our blocking thread pool size down during times of less activity.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-12029) Replace Blocking Executor with an EnhancedQueueExecutor
by Will Burns (Jira)
Will Burns created ISPN-12029:
---------------------------------
Summary: Replace Blocking Executor with an EnhancedQueueExecutor
Key: ISPN-12029
URL: https://issues.redhat.com/browse/ISPN-12029
Project: Infinispan
Issue Type: Enhancement
Components: Core
Reporter: Will Burns
Assignee: Will Burns
Fix For: 12.0.0.Final, 11.0.1.Final
The blocking executor today uses a simple ThreadPoolExecutor. Unfortunately, this means that we will eventually start all configured threads (since core = max and we require a queue). Setting core size to less than max is not desirable as well as it will enqueue additional tasks rather than spawn a thread.
The EnhancedQueueExecutor does exactly what we want and also has some additional features. We should utilize this which will keep our blocking thread pool size down during times of less activity.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-12002) Rolling Upgrades location aware data retrieving
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12002?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12002:
-------------------------------------
Status: Open (was: New)
> Rolling Upgrades location aware data retrieving
> -----------------------------------------------
>
> Key: ISPN-12002
> URL: https://issues.redhat.com/browse/ISPN-12002
> Project: Infinispan
> Issue Type: Enhancement
> Components: Remote Protocols
> Affects Versions: 9.4.19.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> Currently the Rolling upgrades data retrieval is done using several tasks in parallel, where each task retrieves from the source cluster a subset of the data from one or more segments.
> Each task should only retrieve data from segments that are confined to a single source server, to avoid further remote calls inside the source server.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months