Karakun Support Forums

Hello and grüezi,

we are on OpenWebStart 1.12.0, and our webapp can be launched from production server as well as from developer test server just fine. Only when the exact same package is launched from the specialist department test server, the jnlp and jar file is downloaded into the local cache and that’s it, nothing more happens. The last entries in the stage2.log show, that OWS tries to access/download a file xbean.jar from the webapp's url. This is failing, since xbean.jar is not part of our webapp. Any hint what causes this strange behaviour only with that server and how to solve this? The stage2 logs from the other two servers don’t list the xbean.jar at all.

Thanks and greetings

Firstly, this is a public forum, so any log files you attach can be seen by others. Make sure they don’t include anything sensitive before posting. You get a private forum when you buy support: https://openwebstart.com/support/

OWS downloads jar files specified in the Jnlp file. However, some jar files may include Jar Index pointing to other jars. Therefore, OWS tries to download those Jars before loading a class from those Jars. The client.jar specified in your Jnlp must be having a Jar Index pointing to xbean.jar. Your prod and dev test servers must be hosting xbean.jar. You may have overlooked deploying xbean.jar to specialist dept. test server.

GOOD NEWS: it works now from the specialist dept. test server too. The jnlp specifies only the client.jar to download. This single jar file contains all, both our logic and some Apache libs (POI) it uses. In one of those libs (xmlbeans-2.6.0.jar) there is this file META-INF/INDEX.LIST, which references to xbean.jar. And our Ant build copied this file over to the client jar. After deleting INDEX.LIST the webapp starts correctly now.
I also checked the developer test server, there is no xbean.jar or xmlbean-2.6.0.jar anywhere...

Happy that it works. Thanks for letting us know.