Yes, this is true. This blog entry from Oracle has the details. As I understand it, you have three options for continuing to work: Sign your app with a trusted cert Normally, this is done by acquiring a cert from one of the vendors whose root certs are trusted by Java by default. You can … Read more
Go to folder C:\Program Files (x86)\Java\jre1.8.0_291\lib\security. In file java.security, find option jdk.tls.disabledAlgorithms and delete TLSv1.
We experienced the same Problem with Java 7 Update 45 (1.7.0_45). The JNLP Spec gave a hint for a work-around: Properties set in the jnlp file will normally be set by Java Web Start after the VM is started but before the application is invoked. Some properties are considered “secure” properties and can be passed … Read more
I think your suggestion of opening a port to listen when you start your application is the best idea. It’s very easy to do and you don’t need to worry about cleaning it up when you close your application. For example, if you write to a file but someone then kills the processes using Task … Read more
(1) First, you need to create a text file with all of the attributes you want to add. My text file looks like this: Permissions: all-permissions Codebase: http://www.codebase.com/myApp/dist Application-Name: My Application I named it addToManifest.txt. Obviously, you’ll need to change the parameters to match your application’s needs. (2) Next, you need to add this to … Read more
It’s quite the same like with any other Java process you want to debug remotely: You have to set up some arguments for the VM (-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=n,suspend=y,address=12345 ) and then connect to the given port. In Java webstart 6.0 this can be done with the -J option, in earlier version via environment variable JAVAWS_VM_ARGS. … Read more