[jira] [Resolved] (GEODE-10097) Do not use Thread.sleep in MessageDispatcher for re-authentication feature

2022-04-14 Thread Jinmei Liao (Jira)


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

Jinmei Liao resolved GEODE-10097.
-
Resolution: Fixed

> Do not use Thread.sleep in MessageDispatcher for re-authentication feature
> --
>
> Key: GEODE-10097
> URL: https://issues.apache.org/jira/browse/GEODE-10097
> Project: Geode
>  Issue Type: Improvement
>  Components: client queues, client/server
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
>  Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> MessageDispatcher uses Thread.sleep and wakes up intervals to recheck 
> authorization to see if new subject has re-logged in or not, if not, it will 
> call "authorize" again and again till timeout. Suggest using "wait/notify" 
> mechanism to wait for the subject to be updated, this way we don't use 
> Thread.sleep and not place unnecessary calls to the security manager.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Resolved] (GEODE-10097) Do not use Thread.sleep in MessageDispatcher for re-authentication feature

2022-03-15 Thread Jinmei Liao (Jira)


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

Jinmei Liao resolved GEODE-10097.
-
Fix Version/s: 1.15.0
   1.16.0
 Assignee: Jinmei Liao
   Resolution: Fixed

> Do not use Thread.sleep in MessageDispatcher for re-authentication feature
> --
>
> Key: GEODE-10097
> URL: https://issues.apache.org/jira/browse/GEODE-10097
> Project: Geode
>  Issue Type: Improvement
>  Components: client queues, client/server
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
>  Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0, 1.16.0
>
>
> MessageDispatcher uses Thread.sleep and wakes up intervals to recheck 
> authorization to see if new subject has re-logged in or not, if not, it will 
> call "authorize" again and again till timeout. Suggest using "wait/notify" 
> mechanism to wait for the subject to be updated, this way we don't use 
> Thread.sleep and not place unnecessary calls to the security manager.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)