<html>
<head>
<base href="https://icedtea.classpath.org/bugzilla/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - net.sourceforge.jnlp.runtime.AppletEnvironment.startApplet"
href="https://icedtea.classpath.org/bugzilla/show_bug.cgi?id=3650#c13">Comment # 13</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - net.sourceforge.jnlp.runtime.AppletEnvironment.startApplet"
href="https://icedtea.classpath.org/bugzilla/show_bug.cgi?id=3650">bug 3650</a>
from <span class="vcard"><a class="email" href="mailto:jvanek@redhat.com" title="JiriVanek <jvanek@redhat.com>"> <span class="fn">JiriVanek</span></a>
</span></b>
<pre>(In reply to Radhadatta from <a href="show_bug.cgi?id=3650#c9">comment #9</a>)
<span class="quote">>
> (In reply to JiriVanek from <a href="show_bug.cgi?id=3650#c8">comment #8</a>)
> > Try to add deployment.https.noenforce=true into your deployment.proeprties
> > file.
> > I addition, this should be fixed by:
> > <a href="http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2018-November/040429">http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2018-November/040429</a>.
> > html
> >
> > So you can try with self built itw and that patch.
>
> Hi ,
>
> Below is my updated deployment.properties file.
>
> Location of the deployment.properties file= C:\Users\..\.config\icedtea-web
>
> #Netx deployment configuration
> #Sat Nov 24 15:27:15 IST 2018
> deployment.log.headers=true
> deployment.log=true
> deployment.log.file=true
> deployment.security.level=ASK_UNSIGNED
> deployment.https.noenforce=true
>
> Not sure If you are suggesting here to change.</span >
YY. This shoudl do the job.
<span class="quote">>
> Can you please tell me how can I do the self build itw</span >
<a href="http://icedtea.classpath.org/wiki/IcedTea-Web">http://icedtea.classpath.org/wiki/IcedTea-Web</a>
On windows, you have to use cygwin, and it is not fun to make it alive.
I Really dont know how to help you.
If you can prepare reproducer I can run, and debug ITW, it will help a lot.
It canbe also windows specific, where I will be for no use at all.
Best for you will be to debug ITW itself on your own.
Still first step should be to prepare reproducer, which I will forst verify,
that it is itw general(not windows specific issue)
If you cant publish the app you are running, try to get its sources, and check
wat it is doing. As ITW is dying in arly stages, it should be easy enough.
Maybe they have jsut wrongly palced synchronised keyword...</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>