Applets not working in Java version 1.6 update 29

[Former Member]

Hi,

We are using MII 12.0.2 in Java 1.4.07 server.

In users PC, currently java version are upgraded to Java 1.6 update 29. Till date applets are worked in earlier versions like update 26. But currently no applet is working. It is showing error as

load: class iGrid not found.

java.lang.ClassNotFoundException: iGrid

at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)

at sun.plugin2.applet.Plugin2ClassLoader.loadClass0(Unknown Source)

at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source)

at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source)

at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source)

at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Exception: java.lang.ClassNotFoundException: iGrid

Error is showing for all applet types like iCommand, iBrowser etc.,

If we downgrad the Java version , it is working.

How to solve this problem? is this type of problem (Java related) solved in MII 12.1 or 12.2 versions?

Regrads,

Senthil

Edited by: senthil kumar on Feb 7, 2012 9:06 AM

[Former Member · Accepted solution]

Hi Senthil,

The problem is because of java version update 29.

Check SAP Note [1649526|https://service.sap.com/sap/support/notes/1649526]

Which suggests 2 options:

1. Rollback to a version previous of the JRE less than 1.6.0_29

2.Update the java policy

In the java.policy file, add the following line:

permission com.sun.deploy.security.SecureCookiePermission "*.some.site.com:80-", "listen,accept,connect,resolve";

Where "*.some.site.com:80" is the domain that applets are running in and the port is the server port of the webserver.

Add this inside the section that starts with:

// default permissions granted to all domains

grant {

// other existing permissions

// Add the line above here

};

The file you can find under the folder "../Java/JRE6/lib/security".

Regards

Anshul

[agentry_src · Accepted solution]

You may also want to take a look at this thread: [Pedro's Fix|http://forums.sdn.sap.com/thread.jspa?threadID=2066187]

Regards,

Mike

[Former Member · Accepted solution]

Hi,

I tried this by giving the MII Hostname in Policy file in my PC. But it is failed.

In which format we should give the MII_HOSTNAME and Port. I gave as

permission com.sun.deploy.security.SecureCookiePermission "<IP ADDRESS MII SERVER>:<PORT>-", "listen,accept,connect,resolve";

i tried with other options also like "http://<IP ADDRESS MII SERVER>:<PORT>-", . but it also fails.

Regards,

Senthil

[Former Member · Accepted solution]

Hi,

This is working now. I gave as "<mii server ip>:port-" and restarted the machine.

Then it works fine.

Thanks,

Regrads

Senthil

Edited by: senthil kumar on Feb 14, 2012 11:54 AM

[ganimede_dignan · Accepted solution]

Hi,

I've got the same issue on a 12.2.5.6 (but already try with 12.2.5.5 without success). The NetWeaver is 7.20 CE con a Win 2008 R2 + MSSQL 2008 R2.

We have already try with NW initial shipment SP level without success. Already try with Stack 7,8 and 9 without success.

We have already try to update java.policy file on client and on server without success... the file was updated as:

// Standard extensions get all permissions by default

grant codeBase "file:${{java.ext.dirs}}/*" {

          permission java.security.AllPermission;

};

grant codeBase "file:${java.home}/../lib/jvmx.jar" {

          permission java.security.AllPermission;

};

// default permissions granted to all domains

grant {

          // Allows any thread to stop itself using the java.lang.Thread.stop()

          // method that takes no argument.

          // Note that this permission is granted by default only to remain

          // backwards compatible.

          // It is strongly recommended that you either remove this permission

          // from this policy file or further restrict it to code sources

          // that you specify, because Thread.stop() is potentially unsafe.

          // See the API specification of java.lang.Thread.stop() for more

        // information.

          permission java.lang.RuntimePermission "stopThread";

          // allows anyone to listen on un-privileged ports

          permission java.net.SocketPermission "localhost:1024-", "listen";

          // Custom Settings

          permission com.sun.deploy.security.SecureCookiePermission "http://server.dom.com:50000-", "listen,accept,connect,resolve";

          permission com.sun.deploy.security.SecureCookiePermission "server.dom.com:50000-", "listen,accept,connect,resolve";

          permission com.sun.deploy.security.SecureCookiePermission "http://localhost:50000-", "listen,accept,connect,resolve";

          permission com.sun.deploy.security.SecureCookiePermission "localhost:50000-", "listen,accept,connect,resolve";

          // "standard" properies that can be read by anyone

          permission java.util.PropertyPermission "java.version", "read";

          permission java.util.PropertyPermission "java.vendor", "read";

          permission java.util.PropertyPermission "java.vendor.url", "read";

          permission java.util.PropertyPermission "java.class.version", "read";

          permission java.util.PropertyPermission "os.name", "read";

          permission java.util.PropertyPermission "os.version", "read";

          permission java.util.PropertyPermission "os.arch", "read";

          permission java.util.PropertyPermission "file.separator", "read";

          permission java.util.PropertyPermission "path.separator", "read";

          permission java.util.PropertyPermission "line.separator", "read";

          permission java.util.PropertyPermission "java.specification.version", "read";

          permission java.util.PropertyPermission "java.specification.vendor", "read";

          permission java.util.PropertyPermission "java.specification.name", "read";

          permission java.util.PropertyPermission "java.vm.specification.version", "read";

          permission java.util.PropertyPermission "java.vm.specification.vendor", "read";

          permission java.util.PropertyPermission "java.vm.specification.name", "read";

          permission java.util.PropertyPermission "java.vm.version", "read";

          permission java.util.PropertyPermission "java.vm.vendor", "read";

          permission java.util.PropertyPermission "java.vm.name", "read";

};

Have you got any suggest?

[ganimede_dignan · Accepted solution]

Any Help?

[agentry_src · Accepted solution]

Please check the NW versions your version of MII.  I do not believe 7.2 is on the list.  Should be only 7.1 & 7.3, maybe only 7.3 are supported.

Regards, Mike

[ganimede_dignan · Accepted solution]

Same error in NW 7.11 CE, 720 CE, 7.30 and 7.31... but with MII 12.1.X no problem.

[agentry_src · Accepted solution]

Do you still have java version 1.6.0_29 on all these NW installations?  Why are you switching NW versions instead of updating your Java?

If so, you are ripping up the foundations to fix a leaky roof.  I do not understand your approach here.

[ganimede_dignan · Accepted solution]

Last supported Java version for each tested system NW 7.11 CE, 720 CE, 7.30 and 7.31

[agentry_src · Accepted solution]

Please open a new thread as the error you are seeing is not the same as the original topic of this thread.

Regards, Mike