Bug 3472 - Secure Conversation Context creation is not thread safe
: Secure Conversation Context creation is not thread safe
Status: RESOLVED FIXED
: Java WS Core
globus_wsrf_core
: 4.0.0
: PC All
: P3 critical
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-06-13 09:57 by
Modified: 2005-06-13 12:17 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2005-06-13 09:57:13
When secure contexts are created and destroyed concurrently 
ConcurrentModificationExceptions errors are thrown.
The SecureContextHome.create operation needs to by synchronized to avoid this 
behavior. Further the Timer framework does not catch the exception and causes 
all timer threads to stop.
------- Comment #1 From 2005-06-13 10:57:10 -------
I don't see how _all_ the timer threads could stop by one exception but I can 
see that _one_ timer thread can die on exception. Can you clarify?
------- Comment #2 From 2005-06-13 11:17:06 -------
I believe it stops the critical resource sweeper thread thus stopping all the 
expired resources from getting destroyed, but I have asked the developer who 
is seeing these errors for more info.
------- Comment #3 From 2005-06-13 11:20:37 -------
Ah, ok, that's different. 
------- Comment #4 From 2005-06-13 11:58:21 -------
I fixed the timer code to catch the unexpected exception and log the error in 
case. I committed to fixes to trunk and globus_40_branch. 
------- Comment #5 From 2005-06-13 12:17:28 -------
Made the create function synchronized. Fix committed to trunk and 
globus_40_branch.