Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SHIRO-443: Creation of session validation scheduler made thread safe #4

Closed
wants to merge 1,607 commits into from

Conversation

cstamas
Copy link
Member

@cstamas cstamas commented May 23, 2013

To make sure it is created only once, and to not end up with
multiple daemon threads lurking around in case of heavy load on startup
for session creation.

kaosko and others added 30 commits October 28, 2010 09:24
…the 1.0.x branch) to ensure it is not included with the release.

git-svn-id: https://svn.apache.org/repos/asf/shiro/trunk@1028529 13f79535-47bb-0310-9956-ffa450edef68
spring: 3.0.5.RELEASE
ehcache: 2.2.0
aspectj: 1.6.9
groovy: 1.7.5
quartz: 1.6.1
slf4j: 1.6.1
junit: 4.8.2
easymock: 3.0



git-svn-id: https://svn.apache.org/repos/asf/shiro/trunk@1028530 13f79535-47bb-0310-9956-ffa450edef68
…erasure and one test case - Shiro will run fine on 1.5, it just can't build on it at the moment. I'll create another issue to address this for Shiro 1.1.1 or 1.2

git-svn-id: https://svn.apache.org/repos/asf/shiro/trunk@1028866 13f79535-47bb-0310-9956-ffa450edef68
…le subclass to accompany new 'Testing' documentation page. Upgraded the maven gpg plugin from version 1.0 to 1.1

git-svn-id: https://svn.apache.org/repos/asf/shiro/trunk@1037950 13f79535-47bb-0310-9956-ffa450edef68
…hen using only mock Subject instances (without the presence of a SecurityManager)

git-svn-id: https://svn.apache.org/repos/asf/shiro/trunk@1044106 13f79535-47bb-0310-9956-ffa450edef68
…compatible changes and new features. Any point release (1.1.x) bug fixes will be done in the branches/shiro-root-1.1.x branch and merged into the trunk.

git-svn-id: https://svn.apache.org/repos/asf/shiro/trunk@1044157 13f79535-47bb-0310-9956-ffa450edef68
…. Now deploys successfully, although Spring remoting is failing for the Swing app.

git-svn-id: https://svn.apache.org/repos/asf/shiro/trunk@1044181 13f79535-47bb-0310-9956-ffa450edef68
…horizingRealm should implement it directly

https://issues.apache.org/jira/browse/SHIRO-231
- implemented as specified
- ModularRealmAuthorizer now invokes only AuthorizingRealm to participate in authorization
- Fix AuthorizingRealmTest to expect AuthorizingRealm only


git-svn-id: https://svn.apache.org/repos/asf/shiro/trunk@1057032 13f79535-47bb-0310-9956-ffa450edef68
…horizingRealm should implement it directly

https://issues.apache.org/jira/browse/SHIRO-231
- remove obsolete import

git-svn-id: https://svn.apache.org/repos/asf/shiro/trunk@1057034 13f79535-47bb-0310-9956-ffa450edef68
…horizingRealm should implement it directly

https://issues.apache.org/jira/browse/SHIRO-231
- ModularRealmAuthorizer should test for Authorizer type, not AuthorizingRealm

git-svn-id: https://svn.apache.org/repos/asf/shiro/trunk@1057039 13f79535-47bb-0310-9956-ffa450edef68
…efore but apparently never committed

git-svn-id: https://svn.apache.org/repos/asf/shiro/trunk@1069525 13f79535-47bb-0310-9956-ffa450edef68
…ment to avoid Maven 3.0.x issue where parent is not in local repo yet.

https://issues.apache.org/jira/browse/SHIRO-236
- applied the proposed patch as is (add relativePath element to the poms)

git-svn-id: https://svn.apache.org/repos/asf/shiro/trunk@1069529 13f79535-47bb-0310-9956-ffa450edef68
…de method info in stack trace

https://issues.apache.org/jira/browse/SHIRO-243
- catch, re-wrap and re-throw AuthorizationException with Method Interceptor specific message

git-svn-id: https://svn.apache.org/repos/asf/shiro/trunk@1069537 13f79535-47bb-0310-9956-ffa450edef68
Les Hazlewood and others added 27 commits July 25, 2012 20:37
… backwards and forwards compatible. A more suitable longer term solution should be addressed for Shiro 1.3 / 2.0 +

git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1403599 13f79535-47bb-0310-9956-ffa450edef68
…by the ReflectionBuilder. Removed this duplicate functionality from the IniSecurityManagerFactory (don't want to call init twice)

git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1457316 13f79535-47bb-0310-9956-ffa450edef68
To make sure it is created only once, and to not end up with
multiple daemon threads lurking around in case of heavy load on startup
for session creation.
With previous commit scheduler.enableSessionValidation()
would be still invoked more than once. The
ExecutorServiceSessionValidationScheduler implementation
would replace ScheduledExecutorService in that case, which
is undesired.
asfgit pushed a commit that referenced this pull request Mar 25, 2016
To make sure it is created only once, and to not end up with
multiple daemon threads lurking around in case of heavy load on startup
for session creation.

closes #4
@asfgit asfgit closed this in 2537d08 Mar 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants