JDK-8058736 : bigapps/Weblogic+medrec/nowarnings: Can't connect to X11 window server..
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris
  • CPU: sparc
  • Submitted: 2014-09-18
  • Updated: 2014-12-12
  • Resolved: 2014-09-29
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 9
9Resolved
Related Reports
Relates :  
Description
WARNING: -------------------------------
Errors while execute: 'Check printer subprocess
Exception in thread "Thread-2" java.lang.InternalError: Can't connect to X11 window server using '$DISPLAY_SITE' as the value of the DISPLAY variable.
	at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
	at sun.awt.X11GraphicsEnvironment.access$100(X11GraphicsEnvironment.java:52)
	at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:155)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:131)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:169)
	at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:68)
	at sun.awt.X11.XToolkit.<clinit>(XToolkit.java:89)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:169)
	at java.awt.Toolkit$2.run(Toolkit.java:834)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:826)
	at sun.print.CUPSPrinter.<clinit>(CUPSPrinter.java:61)
	at sun.print.UnixPrintServiceLookup.getDefaultPrintService(UnixPrintServiceLookup.java:503)
	at sun.print.UnixPrintServiceLookup.refreshServices(UnixPrintServiceLookup.java:186)
	at sun.print.UnixPrintServiceLookup$PrinterChangeListener.run(UnixPrintServiceLookup.java:734)
-------------------------------

Comments
JDK-8059390 handles (3) from above.
30-09-2014

Three problems have happened during the failing run. (1) Sep 18, 2014 7:06:20 AM: Exception in thread "main" gtee.util.FileCacheException: File does not exist: /export/local/aurora/sandbox/gtee/etc/tlists/lists/testbase/bigapps/allbugs (2) Sep 18, 2014 7:07:21 AM: Exception in thread "Thread-2" java.lang.InternalError: Can't connect to X11 window server using '$DISPLAY_SITE' as the value of the DISPLAY variable. (3) between Sep 18, 2014 8:21:52 AM and Sep 18, 2014 8:27:54 AM: Java HotSpot(TM) 64-Bit Server VM warning: CodeCache is full. Compiler has been disabled. Java HotSpot(TM) 64-Bit Server VM warning: Try increasing the code cache size using -XX:ReservedCodeCacheSize= CodeCache: size=131072Kb used=129451Kb max_used=129455Kb free=1620Kb bounds [0xffffffff6f000000, 0xffffffff77000000, 0xffffffff77000000] total_blobs=58200 nmethods=57083 adapters=987 (1) and (2) are two configuration problems that don't cause the test to fail. (1) is handled by INTJDK-7613503, (2) is handled by INTJDK-7613486. I suggest to close this issue as duplicate of INTJDK-7613486 and open a new issue dedicated to (3) (the problem caused by code cache capacity being exhausted). Please let me know if you think we should proceed differently.
29-09-2014

A solution could be to increase the code cache size (and thus enable the test to run faster), or to allocate more time for running the test (increase the value of the timeout).
29-09-2014

hotspot/compiler doesn't seem to be the right category since this is not a Compiler issue. Where should we move it to?
23-09-2014

ILW=Test fail, a few times, none + nightly = HLH = P2
19-09-2014