I am not sure if this is actually a AWT regression since 1.4, or JWS
bug.

I need JWS developer's review and support for generating a demo case if
it's a AWT bug.

This happens in our automation development work and, general user will
rarely meet this.

It happens on Windows platform.

To reproduce the bug, on a clean machine without any JRE/JDK/JWS installed,
install latest Hopper build (or Merlin fcs JRE). In Hopper JRE, JWS version
is 1.2, in Merlin FCS, JWS version is 1.0.1_02. This doesn't matter.

Step to reproduce:
1. Install JRE, using default configuration.
2. After installation, close other running application window.
3. double click the Java Web Start Icon on the desktop.
4. After double click the icon, don't move the mouse, just wait the
   Java Web Start application manager to show up and wait all the icons
   inside the panel to be updated. It might take a while.
5. After JWS has downloaded all the resources from the demo site and
   no more activity is going, the application manager window has
   the focus, but, if you press Alt+F4 to close it, or press Alt+F to
   open file menu. It won't work.

It takes some trial and error to reproduce the bug. Using Hopper, I can
reproduce it 1 out of 4 times, using Merlin, I can reproduce it 1 out of
9 times. I can't reproduce it using 1.3.1_02.

Here are some evaluation.

Initially I tried to explain the behavior in this:
The Java Web Start shortcut is pointing to javaws.exe file, which subsequently
launch a Java program (Application manager) and die silently. So the focus
is on that javaws.exe file and, when it dies, the focus is going to nowhere.
That's why Application manager does not has input focus.

However, If you try to launch an application, then close it. Now there is
something in the cache. Now repeat abve 4 and 5 steps, you will always get
the focus in Application manager.

I think there might be some race condition happening after the initial
launching of the Java Web Start.

It's taking me quite a long time to get a thread dump. See the comments
part.

Instead of launching from javaws.exe, I tried to launch javaws.jar file
directly, which you know how to do that.

The trick is if you type the command in a Windows prompt, or run a bat file
in a windows prompt, you can't reproduce the bug. The reason might be the
opening Windows prompt window helped something in focus. You should create
a shortcut to the bat file used to launch javaws.jar file. Then, when no
other application window running, double click the shortcut on the desktop.


###@###.### 2002-07-22