[JBoss JIRA] (ISPN-7636) HR 2.6 decoder misreads add client listener command
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-7636?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-7636:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.0.0.CR4
Resolution: Done
> HR 2.6 decoder misreads add client listener command
> ---------------------------------------------------
>
> Key: ISPN-7636
> URL: https://issues.jboss.org/browse/ISPN-7636
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 9.0.0.CR2
> Reporter: Vojtech Juranek
> Assignee: Vojtech Juranek
> Priority: Critical
> Fix For: 9.0.0.CR4
>
>
> HR 2.6 decoder misreads add client listener command, expecting more input form client, which results in hanged HR client, waiting for response from server:
> {noformat}
> java.lang.Thread.State: RUNNABLE
> at sun.nio.ch.Net.poll(Native Method)
> at sun.nio.ch.SocketChannelImpl.poll(SocketChannelImpl.java:954)
> - locked <0x00000000d6ea7db0> (a java.lang.Object)
> at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:204)
> - locked <0x00000000d6ea7da0> (a java.lang.Object)
> at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103)
> - locked <0x00000000d6ea80d0> (a sun.nio.ch.SocketAdaptor$SocketInputStream)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
> - locked <0x00000000d6ea7f30> (a java.io.BufferedInputStream)
> at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:220)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:325)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeaderOrEvent(Codec20.java:225)
> at org.infinispan.client.hotrod.impl.operations.AddClientListenerOperation.executeOperation(AddClientListenerOperation.java:97)
> at org.infinispan.client.hotrod.impl.operations.AddClientListenerOperation.executeOperation(AddClientListenerOperation.java:27)
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56)
> at org.infinispan.client.hotrod.impl.RemoteCacheImpl.addClientListener(RemoteCacheImpl.java:439)
> {noformat}
> Can be easily reproduced with many tests from HR client testsuite (e.g. {{ClusterInvalidatedNearCacheTest}}) - tests just hangs
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (ISPN-7644) Administration console - Loader tab allows invalid configuration to be set.
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7644?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-7644:
-------------------------------
Summary: Administration console - Loader tab allows invalid configuration to be set. (was: Administration console - Loader tab invalid configuration to be set.)
> Administration console - Loader tab allows invalid configuration to be set.
> ---------------------------------------------------------------------------
>
> Key: ISPN-7644
> URL: https://issues.jboss.org/browse/ISPN-7644
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.CR2
> Reporter: Roman Macor
> Assignee: Ryan Emerson
>
> Click on cache container -> cache -> configuration -> loader tab
> Some options in loader type drop down such as "Async Cache loader" (but there might be more of them) result in following error, after cluster restart:
> ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 19) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "datagrid-infinispan"),
> ("cache-container" => "clustered"),
> ("configurations" => "CONFIGURATIONS"),
> ("distributed-cache-configuration" => "distributedCache")
> ]) - failure description: "DGISPN0102: org.infinispan.persistence.async.AsyncCacheLoader is not a valid cache store"
> Then there are valid options such as "Single File Store" which work if there is a corresponding cache store set up, in this case, File store. But if there isn't a cache store configured, the cache is no longer available after restart and configuration cannot be fixed from the console.
> I suggest we add a restriction when configuring cache loaders in the console which wouldn't allow the users to configure cache loader without having to configure appropriate cache store first.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (ISPN-7644) Administration console - Loader tab allows invalid configuration to be set.
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7644?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-7644:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/200
> Administration console - Loader tab allows invalid configuration to be set.
> ---------------------------------------------------------------------------
>
> Key: ISPN-7644
> URL: https://issues.jboss.org/browse/ISPN-7644
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.CR2
> Reporter: Roman Macor
> Assignee: Ryan Emerson
>
> Click on cache container -> cache -> configuration -> loader tab
> Some options in loader type drop down such as "Async Cache loader" (but there might be more of them) result in following error, after cluster restart:
> ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 19) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "datagrid-infinispan"),
> ("cache-container" => "clustered"),
> ("configurations" => "CONFIGURATIONS"),
> ("distributed-cache-configuration" => "distributedCache")
> ]) - failure description: "DGISPN0102: org.infinispan.persistence.async.AsyncCacheLoader is not a valid cache store"
> Then there are valid options such as "Single File Store" which work if there is a corresponding cache store set up, in this case, File store. But if there isn't a cache store configured, the cache is no longer available after restart and configuration cannot be fixed from the console.
> I suggest we add a restriction when configuring cache loaders in the console which wouldn't allow the users to configure cache loader without having to configure appropriate cache store first.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (ISPN-7637) Administration console - Store config change fails if wb is enabled, modal is opened and no value changed.
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7637?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-7637:
-------------------------------
Status: Open (was: New)
> Administration console - Store config change fails if wb is enabled, modal is opened and no value changed.
> ----------------------------------------------------------------------------------------------------------
>
> Key: ISPN-7637
> URL: https://issues.jboss.org/browse/ISPN-7637
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.CR2
> Reporter: Roman Macor
> Assignee: Ryan Emerson
> Priority: Minor
>
> The issue is that when the user opens one of the pop-up dialogs in cache configuration (e.g. cache store -> Write behind), doesn't change anything and clicks OK, make some other changes, there is an error pop up when they try to save changes.
> Steps to reproduce:
> Set up a file store:
> Cache container -> cache -> configuration -> Store tab -> Select file store -> apply -> ok -> restart later
> Make a change:
> - Cache container -> cache -> configuration -> Store tab
> - change an attribute e.g. Read Only
> - click on write behind (Don't change anything) -> click OK (WORKAROUND: if we click Cancel here instead of OK, everything works fine)
> - apply changes -> confirm
> result:
> Error pop-up:
> {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-5":"WFLYCTL0201: Unknown attribute 'modified'"}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (ISPN-7637) Administration console - Store config change fails if wb is enabled, modal is opened and no value changed.
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7637?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-7637:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/200
> Administration console - Store config change fails if wb is enabled, modal is opened and no value changed.
> ----------------------------------------------------------------------------------------------------------
>
> Key: ISPN-7637
> URL: https://issues.jboss.org/browse/ISPN-7637
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.CR2
> Reporter: Roman Macor
> Assignee: Ryan Emerson
> Priority: Minor
>
> The issue is that when the user opens one of the pop-up dialogs in cache configuration (e.g. cache store -> Write behind), doesn't change anything and clicks OK, make some other changes, there is an error pop up when they try to save changes.
> Steps to reproduce:
> Set up a file store:
> Cache container -> cache -> configuration -> Store tab -> Select file store -> apply -> ok -> restart later
> Make a change:
> - Cache container -> cache -> configuration -> Store tab
> - change an attribute e.g. Read Only
> - click on write behind (Don't change anything) -> click OK (WORKAROUND: if we click Cancel here instead of OK, everything works fine)
> - apply changes -> confirm
> result:
> Error pop-up:
> {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-5":"WFLYCTL0201: Unknown attribute 'modified'"}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (ISPN-7644) Administration console - Loader tab allows invalid configuration to be set.
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7644?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-7644:
-------------------------------
Status: Open (was: New)
> Administration console - Loader tab allows invalid configuration to be set.
> ---------------------------------------------------------------------------
>
> Key: ISPN-7644
> URL: https://issues.jboss.org/browse/ISPN-7644
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.CR2
> Reporter: Roman Macor
> Assignee: Ryan Emerson
>
> Click on cache container -> cache -> configuration -> loader tab
> Some options in loader type drop down such as "Async Cache loader" (but there might be more of them) result in following error, after cluster restart:
> ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 19) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "datagrid-infinispan"),
> ("cache-container" => "clustered"),
> ("configurations" => "CONFIGURATIONS"),
> ("distributed-cache-configuration" => "distributedCache")
> ]) - failure description: "DGISPN0102: org.infinispan.persistence.async.AsyncCacheLoader is not a valid cache store"
> Then there are valid options such as "Single File Store" which work if there is a corresponding cache store set up, in this case, File store. But if there isn't a cache store configured, the cache is no longer available after restart and configuration cannot be fixed from the console.
> I suggest we add a restriction when configuring cache loaders in the console which wouldn't allow the users to configure cache loader without having to configure appropriate cache store first.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (ISPN-7637) Administration console - Store config change fails if wb is enabled, modal is opened and no value changed.
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7637?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-7637:
-------------------------------
Summary: Administration console - Store config change fails if wb is enabled, modal is opened and no value changed. (was: Administration console - minor issue in cache configuration)
> Administration console - Store config change fails if wb is enabled, modal is opened and no value changed.
> ----------------------------------------------------------------------------------------------------------
>
> Key: ISPN-7637
> URL: https://issues.jboss.org/browse/ISPN-7637
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.CR2
> Reporter: Roman Macor
> Assignee: Ryan Emerson
> Priority: Minor
>
> The issue is that when the user opens one of the pop-up dialogs in cache configuration (e.g. cache store -> Write behind), doesn't change anything and clicks OK, make some other changes, there is an error pop up when they try to save changes.
> Steps to reproduce:
> Set up a file store:
> Cache container -> cache -> configuration -> Store tab -> Select file store -> apply -> ok -> restart later
> Make a change:
> - Cache container -> cache -> configuration -> Store tab
> - change an attribute e.g. Read Only
> - click on write behind (Don't change anything) -> click OK (WORKAROUND: if we click Cancel here instead of OK, everything works fine)
> - apply changes -> confirm
> result:
> Error pop-up:
> {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-5":"WFLYCTL0201: Unknown attribute 'modified'"}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (ISPN-7644) Administration console - Loader tab invalid configuration to be set.
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7644?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-7644:
-------------------------------
Summary: Administration console - Loader tab invalid configuration to be set. (was: Administration console - loader tab allows to set invalid options)
> Administration console - Loader tab invalid configuration to be set.
> --------------------------------------------------------------------
>
> Key: ISPN-7644
> URL: https://issues.jboss.org/browse/ISPN-7644
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.CR2
> Reporter: Roman Macor
> Assignee: Ryan Emerson
>
> Click on cache container -> cache -> configuration -> loader tab
> Some options in loader type drop down such as "Async Cache loader" (but there might be more of them) result in following error, after cluster restart:
> ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 19) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "datagrid-infinispan"),
> ("cache-container" => "clustered"),
> ("configurations" => "CONFIGURATIONS"),
> ("distributed-cache-configuration" => "distributedCache")
> ]) - failure description: "DGISPN0102: org.infinispan.persistence.async.AsyncCacheLoader is not a valid cache store"
> Then there are valid options such as "Single File Store" which work if there is a corresponding cache store set up, in this case, File store. But if there isn't a cache store configured, the cache is no longer available after restart and configuration cannot be fixed from the console.
> I suggest we add a restriction when configuring cache loaders in the console which wouldn't allow the users to configure cache loader without having to configure appropriate cache store first.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (ISPN-7644) Administration console - loader tab allows to set invalid options
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7644?page=com.atlassian.jira.plugin.... ]
Ryan Emerson commented on ISPN-7644:
------------------------------------
[~rmacor] The Asynch cache loader options shouldn't be explicitly be exposed to the user like they currently are. I will remove them from the dropdown.
I was unable to reproduce your problem with "Single File Store". If I define the loader as a "Single File Store" on the default config, but I don't specify a store, then upon restart the loader is still defined as expected.
> Administration console - loader tab allows to set invalid options
> -----------------------------------------------------------------
>
> Key: ISPN-7644
> URL: https://issues.jboss.org/browse/ISPN-7644
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.CR2
> Reporter: Roman Macor
> Assignee: Ryan Emerson
>
> Click on cache container -> cache -> configuration -> loader tab
> Some options in loader type drop down such as "Async Cache loader" (but there might be more of them) result in following error, after cluster restart:
> ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 19) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "datagrid-infinispan"),
> ("cache-container" => "clustered"),
> ("configurations" => "CONFIGURATIONS"),
> ("distributed-cache-configuration" => "distributedCache")
> ]) - failure description: "DGISPN0102: org.infinispan.persistence.async.AsyncCacheLoader is not a valid cache store"
> Then there are valid options such as "Single File Store" which work if there is a corresponding cache store set up, in this case, File store. But if there isn't a cache store configured, the cache is no longer available after restart and configuration cannot be fixed from the console.
> I suggest we add a restriction when configuring cache loaders in the console which wouldn't allow the users to configure cache loader without having to configure appropriate cache store first.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (ISPN-7652) Incorrect River marshaller in server
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7652?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño commented on ISPN-7652:
----------------------------------------
The same errors happening in 8.2.x are not appearing in master. This is most likely because master does not rely as heavily in JBoss Marshalling as a result of the new marshaller. Still, the same changes should be applied to master too since the server could be plugged with user classes that end up relying on JBoss Marshalling's River marshaller.
> Incorrect River marshaller in server
> ------------------------------------
>
> Key: ISPN-7652
> URL: https://issues.jboss.org/browse/ISPN-7652
> Project: Infinispan
> Issue Type: Task
> Components: Marshalling, Server
> Affects Versions: 8.2.6.Final, 9.0.0.CR3
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 9.0.0.CR4, 8.2.7.Final
>
>
> After upgrading JBoss Marshalling to 2.0.0.Beta3, we forgot to apply similar changes to force JBoss Marshaller's River to be in sync. As a result, the server currently ships River 1.4.10 version which causes issues mentioned [here|https://github.com/infinispan/infinispan/pull/4709]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months