[JBoss JIRA] (ISPN-7251) Administration console - changing configuration in standalone mode should not promt restart dialog
by Roman Macor (JIRA)
Roman Macor created ISPN-7251:
---------------------------------
Summary: Administration console - changing configuration in standalone mode should not promt restart dialog
Key: ISPN-7251
URL: https://issues.jboss.org/browse/ISPN-7251
Project: Infinispan
Issue Type: Bug
Components: JMX, reporting and management
Affects Versions: 9.0.0.Alpha4
Reporter: Roman Macor
Assignee: Vladimir Blagojevic
Start server in standalone mode, with clustered configuration:
bin/standalone.sh -c clustered.xml
Change cache or cache container configuration:
e.g. click on cache container -> Configuration -> change settings -> click save/apply changes -> restart required dialog is displayed -> click restart now
Result nothing happens.
Expected result: Dialog saying manual restart is required for this change to take effect, no action buttons offered. This works correctly in standalone mode with non-clustered configuration (started by bin/standalone.sh)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ISPN-7250) ORA-00928: missing SELECT keyword when inserting entry with Oracle cache store
by Gustavo Fernandes (JIRA)
Gustavo Fernandes created ISPN-7250:
---------------------------------------
Summary: ORA-00928: missing SELECT keyword when inserting entry with Oracle cache store
Key: ISPN-7250
URL: https://issues.jboss.org/browse/ISPN-7250
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 9.0.0.Alpha4
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
Tested with Oracle 11g express edition
Example of query currently sent to Oracle:
{code:sql}
MERGE INTO "ISPN_cache" USING (VALUES ('Az4s','030',1)) AS tmp (datum, version, id) ON (datum = tmp.datum) WHEN MATCHED THEN UPDATE SET version = tmp.version, id = tmp.id WHEN NOT MATCHED THEN INSERT (datum, version, id) VALUES (tmp.datum, tmp.version, tmp.id)
{code}
which does not seem valid
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ISPN-7248) Administration console - start/stop/remove node actions should not be available in standalone mode
by Roman Macor (JIRA)
Roman Macor created ISPN-7248:
---------------------------------
Summary: Administration console - start/stop/remove node actions should not be available in standalone mode
Key: ISPN-7248
URL: https://issues.jboss.org/browse/ISPN-7248
Project: Infinispan
Issue Type: Bug
Components: JMX, reporting and management
Affects Versions: 9.0.0.Alpha4
Reporter: Roman Macor
Assignee: Vladimir Blagojevic
Start the server in standalone mode, with clustered configuration:
bin/standalone.sh -c clustered.xml -> in administration console, click on clusters tab -> cluster -> node
Result: There is an action button with start, stop and remove action. Clicking on actions prompts a confirmation dialog but after confirming, doesn't do anything.
Expected result: Action button shouldn't be there.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ISPN-7247) Administration console - changing any cache configuration adds security tag to the configuration
by Roman Macor (JIRA)
Roman Macor created ISPN-7247:
---------------------------------
Summary: Administration console - changing any cache configuration adds security tag to the configuration
Key: ISPN-7247
URL: https://issues.jboss.org/browse/ISPN-7247
Project: Infinispan
Issue Type: Bug
Components: JMX, reporting and management
Affects Versions: 9.0.0.Alpha4
Reporter: Roman Macor
Assignee: Vladimir Blagojevic
Steps to reproduce:
click on cache container -> cache -> configuration -> change a value (e.g. number of owner 2 -> 1) -> click apply changes -> click restart later
Check the configuration file - domain.xml, the modified cache now has security tag:
<security>
<authorization roles=""/>
</security>
This result in error when we stop the server and start it again:
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.datagrid-infinispan.clustered.default.config: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered.default.config: Failed to start service
[Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
[Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[Server:server-one] at java.lang.Thread.run(Thread.java:745)
[Server:server-one] Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000414: Global security authorization should be enabled if cache authorization enabled.
...
09:57:05,492 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
[Server:server-one] ("subsystem" => "datagrid-infinispan-endpoint"),
[Server:server-one] ("memcached-connector" => "memcached-connector")
[Server:server-one] ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
[Server:server-one] 09:57:05,493 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
[Server:server-one] ("subsystem" => "datagrid-infinispan-endpoint"),
[Server:server-one] ("hotrod-connector" => "hotrod-connector")
[Server:server-one] ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
[Server:server-one] 09:57:05,494 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
[Server:server-one] ("subsystem" => "datagrid-infinispan-endpoint"),
[Server:server-one] ("rest-connector" => "rest-connector")
[Server:server-one] ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
[Server:server-one] 09:57:05,495 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
[Server:server-one] ("subsystem" => "datagrid-infinispan-endpoint"),
[Server:server-one] ("websocket-connector" => "websocket-connector")
[Server:server-one] ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
[Server:server-one] 09:57:05,496 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
[Server:server-one] ("subsystem" => "datagrid-infinispan"),
[Server:server-one] ("cache-container" => "clustered"),
[Server:server-one] ("configurations" => "CONFIGURATIONS"),
[Server:server-one] ("distributed-cache-configuration" => "default")
[Server:server-one] ]) - failure description: {
[Server:server-one] "WFLYCTL0080: Failed services" => {"jboss.datagrid-infinispan.clustered.default.config" => "org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered.default.config: Failed to start service
[Server:server-one] Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000414: Global security authorization should be enabled if cache authorization enabled."},
[Server:server-one] "WFLYCTL0412: Required services that are not installed:" => ["jboss.datagrid-infinispan.clustered.default.config"],
[Server:server-one] "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
[Server:server-one] }
[Server:server-one] 09:57:05,496 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
[Server:server-one] ("subsystem" => "datagrid-infinispan"),
[Server:server-one] ("cache-container" => "clustered"),
[Server:server-one] ("distributed-cache" => "default")
[Server:server-one] ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ISPN-7246) Memory leak with LIRS eviction strategy
by ted won (JIRA)
[ https://issues.jboss.org/browse/ISPN-7246?page=com.atlassian.jira.plugin.... ]
ted won updated ISPN-7246:
--------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1399494
> Memory leak with LIRS eviction strategy
> ---------------------------------------
>
> Key: ISPN-7246
> URL: https://issues.jboss.org/browse/ISPN-7246
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 8.2.5.Final
> Environment: * Infinispan 8.2.5.Final Library mode
> * LIRS eviction strategy
> Reporter: ted won
> Labels: core, eviction, leak, lirs, strategy
> Attachments: reproducer.zip
>
>
> There is a memory leak with the default eviction strategy. It's a leak in org.infinispan.commons.util.concurrent.jdk8backported.BoundedEquivalentConcurrentHashMapV8 with LIRS eviction strategy.
> There are cache entries in org.infinispan.container.DefaultDataContainer.entries and its size are bigger than cache size after eviction occurred.
> DefaultDataContainer.entries retain keys and values for evicted entries in the cache.
> After full GC, DefaultDataContainer.entries size wasn't changed.
> The following minimum reproducer exhibits a leak. Eviction is supposed to suppress OOME.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ISPN-7246) Memory leak with LIRS eviction strategy
by ted won (JIRA)
[ https://issues.jboss.org/browse/ISPN-7246?page=com.atlassian.jira.plugin.... ]
ted won updated ISPN-7246:
--------------------------
Description:
There is a memory leak with the default eviction strategy. It's a leak in org.infinispan.commons.util.concurrent.jdk8backported.BoundedEquivalentConcurrentHashMapV8 with LIRS eviction strategy.
There are cache entries in org.infinispan.container.DefaultDataContainer.entries and its size are bigger than cache size after eviction occurred.
DefaultDataContainer.entries retains keys and values for evicted entries in the cache.
After full GC, DefaultDataContainer.entries size wasn't changed.
The following minimum reproducer exhibits a leak. Eviction is supposed to suppress OOME.
was:
There is a memory leak in org.infinispan.commons.util.concurrent.jdk8backported.BoundedEquivalentConcurrentHashMapV8 with LIRS eviction strategy.
There are cache entries in org.infinispan.container.DefaultDataContainer.entries and its size are bigger than cache size after eviction occurred.
DefaultDataContainer.entries retains keys and values for evicted entries in the cache.
After full GC, DefaultDataContainer.entries size wasn't changed.
The following minimum reproducer exhibits a leak. Eviction is supposed to suppress OOME.
> Memory leak with LIRS eviction strategy
> ---------------------------------------
>
> Key: ISPN-7246
> URL: https://issues.jboss.org/browse/ISPN-7246
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 8.2.5.Final
> Environment: * Infinispan 8.2.5.Final Library mode
> * LIRS eviction strategy
> Reporter: ted won
> Labels: core, eviction, leak, lirs, strategy
> Attachments: reproducer.zip
>
>
> There is a memory leak with the default eviction strategy. It's a leak in org.infinispan.commons.util.concurrent.jdk8backported.BoundedEquivalentConcurrentHashMapV8 with LIRS eviction strategy.
> There are cache entries in org.infinispan.container.DefaultDataContainer.entries and its size are bigger than cache size after eviction occurred.
> DefaultDataContainer.entries retains keys and values for evicted entries in the cache.
> After full GC, DefaultDataContainer.entries size wasn't changed.
> The following minimum reproducer exhibits a leak. Eviction is supposed to suppress OOME.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ISPN-7246) Memory leak with LIRS eviction strategy
by ted won (JIRA)
[ https://issues.jboss.org/browse/ISPN-7246?page=com.atlassian.jira.plugin.... ]
ted won updated ISPN-7246:
--------------------------
Description:
There is a memory leak with the default eviction strategy. It's a leak in org.infinispan.commons.util.concurrent.jdk8backported.BoundedEquivalentConcurrentHashMapV8 with LIRS eviction strategy.
There are cache entries in org.infinispan.container.DefaultDataContainer.entries and its size are bigger than cache size after eviction occurred.
DefaultDataContainer.entries retain keys and values for evicted entries in the cache.
After full GC, DefaultDataContainer.entries size wasn't changed.
The following minimum reproducer exhibits a leak. Eviction is supposed to suppress OOME.
was:
There is a memory leak with the default eviction strategy. It's a leak in org.infinispan.commons.util.concurrent.jdk8backported.BoundedEquivalentConcurrentHashMapV8 with LIRS eviction strategy.
There are cache entries in org.infinispan.container.DefaultDataContainer.entries and its size are bigger than cache size after eviction occurred.
DefaultDataContainer.entries retains keys and values for evicted entries in the cache.
After full GC, DefaultDataContainer.entries size wasn't changed.
The following minimum reproducer exhibits a leak. Eviction is supposed to suppress OOME.
> Memory leak with LIRS eviction strategy
> ---------------------------------------
>
> Key: ISPN-7246
> URL: https://issues.jboss.org/browse/ISPN-7246
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 8.2.5.Final
> Environment: * Infinispan 8.2.5.Final Library mode
> * LIRS eviction strategy
> Reporter: ted won
> Labels: core, eviction, leak, lirs, strategy
> Attachments: reproducer.zip
>
>
> There is a memory leak with the default eviction strategy. It's a leak in org.infinispan.commons.util.concurrent.jdk8backported.BoundedEquivalentConcurrentHashMapV8 with LIRS eviction strategy.
> There are cache entries in org.infinispan.container.DefaultDataContainer.entries and its size are bigger than cache size after eviction occurred.
> DefaultDataContainer.entries retain keys and values for evicted entries in the cache.
> After full GC, DefaultDataContainer.entries size wasn't changed.
> The following minimum reproducer exhibits a leak. Eviction is supposed to suppress OOME.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month