urgent! incompatible with newest Java released 17 July 2014

Three different students, all PC users, have told me that their computers automatically uploaded and installed Java either last night (July 16) or today, and now MarvinSketch 6.2.1 will not load or run. Do you know anything about this, or how it can be solved?

Hi Bob,

yes we are aware of this issue, and investigating it.

We found a page with a possible solution, but we are struggling with creating a test environment, where we are able to check whether the suggested solution solves the issue in our case or not.

If you are in contact, and can make some changes in the marvin.js javascript library or in the applet parameters, itself, and test it, then it may speed up the investigation process.

Here you can find the solution we are experimenting with: http://stackoverflow.com/questions/24792360/issues-with-java-7u65/24795038#24795038

I attach you a marvin.js file, which contains the suggested modification.

Regards,
Istvan 

I will see if I can find one of the students who allowed Java to update on their PC and get them to try a few tests. I think they will not be responsive right now, because we have an exam tonight at 6 pm EDT. 

Thank you very much!

Currently it is half past ten in the evening here, so I think we will not have any development until tomorrow morning, so any information could be useful for us in the morning that you can find while testing it.

Regards,
Istvan 

Doesn't Czisi make you work all night?

I found one of the students, and your new marvin.js file working with Marvin 14.7.14.0 or 6.3.1 fixes the problem for him. I am not brave enough to try the new marvin.js file with Marvin 6.2.1 right before an exam is supposed to start.

He is running Chrome 35.0.1916.153 m on Windows 7 Home Premium on Dell XPS L501X.  

Hi Bob,

we do it on ourselves if we feel the urge as we felt it regarding this issue.

We still not managed to create a reproduction environment though, but we are getting testing results from elsewhere also, and it seems the modification does not ruin other environments, so this change is a possible candidate to be released, as an official solution. We are still would like to do some experiments on it before we are releasing it, but we would like to create a public announcement today on this.

Regards,
Istvan 

Great! Several MacOS users told me last night that they updated Java a few days ago and hadn't had a problem, so it appears to be a PC-only problem. Later today I will see if Marvin 6.2.1 works with the new marvin.js. 

Hi,

I would like to thank you for anyone who participated in the testing of this issue, at the end we could not managed to reproduce the issue with the Java update on our side, but got back enough feedback now to safely say, the previously attached marvin.js file solves the issue, when it is used to embed the applet onto a web page.

The solution as it is written in the linked article from stackoverflow is the switch from java_arguments parameter to java-vm-args. The parameter value do not need to be changed, just the parameter name.

We are aware one case, where a complete reinstallation of the Java Runtime Environment has solved the issue, along with the deletion of its folders - between uninstallation and installation - in the Program Files, and in the AppData\LocalLow folders. In this case it seemed that JavaFx libraries are crashed meanwhile they were being loaded, and the Java Plugin coulnd not even start.

Our upcoming 6.1.9, 6.2.4, 6.3.3 and the frequent releases from 14.7.28 will contain the corrected marvin.js file, and you can also download the current version of the marvin.js file from our site at http://www.chemaxon.com/marvin/marvin.js.

So we can say that, it is safe to just overwrite the file in your Marvin Applet folder on the server, but to make sure, create a backup copy, and run a quick test, if the problem persist by your user, please do not hasitate to contact us.

Best regards,
Istvan 

The 1.7.0_u67 update for java contains a fix for this issue, it was released to the public on August 4, 2014.

The release notes explicitly mention this issue here: http://www.oracle.com/technetwork/java/javase/7u67-relnotes-2251330.html

Regards,
Istvan