Insecure JNLP java_vm_args cannot avoid security alerts even with a signed JNLP

Question

I am using a signed JNLP launch file that is validated against JNLP-INF/APPLICATION_TEMPLATE.JNLP in my main resource JAR (which I know works because if I change the JNLP in an invalid way the Java Plugin JNLP Client complains as expected). The main resource JAR is also properly signed with a real code signing certificate, marked as a Trusted-Library in the Manifest, and has "all-permissions" in the JNLP.
In my JNLP launch file, I have some java_vm_args that are considered insecure. For example, --XX:+PrintGC. Despite the fact that the JNLP is signed, I get two security alerts:
1) A yellow exclamation mark alert which when More Information are examined asserts that the JNLP file is NOT signed.
2) If I accept and run anyway, then I get another alert saying:
"This application is going to perform an insecure operation. Do you want to continue?"
Is there any way to avoid these issues while still being able to specify arbitrary VM arguments for the applet?

Answer 1

Found the answer in your link.  :-)
If the Application-Library-Allowable-Codebase attribute is present and matches the location from which the RIA is started, then a single host is listed in the Location field for the prompt and the option to hide future prompts is provided. If this attribute is present and the files are accessed from a location not included for the attribute, then the RIA is blocked. If this attribute is not present, then multiple hosts that correspond to the locations of the JAR file and the JNLP file or HTML page are listed in the Location field for the prompt. When multiple hosts are shown, the user is not given the option to hide future prompts. Use of this attribute is recommended so the files for the RIA are accessed only from known locations.