Do not implement the Tomcat native library

Guidewire recommends that you do not implement the Tomcat Native Library. The major pitfall of using the library is that it mixes Java code and C/C++ code in the same process. This mixture of coding languages requires the use of the Java Native Interface (JNI), which is not optimal for performance. Guidewire has observed performance degradation in tests with the Tomcat Native Library implemented.

The primary intent of the Tomcat Native Library is to execute some capabilities in native code versus Java. One such capability is encryption, which is calculation intensive and not optimally suited for Java. If you want to use encryption, consider offloading the encryption task to a dedicated component such as a hardware appliance, Apache Web Server, or Microsoft Internet Information Server. These components are designed for such capabilities and are therefore more secure. Additionally, having a dedicated component enables you to build a more secure network organization with a DMZ.

The Tomcat server reports a message similar to the following upon startup if the Tomcat Native Library is not implemented:

INFO: The Apache Tomcat Native library which allows optimal performance in production
environments was not found on the java.library.path: 

You can safely ignore this message.