HTTP DEQW status -- WEB400

× 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.

Subject: [WEB400] HTTP DEQW status
From: "Mark Villa" <markvilla@xxxxxxxxxxx>
Date: Thu, 23 Jan 2003 23:31:32 -0500
Importance: Normal
List-archive: <http://archive.midrange.com/web400>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: Web Enabling the AS400 / iSeries <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo.cgi/web400>,<mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo.cgi/web400>,<mailto:web400-request@midrange.com?subject=unsubscribe>

When I see HTTP jobs (QZHBHJOB) go into a DEQW status, while I am testing
(and the program bombs)
I am thinking that HTTP thread will never do any more work or get cleaned
up.

Assuming this can happen in normal operations, do you guys kill these jobs
by monitoring for them?
Or has anyone address it properly, using a coding technique perhaps?

I have seen this occur for several releases now and since I do not have a
high volume site to test with I wanted to ask.

(my programs bomb a lot)


Mark Villa in Charleston SC

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: HTTP DEQW status , Nathan M. Andelin

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.