Bug 3472 – Secure Conversation Context creation is not thread safe

Bug 3472 - Secure Conversation Context creation is not thread safe

Summary:

Secure Conversation Context creation is not thread safe

Status:	RESOLVED FIXED

Product:	Java WS Core
Component:	globus_wsrf_core
Version:	4.0.0
Platform:	PC All

Importance:	P3 critical
Target Milestone:	---
Assigned To:	Jarek Gawor

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-06-13 09:57 by Thomas Sandholm
Modified:	2005-06-13 12:17 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

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

Description From Thomas Sandholm 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 Jarek Gawor 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 Thomas Sandholm 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 Jarek Gawor 2005-06-13 11:20:37 -------

Ah, ok, that's different.

------- Comment #4 From Jarek Gawor 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 Jarek Gawor 2005-06-13 12:17:28 -------

Made the create function synchronized. Fix committed to trunk and 
globus_40_branch.