-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P2
-
Affects Version/s: 9
-
Component/s: deploy
-
b127
-
b175
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8182789 | 10 | Andy Herrick | P2 | Resolved | Fixed | b14 |
| JDK-8182507 | 9.0.4 | Andy Herrick | P2 | Resolved | Fixed | b01 |
This is a regression in JDK9.
Due to a change in DynamicProxyManager caused by warning cleanup (JDK-JDK-8156586) when a proxy is removed from the ProxyCache we usually get a java.util.ConcurrentModificationException.
We are returning (from getProxyList()) the cached List of proxys instead of a clone of it.
fix is trivial:
List<Proxy> dup = new ArrayList<Proxy>();
- dup = pInfo;
+ dup.addAll(pInfo);
return dup;
Due to a change in DynamicProxyManager caused by warning cleanup (JDK-JDK-8156586) when a proxy is removed from the ProxyCache we usually get a java.util.ConcurrentModificationException.
We are returning (from getProxyList()) the cached List of proxys instead of a clone of it.
fix is trivial:
List<Proxy> dup = new ArrayList<Proxy>();
- dup = pInfo;
+ dup.addAll(pInfo);
return dup;
- backported by
-
JDK-8182507 unreachable proxy server causes ConcurrentModificationException
-
- Resolved
-
-
-
- Resolved
-