Hi, Gel.
This is a bit odd.
Because the signed appserv-jwsacc.jar is present in ${install-dir}/domains/test004/java-web-start, that means several things:
1. The server received the HTTP request for the JNLP document and sent it as the response back to the client.
2. The Java Web Start client received the JNLP document and interpreted it which triggered the request for appserv-jwsacc.jar from the server.
3. Because the signed JAR is created only upon the first request for it after the domain was created, the fact that the signed JAR exists in that directory means the server received and at least partly acted on the request for the __JWSappclients/__appserver/aslib/appserv-jwsacc.jar file.
At that point it's hard to know what's going wrong. I am a bit surprised at the absence of any errors in the server.log.
One thing you could try just to help verify what I've described above is to turn on the HTTP service access logging. In the admin GUI in the left-hand-side navigation panel go to Configurations->server-config. Click on HTTP Service. Click the check-box to enable access logging. Then retry your experiment and let's see what requests and results are logged there. (The access log will be in the domain's log/access directory.)
One other question: What JDK are you using on the server side and on the client side?
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=240500