[JBoss JIRA] (ISPN-11249) Unexpected functionality added by Java8 default interface methods
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11249?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11249:
-----------------------------------
Fix Version/s: 11.0.0.Beta1
(was: 11.0.0.Alpha2)
> 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.4.Final, 11.0.0.Beta1
>
>
> 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)
4 years, 2 months
[JBoss JIRA] (ISPN-11248) Add test for ServerTask that utilizes protostream stored entries
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11248?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11248:
-----------------------------------
Fix Version/s: 11.0.0.Beta1
(was: 11.0.0.Alpha2)
> Add test for ServerTask that utilizes protostream stored entries
> ----------------------------------------------------------------
>
> Key: ISPN-11248
> URL: https://issues.redhat.com/browse/ISPN-11248
> Project: Infinispan
> Issue Type: Task
> Reporter: Will Burns
> Priority: Major
> Fix For: 11.0.0.Beta1
>
>
> We currently have a single ServerTask that just prints out "Hello <name>". We should add a new test that actually tests a very likely use case of storing entries in protostream and using a task that deserializes them properly (this could be done automatically by the encoding layer of the cache, if it is working).
> We may also want to look into sharing this with a custom loader, as we have users doing this today. And it is quite clunky, so we can see how the usability is in 11.0.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months
[JBoss JIRA] (ISPN-11381) AdvancedCache.getGroup(key) may return incomplete results during state transfer
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11381?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11381:
-----------------------------------
Fix Version/s: 11.0.0.Beta1
(was: 11.0.0.Alpha2)
> AdvancedCache.getGroup(key) may return incomplete results during state transfer
> -------------------------------------------------------------------------------
>
> Key: ISPN-11381
> URL: https://issues.redhat.com/browse/ISPN-11381
> Project: Infinispan
> Issue Type: Bug
> Components: 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: 11.0.0.Beta1
>
>
> {{AdvancedCache.getGroup(groupKey)}} returns all the keys that belong to a group.
> If the originator is not an owner, the command is forwarded to the primary owner. If the originator is a primary or a backup owner for the group key, the command is executed locally.
> During state transfer, a node may be a write owner for the group key but not a read owner. Currently {{GroupingInterceptor}} uses {{LocalizedCacheTopogy.isWriteOwner(groupKey)}} instead of {{isReadOwner(groupKey)}}, so it executes the command on the originator instead of forwarding it to the primary owner.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months
[JBoss JIRA] (ISPN-11388) Refactor CacheIgnoreManager - AbstractProtocolServer collaboration
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11388?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11388:
-----------------------------------
Fix Version/s: 11.0.0.Beta1
(was: 11.0.0.Alpha2)
> Refactor CacheIgnoreManager - AbstractProtocolServer collaboration
> ------------------------------------------------------------------
>
> Key: ISPN-11388
> URL: https://issues.redhat.com/browse/ISPN-11388
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 10.1.0.Final
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 11.0.0.Beta1
>
>
> Given the interactions between CacheIgnoreManager and AbstractProtocolServer it seems that CacheIgnoreManager should be a global component in the registry of the EmbeddedCacheManager sitting behind the AbstractProtocolServer. It should be looked up from there, or better injected, rather than being received in ProtocolServer.start method. The start method also has an overloaded version that does not take a CacheIgnoreManager to support tests the do not need it. This lack of orthogonality is annoyoing.
> Another aspect to refactor: the startInternal method receives parametters that it assigns to fields. It seems that this should have been done already in the start method. That would get rid of some clunky hacks and some comments/excuses for the said hacks.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months
[JBoss JIRA] (ISPN-11390) Non-components cannot export metrics
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11390?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11390:
-----------------------------------
Fix Version/s: 11.0.0.Beta1
(was: 11.0.0.Alpha2)
> Non-components cannot export metrics
> ------------------------------------
>
> Key: ISPN-11390
> URL: https://issues.redhat.com/browse/ISPN-11390
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management, Server
> Affects Versions: 10.1.3.Final
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 11.0.0.Beta1
>
>
> AbstractProtocolServer's worker thread pool and the protocol are such examples. They expose managed attributes but those cannot be currently exported as microprofile metrics due to fact these are not registered in the component registry.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months