0

have you ever got the situation some websphere used port occupied even after that websphere process has been stopped or killed? as for such issue, how to fix it? well, i know it can be gone after server reboot. but you know, it's not the best one and we can't do it often since it's SERVER stuff.

thanks in advance

wing2ofsky
  • 926
  • 4
  • 27
  • 48
  • oh,that's my fault. it's ok now! Please help me out, master. @rkosegi – wing2ofsky Jun 04 '12 at 03:24
  • I usually "kill -9" any Java processes over 300MB when I'm looking to do that... – Jonathan W Jun 04 '12 at 21:05
  • Your issue isn't WebSphere related. BTW, a solution to your real problem was already addressed [here](http://stackoverflow.com/questions/9168392/shell-script-to-kill-the-process-listening-on-port-3000) – MrJames Jun 04 '12 at 23:13

1 Answers1

2

Are you certain it's WebSphere holding the port? If you've stopped all the WebSphere processes, especially if you've stopped them normally, I can't imagine that it is still holding the port.

On AIX, you can see which process is holding the port with the combination of netstat and rmsock described here (or if you have lsof installed, that's even easier.)

dbreaux
  • 4,982
  • 1
  • 25
  • 64
  • yeah, i'm pretty much sure it's the Websphere holding the port since the port is 9080 used as WC_Default by Websphere. Yes, it's very weird indeed. the process gone but the port still be holding there. – wing2ofsky Jun 05 '12 at 00:27
  • Even if you're pretty sure, you should use the steps describe to be certain. Then if we know it's WebSphere, we can proceed from there. – dbreaux Jun 05 '12 at 13:01