Bug #24226 DISPLAY environment variable can cause problems for Tomcat running

Description:
If the DISPLAY environment variable is set when starting Tomcat, it can cause issues and force Tomcat to shutdown with a message on first access similar to:

X connection to localhost:10.0 broken (explicit kill or server shutdown).

How to repeat:
Set your DISPLAY to something that doesn't work, start Tomcat, access dashboard, view tomcat error log.

Suggested fix:
Unset DISPLAY before launching Tomcat in the startup scripts in order to ensure that Tomcat runs in headless mode.

Need to figure out if unsetting DISPLAY would still be needed if we run Java/Tomcat headless.  

-Djava.awt.headless=true

Submitted changes to Keith, should be included in the build today, over to QA now.

Seems the "unset DISPLAY was not added to startup.sh or catalina.sh (and we also seem to have a problem with the headless setting, which is now within another bug). 

I still see no problem with using "unset DISPLAY" within startup.sh/catalina.sh as well as the headless setting - but would like Sloan's feedback. 

Assigning to Keith (as fixes were sent to him), Sloan, your feedback as well?

This is affecting a number of customers - I would like this fixed in 1.1.0 if at all possible. It affects graphing. 

----

[root@net-sup1 bin]# grep DISPLAY catalina.sh 
[root@net-sup1 bin]# grep DISPLAY startup.sh 

----

Sloan, Is it ok for "unset DISPLAY" to be included in the catalina.sh script? Mark had entered the comment: "I still see no problem with using "unset DISPLAY" within startup.sh/catalina.sh as well as the headless setting - but would like Sloan's feedback."

Bitrock, Please add "unset DISPLAY" to the apache-tomcat/bin/setenv.sh file.

Keith, can you change in your builds for now?

New patch sent to keith

checked OK with 1.1.0.4876

Added to changelog.

The update installer should modify the "catalina.sh" script to include "unset DISPLAY".  This bug is being re-opened to track this change.

Patch sent to Keith

Patch installed in versions => 1.1.1.5646

Verified it's now in the update in build 1.1.1.5646.