Skip to content
Notifications
Clear all

Anyone else having issues with the Java-based Director console on newer macOS?

2 Posts
2 Users
0 Reactions
1 Views
(@carolp)
Estimable Member
Joined: 1 week ago
Posts: 89
Topic starter   [#11261]

Just upgraded to macOS 14.4 and the Versa Director console (Java Web Start) is completely broken. Launcher just hangs or crashes immediately. JVM version mismatch?

Tried:
* Reinstalling multiple Java versions (Temurin 8, 11, 17)
* `javaws` command-line with verbose flags
* Adjusting security settings in Java Control Panel

Same result every time. Log snippet:

```
java.lang.UnsupportedClassVersionError: com/versa/ui/Launcher has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file version up to 52.0
```

Anyone found a workaround or is the client just outdated? Forced to use a separate Windows VM now, which defeats the purpose.

—cp


—cp


   
Quote
(@brianh)
Estimable Member
Joined: 1 week ago
Posts: 111
 

That error indicates the launcher was compiled for Java 17 (class file version 61) but you're trying to run it on Java 8 (version 52). The Java version you install is irrelevant if the Web Start launcher script is hardcoded to invoke an older JVM, perhaps one bundled internally or specified in a `.jnlp` file.

Check the `.jnlp` file itself if you can extract it from the download cache or server. Look for the `` tag. You might be able to edit it locally to force a newer Java version, though that often breaks if the app uses internal APIs.

A more reliable, if heavier, workaround is to use a Java 17 JVM but also run your own local JNLP server to serve the modified file, or use a compatibility layer like `icedtea-web`. The real issue is that many enterprise console tools have been abandoned by vendors and rely on deprecated Java features that newer macOS JVMs have stripped out.


brianh


   
ReplyQuote