Tim Holloway wrote:"export" doesn't promote the environment assignment to other command shells. It merely ensures that the assignment will be visible in the child shells your current shell spawns.
As long as you have JAVA_HOME set to the proper JDK in the shell that launches Tomcat, its value in other shells doesn't matter.
Although I don't have much use for IcedTea myself, so I do my exports for things like JAVA_HOME at a higher level. There are many places to do this. One is the profile of the user account that Tomcat is launched under. Another is the set of profiles used globally by the various shells and defined in the /etc directory.
Jeanne Boyarsky wrote:If you type this command, does it show your changes to the path? (I'm guessing it doesn't.)
When you say you exit from the console, does that mean opening a new SSH connection or something else?
Tim Holloway wrote:For best results, point the Tomcat JAVA_HOME to a Java 7 JDK. That will get rid of the websockets message.
The native library message is an indicator that you don't have the Apache Tomcat Native library built into your copy of Tomcat. Unless you are an advanced Tomcat user and you absolutely, positively MUST have the maximum in performance, however, you should leave this alone. You can't just drop something in and/or set an option to use the TNL, you have to build a complete custom built of Tomcat from source code with TNL enabled in the build. It's almost never worth this much trouble.
I've used Tomcat since at least version 3 and I don't think I've ever done a TNL build, even briefly. In my opinion, if you're that close to Tomcat's limits, you're probably better off doing some tuning and/or clustering.
So, like Bear said. Ignore the message.
Bear Bibeault wrote:It will cause no problems.