we have a similiar issue on our CI server with the same version of Tomcat and LCDS, we are forced to kill -KILL (-f) the process. as yet we have found no work around.
I don't know if you have tried forcing the kill yet, just going kill pid does not always work for us. ps ax | grep lcds (or lsof -i :2038) shows the port still in use by a java process. if you find a sollution please repost. We are only using data management. On Tue, Jun 30, 2009 at 12:35 PM, Besite - Bart <b...@besite.be> wrote: > > > Hello, > > We are running a Livecycle application that runs in Tomcat 6 environment > (Our livecycle version is 2.6.1). Our application makes use > of Data Management Service and Messaging Service (and so underlying there > are rtmp connections on port 2038 and port 2039) > > We are facing a problem restarting tomcat... The Tomcat log shows the > following error : > > "SocketServer 'my-rtmp-SocketServer' cannot bind to accept client > connections on port '2038' because another process has already bound the > port. Please ensure that multiple " > > This error occurs when clients are still connected to our Application while > restarting Tomcat. > Even if we kill the processes that bind to port 2038, the port is not > released. > > We now have a "workaround" : we stop Tomcat, we wait until the port is > finally given free (sometimes it takes about three minutes) and then > we start Tomcat again... However, this is not an option in our production > environment, because we want to be able to deploy a new version in less than > a minute.. > > I suppose some of you have encountered this problem ? If you have a > solution for this problem,.. please let us know ; > > Thank you ! > Bart Ronsyn > > > > -- j:pn \\no comment
