The “archive” parameter was pointing to a jar file that was not signed with a valid certificate.
The .jar file contained more than one signature. This could be seen by unzipping the .jar file. Within the META-INF folder, there were two sets of .DSA and .SF files, where there only should have been one.
If the unsigned .jar file is available, proceed to Step 4. Otherwise, follow the steps below:
1. Unzip the jar file
2. Delete the folder META-INF
3. Re-jar the classes again, for example, on Unix:
jar -cvf host.jar *.*
4. Sign the jar file using a valid certificate (in the example below, sign_webutil.sh is used, instead you can use your own signer)