Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Hanging on DLL call
Message
From
21/06/2001 02:29:00
 
General information
Forum:
Visual FoxPro
Category:
West Wind Web Connection
Miscellaneous
Thread ID:
00521725
Message ID:
00521767
Views:
26
G'Day mate,
It's a piece of cake to right the app actually and send emails. But I'll look at it of course. But the Wininet DLL call is hanging every attached app if IIS is hung or screwed in a special way, which I don't think you see every day. (I believe it's being caused by a related email problem on the network with huge numbers of emails being thrown around - some 30,000/hour)
So the WW Web Moniter would probably suffer the same fate since Rick would still be using the httpgetex I bet.
Also we're not using WWC on the site, we have our own scripters running over x-works, soon to be Foxisapi (we hope) XWorks works great and is fast but the author has taken a dive! So the move to FoxISAPI actually looks fairly simple now that MS have built a decent one (or maybe it's the Rick Strahl version :-)
So do you know if WW Web Monitor will monitor any page request?
David

>David,
>
>Have you had a look at Rick's West Wind Web Monitor. It's a neat little app that does what you're after. It can monitor as many sites as you like, check for a particluar string in the HTML returned etc, and when it detects a site that's down, it can do any or all of:
>
  • Send an e-mail
    >
  • Call a web address (perhaps a reset page)
    >
  • Kick off an exe on the monitoring machine
    >We use it quite a bit to monitor a WWC site at 90 second intervals and it works like a charm.
    >
    >Cheers,
    >
    >Andrew
    >
    >>We had a period yesterday where a client's MIIS was misbehaving badly because of a mail server load and I was writing an app to detect when our VFP generated site was down.
    >>
    >>So the technique I wanted to use was simply to request a dynamic page using wwipstuff.httpget() and then comparing the content with what it should be.
    >>
    >>However when the remote IIS was misbehaving the following code line, in wwipstuff.httpgetex(), causes VFP to hang indefinitely.
    >>
    lnRetval=HttpSendRequest(hHTTPResult,;
    >>   tcHeaders,LEN(tcHeaders),;
    >>   lcPostBuffer,tnPostSize)
    >>
    >>SO even though at this stage we had a valid "connect", the httpsendrequest failed and never timed out. (Timeout is set to 5 seconds.)
    >>
    >>So this means my app is useless for detecting such an outage.
    >>
    >>Anyone know an answer or can suggest another method?
  • Previous
    Next
    Reply
    Map
    View

    Click here to load this message in the networking platform