1 Reply Latest reply on Nov 30, 2015 2:17 AM by vata2999

JBoss APR Installation The native library was not found

vata2999 Nov 28, 2015 1:53 AM

I'm trying to install APR on Jboss eap 6.4 but I keep getting this message

The native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/packages/lib/i386:/lib:/usr/lib

I tried following steps :

yum install yum install apr-devel openssl-devel
ls /usr/lib // the output shows /usr/lib/libapr-1.so.0
download jboss-native-2.0.10-linux2-i64-ssl.tar.gz
extract it in jboss-eap-6.4/modules/system/layers/base/org/jboss/as/web/main/lib/
e.g jboss-eap-6.2/modules/system/layers/base/org/jboss/as/web/main/lib/libapr-1.so
add  -Djava.library.path=jboss-eap-6.4/modules/system/layers/base/org/jboss/as/web/main/lib/ to JAVA_OPTS

am I missing something ?

according to [JBPAPP6-408] APR in jboss-eap-native-6.0.0.ER3-sun10.* does not load - JBoss Issue Tracker and Using native libraries (apr) with JBoss 7.0.2 it should work

1. Re: JBoss APR Installation The native library was not found

vata2999 Nov 30, 2015 2:17 AM (in response to vata2999)

I realized that I didn't install tomcat-native but now I get this error

BWEB003043: Error initializing endpoint: java.lang.Exception: Invalid Server SSL Protocol (error:00000000:lib(0):func(0):reason(0))
    at org.apache.tomcat.jni.SSLContext.make(Native Method) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
    at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:609) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
    at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:104) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
    at org.apache.catalina.connector.Connector.init(Connector.java:986) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
    at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:318) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_67]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_67]
    at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67]

10:39:30,300 INFO [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-4) JBWEB003001: Coyote HTTP/1.1 initializing on : http-localhost/127.0.0.1:8080
10:39:30,350 INFO [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-4) JBWEB003000: Coyote HTTP/1.1 starting on: http-localhost/127.0.0.1:8080
10:39:30,376 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.web.connector.https: org.jboss.msc.service.StartException in service jboss.web.connector.https: JBAS018007: Error starting web connector
    at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:393)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_67]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_67]
    at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67]
Caused by: LifecycleException: JBWEB000023: Protocol handler initialization failed
    at org.apache.catalina.connector.Connector.init(Connector.java:989)
    at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:318)
    ... 5 more

I'm using self-signed SSL
Actions