Re: Ending a node web server from QSH session

Hi Kelly,

I am stretching the definition of "race condition"**. As best I can tell,
what is happening is the socket api has lost tcp/ip connectivity yet is
still trying to listen on the socket and in some fashion goes into an
infinite loop trying to do that listening.

**https://en.wikipedia.org/wiki/Race_condition

I tried NETSTAT, option 3, then option 8. My only option then was 5 to

work with the job. So ending the job this way would be NETSTAT, option 3,
option 8, option 5, option 41.

Another approach that I am using much more these days (because I am in a
PASE shell more than 5250) is to use the ps command. Type this in a shell
to see your jobs:

$ ps -U aaron

... where "aaron" is your IBM i profile. That will display a list of jobs
and their pids (process id) which is relative to a job in WRKACTJOB. You
will see "node" in one of the columns displayed. You can then use the
"kill" command to end that process:

$ kill -9 123456

... where 123456 is the pid obtained from the ps command.


Aaron Bartell
litmis.com - Open Source and IBM i. No Limits.


On Thu, Aug 20, 2015 at 5:43 PM, Kelly Cookson <KCookson@xxxxxxxxxxxx>
wrote:

Aaron and Kevin,

I just did NESTAT, option 3, then option 4. But you are both correct. This
doesn't end the job. It only ends the TCP connection.

I tried NETSTAT, option 3, then option 8. My only option then was 5 to
work with the job. So ending the job this way would be NETSTAT, option 3,
option 8, option 5, option 41.

Aaron,

What does it mean to have a job in a race condition?

Thanks,

Kelly Cookson
IT Project Leader
Dot Foods, Inc.
1.217.773.4486 ext. 12676
kcookson@xxxxxxxxxxxx



-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Aaron
Bartell
Sent: Thursday, August 20, 2015 3:57 PM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] Ending a node web server from QSH session

Note that option 4 on that screen isn't necessarily ending the job and
instead is issuing the ENDTCPCNN command. This doesn't guarantee the job
will end and instead only that the TCP connection is ended. This has
different consequences depending on the language you are using and can
sometimes put the corresponding job into a race condition. Better to end
the job instead of the TCP connection.

I learned the hard way on this one awhile back :-)

Aaron Bartell
litmis.com - Open Source and IBM i. No Limits.


On Thu, Aug 20, 2015 at 3:35 PM, Kelly Cookson <KCookson@xxxxxxxxxxxx>
wrote:

Never mind. I figured out that I could use NETSTAT, option 3 and look
for my port number. Then take option 4 to end the job. That seems to
have worked.

Thanks,

Kelly Cookson
IT Project Leader
Dot Foods, Inc.
1.217.773.4486 ext. 12676
kcookson@xxxxxxxxxxxx

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list To post a message email: WEB400@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.