Okay, I think I see what happened. It has to do with the fact that I'm running my node web server in an interactive QSH session.
When everything is running, there are three jobs active:
1. My interactive 5250 session.
2. The qshell interpreter (QZSHSH)
3. A job that appears to be the node program (QP0ZSPWT).
If I use F3 to exit out of the interactive qshell session, my interactive 5250 session remains active, but the QZSHSH job and the QP0ZSPWT jobs are no longer active.
However, the NETSTAT command shows that my TCP connection is still listening. NETSTAT option 3, then option 8 shows no jobs. The result is that, when I point my browser to the URL, it just spins and spins forever. That would make sense. The browser found a listener, but the listener has no active jobs to return a response.
In this particular circumstance, I'm using NETSTAT, option 3, then option 4 to end the TCP connection. There are no jobs to end.
Thanks for the insights and tips. I'm a complete beginner at this and have a lot to learn.
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 Kelly Cookson
Sent: Thursday, August 20, 2015 5:44 PM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] Ending a node web server from QSH session
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.
midrange.com
