process is using port 8080

After restart TeamSite and just login and logout still I can see couple of process is using on port 8080.

e.g here just after restart and only one time login and logout
bash-3.00$ lsof | grep 8080
java 1942 iwui 150r VREG 85,211 39853 1278080 /usr/iw-home/ApplicationContainer/server/default/tmp/deploy/tmp4361479137324264845policy.jar
java 1942 iwui 162u IPv4 0x30021978a40 0t0 TCP *:8080 (LISTEN)
java 1942 iwui 257r VREG 85,211 2198080 78496 /usr/iw-home/ApplicationContainer/server/default/deploy/iw-basicreportcenter.war/WEB-INF/lib/hibernate-3.2.1.ga.jar
java 1942 iwui 573w VREG 85,211 331 418080 /usr/iw-home/TeamSite/local/logs/iwui/livesite.preview.log
java 1942 iwui 766u IPv4 0x30063c76f00 0t345 TCP localhost:58709->localhost:8080 (CLOSE_WAIT)
java 1942 iwui 772u IPv4 0x3005bfa2e00 0t344 TCP localhost:58711->localhost:8080 (CLOSE_WAIT)
java 1942 iwui 780u IPv4 0x3003e7ac740 0t334 TCP localhost:58712->localhost:8080 (CLOSE_WAIT)
java 1942 iwui 784u IPv4 0x300100d3900 0t335 TCP localhost:58713->localhost:8080 (CLOSE_WAIT)
java 1942 iwui 794u IPv4 0x30029c35200 0t363 TCP localhost:58714->localhost:8080 (CLOSE_WAIT)
java 1942 iwui 798u IPv4 0x3005c466ac0 0t339 TCP localhost:58716->localhost:8080 (CLOSE_WAIT)
java 1942 iwui 801u IPv4 0x3003edfd600 0t332 TCP localhost:58717->localhost:8080 (CLOSE_WAIT)
java 1942 iwui 804u IPv4 0x30063c5b580 0t335 TCP localhost:58718->localhost:8080 (CLOSE_WAIT)
java 1942 iwui 806u IPv4 0x30063d25200 0t338 TCP localhost:58719->localhost:8080 (CLOSE_WAIT)
java 1942 iwui 810u IPv4 0x300217b9200 0t331 TCP localhost:58721->localhost:8080 (CLOSE_WAIT)
java 1942 iwui 814u IPv4 0x30063c88a00 0t331 TCP localhost:58722->localhost:8080 (CLOSE_WAIT)
java 1942 iwui 817u IPv4 0x3005bf5fcc0 0t335 TCP localhost:58723->localhost:8080 (CLOSE_WAIT)

Due to these process it happend UI not up after restart and log shows an error "java.net.BindException: Address already in use:8080" connection holding to 8080. For this everytime manually kill these process.
arafi
TS:7.21
OS Smiley Frustrated

unOS10

Find more posts tagged with

Comments

Adam Stoller

How are you restarting TeamSite?
When are you running lsof?

Please provide detailed information regarding the above as it may be just a question of impatience on your part...

arafi

Thanks for your quick response

I can run restart server using pbrun please see below
/usr/local/bin/pbrun -b /etc/init.d/iw.server stop
/usr/local/bin/pbrun -b /etc/init.d/iw.server start

After restart I checked log both iwserver and jboss log when system restarted successfully. I login into TeamSite and see its working fine then logout. Only for testing connection still holding on port808 I ran lsof command.

Regards,
Arafi

Adam Stoller

I have never used pbrun to initiate the TeamSite services - and I'm not sure using it is "supported". Who are you expecting to own the TeamSite server processes?

Normally TeamSite is started as root - either directly or via sudo.

If you're running lsof after restarting the service, it makes sense that the ports are in use.

Logging out should not kill the process (and are you talking about logging out of TeamSite, logging out of a client system, or logging out of the server?)

arafi

Thanks ghoti,

We got root access only for installation purpose and after that OS team gave us pbrun access to run our application and command. Basically pbrun command is used to request that an application or command be run in a controlled account.

http://www.unix.com/solaris/161787-what-difference-between-sudo-pbrun.html

I have mentioned logging out from client system. You are right logging out should not kill process I got same thing in development server.
Regards,
arafi

Adam Stoller

Despite what the OP in that referenced thread indicated - I didn't feel that the response they were given was particularly clear about the differences / distinctions between the two programs (pbrun and sudo) - but it seems that pbrun uses some sort of configuration file to determine how it executes the command if the request to run the command is "accepted". That being the case, it seems you'd have to figure out:

/bin/* - and see if you run into the same problem that way. If you don't - then the problem is with pbrun and/or how it has been configured. If the problem persists though - you should probably open a ticket with Support and ask for a LiveMeeting session with a Tech Support Engineer so that they can see exactly what you are doing, how you are doing it, and what all the results are.