Java update 1.6.0_51 (update 16) breaks Tomcat in 10.6 server - help!

Question

Hi all,
After updating Java on our Xserves running OS X Server 10.6.8 last night, our mission critical Java Tomcat applications were unable to run.
Doing some research we discovered the following in the system logs:
at org.apache.catalina.startup.Bootstrap.createClassLoader(Bootstrap.java:183)
at org.apache.catalina.startup.Bootstrap.initClassLoaders(Bootstrap.java:92)
at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:207)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:391)
Aug 13, 2013 9:20:03 AM org.apache.catalina.startup.Bootstrap initClassLoaders
SEVERE: Class loader creation threw exception
java.lang.InternalError: Can't connect to window server - not enough permissions.
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1827)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1724)
In the prior release of Java, the Tomcat server was running in the background (headless?) and ran beautifully for the past 3 years.
I was able to manually start Tomcat by running /Library/Tomcat/bin/startup.sh , but manually starting Tomcat now launches org.apache.catalina.startup.bootstrap app which sits in the dock.  The problem comes when I log out of the root account, that bootstrap process is killed off and stops Tomcat and thus none of our clients can process credit cards.
There must be a way to get Tomcat to run again in the background without trying to connect to the Window server.  I've seen some postings mention the command or configuration "-Djava.awt.headless=true" as a solution to this problem, but I am not sure where or how that command or configuration is supposed to be set or installed to fix this problem.
Right now, I am having to maintain an active sign-in to our production servers in order to keep Tomcat running due to the change.
I'm in dire straits until I can get this permanently fixed.
"Help me Obi-Wan Kanobi, you're my only hope"

Answer 1

I am going to answer my own posting, since others may need this information to troubleshoot or solve their problems.
I was able to use this configuration directive in the "Tomcat/bin/catalina.sh" file to correct the issue.  I placed this right after the introductory comments found at the top of the file:
     CATALINA_OPS="-Djava.awt.headless=true"
This allowed the Catalina Bootstrap process - which is kicked off by the Tomcat Daemon that OS X Server runs every 10 seconds, to now tell Tomcat to run itself in the background (like its supposed to) instead of trying to run in a windowed interactive mode.
This also killed off the org.apache.catalina.startup.bootstrap app which was sitting in the dock.
Now I can again, log out of the server, using Remote Desktop, without causing Tomcat to shut down.
I hope this helps someone else with a similar issue.