3 Replies Latest reply: Jan 17, 2012 9:48 AM by sabre150 RSS

    Unsigned Java applet not working properly on windows 7 with java 1.6U24 or later

    911307
      Hi,

      I think I am facing exactly the same problem as was mentioned in this old post from a year earkier:
      Applet is not working properly on windows 7 with java update 23

      I initially resurrected that post and attempted to hijack it away for my own issue, but a kind moderator has split it out so that my question can stand on its own merits (or not).

      ---


      Java applet (unsigned) in a web application is not working properly in Windows 7, IE 9 with java 1.6 update 24 and onwards. The latest we tried is java 1.6 update 27. The applet works perfectly fine in Windows XP machines with any version of JVM.
      Have you got a solution to this issue? Is this anything regarding the java policy file or crossdomain.xml file?

      Hoping to get some solution/workaround for the problem.

      Thanks in advance!


      Regards,
      Maithily
        • 1. Re: Unsigned Java applet not working properly on windows 7 with java 1.6U24 or later
          sabre150
          EJP posted a response recently (I can't find it at the moment) advocating "Protocol relative URLs" and this sounds as if it could result from the same basic problem. See http://paulirish.com/2010/the-protocol-relative-url/ .
          • 2. Re: Unsigned Java applet not working properly on windows 7 with java 1.6U24 or later
            911307
            Hi sabre150,

            Thanks for the response. But I don't think the problem is due to Protocol relative URLs. This seems to be a permissions issue. I get the following exception

            java.security.AccessControlException: access denied (java.net.SocketPermission 66.150.109.50:443 connect,resolve)
            at java.security.AccessControlContext.checkPermission(Unknown Source)
                 at java.security.AccessController.checkPermission(Unknown Source)
                 at java.lang.SecurityManager.checkPermission(Unknown Source)
                 at java.lang.SecurityManager.checkConnect(Unknown Source)
                 at sun.plugin2.applet.Applet2SecurityManager.checkConnect(Unknown Source)
                 at java.net.Socket.connect(Unknown Source)
                 at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(Unknown Source)
                 at sun.net.NetworkClient.doConnect(Unknown Source)
                 at sun.net.www.http.HttpClient.openServer(Unknown Source)
                 at sun.net.www.http.HttpClient.openServer(Unknown Source)
                 at sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)
                 at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
                 at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)
                 at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
                 at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
                 at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
                 at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(Unknown Source)
                 at sun.net.www.protocol.https.HttpsURLConnectionImpl.getHeaderField(Unknown Source)


            But this is only in Windows 7 machines. In Windows XP it is working fine.
            • 3. Re: Unsigned Java applet not working properly on windows 7 with java 1.6U24 or later
              sabre150
              908304 wrote:
              Thanks for the response. But I don't think the problem is due to Protocol relative URLs. This seems to be a permissions issue.
              So is the non Protocol relative URLs issue!
              I get the following exception

              java.security.AccessControlException: access denied (java.net.SocketPermission 66.150.109.50:443 connect,resolve)
              at java.security.AccessControlContext.checkPermission(Unknown Source)
                   at java.security.AccessController.checkPermission(Unknown Source)
                   at java.lang.SecurityManager.checkPermission(Unknown Source)
                   at java.lang.SecurityManager.checkConnect(Unknown Source)
                   at sun.plugin2.applet.Applet2SecurityManager.checkConnect(Unknown Source)
                   at java.net.Socket.connect(Unknown Source)
                   at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(Unknown Source)
                   at sun.net.NetworkClient.doConnect(Unknown Source)
                   at sun.net.www.http.HttpClient.openServer(Unknown Source)
                   at sun.net.www.http.HttpClient.openServer(Unknown Source)
                   at sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)
                   at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
                   at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)
                   at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
                   at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
                   at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
                   at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(Unknown Source)
                   at sun.net.www.protocol.https.HttpsURLConnectionImpl.getHeaderField(Unknown Source)


              But this is only in Windows 7 machines. In Windows XP it is working fine.
              Windows 7 is much more fussy than XP about permissions. I can't make you investigate the Protocol relative URLs issue but surely it must be worth spending some time on it.