[JBoss JIRA] (ISPN-11249) Unexpected functionality added by Java8 default interface methods
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-11249?page=com.atlassian.jira.plugi... ]
Ryan Emerson reassigned ISPN-11249:
-----------------------------------
Assignee: Will Burns
> Unexpected functionality added by Java8 default interface methods
> -----------------------------------------------------------------
>
> Key: ISPN-11249
> URL: https://issues.redhat.com/browse/ISPN-11249
> Project: Infinispan
> Issue Type: Bug
> Reporter: Wolf-Dieter Fink
> Assignee: Will Burns
> Priority: Critical
> Fix For: 10.1.3.Final, 11.0.0.Alpha2
>
>
> With Java8 there are interfaces which implement default methods.
> Those defaults are available if not overridden, but the function behind might not be correct because the method was not meant to be implemented.
> There are issues with the transaction and locking because of the remote invocation, so the conditional operation will not work consistent.
> Such methods need to be checked and throw a UnsupportedOperation.
> This appears for the compute(...) methods
> compute(key, BiFunct) -> default to java.util.concurrent.ConcurrentMap interface
> compute() methods with expiration will throw an UnsupportedOperationException as expected.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11377) Change default flow control protocol back to UFC/MFC
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11377?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-11377:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/7938
> Change default flow control protocol back to UFC/MFC
> ----------------------------------------------------
>
> Key: ISPN-11377
> URL: https://issues.redhat.com/browse/ISPN-11377
> Project: Infinispan
> Issue Type: Task
> Components: Configuration, Core
> Affects Versions: 9.4.18.Final, 10.1.2.Final, 11.0.0.Alpha1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.1.3.Final, 11.0.0.Alpha2
>
>
> The server default configuration started using {{UFC_NB}} and {{MFC_NB}} in order to avoid blocking on the Netty event loop threads, slowing client requests, and then the core default configurations started using {{UFC_NB}} and {{MFC_NB}} as well with ISPN-9886.
> Unfortunately the _NB variants aren't really non-blocking: they have an extra queue for messages that require more credits, but that queue is limited (2MB by default), and once the queue is full, they also block. They also have much more complex locking than the blocking variants: we actually had to increase max_credits from 2MB to 3MB in order to get the same performance with {{UFC_NB}} that we had with {{UFC}}.
> We're changing the defaults back to {{UFC}} and {{MFC}} while we investigate possible alternatives to avoid blocking.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month