[JBoss JIRA] (ISPN-9618) Overlay for Java 10 could be Java 9
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9618?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant commented on ISPN-9618:
---------------------------------------
It could, but Java 9 and Java 10 are both unsupported, so it doesn't make any difference IMHO.
> Overlay for Java 10 could be Java 9
> -----------------------------------
>
> Key: ISPN-9618
> URL: https://issues.jboss.org/browse/ISPN-9618
> Project: Infinispan
> Issue Type: Bug
> Components: Build
> Affects Versions: 9.4.0.Final
> Reporter: tommaso borgato
> Priority: Major
>
> The following classes are in overlay for Java 10:
> - commons/src/main/java10/org/infinispan/commons/jdkspecific/CallerId.java
> - commons/src/main/java10/org/infinispan/commons/jdkspecific/ProcessorInfo.java
> CallerId uses StackWalker that is available since Java 9.
> ProcessorInfo uses Runtime.getRuntime().availableProcessors() that was fixed in java 9 (https://bugs.java.com/view_bug.do?bug_id=6515172)
> Question: can those classes be in overlay for Java 9 instead of Java 10 ?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (ISPN-9627) Removing a listener after cache manager stop throws an exception
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/ISPN-9627?page=com.atlassian.jira.plugin.... ]
Paul Ferraro edited comment on ISPN-9627 at 10/22/18 12:24 PM:
---------------------------------------------------------------
I understand the reasoning - I only pointed this out as an issue of compatibility. -Note that previously, listener registration was also allowed prior to starting the cache manager.-
was (Author: pferraro):
I understand the reasoning - I only pointed this out as an issue of compatibility. Note that previously, listener registration was also allowed prior to starting the cache manager.
> Removing a listener after cache manager stop throws an exception
> ----------------------------------------------------------------
>
> Key: ISPN-9627
> URL: https://issues.jboss.org/browse/ISPN-9627
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.4.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 9.4.1.Final
>
>
> {{DefaultCacheManager.removeListener()}} needs the {{CacheManagerNotifier}} component and fails if the component can't be accessed, e.g. because the manager is stopped. Since listeners are removed automatically on stop, a {{DefaultCacheManager.removeListener()}} call after stop should be a no-op.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (ISPN-9627) Removing a listener after cache manager stop throws an exception
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/ISPN-9627?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on ISPN-9627:
------------------------------------
I understand the reasoning - I only pointed this out as an issue of compatibility. Note that previously, listener registration was also allowed prior to starting the cache manager.
> Removing a listener after cache manager stop throws an exception
> ----------------------------------------------------------------
>
> Key: ISPN-9627
> URL: https://issues.jboss.org/browse/ISPN-9627
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.4.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 9.4.1.Final
>
>
> {{DefaultCacheManager.removeListener()}} needs the {{CacheManagerNotifier}} component and fails if the component can't be accessed, e.g. because the manager is stopped. Since listeners are removed automatically on stop, a {{DefaultCacheManager.removeListener()}} call after stop should be a no-op.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months