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 <esengst...@gmail.com> 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 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, 2014 at 3:45 PM, Christopher Schultz < > ch...@christopherschultz.net> wrote: > >> -----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 >> > catalina.out: >> > >> > failed loading capabilities library -- /usr/lib/libcap.so: cannot >> > open shared object file: No such file or directory. Jan 16, 2014 >> > 4:34:20 PM org.apache.catalina.mbeans.JmxRemoteLifecycleListener >> > createServer SEVERE: The JMX connector server could not be created >> > or failed to start for the Platform server java.io.IOException: >> > Cannot bind to URL [rmi://localhost:1900/jmxrmi]: >> > javax.naming.CommunicationException [Root exception is >> > java.rmi.ConnectIOException: non-JRMP server at remote endpoint] >> > at >> > javax.management.remote.rmi.RMIConnectorServer.newIOException(Unknown >> > >> > >> Source) >> > at javax.management.remote.rmi.RMIConnectorServer.start(Unknown >> > Source) at >> > >> org.apache.catalina.mbeans.JmxRemoteLifecycleListener.createServer(JmxRemoteLifecycleListener.java:304) >> > >> > >> at >> > >> org.apache.catalina.mbeans.JmxRemoteLifecycleListener.lifecycleEvent(JmxRemoteLifecycleListener.java:258) >> > >> > >> at >> > >> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) >> > >> > >> at >> > >> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) >> > >> > >> at >> > >> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402) >> > >> > >> at >> > org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:347) >> > >> > >> at >> > >> org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:725) >> > >> > >> at >> > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) >> > >> > >> at org.apache.catalina.startup.Catalina.start(Catalina.java:691) >> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at >> > sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at >> > java.lang.reflect.Method.invoke(Unknown Source) at >> > org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:322) at >> > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at >> > sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at >> > java.lang.reflect.Method.invoke(Unknown Source) at >> > >> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243) >> > >> > >> Caused by: javax.naming.CommunicationException [Root exception is >> > java.rmi.ConnectIOException: non-JRMP server at remote endpoint] at >> > com.sun.jndi.rmi.registry.RegistryContext.bind(Unknown Source) at >> > com.sun.jndi.toolkit.url.GenericURLContext.bind(Unknown Source) at >> > javax.naming.InitialContext.bind(Unknown Source) at >> > javax.management.remote.rmi.RMIConnectorServer.bind(Unknown >> > Source) ... 20 more Caused by: java.rmi.ConnectIOException: >> > non-JRMP server at remote endpoint at >> > sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source) >> > at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source) >> > at sun.rmi.server.UnicastRef.newCall(Unknown Source) at >> > sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source) ... 24 >> > more >> > >> > the ports still get opened but I can not connect via jconsole using >> > ssl or not. If I set com.sun.management.jmxremote.ssl=true I can >> > connect properly without ssl. >> > >> > The relevant configuration from server.xml: >> > >> > <Listener >> > className="org.apache.catalina.mbeans.JmxRemoteLifecycleListener" >> > rmiRegistryPortPlatform="1900" rmiServerPortPlatform="11900" /> >> > >> > and java properties: >> > >> > -Djavax.net.ssl.keyStore=$KEYSTORE >> > -Djavax.net.ssl.keyStorePassword=$KEY_PASS >> > -Dcom.sun.management.jmxremote.ssl.need.client.auth=true >> > -Djavax.net.ssl.trustStore=$TRUSTSTORE >> > -Djavax.net.ssl.trustStorePassword=$TRUST_PASS >> > -Dcom.sun.management.jmxremote.registry.ssl=true >> > -Dcom.sun.management.jmxremote >> > -Dcom.sun.management.jmxremote.authenticate=false >> > -Djava.rmi.server.hostname=$HOST_IP >> > -Dcom.sun.management.jmxremote.ssl=true >> > >> > Is it supported to use these together? If so what am I doing >> > wrong? >> >> Why is libcap.so (not) being loaded? >> >> - -chris >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1 >> Comment: GPGTools - http://gpgtools.org >> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ >> >> iQIcBAEBCAAGBQJS2FLjAAoJEBzwKT+lPKRYs5oQAIjwUrNfiSKII5mto5mRFhmf >> g7qMBbZAkVBPFAR1AAyrulNRHDk4UXwiXF16I4zWfmqEvsGa0g63Swdcp3SdydbM >> 9pruhSnUxoD/V9n6WgiwPNKCg4mkJcKBTTxMDaTXbyR+BA604e6ZFFfNo/Pxgb/l >> R1mo10H6ucCglRTftEN0zGT9D6ust9TCeFpVZdtnMUWKsz1NZk5ipKegSwcucktr >> AuYuV8AEuLFTH9Cc6OPjAVCDPWrmA3jhAImbX1je4dpqM9GgoYmcSemQkx7fSAdT >> nvfVRTpc3s4N/gsir3wWQvttjGea6e+21lkEm1KgnLohsFXV/omb61lkTnxVktDz >> ejMuizVJ0fYCSJhKdW2GtubDAfJclP4GTxFFsEZSLroaNbV5BX6XqiiYdEJFM5qV >> /BszNs9CMVFLtQCL8t3nkZBtYLf0r3T+Y3bpf+cOUvq1ftCmRoG5/9qrqmoAd//C >> RcfrQ3uKRmLZy4fbB3gF1vQX5inJ6UM99WqKLUbb5jnsTGI6NWHVnmvz8AbjvapE >> WYSiwYz1Fe6vqfiIVcPpMuPGadTex4wdAy2Q9Se3j3ZYFsyHr43xL44Y7XDpzWKO >> egxJG3cMTapWC4F3+g75x674I0xFk4i1x46Ug870oowZxy8lEIxpbuTRAV39Jb66 >> BsB2/eQhGTclw4WVXYfi >> =6wLD >> -----END PGP SIGNATURE----- >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> >
