========================================================================
Merlin build: beta_refresh-b66
Solaris9 build: s81_39 with "Entire distribution OEM support" installing
CDE version : 1.5 39b
========================================================================

Tested for Solaris 9(sparc and x86):
Swing application such as "SwingSet2","Notepad" and "Java2D", can not work properly.

To reproduce;
1. Launch SwingSet2 ($JAVAHOME/demo/jfc/SwingSet2/SwingSet.jar) on Solaris9/ja or C locale.
2. The frame appears and loading messages are displayed.
   
Then, after loading messages, there is nothing displayed in the frame.
(please see attached gif file)
However, this problem is not seen in Solaris9(s81_39)/ja_JP.UTF8 lcoale.

This phenomenon does not occur on Solaris8, 7, and 2.6.

This problem did not ouccur on Solaris9(s81_38)/ja locale with Merlin_b63b.
                                        ^^^^^^
Therefore, I'm not sure whether this problem is caused by merlin(b66) or Solaris9(s81_39).


> java -version
jva version "1.4.0-beta_refresh"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta_refresh-b66)
Java HotSpot(TM) Client VM (build 1.4.0-beta_refresh-b66, mixed mode)

> uname -a
SunOS ohio 5.9 s81_39 sun4u sparc SUNW,Ultra-1

* Solaris 9 x86 can not verify this problem, due to #4465657

-----------------------------------------------------------------------------
When I run the SwingSet2 demo on s9 sparc, got the thread dump as below;

"Thread-4" prio=5 tid=0x28fd0 nid=0x1 waiting on monitor [0..ffbfe7e8]

"TimerQueue" daemon prio=5 tid=0x6b2a30 nid=0xf waiting on monitor [f3d7f000..f3d7fc68]
        at java.lang.Object.wait(Native Method)
        - waiting on <f551cc90> (a javax.swing.TimerQueue)
        at javax.swing.TimerQueue.run(TimerQueue.java:234)
        - locked <f551cc90> (a javax.swing.TimerQueue)
        at java.lang.Thread.run(Thread.java:579)

"AWT-InputMethodManager" daemon prio=6 tid=0x37dd70 nid=0xe waiting on monitor [f3b7f000..f3b7fc68]
        at java.lang.Object.wait(Native Method)
        - waiting on <f546ddf0> (a sun.awt.im.ExecutableInputMethodManager)
        at java.lang.Object.wait(Object.java:425)
        at sun.awt.im.ExecutableInputMethodManager.waitForChangeRequest(InputMethodManager.java:361)
        - locked <f546ddf0> (a sun.awt.im.ExecutableInputMethodManager)
        at sun.awt.im.ExecutableInputMethodManager.run(InputMethodManager.java:302)
        at java.lang.Thread.run(Thread.java:579)

"Thread-1" daemon prio=5 tid=0x37d568 nid=0xd waiting on monitor [f3c7f000..f3c7fc68]
        at java.lang.Object.wait(Native Method)
        - waiting on <f54751e8> (a java.util.TaskQueue)
        at java.util.TimerThread.mainLoop(Timer.java:432)
        - locked <f54751e8> (a java.util.TaskQueue)
        at java.util.TimerThread.run(Timer.java:385)

"AWT-EventQueue-0" prio=5 tid=0x33ff80 nid=0xb waiting on monitor [f3e7f000..f3e7fc68]
        at java.lang.Object.wait(Native Method)
        - waiting on <f53b3b38> (a java.awt.EventQueue)
        at java.lang.Object.wait(Object.java:425)
        at java.awt.EventQueue.getNextEvent(EventQueue.java:325)
        - locked <f53b3b38> (a java.awt.EventQueue)
        at java.awt.EventDispatchThread.pumpOneEvent(EventDispatchThread.java:145)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:136)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:131)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:99)

"AWT-Motif" daemon prio=6 tid=0x33efd0 nid=0xa runnable [f3f7f000..f3f7fc68]
        at sun.awt.motif.MToolkit.run(Native Method)
        at java.lang.Thread.run(Thread.java:579)

"AWT-Shutdown" prio=5 tid=0x2bfb18 nid=0x9 waiting on monitor [f407f000..f407fc68]
        at java.lang.Object.wait(Native Method)
        - waiting on <f53aaf10> (a java.lang.Object)
        at java.lang.Object.wait(Object.java:425)
        at sun.awt.AWTAutoShutdown.run(AWTAutoShutdown.java:262)
        - locked <f53aaf10> (a java.lang.Object)
        at java.lang.Thread.run(Thread.java:579)

"Signal Dispatcher" daemon prio=10 tid=0xa0998 nid=0x7 waiting on monitor [0..0]

"Finalizer" daemon prio=8 tid=0x9b588 nid=0x4 waiting on monitor [faf7f000..faf7fc68]
        at java.lang.Object.wait(Native Method)
        - waiting on <f53b70b8> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
        - locked <f53b70b8> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:126)
        at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:162)

"Reference Handler" daemon prio=10 tid=0x9abe0 nid=0x3 waiting on monitor [fd0ff000..fd0ffc68]
        at java.lang.Object.wait(Native Method)
        - waiting on <f53b7118> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(Object.java:425)
        at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:110)
        - locked <f53b7118> (a java.lang.ref.Reference$Lock)

"VM Thread" prio=5 tid=0x998d8 nid=0x2 runnable

"VM Periodic Task Thread" prio=10 tid=0x9f840 nid=0x5 waiting on monitor
"Suspend Checker Thread" prio=10 tid=0xa00b0 nid=0x6 runnable


[rieko.suzuki@Japan 2001-06-05]
============================================================================

This problem does NOT occur on Solaris9 with 64 bit & Server VM.
                  ^^^ ^^^^^^^^^^^^^^^^^^^
Swing application works fine with merlin b66 64bit & ServerVM, using the following command.

- Tested for Sparc 9 with 64 bit & Server VM:

% java -d64 -version
java version "1.4.0-beta_refresh"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta_refresh-b66)
Java HotSpot(TM) Client VM (build 1.4.0-beta_refresh-b66, mixed mode)

% java -d64 -jar SwingSet2.jar <------- works fine

- Tested for Sparc 9 with 64 bit & Client VM:

% java -jar SwingSet2.jar <---- NG

- Tested for Sparc 9 with 32 bit & Client VM:

% java -jar SwingSet2.jar <---- NG

Therfore, I wonder if this problem occurs on Solaris 9 with Client VM.

[rieko.suzuki@Japan 2001-06-08]
=============================================================================
Tested again with merlin-beta-refresh b67 on two solaris sparc9 machines(ohio and ronrico)

I tryied with "-Xint" in command line, however, this problem is reproducible.

machine name OS 32/64 locale
------------------------------------------------
ronrico Sparc 9(s81_39) 64bit ja
ohio Sparc 9(s81_39) 32bit ja


ronrico(64bit OS)
- Server VM
  % java -d64 -server -jar SwingSet2.jar <------- this problem does not occur.
  % java -d64 -server -Xint SwingSet2.jar <------- this problem does not occur.
  % java -server -jar SwingSet2.jar <------- this problem does not occur.
  % java -server -Xint -jar SwingSet2.jar <------- NG

- Client VM
  % java -jar SwingSet2.jar <----- NG
  % java -Xint -jar SwingSet2.jar <----- NG

ohio(32bit OS)
- Server VM
  % java -server -jar SwingSet2.jar <--- NG
  % java -server -Xint SwingSet2.jar <--- NG

- Clinet VM
  % java -jar SwingSet2.jar <--- NG
  % java -Xint -jar SwingSet2.jar <--- NG

I created temporary account on ohio.japan and ronrico.japan for this bug fonfirmation.
I let you know the account info about these machines by e-mail later.

[rieko.suzuki@Japan 2001-06-14]
=============================================================================
Here is the result of more investigation on ohio(32bit OS);

In case of ohio(32bit OS) & ServerVM,
if no application is running on ohio except SwingSet2, this problem does NOT occur.

- No application is running except SwingSet2
  % java -server -jar SwingSet2.jar <---- OK
  % java -server -Xint SwingSet2.jar <--- OK

However, if an other application, such as dtmail, is running on ohio, this problem occurs.

- Dtmail application and SwingSet2 are running on ohio
  % java -server -jar SwingSet2.jar <---- NG
  % java -server -Xint SwingSet2.jar <--- NG

[rieko.suzuki@Japan 2001-06-14]
=============================================================================
I confirmed that this problem is no more reproducible on Solaris9/(Sparc and x86) s81_40 which is latest build using Merlin beta-refresh b68.
It is not reproducible using 64-bit/32-bit ServerVM and ClientVM.
Swing application works fine on Solaris9(x86/sparc).
     
Tested with Merlin-beta-refresh b68 on Solaris9(s81_40)
bombay Solaris9/x86 (s81_40)
----------------------------
- 32bit OS && Server VM
  % java -server -jar SwingSet2.jar --------> OK
  % java -server -Xint -jar SwingSet2.jar --> OK

- 32bit OS && Client VM
  % java -jar SwingSet2.jar ---------> OK
  % java -Xint -jar SwingSet2.jar -----> OK

ronrico Solaris9/sparc (s81_40)
--------------------------------
- 64 bit OS && Server VM
  % java -d64 -server -jar SwingSet2.jar --------> OK
  % java -d64 -server -Xint -jar SwingSet2.jar ---> OK
  % java -server -jar SwingSet2.jar ------->OK
  % java -server -Xint -jar SwingSet2.jar ------->OK

- 64 bit OS && Clinet VM
  % java -jar SwingSet2.jar ---------> OK
  % java -Xint -jar SwingSet2.jar -----> OK

- 32 bit OS && Server VM
  % java -server -jar SwingSet2.jar -------> OK
  % java -server -Xint -jar SwingSet2.jar -------> OK

- 32 bit OS && Client VM
  % java -jar SwingSet2.jar ---------> OK
  % java -Xint -jar SwingSet2.jar -----> OK

[rieko.suzuki@Japan 2001-06-18]