I've been trying to get OI to read a pdf and send it to the browser it works fine for files under 2mb for sure but large file like 14mb don't work the browser timeouts i have sent a log file to tell me how long the process takes to read the file only takes a 1-2 seconds. I have tried doing a OSFBread and reading the document in segments takes longer to process the routine but still not longer the 300 seconds. also i have found a topic here to change the wrapper.conf file buffer to a bigger value the 64 to I have changed that to. I'm just wondering if anyone has this issue and found a solution.

Hi, Jensen. If you run the EngineServer from the command line (not as a service), do you see the response coming back from the EngineServer properly? Just making sure the problem is somewhere in the EngineServer-]OECGI2-]web server section of the process, rather than the OEngine-]EngineServer portion of the process.

If the problem was with the 'wrapper' setting, then you'd see the problem too when running from the command line (java will abort, if running out of memory is the issue).

Is it safe to assume you're running the latest OECGI2.EXE (I believe that I sent one to Bob Carten to send to you in June…?)

Check out articles like:

http://www.bigresource.com/ASP-How-to-Extend-the-Session-TimeOut-9S0UxYdy.html

Or else buy S/Web from Sprezzatura - their config utility does it for you.

IIS has some config settings to enable Windows web servers to handle such code.

Might I say that once you get to 14mb you're probably best to carve up the data further, by state or by some sort of alphabetic index (A-Z) subcategories or similar.

If someone gave you 14MB of stuff to read you'd tell them to shove it.

Same rule applies for web pages.

I gave up on this a year ago. My solution is to copy the large pdf to a public folder and have the browser redirect to download the file.

Daily I clean up the public folder.

Dave

You could also use the FTP functionality which is feature of OI to place the large file on a third party website, then use OECGI2 to provide a link or an IFRAME or FRAME to the large file.

Begin processing time: 8/15/2009 16:32:39

RUN RUN_OECGI_REQUEST 'm=manuals&file_id=1089959068

Stop processing time: 8/15/2009 16:39:07

Execution time: 387375 milliseconds.

Execution status: successful.

I just started the log on a oegine and ran the request as you can see it said the execution was successful but took 387 seconds which is weird since to run the stored proc it only took 1-2 seconds so I'm more thinking when the response goes through other routines like INET_FINALIZE there is so much data it takes a long time to pass it because i did a OSBread and passed the data to a log to see if it was taking to long to just read the file. when opening the log file in the editor it took like a couple minutes though.

I tried the command line everything is fine to so its not a ram issue I didn't think it was since it didn't change anything when i changed the wrapper.conf file

also Bryan would you know why the openEngine take so long to shut down we have put the max to 5 and timeout of 0 but the openEngine will stay open in idle status for way longer then a minute startup and shutdown flags are at 1

Oops I lied. I just look at the wrapper.log file it did say procedure aborted out of memory heap.

anyway i found out how to load large files now just sometimes it will work and sometimes it won't since OI doesn't really pass all the needed information from a request like the HTTP_RANGE. I created a common to store ranges for me. if the oengine that process the first request processes the next request it works fine but sometimes the request will be used by another oengine and i will have failure.

Hi, Jensen. Glad to see (in your next posting) that you solved the problem you were having with the large file.

If you're discussing the 'idle timeout' setting in the eserver.cfg file, I believe a timeout of "0" says "don't ever shut down the engines that have been cached."

Hope that helps,

- Bryan Shumsky

Revelation Software

View this thread on the forum...