Mailing-List: contact dev-help@shiro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@shiro.apache.org
Date: Tue, 21 Feb 2017 15:13:45 +0000 (UTC)
From: "Brian Demers (JIRA)" <jira@apache.org>
To: dev@shiro.apache.org
Message-ID: <JIRA.13044068.1487358049000.19202.1487690025011@Atlassian.JIRA>
In-Reply-To: <JIRA.13044068.1487358049000@Atlassian.JIRA>
References: <JIRA.13044068.1487358049000@Atlassian.JIRA> <JIRA.13044068.1487358049611@jira-lw-us.apache.org>
Subject: [jira] [Commented] (SHIRO-613) StoppedSessionException: Session
 with id has been explicitly stopped.  No further interaction under this
 session is allowed.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 21 Feb 2017 15:13:50 -0000


    [ https://issues.apache.org/jira/browse/SHIRO-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876132#comment-15876132 ] 

Brian Demers commented on SHIRO-613:
------------------------------------

It can, that is the point of that method, but it relies on a the Subject creation and association with the thread.  This can be done in a few ways (and handled out of the box in servlet and non-servlet environments).

That said, you may want to take a look at [Shiro's Thread Association|https://shiro.apache.org/subject.html#thread-association] doc for more details.

> StoppedSessionException: Session with id has been explicitly stopped.  No further interaction under this session is allowed.
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SHIRO-613
>                 URL: https://issues.apache.org/jira/browse/SHIRO-613
>             Project: Shiro
>          Issue Type: Bug
>          Components: Authentication (log-in), Session Management
>    Affects Versions: 1.3.2
>            Reporter: sreenivas Harshith
>              Labels: Sessiontimeout, StoppedSessionException, login, session
>
> I am using default shiro native session manager and Session DAO backed by Db store for storing sessions. I have set the session timeout to 10 min and I have the same user login multiple times, say 8 times. Once the session is expired I tried to login with same user credentials from a different client and shiro is calling this delete(Session sn) method implemented in my DAO to delete those old sessions that are expired. Once the deletion is completed it throws an exception with the deleted Session id saying org.apache.shiro.session.StoppedSessionException: Session with id [a9dd97a1-90d4-435c-b363-f74052dfa0dc] has been explicitly stopped.  No further interaction under this session is allowed, and  it fails to login the user.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)