Steps to reproduce:
1. Enable accesibility
   Click Launch menu -> Preferences -> Assistive Technology Preferences
   Check "Enable assistive technologies"
   Log out and log in again.
2. Start a terminal
3. Enable debug information in the terminal
   export GNOME_ACCESSIBILITY=1
4. Start a java application
   for example, java -jar /usr/java/demo/jfc/Notepad/Notepad.jar


Stack trace:
java -jar SwingSet2.jar
Java Accessibility Bridge for GNOME loaded.

org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No
        at com.sun.corba.se.impl.logging.ORBUtilSystemException.writeErrorSend(ORBUtilSystemException.java:2231)
        at com.sun.corba.se.impl.logging.ORBUtilSystemException.writeErrorSend(ORBUtilSystemException.java:2253)
        at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.writeLock(SocketOrChannelConnectionImpl.java:933)
        at com.sun.corba.se.impl.encoding.BufferManagerWriteStream.sendFragment(BufferManagerWriteStream.java:78)
        at com.sun.corba.se.impl.encoding.BufferManagerWriteStream.sendMessage(BufferManagerWriteStream.java:96)
        at com.sun.corba.se.impl.encoding.CDROutputObject.finishSendingMessage(CDROutputObject.java:144)
        at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.finishSendingRequest(CorbaMessageMediatorImpl.java:247)
        at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete1(CorbaClientRequestDispatcherImpl.java:342)
        at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(CorbaClientRequestDispatcherImpl.java:323)
        at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:129)
        at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
        at org.GNOME.Accessibility._RegistryStub.ref(_RegistryStub.java:519)
        at org.GNOME.Accessibility.EventQueueRegistry.<init>(EventQueueRegistry.java:38)
        at org.GNOME.Accessibility.AccessUtil.getRegistryObject(AccessUtil.java:143)
        at org.GNOME.Accessibility.JavaBridge.registerApplication(JavaBridge.java:1058)
        at org.GNOME.Accessibility.JavaBridge.<init>(JavaBridge.java:341)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at java.lang.Class.newInstance0(Class.java:355)
        at java.lang.Class.newInstance(Class.java:308)
        at java.awt.Toolkit.loadAssistiveTechnologies(Toolkit.java:773)
        at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:861)
        at sun.swing.SwingUtilities2$AATextInfo.getAATextInfo(SwingUtilities2.java:120)
        at javax.swing.plaf.metal.MetalLookAndFeel.initComponentDefaults(MetalLookAndFeel.java:1556)
        at javax.swing.plaf.basic.BasicLookAndFeel.getDefaults(BasicLookAndFeel.java:130)
        at javax.swing.plaf.metal.MetalLookAndFeel.getDefaults(MetalLookAndFeel.java:1591)
        at javax.swing.UIManager.setLookAndFeel(UIManager.java:537)
        at javax.swing.UIManager.setLookAndFeel(UIManager.java:577)
        at javax.swing.UIManager.initializeDefaultLAF(UIManager.java:1331)
        at javax.swing.UIManager.initialize(UIManager.java:1418)
        at javax.swing.UIManager.maybeInitialize(UIManager.java:1406)
        at javax.swing.UIManager.getDefaults(UIManager.java:656)
        at javax.swing.UIManager.put(UIManager.java:985)
        at SwingSet2.main(SwingSet2.java:229)

In fact, this bug is not always able to be reproduced easily. At some
time, I can reproduce it under the user "caiqm" on my Solaris nevad build_75. But after logging in the system with another user "test", the bug has gone.
So I doubted perhaps there was some cache which made this bug. I moved
"caiqm" home directory and made a new empty directory. But I could still
reproduce this bug. This really made me confused.

Additionally, if you start at-spi-registryd manually while not start it by gnome-session, this bug can't be reproduced.


Other information: