Tested with j2sdk 1.3.0 Linux beta build b05 on
both of on Redhat6.1J original and upgrade version

with HotSpot (-hotspot)
Xlib: unexpected async reply error occurs.

with Classic VM
java.awt.AWTException: cannot open XIM occurs.
The detail of AWTException is below;

java.awt.AWTException: cannot open XIM
        at sun.awt.motif.X11InputMethod.<init>(X11InputMethod.java:148)
        at sun.awt.motif.X11InputMethodDescriptor.createInputMethod(X11InputMeth
odDescriptor.java:78)
        at sun.awt.im.InputContext.getInputMethodInstance(InputContext.java:686)
        at sun.awt.im.InputContext.getInputMethod(InputContext.java:636)
        at sun.awt.im.InputContext.dispatchEvent(InputContext.java:188)
        at sun.awt.im.InputMethodContext.dispatchEvent(InputMethodContext.java:1
77)
        at java.awt.Component.dispatchEventImpl(Component.java:2529)
        at java.awt.Container.dispatchEventImpl(Container.java:1213)
        at java.awt.Window.dispatchEventImpl(Window.java:912)
        at java.awt.Component.dispatchEvent(Component.java:2499)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:319)
        at java.awt.EventDispatchThread.pumpOneEvent(EventDispatchThread.java:10
3)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:84)



To reproduce "Xlib: unexpected async reply"

1. Launch StylePad, which is bundled in J2SDK, with Hotspot
(java -hotspot -jar Stylepad.jar).
2. When loading a demo finishes and a demo starts, a mouse pointer is on the demo frame, Xlib: unexpected async reply occurs and a demo hangs.
(If not, you move a mouse pointer onto the demo Frame, the error occurs.)

To reproduce "java.awt.AWTException: cannot open XIM".

1. Launch StylePad demo, which is bundled in J2SDK, with Classic VM
(java -jar Stylepad.jar).
2. When loading a demo finishes and a demo starts, a mouse pointer is on the demo frame, java.awt.AWTException: cannot open XIM occurs and a demo can work.
(If not, you move a mouse pointer onto the demo Frame, the error occurs.)

The same phenomenon is found on SwinSet2 demo.
Our all Swing testing cases can not work due to this phenomenon.


This problem is not reproducible on Redhat 6.2J.