iSymphony JNLP client will not launch after upgrading Java to 1.7.0_45
On this page
Symptoms
After an upgrade to Java 1.7.0_45 the launcher will warn you about the potental risk of launching an unsigned application and will also prompt you to block the application. After you choose not to block the application the client does not start.
Cause
Java 1.7.0_45 introduced an undocumented security modification that prevents insecure JNLP properties from being passed to the JVM preventing the client framework from launching.
Resolution
Upgrade to iSymphony 2.8.1+.
If you can access the iSymphony client Administration Interface you can update using the Automated Update Instructions in the Updating iSymphony guide.
If you cannot access the client you will have to use the following commands to update the server via the iSymphony CLI.
check_for_updates
update
After running the update command you will be droped back down to the iSymphony prompt while the update is downloaded. Once the download is compete you will be kicked out of the iSymphony CLI as the iSymphony Server is restarted for the update to apply. After a few minutes log back into the iSymphony CLI via the command telnet localhost 50001 and then type version to check that the server update was successful and you are now running the correct version. If the version is reporting correctly the update was applied and you can restart your clients to update the client files.
If the version is not correct and the update did not seem to apply run the following commands to install the update manually.
chmod +x install.sh
./install.sh
Next restart the server based on the type of installation you have.
RPM
TAR
/opt/isymphony/server/startup.sh
Workaround
Launch the application from the client command line with the following command that specifies the needed properties directly. You will need to insert the ip or hostname of your iSymphony server in the command.