See the Java Policy Permissions information in the Related Information section for more details on security options and risks. If using a JRE version that is supported and is known not to cause the described issues, is not possible, the solutions to this problem involve changing the java.policy file on the client machine to resolve both errors listed above.ĮSRI is not responsible for issues or problems that may result due to the following security changes. How To: Force the ArcIMS Java Viewer Applet to run using a specific version of the Java Plug-In To define a specific version of the JRE to be used for the Java Viewer on client machines that do not yet have a Java version installed, use the following document Java Viewer-JRE Settings. This can be downloaded from the Java Sun Website. The Java version known to not cause the described issues is JRE 1.4.2 (initial). Therefore the workarounds listed for the JRE versions 1.4.2_01 and higher apply to all ArcIMS Java Viewers regardless of the ArcIMS version used.
JRE 1.4.2_06 and 1.4.2_08 are listed as supported with ArcIMS 9.1, however the same client side issue still exists in these Java Runtime Environment versions. Verify that a supported JRE version is used by way of the ArcIMS Support Site in the Releated Information Section below. JRE 1.4.2_01 and later versions are not explicitly supported with ArcIMS 4.0.1 and ArcIMS 9.0. While no specific security threat has been associated with this issue, Sun has proactively decided to implement tighter security standards within its products.
JRE's prior to 1.4.2_01 were less restrictive with respect to JavaScript > Java communication, therefore the Java Viewer functiond without explicit security changes. As a result, permissions granted for the applet codebase in the java.policy file, as a default found at $JAVA_HOME/lib/security, are not honored in a JavaScript > Java call.
APPLET VIEWER JAVA BLOCKED BY SECURITY SETTINGS CODE
Since the origin of JavaScript code cannot be verified, Java code called from the JavaScript is not considered to be from the same codebase. With JRE 1.4.2_01 and later versions, Sun introduced new security restrictions for JavaScript > Java calls. : :Īccess denied( modifyThreadGroup)Īt .(Unknown Source)Īt .IMSMap.enableFunction(Unknown Source)Īt (Unknown Source) : access denied ( modifyThreadGroup)Īt (Unknown Source)Īt (Unknown Source)Īt (Unknown Source)Īt (Unknown Source)Īt (Unknown Source)Īt .(Unknown Source)Īt .(Unknown Source)Īt .ui.(Unknown Source)Īt .ui.(Unknown Source)Īt .IMSOverviewMap.redraw(Unknown Source)Īt 0(Native Method)Īt (Unknown Source)Īt (Unknown Source)Īt .invoke(Unknown Source)Īt .invoke(Unknown Source)Īt .invokeImpl(Unknown Source)Īt $2.run(Unknown Source)Īt (Native Method)Īt .invoke(Unknown Source) Verify one of the following errors appears in the Java Console: The Java Console should start in a separate dialog window.Ħ.
Start a new browser application and load the Java Viewer. Verify the box is checked next to the browser used on the Browser tab.ĥ. ace=true =basic|net|security|ext|liveconnectĤ. Add the following text to the Java Runtime Parameters box on the Advanced tab: Select 'Show Console' on the Basic tab.ģ. Go to Start > Settings > Control Panel > Java Plug-inĢ. Bug: Java Viewer and Manager does not load successfully when using JRE 1.4.2_01 or later versions DescriptionĪny combination of the following problems or errors may indicate that the Java Custom or Standard Viewer is not successfully loading due to the use of JRE version 1.4.2_01 or later:Īccess denied modifyThreadGroup)"įollow the steps below to troubleshoot and confirm the source of the errors on the client machine where the Java Viewer errors are occurring:ġ.