Red Hat Bugzilla – Bug 1255444
Unable to launch java web applications. (ASDM, idrac consoles, calculator)
Last modified: 2015-08-31 05:11:49 EDT
Created attachment 1065300 [details]
Java console output
Description of problem:
Java web applications error out with "Fatal: Read Error: Could not read or parse the JNLP file. ..."
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Visit http://www-pw.physics.uiowa.edu/das2/javaPlatformTest.jbf.html
2. Use the second test, "Test WebStart with the Calculator."
(Alternatively try start a Cisco ASDM applet, if you have access to one)
Application fails to start, error messages from java console attached below.
Sorry the target applications very poorly written.
Theirs Calculator.jnlp is so badly written that there is nothing I can do with it.
Workaround for you is to download http://www-pw.physics.uiowa.edu/das2/Calculator.jnlp
replace incorrect closing tag of vender by vendor and removing href="Calculator.jnlp".
Then you can locally run javaws downloaded/Calcualtor.jnlp and it will handle resurces.
Application is working fine like this.
The correct step is to contact authors of application and tell them to fix thir jnlp. They can not close <vendor> by </vender>. Then the app will work also from browser as you are expecting. (they do nto need to fix/remove href then)
Now you can use this:
sed -i s/vender/vendor/ Calculator.jnlp
sed -i "s/href=\"Calculator.jnlp\"//" Calculator.jnlp
rm -rf $a
I will close this as notabug, however if the error from idrac/asdm is different, please open another bug.
I have access to some idracs, but to no cisco ASDM.
I'm more over assuring that idrac is working. If it do not, please, let me know!
Ideally again with full stacktrace and even more ideally with working reproducer
Tahnk you, and sorry for inconvenience.
After a lot of trial and error it seems as if the ASDM issue was caused by old/incompatible ciphers. IcedTea still reported this as a parsing error though.
Using an old laptop and navigating ASDM to:
Configuration > Device Management > Advanced > SSL Settings
...and removing the RC4-MD5 and enabling AESxxx-SHA1 variants made IcedTea working again.
Thank you for investigations. I should probably tell you that last update of JDK (not ITW) had default disabling of legacy algorithms. Sorry,
ITW is reporting it as "cannot parse" pecause the underlying https connection never download target JNLP. So ITW get only "empty file" which it can not parse.
Only in verbose mode od in console you can see chain of exceptions with failed connection and reason.