[ome-devel] WebStart problem with 5.0.1 VirtualBox appliance

[Josh Moore]

Hi Niko,

> Any hints/thoughts? It's nothing urgent as I can still use the "normal" client, I just wanted to know if that's a problem on my side, or on Linux in general, or some other funny stuff?

This is our fault: see http://trac.openmicroscopy.org.uk/ome/ticket/12337

The OVA is built along with the rest of the artifacts. But the jar signing is done overnight after the fact.
We'll have to re-evaluate how to get all those ducks in a(n ordered) row.

Sorry for the trouble.

Cheers,
~Josh.


On May 28, 2014, at 9:24 PM, Niko Ehrenfeuchter wrote:

> Dear all,
> 
> I'm having a problem using the insight client via WebStart on the 5.0.1 demo appliance of OMERO (can't try with 5.0.2 right now as I'm currently on a low bandwidth connection). The webclient is running fine as well as the downloaded OMERO.insight package.
> 
> Running the webstart jnlp via
> 
>> /usr/lib/jvm/jre-7-oracle-x64/bin/javaws -verbose http://localhost:8080/webstart/jars/insight.jnlp
> 
> results in the following error below. I made sure to have the latest Java 7 (u60, also tried with u51) and tried to adjust the security settings to the lowest possible level. I also (unsuccessfully) played with the "Keep temporary files on my computer" setting in the Java Control Panel as there were some hints on the web saying this could help for this problem:
> 
>> com.sun.deploy.net.JARSigningException: Found unsigned entry in resource: http://localhost:8080/static/webstart/jars/omero.insight.jar
>> 	at com.sun.javaws.security.SigningInfo.getCommonCodeSignersForJar(Unknown Source)
>> 	at com.sun.javaws.security.SigningInfo.check(Unknown Source)
>> 	at com.sun.javaws.security.JNLPSignedResourcesHelper.checkSignedResourcesHelper(Unknown Source)
>> 	at com.sun.javaws.security.JNLPSignedResourcesHelper.checkSignedResources(Unknown Source)
>> 	at com.sun.javaws.Launcher.prepareResources(Unknown Source)
>> 	at com.sun.javaws.Launcher.prepareAllResources(Unknown Source)
>> 	at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
>> 	at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
>> 	at com.sun.javaws.Launcher.launch(Unknown Source)
>> 	at com.sun.javaws.Main.launchApp(Unknown Source)
>> 	at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
>> 	at com.sun.javaws.Main.access$000(Unknown Source)
>> 	at com.sun.javaws.Main$1.run(Unknown Source)
>> 	at java.lang.Thread.run(Unknown Source)
> 
> Any hints/thoughts? It's nothing urgent as I can still use the "normal" client, I just wanted to know if that's a problem on my side, or on Linux in general, or some other funny stuff?
> 
> Cheers
> Niko