wms layer does not work

[Klerik7]

Hi,

I found out that my wms layer or cadastral map in my country is not working...

by installing older versions I found out that the last version that works is version 19286...I tried it on another pc,
but the problem persists...interestingly enough, another user also has version 19342, so I don't understand it at all...

wms_endpoint:https://kataster.skgeodesy.sk/eskn/services/NR/kn_wms_orto/MapServer/WmsServer

wms_endpoint:https://zbgisws.skgeodesy.sk/zbgis_wms_featureinfo/service.svc/get?request=GetCapabilities&service=WMS

Revision:19287
Is-Local-Build:true
Build-Date:2025-01-22 09:53:16

Identification: JOSM/1.5 (19287 SVN en) Windows 10 64-Bit
OS Build number: Windows 10 Home 22H2 (19045)
Memory Usage: 496 MB / 4556 MB (304 MB allocated, but free)
Java version: 21.0.6+7-LTS, Azul Systems, Inc., OpenJDK 64-Bit Server VM
Look and Feel: com.sun.java.swing.plaf.windows.WindowsLookAndFeel
Screen: \Display0 2560x1314x32bpp@64Hz (scaling 1.00×1.00)
Maximum Screen Size: 2560×1314
Best cursor sizes: 16×16→32×32, 32×32→32×32
System property file.encoding: UTF-8
System property sun.jnu.encoding: Cp1250
Locale info: en_SK
Numbers with default locale: 1234567890 -> 1234567890
VM arguments: [-Djpackage.app-version=1.5.19287, -XX:MaxRAMPercentage=75.0, --add-modules=java.scripting,java.sql,javafx.controls,javafx.media,javafx.swing,javafx.web, --add-exports=java.base/sun.security.action=ALL-UNNAMED, --add-exports=java.desktop/com.sun.imageio.plugins.jpeg=ALL-UNNAMED, --add-exports=java.desktop/com.sun.imageio.spi=ALL-UNNAMED, --add-opens=java.base/java.lang=ALL-UNNAMED, --add-opens=java.base/java.nio=ALL-UNNAMED, --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED, --add-opens=java.base/jdk.internal.ref=ALL-UNNAMED, --add-opens=java.desktop/javax.imageio.spi=ALL-UNNAMED, --add-opens=java.desktop/javax.swing.text.html=ALL-UNNAMED, --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED, -Djpackage.app-path=%UserProfile%\AppData\Local\JOSM\JOSM.exe]
Dataset consistency test: No problems found

Last errors/warnings:
- 00353.033 W: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. Cause: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. Cause: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
- 00353.046 W: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. Cause: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. Cause: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
- 00353.148 W: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. Cause: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. Cause: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
- 00389.592 E: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. Cause: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. Cause: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
- 00391.255 W: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. Cause: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. Cause: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
- 00391.255 W: Already here sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
- 00391.357 E: Failed to locate image 'https://zbgis.skgeodesy.sk/rts/images/logos/zbgis.png'
- 00391.370 W: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. Cause: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. Cause: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
- 00391.370 W: Already here sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
- 00391.472 E: Failed to locate image 'https://zbgis.skgeodesy.sk/rts/images/logos/zbgis.png'

[stoecker]

Are you sure it is still active? The logo image gives an 404 error.

[stoecker]

Service still works, I fixed the icon. So it seems Java does not accept the Slovak certificate.

We will need an exception again...

[Klerik7]

Do you think the problem is somewhere in Java?

[stoecker]

Java does have (like browsers also) an own certificate store, but Java does not have all root certificates. That's no issue for Linux, as there the system store is used. On Windows it can be an issue, especially for these government certificates.

We have a workaround to pull such CAs from Windows Certstore, but that manually needs to be checked and added.

But in trunk/src/org/openstreetmap/josm/io/CertificateAmendment.java​ "CA Disig Root R2" exists, so maybe it is a problem with your system? Can you access other TLS protected servers from JOSM? Can you access zbgis.skgeodesy.sk in Windows browser?

[Klerik7]

Yes, I can access this page in the Windows browser without any issues... but that doesn't explain why it works perfectly in version 19286. The same issue occurs in Windows 7.

[stoecker]

Please tell what you do to verify that it last worked in 19286 and how you start JOSM?

[Klerik7]

I have JOSM installed as an .exe file. On my old laptop, I have version 18772, and I found that it works without any issues. So, I started testing newer and newer installations, and the last version that works is 19286.

A small addition: I also had version 193XX working (I don’t remember the exact number), but around January 5, 2025, there was a hacker attack on our cadastre, so these services were down for a long time. The services were restored at the end of March, and that’s when I noticed that it no longer worked as before. I found that it only works up to version 19286.

However, this doesn’t explain the case of another user from my country, for whom it still works on version 19342, as I mentioned at the beginning. I really don’t understand this.

[stoecker]

As these version aren't available from this website I assume you download the exe files from GitHub?

Can you check which java version 19286 and 19287 (thus the first non-working) have? The changes between r19286:19287 cannot be the reason for any difference.

[Klerik7]

Yes, I downloaded it from GitHub and chose the file for Java 21 since that's the version I have on my PC.

Here, I uploaded a short video showing that in version 19287, clicking on the cadastral layer results in an error. However, when I install version 19286, a dialog box appears where I can select the necessary layers.

​https://youtu.be/t63zPnwPFPM

[stoecker]

Can you please add the status-report of both installations (or specifically the exact Java version). The file size from r19286 to r19287 is smaller, the source code OTOH should have increased it, so I think something outside JOSM changed as well, probably the java version.

[Klerik7]

Revision:19286
Is-Local-Build:true
Build-Date:2025-01-17 10:53:43

Identification: JOSM/1.5 (19286 SVN en) Windows 10 64-Bit
OS Build number: Windows 10 Home 22H2 (19045)
Memory Usage: 388 MB / 4556 MB (91 MB allocated, but free)
Java version: 21.0.5+11-LTS, Azul Systems, Inc., OpenJDK 64-Bit Server VM
Look and Feel: com.sun.java.swing.plaf.windows.WindowsLookAndFeel
Screen: \Display0 2560x1314x32bpp@64Hz (scaling 1.00×1.00)
Maximum Screen Size: 2560×1314
Best cursor sizes: 16×16→32×32, 32×32→32×32
System property file.encoding: UTF-8
System property sun.jnu.encoding: Cp1250
Locale info: en_SK
Numbers with default locale: 1234567890 -> 1234567890
VM arguments: [-Djpackage.app-version=1.5.19286, -XX:MaxRAMPercentage=75.0, --add-modules=java.scripting,java.sql,javafx.controls,javafx.media,javafx.swing,javafx.web, --add-exports=java.base/sun.security.action=ALL-UNNAMED, --add-exports=java.desktop/com.sun.imageio.plugins.jpeg=ALL-UNNAMED, --add-exports=java.desktop/com.sun.imageio.spi=ALL-UNNAMED, --add-opens=java.base/java.lang=ALL-UNNAMED, --add-opens=java.base/java.nio=ALL-UNNAMED, --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED, --add-opens=java.base/jdk.internal.ref=ALL-UNNAMED, --add-opens=java.desktop/javax.imageio.spi=ALL-UNNAMED, --add-opens=java.desktop/javax.swing.text.html=ALL-UNNAMED, --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED, -Djpackage.app-path=%UserProfile%\AppData\Local\JOSM\JOSM.exe]
Dataset consistency test: No problems found

Last errors/warnings:
- 00000.563 W: extended font config - overriding 'filename.Malgun_Gothic=malgun.ttf' with 'MALGUN.TTF'
- 00000.566 W: extended font config - overriding 'filename.Myanmar_Text=mmrtext.ttf' with 'MMRTEXT.TTF'
- 00000.567 W: extended font config - overriding 'filename.Mongolian_Baiti=monbaiti.ttf' with 'MONBAITI.TTF'
- 00001.102 E: java.security.KeyStoreException: Windows-ROOT not found. Cause: java.security.NoSuchAlgorithmException: Windows-ROOT KeyStore not available

[stoecker]

Jupp, Java changed from 21.0.5+11-LTS to 21.0.6+7-LTS - I don find anything obvious in the release notes: ​https://www.oracle.com/java/technologies/javase/21-0-6-relnotes.html

Short term fix: Install r19286 and download the Tested-Jar from this site and copy it to the filesystem manually over the one from the exe. You actually only need the Jar file.

[Klerik7]

But since r19286 works for me even as an .exe, I don’t need to test it, right? And what will be the solution for the future? Should I try an older version of Java?

There always seems to be some issue with Java… In the past, I had to deal with font rendering not being optimal. I was using the .jar version and then switched to the .exe, which helped a bit.

...Do I actually need to have Java installed on my PC? I just realized that JOSM includes its own Java.

[stoecker]

don’t need to test it, right? And what will be the solution for the future? Should I try an older version of Java?

Exactly that does the short term fix. Keep old Java, but use newest JOSM :-)

About solving that trouble: Currently there is nobody who could debug this. I personally don't use Windows at all anymore. If somebody finds the underlying cause I'd fix it, but I will not actively search it.

You can only hope that a newer Java version will again work or somebody else solves it.

...Do I actually need to have Java installed on my PC? I just realized that JOSM includes its own Java.

No. When you install the exe you use that Java version anyway. The Exe is essentially the JOSM-Jar + Java. You can simply replace the JAR file to get the newest version :-)

[Klerik7]

Ok, thanks for your time. It looks like r19369 + Java 22 is currently working for me.

[stoecker]

That's fine when it works with Java 22. Seems they only broke Java 21 update.

[Klerik7]

Probably yes... I downloaded the latest version with Java 22, and it works.

[gaben]

(Update based on comment:18.)

[Klerik7]

so my problem is here again...since version 19380 there is no .exe with java 22 among the installations on github, only java 24 and the same problem pops up again

[stoecker]

As there is still probably nobody who will debug this, my recommendation is to install a working java version and instead of downloading a new installation only upgrade the JAR file. You get the jar from josm-tested.jar (see WikiStart).

That JAR is actually JOSM. Everything else is only to keep it easy for users.

I don't know where the file is stored on Winodws, but probably somewhere in Programs/JOSM I'd expect. Simply overwrite the file.

It's strange thought that Java 21 fails, 22 works and 24 fails again.

[Klerik7]

I just now got to it..

I just switched from .jar to exe because it was causing me problems, first with writing and then it started popping up that something was wrong, some parameters.....so I tried again, so I installed java 22 and started .jar and it throws an error, but it doesn't throw this error in the exe file....

​https://ibb.co/WW1JmRyP

...I agree with the last sentence and I don't understand

[stoecker]

Replying to Klerik7:

I just switched from .jar to exe because it was causing me problems, first with writing and then it started popping up that something was wrong, some parameters.....so I tried again, so I installed java 22 and started .jar and it throws an error, but it doesn't throw this error in the exe file....

You should not switch starting startup procedure or something similar. You somehow misunderstand me. When you download and install a working exe version this consists of Java, a start script and the JAR-File. These are independent of each other.

So you simply can REPLACE the JAR file on disk with the current one WITHOUT changing anything else!

So:

• Install a MSI/EXE working for you
• Find the place where the JAR of that installation is stored (in Programs directory I assume)
• Download current JAR
• Replace the JAR on disk with the current one
• Start JOSM the same way as you did before.

You only need to replace a single file, not change anything else!

[Klerik7]

oh I really misunderstood....
thank you for your advice and better explanation, this is how it really works