Karakun Support Forums

Log files attached. Stage2 log is truncated (I removed most of the logging from after app was launched)

Finally my application is launching
I guess removing APPLICATION_TEMPLATE.JNLP the problem.

Thank you for all help Janak

<application-desc main-class="no.statnett.fifty.intern.client.ApplicationStarter" name="Fifty (@https://mms-sn-nattbygg1-klient-fifty-cm-mms-endpoints.apps.stas-test.statnett.no)" >
<argument>https://mms-sn-nattbygg1-klient-fifty-cm-mms-endpoints.apps.stas-test.statnett.no/larm</argument ...

I unpacked jar and found only 1 APPLICATION_TEMPLATE.JNLP.
I now removed APPLICATION_TEMPLATE.JNLP from the jar and the looping is gone, but startup still does not complete.

I will investigate further, but it looks to me that the loop occurs when APPLICATION_TEMPLATE.JNLP is present in the jar.

JNLP-INF contains only APPLICATION_TEMPLATE.JNLP
Contents of jar (root)

Start of INDEX.LIST:
JarIndex-Version: 1.0

statnett-fifty-intern-client-jar-with-dependencies.jar

JNLP-INF
_351
_351/iec62325
_351/iec62325/tc57wg16
_351/iec62325/tc57wg16/_451_3
_351/iec62325/tc57wg16/_451_3/capacityspecificationdocument
_351/iec62325/tc57wg16/_451_3 ...

Paid support is above my paygrade unfortunately.

Like I said before, this runs smoothly on javaws 1.8. I was under the impression that migrating to OWS would be simple...

The jar file contains everything needed to run the app.
Contents of META_INF look like attachment.

What I find really odd is that this occurs 2 times, 2nd time after app is launched;
[DEBUG][net.adoptopenjdk.icedteaweb.resources.ResourceTracker] Create resource for 'https://mms-sn-nattbygg1-klient-fifty-cm-mms-endpoints.apps.stas-test.statnett.no/larm/statnett-fifty-intern-client-jar-with ...

Still looking for the problem.
I put some System.out statements in the startup and it does not complete.

[ITW-CORE][2023-03-28 14:40:17.773 CEST][DEBUG][net.sourceforge.jnlp.runtime.CachedJarFileCallback] Class-Path attribute cleared for C:\Users\magnusska\.cache\icedtea-web\cache\0\19\statnett ...

I can't find APPLICATION.JNLP

I removed "JavaWebStartServices.installShortcut();"
Same problem.


public static void main(String[] args) throws Exception { // NOSONAR
Locale.setDefault(new Locale("nb", "NO"));
System.setProperty("app.log.dir", "fifty");
JavaWebStartServices.installShortcut ...

APPLICATION.TEMPLATE.JNLP:

<?xml version="1.0" encoding="UTF-8" ?>
<jnlp spec="6.0.10+" href="larm.jnlp" codebase="*">
<information>
<title>*</title>
<vendor>Fifty</vendor>
<homepage>*</homepage>
<description>*</description>
<icon href="*" />
<icon href="*" kind="splash" />
<icon href ...

This is the repeating section of the log:
[ITW-CORE][2023-03-23 12:33:54.673 CET][DEBUG][net.sourceforge.jnlp.tools.JarCertVerifier] App is signed: true
[ITW-CORE][2023-03-23 12:33:54.677 CET][DEBUG][net.sourceforge.jnlp.runtime.classloader.JNLPClassLoader] Creating Jar InputStream from JarEntry ...

I'm wondering if any of the java-vm-args have been obsoleted:

<resources os="Windows" arch="x86">
<j2se version="11" href="http://java.sun.com/products/autodl/j2se" initial-heap-size="1G" max-heap-size="4G" java-vm-args="-Xss2m -XX:+HeapDumpOnOutOfMemoryError" />
</resources>
<resources ...

The problem persists after upgrade to OWS 1.7.0
Log files attached.

Log files attached

I'm trying to launch an application with a jnlp file that works fine with javaws in 1.8.
The source code has been modified to comply with OWS/IcedTea.

jnlp:

<?xml version="1.0" encoding="UTF-8" ?>
<jnlp spec="6.0.10+" href="larm.jnlp" codebase="https://mms-sn-nattbygg1-klient-fifty-cm-mms ...