> we were testing MQ-Listener startup/stop script on a solaris 8 box. > in one occasion, when the script was running the stop procedure it seems > that, somehow, the network port was not closed. > when we started MQ-Listener again, an error message was appeared saying > that the port was being used. > a netstat -a command confirmed that the port was up but bind to > nothing.
How did it confirm it was bound to nothing? What was the state of the port? LISTEN? TIME_WAIT? other? > I wonder if there is a way to close a "zombie" network port without > having to reboot the server. Depends on the state of it. After a close, a socket may remain unavailable for a period of time to capture any retransmissions from a partner of the shutdown process. If this was it, the socket will be in TIME_WAIT. If you cannot wait for this period of time before starting up (I think the default is 4 minutes), having the application open the socket with SO_REUSEADDR can be a solution. If it was in some other state, I'd grab a copy of lsof and have it do a 'lsof -i :<port>', or rummage through the output of 'pfiles <pid>' on every process on the system to see if one of them has an association with the port. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. > _______________________________________________ Solaris-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/solaris-users
