[JBoss JIRA] (ISPN-8490) Add compare-and-swap operation to StrongCounter
by Pedro Ruivo (JIRA)
Pedro Ruivo created ISPN-8490:
---------------------------------
Summary: Add compare-and-swap operation to StrongCounter
Key: ISPN-8490
URL: https://issues.jboss.org/browse/ISPN-8490
Project: Infinispan
Issue Type: Feature Request
Components: Clustered Counter
Reporter: Pedro Ruivo
Assignee: Pedro Ruivo
A compare-and-swap is preferred over the compare-and-set since it can save a RPC to re-fetch the counter's value. This is important for server-mode as well.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8489) Add compare-and-swap operation to StrongCounter
by Pedro Ruivo (JIRA)
Pedro Ruivo created ISPN-8489:
---------------------------------
Summary: Add compare-and-swap operation to StrongCounter
Key: ISPN-8489
URL: https://issues.jboss.org/browse/ISPN-8489
Project: Infinispan
Issue Type: Feature Request
Components: Clustered Counter
Reporter: Pedro Ruivo
Assignee: Pedro Ruivo
A compare-and-swap is preferred over the compare-and-set since it can save a RPC to re-fetch the counter's value. This is important for server-mode as well.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8488) Possibly add WrappedByteArrayWithOffset implementation
by William Burns (JIRA)
William Burns created ISPN-8488:
-----------------------------------
Summary: Possibly add WrappedByteArrayWithOffset implementation
Key: ISPN-8488
URL: https://issues.jboss.org/browse/ISPN-8488
Project: Infinispan
Issue Type: Sub-task
Components: Off Heap
Reporter: William Burns
It could be more beneficial to read the entire key, metadata and value in 1 byte[] and then use a different WrappedByteArrayWithOffset impl or something that has an offset and length into the byte[].
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8487) Global MBean registration happens too soon
by Dan Berindei (JIRA)
Dan Berindei created ISPN-8487:
----------------------------------
Summary: Global MBean registration happens too soon
Key: ISPN-8487
URL: https://issues.jboss.org/browse/ISPN-8487
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 9.2.0.Alpha2
Reporter: Dan Berindei
Fix For: 9.2.0.Beta1
Currently {{DefaultCacheManager}} explicitly starts {{CacheManagerJmxRegistration}} before calling {{ModuleLifecycle#cacheManagerStarting}}, which means MBeans in other modules are not registered in JMX.
We should start {{CacheManagerJmxRegistration}} only during global component registry start, after the modules have registered their components. If we want to make the cache manager available in JMX before {{DefaultCacheManager.start()}}, we should only register that particular MBean. Conversely, on shutdown, components other than the cache manager should be removed from JMX on {{DefaultCacheManager.stop()}} (as per ISPN-118).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8485) Specifying JAVA_OPTS require adding jboss.modules.system.pkgs parameter
by Sebastian Łaskawiec (JIRA)
Sebastian Łaskawiec created ISPN-8485:
-----------------------------------------
Summary: Specifying JAVA_OPTS require adding jboss.modules.system.pkgs parameter
Key: ISPN-8485
URL: https://issues.jboss.org/browse/ISPN-8485
Project: Infinispan
Issue Type: Bug
Components: Cloud Integrations
Reporter: Sebastian Łaskawiec
Currently when specifying {{JAVA_OPTS}} in DeploymentConfig (or StatefulSet) one needs to add {{-Djboss.modules.system.pkgs=org.jboss.logmanager,jdk.nashorn.api}}. We probably could append this automatically.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months