2007/9/13, glassfish_at_javadesktop.org <glassfish_at_javadesktop.org>:
> 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.
I am not sure if it is possible, that the _downloading_ of jars at
1mbit/s can, by itself, cause CPU to go 100%. Even if there are, let's
say, 30 or 60 parallel downloads, this is just 1mbit/s.
>
> Are there any errors logged in server.log?
I was browsing the log, did not find anything suspicious (but our
application is still a little bit verbose and I might miss something).
> 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.
Not really :( They all use it at the same time, as they all work at
the same hours...
I am wondering how to perform some stress test to reproduce problem at my box :/