Assert Failure in IDS/UDO workaround

In case anyone else out there is using the web datablade with IDS/UDO and experiencing frequent Assert Failures (memory errors) in the online.log, we've found a problem and a work around. PROBLEM: The webexplode function was causing several assert failures (50+) a day and Informix tech support could not (and still hasn't) helped us solve the problem. Eventually these errors would cause the database to hang and we would have to recycle it. Soon we found out (by accident) that hitting STOP on the browser when a [large] page is being returned from webexplode can cause the assert failures. Why? A new variable (didn't exist in Illustra) now exists MI_WEBKEEPALIVE. Every MI_WEBKEEPALIVE seconds, Webdriver checks to if the browser is still connected. If it isn't (i.e. STOP/CANCEL is pressed), the query is interupted. Long story short - If the MI_WEBKEEPALIVE number is small (like 5 seconds) you can cause these errors consistently by pressing STOP on your browser. I like the idea of the MI_WEBKEEPALIV variable, but it just doesn't work. People hit STOP a lot - if this feature worked, it would save a lot of processing time. I've been trying to get this message to tech support for couple of weeks and they aren't responding. WORKAROUND: I raised the MI_WEBKEEPALIVE number to be greater than the MI_QRYTIMEOUT number and the assert failures essentially dissapeared. Hopefully, this will stop someone else from suffering. Eric Weaver, InteliHealth