[
https://issues.apache.org/jira/browse/SHIRO-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876232#comment-15876232
]
Brian Demers commented on SHIRO-613:
------------------------------------
Any chance you have a simple reproduce case you can share? (github or
something). That would make it faster to track down (and we can open a more
targeted bug)
As far a releases go, 1.4.0 is just about done, but there is at least one more
feature trying to get in. There is a 3rd party OAuth module (but I haven't used
it personally).
> 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)
