[
https://issues.apache.org/jira/browse/IGNITE-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197118#comment-15197118
]
Anton Vinogradov commented on IGNITE-810:
-----------------------------------------
one more possible fail:
[12:21:16,303][SEVERE][qtp1818554421-89][] Failed to update web session: null
class org.apache.ignite.IgniteClientDisconnectedException: Client node
disconnected: client
at
org.apache.ignite.internal.GridKernalGatewayImpl.readLock(GridKernalGatewayImpl.java:87)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTransactionsImpl.txStart0(IgniteTransactionsImpl.java:152)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTransactionsImpl.txStart(IgniteTransactionsImpl.java:68)
at
org.apache.ignite.cache.websession.WebSessionFilter.doFilter(WebSessionFilter.java:359)
at
try (Transaction tx = txs.txStart(PESSIMISTIC, REPEATABLE_READ)) {
Test: testClientReconnectRequest
> [Test] GridWebSessionFilter does not retry update when transactional cache is
> used
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-810
> URL: https://issues.apache.org/jira/browse/IGNITE-810
> Project: Ignite
> Issue Type: Bug
> Reporter: Artem Shutak
> Labels: Muted_test
>
> When transactional cache is used for web sessions then GridWebSessionFilter
> does not retry updates (for atomic cache updates are retried, see
> GridWebSessionListener.updateAttributes).
> In current implementation we cannot retry transaction since all filter's code
> is executed inside transaction (see GridWebSessionFilter.doFilter).
> Issue is reproduced by WebSessionTransactionalSelfTest.
> See gg-8166.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
