Hello, Witold.
As you pointed out the Java Web Start clients will download the updated app server JARs that are in the new build and this will take some time. From here there is no way to tell if that is what is taking the time and resources.
Are there any errors logged in server.log?
Assuming for a moment that the JAR downloads are triggering this, is there some way that your customer's users can connect in smaller groups at first, rather than so many at once, until all the client systems have retrieved the updated GlassFish JARs? I realize this is not an ideal solution, but it might allow you and the users to get started with the new version.
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=235256