ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anton Vinogradov (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IGNITE-2765) WebSessionFilter doesn't survive client reconnect
Date Mon, 14 Mar 2016 08:16:33 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Anton Vinogradov resolved IGNITE-2765.
--------------------------------------
    Resolution: Fixed

merged to master

> WebSessionFilter doesn't survive client reconnect
> -------------------------------------------------
>
>                 Key: IGNITE-2765
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2765
>             Project: Ignite
>          Issue Type: Bug
>          Components: websession
>    Affects Versions: 1.5.0.final
>            Reporter: Valentin Kulichenko
>            Assignee: Anton Vinogradov
>            Priority: Critical
>              Labels: community, customer, important
>             Fix For: 1.6
>
>
> If a {{WebSessionFilter}} is started with an embedded client, it is not functional after
the client disconnects and reconnects. Any operation throws the exception below.
> {noformat}
> java.lang.IllegalStateException: Cache has been closed or destroyed: WebCache
>  at org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:160)
>  at org.apache.ignite.internal.processors.cache.IgniteCacheProxy.onEnter(IgniteCacheProxy.java:1958)
>  at org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:855)
>  at org.apache.ignite.cache.websession.WebSessionFilter.doFilter0(WebSessionFilter.java:341)
> {noformat}
> We should get a new instance of the cache when the exception is thrown.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message