My client code uses log4j services.
(Under webstart we redirect the output to the console if file appending is not allowed).
Now if I add log4j.jar to the webstart classpath (clientparameters.conf, which generates the classpath for jnlp), the Java application fails to load, claiming it cannot find 'classes/log4j.jar'.
We have that jar in WebNMS/classes, along with many other jars, so I don't really understand why jnlp cannot find it.

Workaround: copy log4j.jar to another name, redefine the classpath, and all is fine! The log4j2.jar is found and it works as expected.

One idea that crossed my mind (but makes little sense) is that the original log4j.jar is for some reason 'locked' by the server code, but I have trouble believing that could be the case...

I'll appreciate any fresh ideas on this.
   Reuben