If you use the JBoss Community Edition to run LiveCycle ES2, the server.log will have an entry such as this: INFO [org.apache.catalina.core.AprLifecycleListener] 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 INFOrmational message. It is essentially informing you that the Tomcat web container of JBoss is not using the Apache Portable Runtime (APR). According to the Apache Software Foundation’s webpage for Tomcat, the Apache Portable Runtime “…provides superior scalability, performance, and better integration with native server technologies”.
If you would really like to address it, you have to download the JBoss Web Native Connector. The steps are:
1) Download the JBoss Web Native Connector for 64-bit Windows (“JBoss Native 2.0.6 Win64 AMD64/EMT64”) from here.
2) Unzip the downloaded file. Copy the contents of the \bin\native\ folder to the \system32\ folder of your Windows installation.
3) Edit %JBOSS_HOME%\server\<your_jboss_configuration>\deploy\jboss-web.deployer\server.xml using a good text editor. Change the protocol setting of the HTTP Connector from “HTTP/1.1” to “org.apache.coyote.http11.Http11AprProtocol“. Save the file.
4) Re-start JBoss. In server.log, you should now see a message such as this : INFO [org.apache.catalina.core.AprLifecycleListener] Loaded Apache Tomcat Native library 1.1.18.
Please note that if you plan to configure Tomcat/JBoss for HTTPS, then you will have to use OpenSSL to create your server’s private key and server certificate (instructions here). Those built with the JDK’s Keytool (%JAVA_HOME%\bin\keytool.exe) will not work.