is OWS ignoring timestamps in expired code-signing-certificates?

[AlBundy33]

our code signing certificae expired this month we have timestamped the signature.
When we try to start our application OWS complains about an expired certificate.

But If I check the certificate on command line all is fine

jarsigner -verify -verbose org.ehcache_3.9.6.jar
...
  s = signature was verified
  m = entry is listed in manifest
  k = at least one certificate was found in keystore

- Signed by "...our certificate..."
    Digest algorithm: SHA-256
    Signature algorithm: SHA256withRSA, 4096-bit key
  Timestamped by "CN=DigiCert Timestamp 2023, O="DigiCert, Inc.", C=US" on Mi. Okt. 18 08:39:52 UTC 2023
    Timestamp digest algorithm: SHA-256
    Timestamp signature algorithm: SHA256withRSA, 4096-bit key

jar verified.

The signer certificate expired on 2024-12-10. However, the JAR will be valid until the timestamp expires on 2031-11-10.

(don't worry about org.ehcache_3.9.6.jar - we've resigned all jars with our certificate)