APM 10.5.1 Webstart failing to launch workstation

[David Richards]

Hi

 

We have just upgraded to 10.5.1 and I can't get the webstart to launch workstation. 

 

I have cleared caches and temp files.

Local copy of Java is version 1.7.0_40 running on Windows

 

This is the error 

 

com.sun.deploy.net.FailedDownloadException: Unable to load resource: http://************/workstationProduct/plugins/com.wily.ui.jasper.report_10.5.1.jar
at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)
at com.sun.deploy.net.DownloadEngine.downloadResource(Unknown Source)
at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
at com.sun.javaws.LaunchDownload$DownloadTask.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

[Haruhiko Davis]

Hi Dave,

It may not be pertinent, but have you installed Hotfix 9 to your EM?

[David Richards]

Hi Hiko, yes we did, right after we ran the installer. Workstation and Webview are working OK, just webstart that is not.

 

2017-05-13 11:29:10,357 [main] INFO com.ca.fix.apm.hotfix.Hotfix - Hotfix 10.5.1-hf9 was applied successfully

[Haruhiko Davis]

Did you also clear your Java cache?

[David Richards]

Yes I followed the text on "clearcache.jsp" 

This is the stacktrace I am seeing

 

com.sun.deploy.net.FailedDownloadException: Unable to load resource: http://sx4c.wload.barclays.co.uk:8081/workstationProduct/plugins/com.wily.core_10.5.1.jar
at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)
at com.sun.deploy.net.DownloadEngine.downloadResource(Unknown Source)
at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
at com.sun.javaws.LaunchDownload$DownloadTask.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

 

java.util.zip.ZipException: invalid entry size (expected 22497669 but got 2019 bytes)
at java.util.zip.ZipInputStream.readEnd(Unknown Source)
at java.util.zip.ZipInputStream.read(Unknown Source)
at com.sun.deploy.net.HttpDownloadHelper.decompressWrite(Unknown Source)
at com.sun.deploy.net.HttpDownloadHelper.download(Unknown Source)
at com.sun.deploy.cache.Cache.downloadResourceToTempFile(Unknown Source)
at com.sun.deploy.cache.Cache.downloadResourceToCache(Unknown Source)
at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)
at com.sun.deploy.net.DownloadEngine.downloadResource(Unknown Source)
at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
at com.sun.javaws.LaunchDownload$DownloadTask.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

[Sri_Guntupalli]

I can see few known issues with java 1.7,

 

Third-Party Known Issues - CA Application Performance Management - 10.5 - CA Technologies Documentation 

 

Technical Advisory: Workstation Web Start Client Fails to Start with Java 7 Update 45 (Java 1.7.0_45), Java 6 Update 65 … 

But looks ok as you are on update 40.

 

Better open a support ticket and upload logs for us to analyse.

 

Regards
Sri

[Lynn Williams]

On clean desktop that had never downloaded workstation before I installed 1.7 u40 and tested against 10.5.1.8 with java console enabled + tracing + logging (Java Configure/javacpl.exe - Advanced tab) . It processed the jnlp file successfully and downloaded the plugins successfully (see attached console output).

I then updated EM to HF9, cleared the desktop cache including C:\Users\Administrator\AppData\Roaming\wily directory and still successful.

(product/workstation/plugins/com.wily.core_10.5.1.jar did not get changed in HF9)

So it seems to be environment specific.

Attachment(s)

10_5_1_8_java_tracing_logging_console_17u40_test.txt.zip   32 KB 1 version

[Hallett German]

  Dear Dave:

      As Lynn suggested, this appears to be environment-specific. The best next action is to open a case as recommended by Sri. If a solution is found, please post here as a way to help others. You may ask follow-up questions as well if needed

Thanks

Hal German

[David Lewis]

Hi Dave,

Along with the suggestions you've had, assuming this is a cluster, I would try getting the webstart from any collector, if that works you can always point the webstart at the MOM to get things going to start off. You can save a copy of the jnlp that you could pass along to others as a temporary step.

After that I would do a comparison of the /product/workstation/plugins folder on MOM and collector, particularly the last error suggests the file size could be incorrect so it would be worth comparing the output on different machines.

Without this being an exact science, if the files on the collector are bigger or if there are more of them, you could do copy/replace of the collector /workstation/plugins folder onto the MOM.

 

Thanks,

David

[Legacy User]

I had this issue on one of my environments that I upgraded in QA from 10.3.  The workaround was to tar up the product/workstation/ folder from another mom and untar it on the problematic server.  I didn't see this on the majority of the environments though, just one.

[David Richards]

Hi thanks for all the suggestions and comments. I have not been in the office while attempting this and have been working over VPN. My colleagues on-site are working OK with webstart access, so I think this may be related.

I will re-try in the office tomorrow and see if the issue is still there and update this thread.

Thanks

[David Richards]

Hi - I have retried webstart launch from my office location and it has worked with no issues. Thanks again for all the help and suggestions.