[JBoss JIRA] (ISPN-3096) ComponentRegistryTest.testConcurrentLookupSameComponentRegistry intermittent failure
by Dan Berindei (JIRA)
Dan Berindei created ISPN-3096:
----------------------------------
Summary: ComponentRegistryTest.testConcurrentLookupSameComponentRegistry intermittent failure
Key: ISPN-3096
URL: https://issues.jboss.org/browse/ISPN-3096
Project: Infinispan
Issue Type: Bug
Components: Test Suite
Affects Versions: 5.3.0.Beta1
Reporter: Dan Berindei
Assignee: Dan Berindei
Priority: Minor
Fix For: 5.3.0.Beta2
The test checks that when the injection method is blocked, calling {{ComponentRegistry.getComponent(...)}} in another thread will return null.
However, if the thread doing the check is delayed for a long time (longer than 1s), the check will fail because the injection thread will have been unblocked.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (ISPN-3094) Cache.putForExternalRead in DIST transactional mode is not replicated to other members
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-3094?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-3094:
--------------------------------
Component/s: Core API
Distributed Cache
> Cache.putForExternalRead in DIST transactional mode is not replicated to other members
> --------------------------------------------------------------------------------------
>
> Key: ISPN-3094
> URL: https://issues.jboss.org/browse/ISPN-3094
> Project: Infinispan
> Issue Type: Bug
> Components: Core API, Distributed Cache
> Affects Versions: 5.2.5.Final
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 5.3.0.Beta2, 5.3.0.Final
>
>
> Since the context is non transactional, no command is enqueued in the transaction's modification list to be replicated at prepare time and also TxDistributionInterceptor does not explicitly replicate the command to other owners immediately after local execution. The command end up executing only on originator. This bug seems to be caused by the DistributionInterceptor class hierarchy refactoring in 5.2.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months