-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Neil,
On 8/19/14, 11:53 AM, Neil Aggarwal wrote: > Christopher: > >> ldd /usr/local/apr/lib/libtcnative-1.so > linux-vdso.so.1 => (0x00007fff145fe000) libssl.so.10 => > /lib64/libssl.so.10 (0x00007f5642498000) libcrypto.so.10 => > /lib64/libcrypto.so.10 (0x00007f56420b3000) libapr-1.so.0 => > /lib64/libapr-1.so.0 (0x00007f5641e83000) libpthread.so.0 => > /lib64/libpthread.so.0 (0x00007f5641c67000) libdl.so.2 => > /lib64/libdl.so.2 (0x00007f5641a63000) libc.so.6 => > /lib64/libc.so.6 (0x00007f56416a1000) libgssapi_krb5.so.2 => > /lib64/libgssapi_krb5.so.2 (0x00007f5641457000) libkrb5.so.3 => > /lib64/libkrb5.so.3 (0x00007f5641177000) libcom_err.so.2 => > /lib64/libcom_err.so.2 (0x00007f5640f72000) libk5crypto.so.3 => > /lib64/libk5crypto.so.3 (0x00007f5640d3d000) libz.so.1 => > /lib64/libz.so.1 (0x00007f5640b27000) libuuid.so.1 => > /lib64/libuuid.so.1 (0x00007f5640921000) libcrypt.so.1 => > /lib64/libcrypt.so.1 (0x00007f56406ea000) > /lib64/ld-linux-x86-64.so.2 (0x00007f5642932000) > libkrb5support.so.0 => /lib64/libkrb5support.so.0 > (0x00007f56404dc000) libkeyutils.so.1 => /lib64/libkeyutils.so.1 > (0x00007f56402d7000) libresolv.so.2 => /lib64/libresolv.so.2 > (0x00007f56400bd000) libfreebl3.so => /lib64/libfreebl3.so > (0x00007f563fe3d000) libselinux.so.1 => /lib64/libselinux.so.1 > (0x00007f563fc18000) libpcre.so.1 => /lib64/libpcre.so.1 > (0x00007f563f9b7000) liblzma.so.5 => /lib64/liblzma.so.5 > (0x00007f563f791000) > > >> echo $LD_LIBRARY_PATH > > This gives me nothing back. Okay. That all looks good to me. Typically, ld looks in LD_LIBRARY_PATH if it is set (which it shouldn't be under normal circumstances) otherwise it looks in a set of default locations that you can find in /etc/ld.so.conf and friends. java.library.path just specifies the place where libraries that aren't already in the ld path can be loaded. Everything above looks like it would be in the default ld path, so all you need is the path to tcnative, which you've already provided to the JVM. Do the tcnative*.so files have the execute bit set? Also, to check the architecture of the binary, use file: $ file /usr/local/apr/lib/libtcnative-1.so On my system, I get this from my just-built 1.1.31: $ file libtcnative-1.so libtcnative-1.so: symbolic link to `libtcnative-1.so.0.1.31' $ file libtcnative-1.so.0.1.31 libtcnative-1.so.0.1.31: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=0x2c5c19e96e4f39a4433a0dabdb82175bf1305f70, not stripped All users should have "read" and "execute" privileges on the file itself, plus the Tomcat user requires "execute" privileges on every directory between / and /usr/local/apr/lib. You might also need Tomcat to have "read" privileges on those directories as well, depending upon how the JVM does its library-searching. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJT84p+AAoJEBzwKT+lPKRYXNYQALlo20BREOsP9wUWy5b247sw cVmpzb3p9cjiyO8BzUCPQWUSlix5QDo61tfyuBl1z27ouBnu2gv8TItkN8sY2vB0 2NmQVW9+Al4HIKTiZA+TccB+maygyWzXkDDrwLTMgHYtYX0rqE+qZ3sgMdkf7vyg BG8YCbIPh5tc+TrxFdZ/lLd+yxMaLiGUBLskuecHiM+T+96YspKjfm637e6itlCN m95ejWQryiu13jZ3fMaFj1fWOljqhvdqTBtHb4gCMrqIMrpjh9GKMEqsTvVWj4ms dm4mxXMPASgpgRRVubBLmlq2Wt7UbqusxZV7fYU9tv6IrRL6NwD1M3ONda7lhhAH Vy2ZD5n/sVMoq+QEfpw6Lt/WWmJeTmUYfqUvUlX+PCX3UhaGpjh++fKxnOKm/GRe o4SqYHvasPqSmZ6L3eeixIsSbvVjIvZUDUCk68GTP7qFT0j4j6UcD6XwtWZeQhGO 0y7b5j2zvVhb+nBPgTNwYctOYgpgwzF05FfBFLASvpJYX8vbZHHtgB+4HlixDvEl 0IklrUeJwCRe7wgtGkz4DmPtGZh3iChJw2VD+BvMnHbcOpcxMjwB8xsFoWCb4QH9 p3RKvEvGL+BJ+1EBL5N+6nJZYPD/IuZIm9Ba28feluN0+fimcDfPZhZFXObjnztl fnHur/IC7/2JMz1My0rC =Ye8e -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
