6 Replies Latest reply: May 24, 2012 5:38 AM by 934635 RSS

    JWS Cache entry not found message - wrong folder

    934635
      Running with JRE 1.7 (4)

      I created a java app that I am running via JWS.

      The app takes a real long time to load up but does eventually load up.

      I noticed in the console that its trying to load the libraries from the wrong location (after it already loads it from the correct location) with a message that either states the jar has expired or cache entry not found.

      The library files are all located in a /lib subdirectory under where the main jar is located.

      As you can see from this message the jar is loaded from the correct place:

      network: Cache entry found [url: http://myserver.com/jws/lib/appframework-1.0.3.jar, version: null] prevalidated=false/0
      cache: Reading Signers from 853 http://myserver.com/jws/lib/appframework-1.0.3.jar | C:\Users\myuser\AppData\LocalLow\Sun\Java\Deployment\cache\6.0\17\2f8a86d1-22be619f.idx
      cache: Done readSigners(http://myserver.com/jws/lib/appframework-1.0.3.jar)
      cache: Read manifest for http://myserver.com/jws/lib/appframework-1.0.3.jar: read=110 full=3927
      security: JAVAWS AppPolicy Permission requested for: http://myserver.com/jws/lib/appframework-1.0.3.jar


      The after that you can see that it is trying to load it from the wrong local (not in /lib) - and it does this over and over:

      cache: Resource http://myserver.com/jws/appframework-1.0.3.jar has expired.
      network: Connecting http://myserver.com/jws/appframework-1.0.3.jar with proxy=DIRECT
      network: Connecting socket://ninesummer.lexlinux.corpnet.local:80 with proxy=DIRECT
      network: ResponseCode for http://myserver.com/jws/appframework-1.0.3.jar : 404
      network: Encoding for http://myserver.com/jws/appframework-1.0.3.jar : gzip
      network: Connecting http://myserver.com/jws/appframework-1.0.3.jar with proxy=DIRECT
      network: Connecting socket://ninesummer.lexlinux.corpnet.local:80 with proxy=DIRECT
      security: JAVAWS AppPolicy Permission requested for: http://myserver.com/jws/lib/appframework-1.0.3.jar
      security: Istrusted: http://myserver.com/jws/launch.jnlp true
      cache: Resource http://myserver.com/jws/appframework-1.0.3.jar has expired.
      network: Connecting http://myserver.com/jws/appframework-1.0.3.jar with proxy=DIRECT
      network: Connecting socket://ninesummer.lexlinux.corpnet.local:80 with proxy=DIRECT

      Any idea what the problem might be?


      Here is some of the info in the jnlp:

      <jnlp codebase="http://myserver.com/jws" href="launch.jnlp" spec="1.0+">

      .
      .
      .


      <j2se version="1.7+"/>
      <jar href="MyApp.jar" main="true"/>


      <jar href="lib/appframework-1.0.3.jar"/>
      <jar href="lib/swing-worker-1.1.jar"/>
      <jar href="lib/commons-collections-3.2.1.jar"/>
      <jar href="lib/commons-configuration-1.8.jar"/>
      <jar href="lib/commons-lang-2.6.jar"/>
      <jar href="lib/commons-logging-1.1.1.jar"/>
      <jar href="lib/jaxb-api.jar"/>
      <jar href="lib/jersey-bundle-1.12.jar"/>
      <jar href="lib/jsr311-api-1.1.1.jar"/>
      <jar href="lib/log4j-1.2.16.jar"/>
      <jar href="lib/AbsoluteLayout.jar"/>

      </resources>
      <application-desc main-class="app.MyApp">

      </application-desc>
      </jnlp>

      Edited by: 931632 on May 2, 2012 1:14 PM