Issues with Marvin in Java1.6.0_38 Version

Hi,

We have downloaded the Java1.6.0_38. and try to open the Marvin applet  it is thorwing the Error,

 Can you please Provide the List of Java 1.6 Version will work for Marvin.

Regards

Siva

Hi Siva,

I am afraid, the applet will not run with java 6 anymore. Unfortunately, it was not our decision; the browsers forbid to run applets with old Java versions because of security reasons. We recommend you to update to the latest java and to the latest version of Marvin applet.

Best Regards,

Efi

Hi,

Our client system is using Java Version Java1.6.0_38 ans some other application also specifically using Java1.6.0_38. We not possible to upgrade the Java version.

Our application is cliam based web application using .Net

Please help to us to use Java1.6.0_38 using Marvin.

Regards

Siva

Hi,

Awaiting for response.

Regards

Siva

Posted: Tue Feb 18, 2014 11:27 am    Post subject: Issues with Marvin in Java1.6.0_38 Version

Hi, Any update on this. Regards Siva

Hi Siva,

sorry for the late answer, finally we got some time to set up the environment with a 1.6.0_u38 Java version, and test the issues you are facing with.

We found that it works smoothly with latest Firefox, on a 64-bit Windows 7 virtual machine.

Please navigate to one of our example page for example this: http://www.chemaxon.com/marvin/examples/applets/sketch/js_triggering.html and check whether it is working or not for you.

If it is working, then we will need all the information about the used server, and the client. Webserver version, applet version you have the problems with, the code snippet where the applet is embedded into the html page, the browser on the client you are using when this problem rises, the operating system which is used on the client side, and the architecture version of the operating system (32-64 bit) and all the mentioned softwares on the client side.

If our example is not working, then we will need the contents of the java console with enabled tracing mode, so the same way as you have sent your other report in this topic according to Firefox issues.

Regards,
Istvan 

Hi,

Sorry for late reply. Still getting the same Error.  When try to use without the Claims authentication Java version 1.6.0_u38 is working fine. When use Claims authentication Java version 1.6.0_u38 is not working for all the Browser. But Same Code is working Java version 1.7.0_u48 and Above in IE only.

Our client is using for Java version 1.6.0_u38 alone.Please help regaridng this.

PFA for

Server :

Os : Windows 7

Mavin : 6.1.0

IIS version 7.0

Client :

Java Version 1.6.0_u38

Regards

Siva

Hi Siva,

from the log, it seems this issue is similar or same as the one in this topic:

https://www.chemaxon.com/forum/ftopic12075.html

Please follow the steps I have suggested there, to proceed with the troubleshooting, and I suggest that we should use that topic for the further communication.

Thanks,
Istvav 

 

Hi,

 

Currently Using the Sample application Provided by Chemaxon. It is hosted in IIS and Tested in Form authentication and Window Authentication , Marvin is working fine in Java1.6.0_38 Version.

 

When Implement the Claim authentication (Our project using) in sample application then Application throwing the Error. Same Code(Claim authentication with sample code) Working fine in Java1.7.0_51Version.

 

PFA for Java Console Output.

 

Please help regarding this.

 

Regards

 

Siva

 

Hi,

Any update on this.

Regards

Siva

Hi,

Any update on this.

Regards

Siva

Dear Siva,

as I stated before, I think that the problem is somewhere in the server side, or in Java if the applet example on our site works.

I finally found the issue for you, your server sets the session cookies marked with the httpOnly flag, and there is a related issue in Java, which has been fixed in 1.7.0_u04 .

You can find it here: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7077220

The possible solution is to upgrade the java on the client side, or leave the httpOnly flag as not set for the session cookies, otherwise Java can not send them back since it does not have access to them, and according to this blog post, place the applet jars to a freely available location does not fix the problem.

Regards,
Istvan