JDK-8051857 : OperationTimedOut exception inside from XToolkit.syncNativeQueue call
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 9
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux_ubuntu
  • CPU: x86_64
  • Submitted: 2014-07-24
  • Updated: 2015-07-23
  • Resolved: 2014-09-26
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7 JDK 8 JDK 9
6u95Fixed 7u80Fixed 8u40Fixed 9 b36Fixed
Related Reports
Duplicate :  
JDK-8039922 - Test javax/swing/system/6799345/TestShutdown.java fails intermittently against JDK 7
Duplicate :  
JDK-8066744 - The case fail automatically with the sun.awt.SunToolkit$OperationTimedOut exception
Duplicate :  
JDK-8066742 - javax/swing/JInternalFrame/4251301/bug4251301.java:it fails automatically and throws sun.awt.SunToolkit$InfiniteLoop exception on terminal
Duplicate :  
JDK-8066743 - The regression-swing case fails automatically and throws sun.awt.SunToolkit$OperationTimedOut exception on terminal
Relates :  
JDK-8049032 - [GNOME 3] issue with jdk8 and realSync
Description
syncNativeQueue() throws an OperationTimedOut: 20001 exception.

Exception in thread "AWT-EventQueue-0" sun.awt.SunToolkit$OperationTimedOut: 20001
	at sun.awt.X11.XToolkit.syncNativeQueue(XToolkit.java:2411)
	at sun.awt.SunToolkit$3.dispatch(SunToolkit.java:1646)
	at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:752)
	at java.awt.EventQueue.access$500(EventQueue.java:97)
	at java.awt.EventQueue$3.run(EventQueue.java:705)
	at java.awt.EventQueue$3.run(EventQueue.java:699)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:75)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:722)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:190)
	at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:115)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:104)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:100)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:92)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:81)

The issue may be similar to JDK-8049032 and others, but the stacktracke does not contains actual realSync() call.

To reproduce the problem run the attached RealsyncTimeout.java test. To compile it use additionally ExtendedRobot class from here:
http://hg.openjdk.java.net/jdk9/jdk9/jdk/raw-file/tip/test/lib/testlibrary/ExtendedRobot.java

The tests can fail occasionally. And may not. The failure is not stable.
Comments
Only if you want to run tests on OEL7 (it starts to use Gnome 3 by default). Please note that JDK-7033533 and JDK-8051857 should be backported together.
03-10-2014
Is JDK 7 and 6 affected? Is backport needed?
03-10-2014
http://cr.openjdk.java.net/~azvegint/jdk/9/8051857/ We have XNextSecondaryLoopEvent() which blocks all events processing except of this specific types: PropertyNotify, SelectionClear, SelectionNotify. Before the JDK-7033533 fix, syncNativeQueue() used a SelectionNotify, but now we are using ConfigureNotify. This leads to a situation when syncNativeQueue() called on EventQueue thread waiting for ConfigureNotify from XAWT thread, and DataTransferer.convertData() called on XAWT thread waiting event processing on the EventQueue thread. Here it is our OperationTimedOut exception.
23-09-2014