[JBoss JIRA] (ISPN-12337) Clustered Expiration can deadlock with Pessimistic Tx on a non owner
by Will Burns (Jira)
Will Burns created ISPN-12337:
---------------------------------
Summary: Clustered Expiration can deadlock with Pessimistic Tx on a non owner
Key: ISPN-12337
URL: https://issues.redhat.com/browse/ISPN-12337
Project: Infinispan
Issue Type: Bug
Components: Expiration, Transactions
Reporter: Will Burns
Assignee: Will Burns
Fix For: 12.0.0.Final
Pessimistic tx first lock a key before doing an operation. This is true of non owners as they will first lock the key on the owner then possibly retrieve the previous value in a subsequent call. Related to ISPN-12332. If the retrieved key is expired we will then attempt to remove it, but it will deadlock as the invoking code already has the lock and expiration is done outside of the current transaction.
Instead we must pass along the fact that the invoking code has the lock, similar to how we perform locking differently when a non tx write sees an expired entry. IF ISPN-12332 is fixed this issue is no longer needed, but that may take more time and may not be implemented.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (ISPN-12336) Avoid trying to load entity when there are no references
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12336?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12336:
-------------------------------------
Summary: Avoid trying to load entity when there are no references (was: Avoid trying to load entity when there is no references)
> Avoid trying to load entity when there are no references
> --------------------------------------------------------
>
> Key: ISPN-12336
> URL: https://issues.redhat.com/browse/ISPN-12336
> Project: Infinispan
> Issue Type: Enhancement
> Components: Embedded Querying
> Affects Versions: 12.0.0.Dev03
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> A call to cache.getAll with an empty collection still goes through all the intercept stack. You may want to short circuit it on the cache itself too [~dan.berindei]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (ISPN-12336) Avoid trying to load entity when there is references
by Gustavo Fernandes (Jira)
Gustavo Fernandes created ISPN-12336:
----------------------------------------
Summary: Avoid trying to load entity when there is references
Key: ISPN-12336
URL: https://issues.redhat.com/browse/ISPN-12336
Project: Infinispan
Issue Type: Enhancement
Components: Embedded Querying
Affects Versions: 12.0.0.Dev03
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
A call to cache.getAll with an empty collection still goes through all the intercept stack. You may want to short circuit it on the cache itself too [~dan.berindei]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (ISPN-12307) Improve media type parsing
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12307?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-12307:
--------------------------------
Status: Open (was: New)
> Improve media type parsing
> --------------------------
>
> Key: ISPN-12307
> URL: https://issues.redhat.com/browse/ISPN-12307
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Dan Berindei
> Priority: Major
>
> Media type parsing has some problems with double-quoted parameters:
> * {{;}} and {{,}} are interpreted as parameter/media type separator even when they occur in a quoted parameter value
> * {{'}} is interpreted as a quoting character, the spec says only {{"}} must be used for quoting
> * Only spaces are allowed, not {{\t}}.
> * Spaces are allowed in too many places, e.g. {{type / subtype}} or {{parameter = value}}
> * Start and end quotes are removed from quoted parameter values, but the escaped characters inside are not unescaped.
> * Quotes are not added back in {{toString()}}, which makes deserialization fail if one of the parameters included an escaped double-quote (e.g. {{type/subtype; param="\""}}).
> Performance can also be improved, as we create many {{String}} instances via {{trim()}}, {{substring()}}, or {{split()}}.
> The clearest explanation of the media type grammar seems to be in
> https://tools.ietf.org/html/rfc7231#section-3.1.1.1
> https://tools.ietf.org/html/rfc7230#section-3.2.6
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (ISPN-12307) Improve media type parsing
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12307?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-12307:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/8697
> Improve media type parsing
> --------------------------
>
> Key: ISPN-12307
> URL: https://issues.redhat.com/browse/ISPN-12307
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Dan Berindei
> Priority: Major
>
> Media type parsing has some problems with double-quoted parameters:
> * {{;}} and {{,}} are interpreted as parameter/media type separator even when they occur in a quoted parameter value
> * {{'}} is interpreted as a quoting character, the spec says only {{"}} must be used for quoting
> * Only spaces are allowed, not {{\t}}.
> * Spaces are allowed in too many places, e.g. {{type / subtype}} or {{parameter = value}}
> * Start and end quotes are removed from quoted parameter values, but the escaped characters inside are not unescaped.
> * Quotes are not added back in {{toString()}}, which makes deserialization fail if one of the parameters included an escaped double-quote (e.g. {{type/subtype; param="\""}}).
> Performance can also be improved, as we create many {{String}} instances via {{trim()}}, {{substring()}}, or {{split()}}.
> The clearest explanation of the media type grammar seems to be in
> https://tools.ietf.org/html/rfc7231#section-3.1.1.1
> https://tools.ietf.org/html/rfc7230#section-3.2.6
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (ISPN-12335) Expose rebalancing progress
by Dan Berindei (Jira)
Dan Berindei created ISPN-12335:
-----------------------------------
Summary: Expose rebalancing progress
Key: ISPN-12335
URL: https://issues.redhat.com/browse/ISPN-12335
Project: Infinispan
Issue Type: Feature Request
Components: Core
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 12.0.0.Final
Rebalancing sometimes takes a long time without logging anything (except at TRACE level). We need to expose the progress somehow: either the number of transferred segments, the number of transferred entries, or maybe even the size of the transferred entries when the size is available.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years