-
Bug
-
Resolution: Fixed
-
P3
-
1.0, 1.2.1, 1.3.0, 1.4.2
-
None
-
only
-
x86, sparc
-
solaris_7, windows_98, windows_nt
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2032671 | 1.4.0 | Anita Jindal | P3 | Resolved | Fixed | beta |
Subject: race condition in IIOPConnection.java
To: ###@###.###
MIME-Version: 1.0
Content-MD5: a6e7xDkIshetlXN0MisxxA==
After long hours of debugging......
Excerpt from Sanjeev's Email.
=============================
In IIOPConnection.CachedWorkerThread, the variable currentWork
is declared as static. This causes a race condition where two
threads start working on the same client request. So two replies
get sent back to the client for one request. So the client's
ReaderThread throws a NullPointerException and dies.
To: ###@###.###
MIME-Version: 1.0
Content-MD5: a6e7xDkIshetlXN0MisxxA==
After long hours of debugging......
Excerpt from Sanjeev's Email.
=============================
In IIOPConnection.CachedWorkerThread, the variable currentWork
is declared as static. This causes a race condition where two
threads start working on the same client request. So two replies
get sent back to the client for one request. So the client's
ReaderThread throws a NullPointerException and dies.
- backported by
-
JDK-2032671 race condition in IIOPConnection.java
-
- Resolved
-
- duplicates
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-