[JBoss JIRA] (ISPN-9344) org.infinispan.commons.marshall.NotSerializableException when use DeltaSpike
by Andrey Grigoriev (JIRA)
Andrey Grigoriev created ISPN-9344:
--------------------------------------
Summary: org.infinispan.commons.marshall.NotSerializableException when use DeltaSpike
Key: ISPN-9344
URL: https://issues.jboss.org/browse/ISPN-9344
Project: Infinispan
Issue Type: Bug
Affects Versions: 9.2.4.Final
Environment: Wildfly 13.0.0.Final (Infinispan 9.2.4)
Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode)
Apache DeltaSpike: 1.8.2
{code:java}
<dependency>
<groupId>org.apache.deltaspike.modules</groupId>
<artifactId>deltaspike-jsf-module-api</artifactId>
<version>1.8.2</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.apache.deltaspike.modules</groupId>
<artifactId>deltaspike-jsf-module-impl</artifactId>
<version>1.8.2</version>
<scope>runtime</scope>
</dependency>
{code}
Reporter: Andrey Grigoriev
I have project on Wildfly 10, and I use DeltaSpike JSF Module (For @WindowScoped bean). When I migrate to Wildfly 13 we have some errors:
{code:java}
ERROR [org.infinispan.interceptors.impl.InvocationContextInterceptor] (default task-2) ISPN000136: Error executing command PrepareCommand, writing keys [SessionCreationMetaDataKey(G7Xi_IuajeE1_Nh517GPjinnDh24LkWB1G8wn0TN),
SessionAttributesKey(G7Xi_IuajeE1_Nh517GPjinnDh24LkWB1G8wn0TN), SessionAccessMetaDataKey(G7Xi_IuajeE1_Nh517GPjinnDh24LkWB1G8wn0TN)]:
org.infinispan.commons.marshall.NotSerializableException: java.lang.ref.WeakReference
Caused by: an exception which occurred:
in field org.jboss.weld.bean.builtin.BeanManagerProxy.reloaderRef
in object org.jboss.weld.bean.builtin.BeanManagerProxy@f0640946
in field org.apache.deltaspike.core.util.context.ContextualStorage.beanManager
in object org.apache.deltaspike.core.util.context.ContextualStorage@1664c5af
in object org.apache.deltaspike.core.util.context.ContextualStorage@1664c5af
in field org.apache.deltaspike.core.impl.scope.AbstractBeanHolder.storageMap
in object org.apache.deltaspike.core.impl.scope.window.WindowBeanHolder@1c45f46e
in field org.jboss.weld.contexts.SerializableContextualInstanceImpl.instance
in object org.jboss.weld.contexts.SerializableContextualInstanceImpl@2a240ffd
in object org.jboss.weld.contexts.SerializableContextualInstanceImpl@2a240ffd
{code}
I asked DeltaSpike team about this, but they say that it is Infinispan problem:
{code:java}
<@struberg> seems like a weld bug if an injected BeanManager is not Serializable
<@struberg> or the serialisation logic in Infinispan cannot deal with it
< manovotn> hmm I can see BeanManagerProxy there, which is Weld's serializable BM version, so I would say it's Infinispan problem
< manovotn> I would try asking there first
<@struberg> point is, I don't think it's a DeltaSpike problem
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (ISPN-9342) Lock timeout when writing to index caches for the first time
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9342?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-9342:
------------------------------------
Status: Open (was: New)
> Lock timeout when writing to index caches for the first time
> ------------------------------------------------------------
>
> Key: ISPN-9342
> URL: https://issues.jboss.org/browse/ISPN-9342
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying, Remote Querying
> Affects Versions: 9.3.0.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> If multiple puts are done concurrently for the first time in an indexed cache, the QueryInterceptor will bottleneck in the entity class internal registration, causing Timeout exceptions.
> {noformat}
> ERROR: ISPN000136: Error executing command PrepareCommand, writing keys [KeyValuePair{key=qci-cache, value=class com.gustavonalle.infinispan.perf.domain.Transaction}]
> org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 10 seconds for key KeyValuePair{key=qci-cache, value=class com.gustavonalle.infinispan.perf.domain.Transaction} and requestor GlobalTransaction:<jedha-4472>:2:remote. Lock is held by GlobalTransaction:<jedha-26225>:1:local
> at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.lock(DefaultLockManager.java:238)
> at org.infinispan.interceptors.locking.AbstractLockingInterceptor.lockAllAndRecord(AbstractLockingInterceptor.java:202)
> at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.checkPendingAndLockAllKeys(AbstractTxLockingInterceptor.java:200)
> at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockAllOrRegisterBackupLock(AbstractTxLockingInterceptor.java:166)
> at org.infinispan.interceptors.locking.OptimisticLockingInterceptor.visitPrepareCommand(OptimisticLockingInterceptor.java:74)
> at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:176)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (ISPN-9342) Lock timeout when writing to index caches for the first time
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9342?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-9342:
------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/6116
> Lock timeout when writing to index caches for the first time
> ------------------------------------------------------------
>
> Key: ISPN-9342
> URL: https://issues.jboss.org/browse/ISPN-9342
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying, Remote Querying
> Affects Versions: 9.3.0.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> If multiple puts are done concurrently for the first time in an indexed cache, the QueryInterceptor will bottleneck in the entity class internal registration, causing Timeout exceptions.
> {noformat}
> ERROR: ISPN000136: Error executing command PrepareCommand, writing keys [KeyValuePair{key=qci-cache, value=class com.gustavonalle.infinispan.perf.domain.Transaction}]
> org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 10 seconds for key KeyValuePair{key=qci-cache, value=class com.gustavonalle.infinispan.perf.domain.Transaction} and requestor GlobalTransaction:<jedha-4472>:2:remote. Lock is held by GlobalTransaction:<jedha-26225>:1:local
> at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.lock(DefaultLockManager.java:238)
> at org.infinispan.interceptors.locking.AbstractLockingInterceptor.lockAllAndRecord(AbstractLockingInterceptor.java:202)
> at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.checkPendingAndLockAllKeys(AbstractTxLockingInterceptor.java:200)
> at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockAllOrRegisterBackupLock(AbstractTxLockingInterceptor.java:166)
> at org.infinispan.interceptors.locking.OptimisticLockingInterceptor.visitPrepareCommand(OptimisticLockingInterceptor.java:74)
> at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:176)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (ISPN-9342) Lock timeout when writing to index caches for the first time
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9342?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-9342:
------------------------------------
Description:
If multiple puts are done concurrently for the first time in an indexed cache, the QueryInterceptor will bottleneck in the entity class internal registration, causing Timeout exceptions.
{noformat}
ERROR: ISPN000136: Error executing command PrepareCommand, writing keys [KeyValuePair{key=qci-cache, value=class com.gustavonalle.infinispan.perf.domain.Transaction}]
org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 10 seconds for key KeyValuePair{key=qci-cache, value=class com.gustavonalle.infinispan.perf.domain.Transaction} and requestor GlobalTransaction:<jedha-4472>:2:remote. Lock is held by GlobalTransaction:<jedha-26225>:1:local
at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.lock(DefaultLockManager.java:238)
at org.infinispan.interceptors.locking.AbstractLockingInterceptor.lockAllAndRecord(AbstractLockingInterceptor.java:202)
at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.checkPendingAndLockAllKeys(AbstractTxLockingInterceptor.java:200)
at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockAllOrRegisterBackupLock(AbstractTxLockingInterceptor.java:166)
at org.infinispan.interceptors.locking.OptimisticLockingInterceptor.visitPrepareCommand(OptimisticLockingInterceptor.java:74)
at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:176)
{noformat}
was:If multiple puts are done concurrently for the first time in an indexed cache, the QueryInterceptor will bottleneck in the entity class internal registration, causing Timeout exceptions
> Lock timeout when writing to index caches for the first time
> ------------------------------------------------------------
>
> Key: ISPN-9342
> URL: https://issues.jboss.org/browse/ISPN-9342
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying, Remote Querying
> Affects Versions: 9.3.0.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> If multiple puts are done concurrently for the first time in an indexed cache, the QueryInterceptor will bottleneck in the entity class internal registration, causing Timeout exceptions.
> {noformat}
> ERROR: ISPN000136: Error executing command PrepareCommand, writing keys [KeyValuePair{key=qci-cache, value=class com.gustavonalle.infinispan.perf.domain.Transaction}]
> org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 10 seconds for key KeyValuePair{key=qci-cache, value=class com.gustavonalle.infinispan.perf.domain.Transaction} and requestor GlobalTransaction:<jedha-4472>:2:remote. Lock is held by GlobalTransaction:<jedha-26225>:1:local
> at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.lock(DefaultLockManager.java:238)
> at org.infinispan.interceptors.locking.AbstractLockingInterceptor.lockAllAndRecord(AbstractLockingInterceptor.java:202)
> at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.checkPendingAndLockAllKeys(AbstractTxLockingInterceptor.java:200)
> at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockAllOrRegisterBackupLock(AbstractTxLockingInterceptor.java:166)
> at org.infinispan.interceptors.locking.OptimisticLockingInterceptor.visitPrepareCommand(OptimisticLockingInterceptor.java:74)
> at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:176)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (ISPN-9320) Automatic hot rod client version selection
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-9320?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant edited comment on ISPN-9320 at 7/2/18 8:37 AM:
---------------------------------------------------------------
I'd also like to see a decoupling of protocol version from available ops:
* return the recognized ops as a response to PING as a list (e.g. SMTP does this in response to EHLO requests)
* version the ops, e.g. if we make incompatible changes to PUT we introduce PUT2 with dedicated ops
But this should really go into Hot Rod 3.
was (Author: nadirx):
I'd also like to see a decoupling of protocol version from available ops:
* return the recognized ops as a response to PING as a list (e.g. SMTP does this in response to EHLO requests)
* version the ops, e.g. if we make incompatible changes to PUT we introduce PUT2 with dedicated ops
> Automatic hot rod client version selection
> ------------------------------------------
>
> Key: ISPN-9320
> URL: https://issues.jboss.org/browse/ISPN-9320
> Project: Infinispan
> Issue Type: Feature Request
> Reporter: Tristan Tarrant
> Assignee: Galder Zamarreño
> Fix For: 9.4.0.Final
>
>
> A HotRod client should be able to automatic detect the server version and downgrade the protocol version if the server is older.
> Older HotRod clients are still able to connect to newer servers.
> It would be helpful if new API functions are rejected with a clear error message that the function is not available if using an old protocol.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (ISPN-9116) Server marshallers/transcoders don't support whitelist when deserializing
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9116?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-9116:
------------------------------------
Security: (was: Red Hat Internal)
> Server marshallers/transcoders don't support whitelist when deserializing
> -------------------------------------------------------------------------
>
> Key: ISPN-9116
> URL: https://issues.jboss.org/browse/ISPN-9116
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 9.3.0.Final, 9.2.5.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> The server deserializes binary payloads and json/xml payload without any checks. This happens when:
> * Compatibility mode is on
> * Remote listeners with filters
> * Remote iteration with filters
> * Remote tasks with parameters
> * Server is configured with MediaType.APPLICATION_OBJECT
> * Potentially with JSON and XML contents sent via REST
> The remote endpoints affected are REST, Hot Rod and Memcached.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (ISPN-9343) Streams should skip loader when preload=true and eviction is not enabled
by William Burns (JIRA)
William Burns created ISPN-9343:
-----------------------------------
Summary: Streams should skip loader when preload=true and eviction is not enabled
Key: ISPN-9343
URL: https://issues.jboss.org/browse/ISPN-9343
Project: Infinispan
Issue Type: Enhancement
Affects Versions: 9.3.0.Final
Reporter: William Burns
Currently stream operations and other bulk operations always read from the loader to ensure they don't miss any entries. However when a cache is configured to have preload=true and eviction is not enabled we should be able to ignore the loader and use in memory only. This would improve the performance of streams substantially in these cases.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months