Opened 6 years ago

Closed 6 years ago

#12246 closed defect (invalid)

JOSM does not quit - JCSCacheManager shutdown stalls due to missing method: java.util.concurrent.ConcurrentHashMap.keySet()

Reported by: cmuelle8 Owned by: cmuelle8
Priority: normal Milestone:
Component: Core Version: latest
Keywords: Cc:


I've experienced this for a while now and think it's worth reporting:

java.lang.NoSuchMethodError: java.util.concurrent.ConcurrentHashMap.keySet()Ljava/util/concurrent/ConcurrentHashMap$KeySetView;
        at org.apache.commons.jcs.utils.threadpool.ThreadPoolManager.getPoolNames(
        at org.apache.commons.jcs.utils.threadpool.ThreadPoolManager.dispose(
        at org.apache.commons.jcs.engine.control.CompositeCacheManager.shutDown(
        at org.openstreetmap.josm.Main.exitJosm(
        at org.openstreetmap.josm.gui.MainApplication$1.windowClosing(
        at java.awt.AWTEventMulticaster.windowClosing(
        at java.awt.AWTEventMulticaster.windowClosing(
        at java.awt.Window.processWindowEvent(
        at javax.swing.JFrame.processWindowEvent(
        at java.awt.Window.processEvent(
        at java.awt.Component.dispatchEventImpl(
        at java.awt.Container.dispatchEventImpl(
        at java.awt.Window.dispatchEventImpl(
        at java.awt.Component.dispatchEvent(
        at java.awt.EventQueue.dispatchEventImpl(
        at java.awt.EventQueue.access$300(
        at java.awt.EventQueue$
        at java.awt.EventQueue$
        at Method)
        at java.awt.EventQueue$
        at java.awt.EventQueue$
        at Method)
        at java.awt.EventQueue.dispatchEvent(
        at org.GNOME.Accessibility.AtkWrapper$5.dispatchEvent(
        at java.awt.EventDispatchThread.pumpOneEventForFilters(
        at java.awt.EventDispatchThread.pumpEventsForFilter(
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(
        at java.awt.EventDispatchThread.pumpEvents(
        at java.awt.EventDispatchThread.pumpEvents(

Attachments (0)

Change History (5)

comment:1 Changed 6 years ago by cmuelle8


java version "1.7.0_91"
OpenJDK Runtime Environment (IcedTea 2.6.3) (7u91-2.6.3-0ubuntu0.15.10.1)
OpenJDK 64-Bit Server VM (build 24.91-b01, mixed mode)

comment:2 Changed 6 years ago by Don-vip

Where does you josm.jar come from? It seems it have been compiled with jdk8 instead of jdk7.

comment:3 Changed 6 years ago by Don-vip

Owner: changed from team to cmuelle8
Status: newneedinfo

can you please also add a status report as requested on newticket? Thanks.

comment:4 Changed 6 years ago by cmuelle8

First things first:

Build-Date:2015-12-31 15:58:29

Identification: JOSM/1.5 (9229 SVN de) Linux Ubuntu 15.10
Memory Usage: 693 MB / 1609 MB (358 MB allocated, but free)
Java version: 1.7.0_91, Oracle Corporation, OpenJDK 64-Bit Server VM
Java package: openjdk-7-jre:amd64-7u91-2.6.3-0ubuntu0.15.10.1

- PicLayer (31772)
- RoadSigns (31772)
- alignways (31772)
- apache-commons (31772)
- editgpx (31106)
- imagery_offset_db (31772)
- kendzi3d (1.0.189)
- kendzi3d-jogl (41)
- kendzi3d-resources (0.0.1)
- log4j (31879)
- openvisible (31106)
- pbf (31772)
- photo_geotagging (31772)
- photoadjust (31772)
- poly (31772)
- print (31772)
- reverter (31772)
- turnlanes (31772)
- turnrestrictions (31772)
- utilsplugin2 (31890)
- wikipedia (31866)

I've done some more research on this - as you've pointed out, I had built with openjdk8 and ran with jdk7. Using this configuration I am able to reproduce the bug reported, just tested with a fresh checkout. The following configurations, however, are fine and do not show bogus behavior:

  • building w/ openjdk7, running w/ openjdk7
  • building w/ openjdk7, running w/ openjdk8
  • building w/ openjdk8, running w/ openjdk8

If you think it's not worth the effort to do research on this, I do not oppose closing the bug. Building with openjdk8 and running with a java version below probably isn't intended by the jdk devs anyway. Maybe a warning will help, however, like:

JOSM was built with a JDK versioned higher than your runtime, please update your runtime!

I know that there is a warning in place currently as MOTD, requesting to upgrade to Java8. But maybe similar problems will arise on a major upgrade of java versions at a later time, again. As such, checking built/runtime pair at start might be helpful to more easily detect potential bug sources.


comment:5 Changed 6 years ago by Don-vip

Resolution: invalid
Status: needinfoclosed

OK thanks for the info.
There's already an error message if you try to run JOSM with Java < 7, and a warning message on startup page of you run it with Java 7.
We take care of compiling JOSM with the adequate JDK. Anyone who tries to compile JOSM by hand must take care of running it with a correct runtime also :)

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain cmuelle8.
as The resolution will be set.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.