On Dec 21, 2007 11:24 AM, Gary Baluha <gumby3203 at gmail.com> wrote:
I'm having a little problem converting some Sitescope web page checks into Hobbit content checks. In particular, I have several URLs of the form:
https://some.machine.name:9212/monitoring/MonitorControlServlet?monitorName=... (names changed to protect the innocent)
The problem is, I can go to that URL manually, and it will show up fine...after about 20 seconds or so. The URL is slow to respond, because it is running a back-end check, and that check simply takes a while to complete. The result is that Hobbit is coming back saying that the website failed to respond after 10.x seconds, even though it would be fine if I waited another 10 seconds or so.
I would like to be able to increase the timeout, but only for URLs similar to above that are expected to take a while to respond. I don't want to increase this timeout across the board, since only a subset of all of the URL monitoring I am doing take so long to respond. Is there any way to do this?
Also on a related, though different note, are a few other tests that I can't get the "content" column to show up. These URLs are of the form:
https://username:password at some.machine.name:9212/monitoring/MonitorControlServlet?monitorName=com.company.common.util.monitoring.URLMonitor&url=https://some.machine.name:9212/LBListener/MessageReceiver&fullDisplay=true&i... <request:AccountInfoRQ xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance" xmlns:request=" com.company.accountrequest"><AccountInfo AccountCardNumber="4264292967999999" PortfolioID="177" SecurityInfo="true"/></request:AccountInfoRQ> (names changed to protect the innocent)
The http check is working fine, but it seems like hobbit is ignoring the fact that I have it set up as a content check. The bb-hosts line for this test looks like: 1.2.3.4 test-name # DESC:"Test description" noconn nosslcert cont;<URL above>;Success badhttp:1:2:3
I also just noticed that for these tests, bbtest is complaining "content-check, but no content-data in <bb-hosts line above>". However, if I manually go to the URL in a browser, it does indeed return "content-data", and it returns in a timely fashion (about 2 or 3 seconds). Any ideas?