Naden Franciscus wrote:
>We are deploying a Java Web Start app to a very large number of Mac users
>and are getting quite a few problems on a certain portion of them. What
>happens is that when the JNLP file is downloaded and opened, it takes about
>3 minutes before downloading the JAR files and opening the app. On other
>machines, there is no such delay. We can't seem to figure it out
>
>Does anyone know of any causes for causing a Web Start app to delay before
>opening ?
I don't know of any cause specific to JNLP or JWS, so it could be anything.
I think you'll have to collect specific information about the machines
where the problem is occurring, and correlate the results looking for a
pattern. At the very least, I suggest getting Mac OS X version, Java
version, architecture (ppc or Intel), total RAM size, and network
connection info. It would also help to see the JNLP file's contents, and
to know the sizes of the jars being downloaded, but I assume you already
know those and can tell us without collecting any client data.
I'm unclear on exactly where the 3-minute delay occurs. Are you saying
that after the JNLP file has been received, yet before any jars begin to be
downloaded, there is a delay of 3 minutes? If so, can you find out what
the machine is doing during that time (see below)?
Or are you saying that after the JNLP file have been received, there is a
delay of 3 minutes until all the jars have been downloaded? If that's so,
I would suspect a low-speed connection, such as a dialup client, or
possibly a dodgy wireless connection.
If the delay comes after the jars have been received and before the app's
first window appears, I would suspect a computer speed problem, such as
disk-thrashing due to swapping, or possibly running under the Rosetta'ed
1.3 JVM on an Intel-based Mac. A real elapsed time of 3 minutes seems
extreme for either of those, so I'm not sure if you have an objective
measure by a stopwatch or a user's subjective opinion that 3 minutes or so
has elapsed.
All of this is just guessing, though, because without specific data, that's
all anyone can do.
If you can get one of the clients to cooperate, have it run Activity
Monitor (in /Applications/Utilities). The user can then directly observe
what's going on during the delay.
You can watch any two activities at once by having Activity Monitor show
one of them on its Dock icon (View menu, Dock Icon item), and the other one
in its main window pane (tab-bar below process list). You can watch CPU
usage plus any two other activities by showing the floating CPU Usage
window (Window menu), then setting up the Dock icon with another activity
and the main window with the third. (The "Show Floating CPU Window" option
is about the same as CPU Usage in this case, if you like it better.)
The three things I would watch at once are CPU Usage, Disk Activity, and
Network. If CPU Usage stays maxed out, then suspect Rosetta emulation or
some other CPU-heavy activity. If Disk Activity is consistently high,
suspect swapping. If Network is busy, suspect connection speed. The
network speed may be low in bytes/sec, but as long as its consistently
busy, it's an indication of network-transfer latencies.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
