Actually, it looks like it's not so much an issue with the max length for the URL, as it is for *any* line in bb-hosts. I started writing an extension script to do the content checking, and even that is getting the URL truncated. The problem appears that everything past 464 characters from the "#" in the bb-hosts file for any host is discarded.
As far as I can tell, there is no environment variable or setting that I can change in the config file to change this. Anyone else have any ideas?
On Dec 24, 2007 11:41 PM, Gary Baluha <gumby3203 at gmail.com> wrote:
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?
I apologize if this is a duplicate email, but it looks like from my end that something didn't post correctly...
Anyway, I figured out why I'm getting this error. From the bb-network.logfile: 2007-12-24 23:14:28 content-check, but no content-data in 'cont;https://USERNAME:PASSWORD at HOSTNAME:9212/monitoring/MonitorControlServlet?monitorName=com.company.common.util.monitoring.URLMonitor&url=https://HOSTNAME:9212/LBListener/MessageReceiver&fullDisplay=true&isPost=tru...
<https://USERNAME:PASSWORD at hostname:9212/monitoring/MonitorControlServlet?monitorName=com.company.common.util.monitoring.URLMonitor&url=https://HOSTNAME:9212/LBListener/MessageReceiver&fullDisplay=true&isPost=true&TLSAction=hotelearningssummaryextract&TLSService=HotelEarnings&payload=><TLSBatchRQ><Parameters><Parameter'
So it appears the full URL from the bb-hosts file is getting truncated. The limit looks to be around 370 (or at least more than 256), and I can't find anywhere to override this, so it appears to be hard-coded without looking through the actual code.