laps,
About the stack traces you posted...
The ones on the server appear as warnings (not errors) because the server found a JAR in which the manifest Class-Path refers to a file which the server cannot find. This is not necessarily an error, because the JAR file spec does not mandate that all JARs listed in a Class-Path actually exist. (The URLClassLoader tolerates Class-Path entries that refer to non-existent files, for example.) But the GlassFish server chooses to warn you in case you had intended the missing JARs to be present. We feel this is particularly important in the case of Java Web Start support for clients, which is where this stack trace originates. We assume that it will be more difficult, in general, for an administrator or application support staff to investigate a missing JAR situation on an end-user system than to look in the server.log file and see a warning. It does absolutely add to the noise in the log file, but we decided that the added potential convenience was worth the added potential annoyance.
The client-side stack trace looks like a known issue that has been fixed in more recent builds of 3.0.1 and 3.1. If you are seeing that with very recent builds please open a new GlassFish issue, ideally with a simple case that reproduces the problem.
- Tim
[Message sent by forum member 'tjquinn']
http://forums.java.net/jive/thread.jspa?messageID=393345