Version 3.0 Beta Test FeedBack

More results....

There are more exceptions in the PB log than are in the event log.
 
According to the windows event log, all exceptions happen at: http://www.warbeats.com/Default.aspx?tabid=57 which is a repository module.

The following searchfor values are displayed in the error log on the OOM errors:

SearchFor: href=['"]?mailto:(\w+[a-zA-Z0-9.\-_]*)@(\w+)\.(\w+)['"]?
SearchFor: (]+__VIEWSTATE[^>]+>)(.*?)</form>
SearchFor:
SearchFor: <form>

The latter two are mine.

Could it be that PB is trying to replace the file content that is being sent?

See the attached log file for the full details.

John,

I think this is figured out now.

My rule to prevent PB from doing anything on repository pages was the following:

pattern="tabid[/|=]⏅|58|36|86|91][/]"

Which seemed to work fine in PB2 (or at least I didn't have problems downloading or OOM)

In PB3 I was getting the OOM and also somewhat random reports of the files not downloading at all (0 byte files). Checking the latter problem, I could always download fine. But then, someone gave me a link, or rather a PERMALINK to a file they could not download. An lo and behold, neither could I.

Well I happend to have the TaskMan on one monitor while I attempted to download this file and I saw the memory rising rapidly immediately after I clicked the download link. And it rose and rose until BAM! OOM

Tried it again, same result. When I download from the file listing page (not the permalink) it worked fine.

Long story short, one of my exclude rules wasn't working - this is what we saw in the log - but only on the PERMALINK pages.

The permalink pages look like this:  http://www.warbeats.com/Default.aspx?tabid=58&id=567

So I look at the rule (see above) a little closer and realized it expected a trailing / which wasn't there. So I removed the trailing slash and everything appears to now be 100% normal.

Thanks for sticking with me throughout this issue.