[JBoss JIRA] (ISPN-5863) Default metadata not merged for DecoratedCache operations
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5863?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5863:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1272052|https://bugzilla.redhat.com/show_bug.cgi?id=1272052] from POST to MODIFIED
> Default metadata not merged for DecoratedCache operations
> ---------------------------------------------------------
>
> Key: ISPN-5863
> URL: https://issues.jboss.org/browse/ISPN-5863
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.0.Alpha1
> Reporter: Wolf-Dieter Fink
> Assignee: Galder Zamarreño
> Priority: Critical
> Fix For: 8.1.0.Beta1
>
>
> If the ISPN server cache is configured with expiration like:
> <cache-container name="local" default-cache="default" statistics="true">
> <state-persistence/>
> <local-cache name="default" start="EAGER">
> <locking acquire-timeout="30000" concurrency-level="1000" striping="false"/>
> <transaction mode="NONE"/>
> <expiration lifespan="1000" interval="20000"/>
> </local-cache>
> The entry should automatic expired in 1second after it is added.
> But a client still have the key
> - after 1 sec where it should have been expired
> - after 20 sec where the reaper should have removed it
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5863) Default metadata not merged for DecoratedCache operations
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5863?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5863:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1272052|https://bugzilla.redhat.com/show_bug.cgi?id=1272052] from ASSIGNED to POST
> Default metadata not merged for DecoratedCache operations
> ---------------------------------------------------------
>
> Key: ISPN-5863
> URL: https://issues.jboss.org/browse/ISPN-5863
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.0.Alpha1
> Reporter: Wolf-Dieter Fink
> Assignee: Galder Zamarreño
> Priority: Critical
> Fix For: 8.1.0.Beta1
>
>
> If the ISPN server cache is configured with expiration like:
> <cache-container name="local" default-cache="default" statistics="true">
> <state-persistence/>
> <local-cache name="default" start="EAGER">
> <locking acquire-timeout="30000" concurrency-level="1000" striping="false"/>
> <transaction mode="NONE"/>
> <expiration lifespan="1000" interval="20000"/>
> </local-cache>
> The entry should automatic expired in 1second after it is added.
> But a client still have the key
> - after 1 sec where it should have been expired
> - after 20 sec where the reaper should have removed it
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5918) Remote transactions can be registered after cache stop and block shutdown
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-5918?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-5918:
-------------------------------
Status: Open (was: New)
> Remote transactions can be registered after cache stop and block shutdown
> -------------------------------------------------------------------------
>
> Key: ISPN-5918
> URL: https://issues.jboss.org/browse/ISPN-5918
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 8.0.1.Final, 8.1.0.Alpha2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 8.1.0.Beta1, 8.1.0.Final
>
>
> The cache status check is done in {{InvocationContextInterceptor}}, but by that time the remote transaction was already registered, and there is nothing to remove it from the transaction table.
> This can be seen in {{TerminatedCacheWhileInTxTest}}, which logs ""Wait very briefly and then make call." and then proceeds to wait for 30s (i.e. until the cache shutdown timeout expires).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5918) Remote transactions can be registered after cache stop and block shutdown
by Dan Berindei (JIRA)
Dan Berindei created ISPN-5918:
----------------------------------
Summary: Remote transactions can be registered after cache stop and block shutdown
Key: ISPN-5918
URL: https://issues.jboss.org/browse/ISPN-5918
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 8.1.0.Alpha2, 8.0.1.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 8.1.0.Beta1, 8.1.0.Final
The cache status check is done in {{InvocationContextInterceptor}}, but by that time the remote transaction was already registered, and there is nothing to remove it from the transaction table.
This can be seen in {{TerminatedCacheWhileInTxTest}}, which logs ""Wait very briefly and then make call." and then proceeds to wait for 30s (i.e. until the cache shutdown timeout expires).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months