Description of problem: Power E*Trade Pro, a Java client, does not load/launch with IcedTea Web Start. It worked fine with Java Web Start in Fedora8.
Version-Release number of selected component (if applicable): I don't know.
How reproducible: Very (every time)
Steps to Reproduce: (Requires a E*Trade account/login, and requires access to Power E*Trade Pro software, a premium feature)
1. Start Firefox. Connect to www.etrade.com. Log in. Make sure you are on the Accounts page.
2. Click on the Start button for Power E*TRade Pro.
3. Click OK on the dialog box suggesting opening the .jnlp file with IcedTea Web Start.
Actual results: A etpro_launch.jnlp file is downloaded, and a dialog box appears suggesting to open with IcedTea Web Start. Click OK. The dialog box disappears, and nothing happens. (I don't remember if there is a brief display of the Iced Tea splash. There is for Java Web Start in Fedora8.)
Expected results: The application running, and displaying streaming quotes from E*Trade.
May be related to Bugs 304031, 415061. The Java application Power E*Trade Pro has two signatures (I think the launcher has a signature and then the application has a signature). In both cases the signatures are invalid (Java Web Start displays notifications to that effect), probably because the server names don't match the ones in the certificates.
Unfortunately, I dont have access to an E*Trade account, so I am going to need your help to fix this.
Could you please post the result of 'java -version'?
Could you please try saving the jnlp file and running it from the command line using the javaws program? Please post any debug output.
javaws -verbose etrade.jnlp
(replace etrade.jnlp with the name of the actual jnlp file)
Created attachment 431305 [details]
Java version info
Created attachment 431307 [details]
Log of Power E*Trade Pro launch by Iced Tea Web Start
Thanks for the logs. I think I understand what the problem is. This patch should fix the problem: http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2010-August/010005.html
This should be fixed in the upcoming java-1.6.0-openjdk-22.214.171.124-126.96.36.199.fc13. Please reopen if not.