(tomcat) branch 11.0.x updated: Be explicit where we have to use ConcurrentHashMap

ConcurrentHashMap 813af12fa3 is described below commit 813af12fa30c2e8a6f0b231a48335847906a7e39 Author: Mark Thomas AuthorDate: Thu Sep 4 16:03:54 2025 +0100 Be explicit where we have to use ConcurrentHashMap --- java/org/apache/tomcat/util/http/FastHttpDateFormat.java | 4 +++- 1 file changed

(tomcat) branch 10.1.x updated: Be explicit where we have to use ConcurrentHashMap

ConcurrentHashMap f24f4fc2f1 is described below commit f24f4fc2f1364f630984ac994883b6cf74a07a25 Author: Mark Thomas AuthorDate: Thu Sep 4 16:03:54 2025 +0100 Be explicit where we have to use ConcurrentHashMap --- java/org/apache/tomcat/util/http/FastHttpDateFormat.java | 4 +++- 1 file changed

(tomcat) branch 9.0.x updated: Be explicit where we have to use ConcurrentHashMap

ConcurrentHashMap cb71338569 is described below commit cb7133856936ef2b0bb211fc3ca4b330372e8824 Author: Mark Thomas AuthorDate: Thu Sep 4 16:03:54 2025 +0100 Be explicit where we have to use ConcurrentHashMap --- java/org/apache/tomcat/util/http/FastHttpDateFormat.java | 4 +++- 1 file changed, 3

(tomcat) branch main updated: Be explicit where we have to use ConcurrentHashMap

ConcurrentHashMap 4bcac32ccc is described below commit 4bcac32cccb7290dfd6e4a66b892d220402d5205 Author: Mark Thomas AuthorDate: Thu Sep 4 16:03:54 2025 +0100 Be explicit where we have to use ConcurrentHashMap --- java/org/apache/tomcat/util/http/FastHttpDateFormat.java | 4 +++- 1 file changed, 3

(tomcat) branch main updated: Clarify that poolMap must use ConcurrentHashMap. No functional change.

ConcurrentHashMap. No functional change. 68a7046763 is described below commit 68a7046763ac3e26692569adeef01a4a65df2ce8 Author: Mark Thomas AuthorDate: Sat Aug 30 12:01:03 2025 +0100 Clarify that poolMap must use ConcurrentHashMap. No functional change. Reported by Coverity scan running on

[Bug 55554] NoSuchMethodError on ConcurrentHashMap$KeySetView

https://bz.apache.org/bugzilla/show_bug.cgi?id=4 --- Comment #9 from Rossen Stoyanchev --- FWIW I do not use Ubuntu packages for Tomcat. I download it from the Tomcat download page. So something there gave me a binary with the same or similar issue. -- You are receiving this mail because: Y

[Bug 55554] NoSuchMethodError on ConcurrentHashMap$KeySetView

https://bz.apache.org/bugzilla/show_bug.cgi?id=4 --- Comment #8 from Emmanuel Bourg --- This issue has been fixed in the version 8.5.9-2 of the tomcat8 package in Debian Stretch. The tomcat8 package in Debian Jessie was built with Java 7 and is not affected. The Ubuntu package is likely to b

[Bug 55554] NoSuchMethodError on ConcurrentHashMap$KeySetView

https://bz.apache.org/bugzilla/show_bug.cgi?id=4 --- Comment #7 from Emmanuel Bourg --- A simple workaround would be to use the default JRE in Ubuntu 16.04 (OpenJDK 8) to run Tomcat. The issue is that the tomcat package in Ubuntu (and Debian too) allows the use of Java 7, it should be restri

[Bug 55554] NoSuchMethodError on ConcurrentHashMap$KeySetView

https://bz.apache.org/bugzilla/show_bug.cgi?id=4 --- Comment #6 from Mark Thomas --- Tomcat 7 should be built with Java 6 with only the WebSocket module built with Java 7. You are best going though the Ubuntu community for issues with the Ubuntu packaging. -- You are receiving this mail be

[Bug 55554] NoSuchMethodError on ConcurrentHashMap$KeySetView

https://bz.apache.org/bugzilla/show_bug.cgi?id=4 --- Comment #5 from Pablo Pazos --- It was reported on many places that for Ubuntu 16.04 Tomcat7 was build with Java8 while the docs said that it should be compatible with Java7: http://tomcat.apache.org/whichversion.html The issue is using T

[Bug 55554] NoSuchMethodError on ConcurrentHashMap$KeySetView

https://bz.apache.org/bugzilla/show_bug.cgi?id=4 --- Comment #4 from romain.manni-bucau --- Just a quick note if anyone encounters it again: some rpm of tomcat are created recompiling tomcat and I let you guess what can happen in such a process: a JDK 8 can be used. Typically the one of Feb 2

[Bug 55554] NoSuchMethodError on ConcurrentHashMap$KeySetView

https://issues.apache.org/bugzilla/show_bug.cgi?id=4 Christopher Schultz changed: What|Removed |Added Resolution|FIXED |INVALID --- Comment #3 from

[Bug 55554] NoSuchMethodError on ConcurrentHashMap$KeySetView

https://issues.apache.org/bugzilla/show_bug.cgi?id=4 [email protected] changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #2 from r

[Bug 55554] NoSuchMethodError on ConcurrentHashMap$KeySetView

https://issues.apache.org/bugzilla/show_bug.cgi?id=4 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 55554] New: NoSuchMethodError on ConcurrentHashMap$KeySetView

https://issues.apache.org/bugzilla/show_bug.cgi?id=4 Bug ID: 4 Summary: NoSuchMethodError on ConcurrentHashMap$KeySetView Product: Tomcat 8 Version: trunk Hardware: PC OS: Linux Status: NEW

Re: ConcurrentHashMap

> From: Ohad Shacham > To: [email protected] > Sent: 08/11/09, 14:47:25 > Subject: ConcurrentHashMap > > Hi, > > > > I noticed that in version 6.0.20 several Hashtables and HashMaps were > replaced by ConcurrentHashMaps. I have noticed that many Hashtabl

ConcurrentHashMap

Hi, I noticed that in version 6.0.20 several Hashtables and HashMaps were replaced by ConcurrentHashMaps. I have noticed that many Hashtables were not replaced; therefore, I assume that a contention detection tool was used to identify the contended Hashtables. I would be happy to know if this is