Yes, it is true. HashMap.get() can cause an infinite loop. Everyone I've talked to didn't believe it either, but yet there it is -- right in front of my very eyes. Now, before anyone jumps up and shouts that HashMap isn't synchronized, I want to make it clear that I know that. In fact, here is the paragraph from the JavaDocs:
Note that this implementation is not synchronized. If multiple threads access this map concurrently, and at least one of the threads modifies the map structurally, it must be synchronized externally. (A structural modification is any operation that adds or deletes one or more mappings; merely changing the value associated with a key that an instance already contains is not a structural modification.) This is typically accomplished by synchronizing on some object that naturally encapsulates the map.
Now, I've always taken that standard warning in all the Collections classes as simply stating the obvious: these data structures are synchronized and if you aren't doing your own synchronization you'll get dirty/unreliable/unknown data and/or behavior.
But never in my wildest dreams would I have thought that without proper synchronization that an infinite loop could occur!
- RIAA sues the dead | The Register
- Javalobby - Java J2EE Programming Forums - Coldtags suite 2.1: 210+ custom JSP tags
- as400 Iseries Tips
- ibm as400 manuals v5r4
- Creating an as400 Query
- as400 subsystem
- AS400 API - QCMDEXC - Execute Command
- AS400 APIs
- AS400 / ISeries Freeware / Shareware
- Free AS400 & iSeries Software Tools & Utilities Downloads