Modify

Opened 3 weeks ago

Last modified 9 hours ago

#15851 reopened defect

InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty

Reported by: jukey Owned by: jukey
Priority: normal Milestone:
Component: Core Version: tested
Keywords: connection ubuntu ssl tls security Cc: jukey

Description

I am using Ubuntu 17.10 and just installed JOSM using the command: apt-get install josm

When I am starting the application it initializes but once that is done it throws the error message you can see below. If I close the erroro dialog I can only do things that work locally in JOSM. I cannot even download OSM data or background images. Also downloading plugins does not work. I updated the application using the repository provided by JOSM ( https://josm.openstreetmap.de/wiki/Download#Ubuntu ) but the behavior did not change.

I find this an important bug as the problem happens on a common ubuntu installationusing the commen JOSM package so a lot of people might be affected.

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2018-01-28 23:08:56 +0100 (Sun, 28 Jan 2018)
Revision:13367
Build-Date:2018-01-28 22:25:44
URL:http://josm.openstreetmap.de/svn/trunk

Identification: JOSM/1.5 (13367 de) Linux Ubuntu 17.10
Memory Usage: 276 MB / 1918 MB (70 MB allocated, but free)
Java version: 9-Ubuntu+0-9b181-4, Oracle Corporation, OpenJDK 64-Bit Server VM
Screen: :0.0 1920x1080
Maximum Screen Size: 1920x1080
Java package: openjdk-9-jre:amd64-9~b181-4
Java ATK Wrapper package: libatk-wrapper-java:all-0.33.3-13
VM arguments: [-Djosm.restart=true, -Djava.net.useSystemProxies=true]

Last errors/warnings:
- W: Already here java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
- W: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
- W: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty. Ursache: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty. Ursache: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
- E: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty. Ursache: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty. Ursache: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
- W: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty. Ursache: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty. Ursache: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
- W: Already here java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
- W: Already here java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
- E: org.openstreetmap.josm.io.OsmApiInitializationException: org.openstreetmap.josm.io.OsmTransferException: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty. Ursache: org.openstreetmap.josm.io.OsmTransferException: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty. Ursache: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty. Ursache: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty. Ursache: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
- W: No configuration settings found.  Using hardcoded default values for all pools.
- W: Region [TMS_BLOCK_v2] Resetting cache

download.overpass.servers=[http://overpass.osm.rambler.ru/cgi/, https://overpass-api.de/api/]
gui.geometry=x=460,y=170,width=1000,height=740
imagery.layers.default=[]
imagery.offsetbookmarks=[]
josm.version=12545
laf=javax.swing.plaf.metal.MetalLookAndFeel
mappaint.renderer-class-name=org.openstreetmap.josm.data.osm.visitor.paint.StyledMapRenderer
mappaint.style.known-defaults=[resource://styles/standard/elemstyles.mapcss, resource://styles/standard/potlatch2.mapcss]
org.openstreetmap.josm.gui.download.DownloadDialog.geometry=x=460,y=240,width=1000,height=600
org.openstreetmap.josm.gui.preferences.PreferenceDialog.geometry=x=610,y=185,width=700,height=710
pluginmanager.version=12545
proxy.policy=use-system-settings

Attachments (1)

Bildschirmfoto vom 2018-01-30 08-23-44.png (14.8 KB) - added by jukey 3 weeks ago.
Screenshot of the error dialog that appears after starting JOSM

Download all attachments as: .zip

Change History (10)

Changed 3 weeks ago by jukey

Screenshot of the error dialog that appears after starting JOSM

comment:1 Changed 3 weeks ago by jukey

Cc: jukey added

comment:2 Changed 3 weeks ago by Don-vip

Keywords: ssl tls security added

comment:3 Changed 3 weeks ago by Don-vip

Summary: Freshly installed JOSM does not connect to internet ressourcesInvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty

comment:4 Changed 2 weeks ago by Don-vip

Owner: changed from team to jukey
Status: newneedinfo

Does the bug only occur with java 9? Can you please try with java 8?

comment:5 Changed 4 days ago by Don-vip

Resolution: needinfo
Status: needinfoclosed

comment:6 Changed 4 days ago by anonymous

The bug accours with the depoendencies installed. Any hint how to change the Java version?

comment:7 Changed 4 days ago by anonymous

Resolution: needinfo
Status: closedreopened

comment:8 Changed 4 days ago by Don-vip

You can use sudo update-java-alternatives

comment:9 Changed 9 hours ago by anonymous

I installed Java 8 and 9 by entering:

sudo apt-get install openjdk-8-jdk openjdk-8-jre openjdk-9-jre openjdk-9-jdk
Reading package lists... Done
Building dependency tree       
Reading state information... Done
openjdk-9-jdk is already the newest version (9~b181-4).
openjdk-9-jre is already the newest version (9~b181-4).
openjdk-8-jdk is already the newest version (8u151-b12-0ubuntu0.17.10.2).
openjdk-8-jre is already the newest version (8u151-b12-0ubuntu0.17.10.2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

This is my attempt to list and set Java 8:

~$ sudo update-java-alternatives -l
java-1.8.0-openjdk-amd64       1081       /usr/lib/jvm/java-1.8.0-openjdk-amd64
java-1.9.0-openjdk-amd64       1091       /usr/lib/jvm/java-1.9.0-openjdk-amd64

~$ sudo update-java-alternatives -s java-1.8.0-openjdk-amd64 
update-alternatives: error: no alternatives for mozilla-javaplugin.so
update-java-alternatives: plugin alternative does not exist: /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so

~$ java --version
Unrecognized option: --version
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

Setting Java to version 9 looks like this:

~$ sudo update-java-alternatives -s java-1.9.0-openjdk-amd64 
update-alternatives: error: no alternatives for mozilla-javaplugin.so
update-java-alternatives: plugin alternative does not exist: /usr/lib/jvm/java-9-openjdk-amd64/lib/IcedTeaPlugin.so

~$ java --version 

openjdk 9-Ubuntu
OpenJDK Runtime Environment (build 9-Ubuntu+0-9b181-4)
OpenJDK 64-Bit Server VM (build 9-Ubuntu+0-9b181-4, mixed mode)

Regardless of the version I chose the initially reported behavior when starting JOSM does not change.

Could this be an OpenJDK issue and I should try the Oracle version instead? Do you have any other suggestion?

Modify Ticket

Change Properties
Set your email in Preferences
Action
as reopened The owner will remain jukey.
as The resolution will be set.
to The owner will be changed from jukey to the specified user.
The owner will change to jukey
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket

Add Comment


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

 
Note: See TracTickets for help on using tickets.