× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Then that's the source of the problem, those have to all be down before the
server will start again.

Is that instance timing out on a communication wait?


--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Steinmetz, Paul via MIDRANGE-L
Sent: Wednesday, February 13, 2019 12:46 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: ENDTCPSVR SERVER(*HTTP) HTTPSVR(BRCWEBLIVE) issue - instance
jobs not ending

Another point I want to mention, that might be relative.
This HTTP instance starts more QZSRCGI jobs to handle the traffic/volume as
needed.
Currently, 18 jobs running for this instance.
When the ENDTCPSVR SERVER(*HTTP) HTTPSVR(BRCWEBLIVE) is issued, one of the
jobs does end immediately.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of
Jim Oberholtzer
Sent: Wednesday, February 13, 2019 1:24 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: ENDTCPSVR SERVER(*HTTP) HTTPSVR(BRCWEBLIVE) issue - instance
jobs not ending

Good question, I had not thought of a restart, and yes, Paul brought this up
last week I think.


--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Justin
Taylor
Sent: Wednesday, February 13, 2019 12:17 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: ENDTCPSVR SERVER(*HTTP) HTTPSVR(BRCWEBLIVE) issue - instance
jobs not ending

Why the end? Why not:
STRTCPSVR SERVER(*HTTP) RESTART(*HTTP) HTTPSVR(BRCWEBLIVE)


I'm getting a déjà vu feeling from this question. Has it come up before?



-----Original Message-----
From: Steinmetz, Paul via MIDRANGE-L [mailto:midrange-l@xxxxxxxxxxxxxxxxxx]
Sent: Wednesday, February 13, 2019 9:36 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>;
'Web Enabling the IBM i (AS/400 and iSeries)' <web400@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: ENDTCPSVR SERVER(*HTTP) HTTPSVR(BRCWEBLIVE) issue - instance jobs
not ending

I have an AJS scheduled job that recycles an HTTP instance once a week.
Runs every Monday morning, 3:30 AM.

Seq Command

10 ENDTCPSVR SERVER(*HTTP) HTTPSVR(BRCWEBLIVE)
20 DLYJOB DLY(80)
30 STRTCPSVR SERVER(*HTTP) HTTPSVR(BRCWEBLIVE)

Since we upgraded/migrated from P7-8205 to P9-9009, this process is failing.
The ENDTCPSVR for the instance is not ending the instance jobs, immediately.
Most are still running a minute later, so when the STRTCPSVR runs, STRTCPWVR
fails with a TCP7410.

Message . . . . : HTTP Server instance BRCWEBLIVE is already active.

Cause . . . . . : The server is trying to use an instance file that is
already in use.

What's interesting, following the STRTCPSVR, all the instance jobs then do
end immediately, all within one second.
IBM support thinks the STRTCPSVR is calling a background job that forces the
end of the instance jobs.
No proof of this as of yet.

Another variable to this is the length of time the instance jobs are
running.
When I tested the process with the instance running for 24 or 48 hours,
everything works fine.

V7R3, latest cum, 2 months back on groups.
No errors found in any logs.
I have an open PMR with IBM.

Any thoughts from the group.

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.