Thanks for the feedback guys. FYI - I didn't see any loops that would cause this on the page.
It just seems odd that we have only been able to generate this error while using tabbed browsing via the "reload all" option? As I mentioned, we can never throw this error under "normal" circumstances while viewing/reviewing sites etc within a single "tab". In addition, the fact that we can "reload/refresh" the errant page (i.e. tab) and get back the same page immediately without the error makes me think there is more to it that we are missing. As much as I hate to take the time to do so, I guess we'll need to swap out the @INCLUDE calls to resolve at this point. Thanks again. John ============================================================== John Hotaling <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] <http://www.AuctionAnything.com> www.AuctionAnything.com AuctionAnything.com, Inc. 509 S. Chickasaw Trail #168 Orlando, FL 32825-7852 Tel: 407.282.8568 Ext 160 Fax: 407.540.9574 ============================================================== _____ From: Robert Shubert [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2008 5:35 PM To: [email protected] Subject: RE: Witango-Talk: Include File Limit Error using Tabbed Browsing The include limit is, I believe, enforced per action. Therefore, if you use a FOR LOOP action to process through a dataset, and then call @INCLUDE only a few times with in the actions in the loop, you should avoid this error. This is a protection put in so that Witango does not exhaust a server's file pointers and crash the file system, which could happen if @INCLUDE were called in an endless loop (@ROWS, @FOR, @WHILE). Robert _____ From: John Hotaling [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2008 3:16 PM To: [email protected] Subject: Witango-Talk: Include File Limit Error using Tabbed Browsing Hello: We've noticed that an "include limit" error occasionally gets generated within our Witango application but have had a hard time tracking it down. Although some of our older code still makes use of include files, we don't have any tafs that should exceed the "call" limit (75 I believe). In fact, we've never thrown this error during our internal testing since moving to V5.5 years ago. Recently, it was brought to our attention that a few errors were being generated using tabbed browsing. The client opens about 10 tabs within Firefox and then uses the "Reload All Tabs" option. We were able to replicate the error (in IE too) but not on a consistent basis (i.e. the same tabs don't always error out and often none error at all). The error generated is the include limit one mentioned above. However, the odd thing is that if the tab that "errors out" is reloaded by itself the page comes back fine. The number of include file calls should be no different so this error is a bit perplexing. The error is: -508. The number of include files so far within the action exceeds the limit. Does anybody have any insight as to why this would happen? I realize the include calls should/could be changed to method calls from a class file but we'd like to avoid that project in the short term if possible while we finish some other items. Any insight/feedback is greatly appreciated as always. Thank you. John ============================================================== John Hotaling [EMAIL PROTECTED] <http://www.AuctionAnything.com> www.AuctionAnything.com AuctionAnything.com, Inc. 509 S. Chickasaw Trail #168 Orlando, FL 32825-7852 Tel: 407.282.8568 Ext 160 Fax: 407.540.9574 ============================================================== ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
