[JBoss JIRA] (ISPN-7273) Standalone page refresh causes the whole app to die
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7273?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-7273.
--------------------------------
Fix Version/s: 9.0.0.Beta1
Resolution: Done
> Standalone page refresh causes the whole app to die
> ---------------------------------------------------
>
> Key: ISPN-7273
> URL: https://issues.jboss.org/browse/ISPN-7273
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 9.0.0.Alpha4
> Environment: Standalone Mode
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Critical
> Fix For: 9.0.0.Beta1
>
>
> When using the console in standalone mode, if the user hits refresh on any screen, then the app is unable to reload as the below DMR error is encountered:
> {code:javascript}
> Objectfailure-description: "WFLYCTL0030: No resource definition is registered for address [("subsystem" => "datagrid-jgroups")]"outcome: "failed"rolled-back: true__proto__: Object__defineGetter__: __defineGetter__()__defineSetter__: __defineSetter__()__lookupGetter__: __lookupGetter__()__lookupSetter__: __lookupSetter__()constructor: Object()hasOwnProperty: hasOwnProperty()isPrototypeOf: isPrototypeOf()propertyIsEnumerable: propertyIsEnumerable()toLocaleString: toLocaleString()toString: toString()valueOf: valueOf()get __proto__: __proto__()set __proto__: __proto__()
> DmrService.ts:152 WFLYCTL0030: No resource definition is registered for address [("subsystem" => "datagrid-jgroups")]
> {code}
> This means that the user must go to <url>/logout in order for the apps state to reset.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (ISPN-7209) Collation not set properly when data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7209?page=com.atlassian.jira.plugin.... ]
Ryan Emerson commented on ISPN-7209:
------------------------------------
[~jholusa] Which JDBC driver are you using, MariaDB or MYSQL? So far I have been able to reproduce this (and other errors) when using the MariaDB JDBC driver in embedded mode as well as the server. However, I have been unable to reproduce any errors when using the MySQL JDBC driver to connect to a MariaDB instance.
> Collation not set properly when data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB
> ------------------------------------------------------------------------------------------------------
>
> Key: ISPN-7209
> URL: https://issues.jboss.org/browse/ISPN-7209
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 9.0.0.Alpha4
> Reporter: Jiří Holuša
> Assignee: Ryan Emerson
>
> Given following scenario:
> 1) store entry to ISPN server via Hot Rod (e.g. with RemoteCache)
> 2) have the server configured to use JdbcStringBasedStore
> 3) used database is MariaDB 10
> Following exception is thrown:
> {code}
> ERROR [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore] (HotRodServerHandler-3-2) ISPN008024: Error while storing string key to database; key: '9A09AJAAAAAAAAA==': java.sql.BatchUpdateException: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '='
> {code}
> Note that his doesn't happen when stored via, for example, Memcached client. Also this issue doesn't appear in library mode, doesn't appear in any with any other database (including MySQL, which is very similar to MariaDB).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (ISPN-7246) Memory leak with LIRS eviction strategy
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-7246?page=com.atlassian.jira.plugin.... ]
William Burns resolved ISPN-7246.
---------------------------------
Resolution: Rejected
This is unfortunately how LIRS is designed to behave.
You can read more information at https://issues.jboss.org/browse/ISPN-7171
> 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)
7 years, 5 months
[JBoss JIRA] (ISPN-7246) Memory leak with LIRS eviction strategy
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-7246?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-7246:
--------------------------------
Status: Open (was: New)
> 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)
7 years, 5 months
[JBoss JIRA] (ISPN-7280) Boolean comparisons fail during parsing of query string
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-7280?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-7280:
--------------------------------
Description:
The query "SELECT _gen0.name, _gen0.age FROM runner _gen0 WHERE _gen0.finished = true" fails at render phase.
java.lang.IllegalStateException: ISPN028517: The predicate org.infinispan.objectfilter.impl.syntax.parser.FilterExpressionBuilder$LazyLeafBooleanExpr@44bfa0bd can not be added since there may be only one root predicate.
was:The query "SELECT _gen0.name, _gen0.age FROM runner _gen0 WHERE _gen0.finished = true" fails at render phase.
> Boolean comparisons fail during parsing of query string
> -------------------------------------------------------
>
> Key: ISPN-7280
> URL: https://issues.jboss.org/browse/ISPN-7280
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying, Remote Querying
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 9.0.0.Beta1
>
>
> The query "SELECT _gen0.name, _gen0.age FROM runner _gen0 WHERE _gen0.finished = true" fails at render phase.
> java.lang.IllegalStateException: ISPN028517: The predicate org.infinispan.objectfilter.impl.syntax.parser.FilterExpressionBuilder$LazyLeafBooleanExpr@44bfa0bd can not be added since there may be only one root predicate.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months