the latest commons-daemon 1.0.15 makes the libcap error go away but does
not fix the CommunicationException
On Thu, Jan 16, 2014 at 4:32 PM, Erik Engstrom wrote:
> I think it is due to this bug in commons-daemon
> https://issues.apache.org/jira/browse/DAEMON-246 but it did not seem to
> keep t
I think it is due to this bug in commons-daemon
https://issues.apache.org/jira/browse/DAEMON-246 but it did not seem to
keep the service from running properly. I will try with the latest version
that is supposed to have a fix for it but I don't think it will help this
problem.
On Thu, Jan 16,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Erik,
On 1/16/14, 4:37 PM, Erik Engstrom wrote:
> I can get SSL working without JmxRemoteLifecycleListener, and I can
> get JmxRemoteLifecycleListener to work correctly without SSL.
> However if I try to use both I get the following error in
> catal
I can get SSL working without JmxRemoteLifecycleListener, and I can get
JmxRemoteLifecycleListener to work correctly without SSL. However if I try
to use both I get the following error in catalina.out:
failed loading capabilities library -- /usr/lib/libcap.so: cannot open
shared object file: No s
