Bugzilla – Bug 3472
Secure Conversation Context creation is not thread safe
Last modified: 2005-06-13 12:17:28
You need to
before you can comment on or make changes to this bug.
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.
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?
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.
Ah, ok, that's different.
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.
Made the create function synchronized. Fix committed to trunk and