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

Kalle Korhonen commented on SHIRO-96:
-------------------------------------

Agree and thanks for the explanations. Yes, I knew that wouldn't be the 
ultimate solution. Digging further into finding out why the value needs to 
exist in the cache in the first place would have been my next task, so you 
saved me a bunch of time and happy to learn that this issue is already on the 
radar. Adding to strong references in put makes sense to me and it solves the 
immediate problem with the test reliability so I'll do what I suggest to close 
this issue and we'll deal with SHIRO-49 separately.

> Add meaningful integration tests to assert key web functionality
> ----------------------------------------------------------------
>
>                 Key: SHIRO-96
>                 URL: https://issues.apache.org/jira/browse/SHIRO-96
>             Project: Shiro
>          Issue Type: Test
>          Components: Authentication (log-in)
>    Affects Versions: 1.0
>         Environment: any
>            Reporter: Kalle Korhonen
>             Fix For: 1.0
>
>         Attachments: integration-tests.patch
>
>
> Related to SHIRO-93 (but you closed it already - could have re-opened as 
> well). Assert login/logout and remember me functionality. Also updating 
> htmlunit to newly released 2.6. Note that tests revealed an interesting 
> thread-safety issue: sometimes 
> getAuthorizationCache().get(upToken.getUsername()); on line 141 of 
> SimpleAccountRealm returned null, causing the authentication to fail. It 
> happened much frequently when I was running the test via Eclipse, but 
> couldn't get it to run when running via Maven. I took an initial look at the 
> CacheManager and didn't follow through completely, but it looked like that a 
> map initialization somewhere may not have been synchronized. Note that these 
> tests run considerably faster than if a human was using a browser but 
> otherwise they don't semantically do anything else different. A patch to 
> follow.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to