Are there any limit to the file size when users download files with oecgi2.exe ?

/Anders

Hi Anders

I don't know of a size limit.

If you are using OECGI2.exe to export binary data you will want to set your own content-type and content-length headers and set request to true ( See Inet_Equates)

There is an OECGI2.exe dated November 2007 which can cause grief with downloaded files. OECGI2.exe versions dated April 2008 or better should work for you. I believe 8.07 has a recent version.

- Bob

- Bob

When I had trouble with timeouts for downloads I ended up sending a "redirect" web page to start and used the browser's download.

Since I needed some security I encoded the filename, copied it (a pdf) to a public folder, then every day day I delete the previous day's files.

Dave

Hi, Anders. There's no file size limit in OECGI2 per se, but there have been reports of the underlying EngineServer running out of memory when attempting to download large (multi-MB) files from OI to the browser.

You can increase the "heap memory" that the EngineServer uses to remedy this problem.

If you are manually invoking the EngineServer on the command line (with the command "java -jar oesocketserver.jar"), you can add a parameter to control the maximum heap size. This parameter is "-Xmx", and is immediately followed by the desired heap size. So, for example, to increase the heap to 256MB, the option to specify would be "-Xmx256m", and the entire command line would be "java -Xmx256m -jar oesocketserver.jar"

If you are using the EngineServer as a service, you must modify the configuration file that the service uses to increase the heap size. In your OI directory, you should have an OESERVER subdirectory, with a CONF subdirectory under it. Edit the file "wrapper.conf" with notepad (or your favourite editor) and look for the line that currently reads:

#wrapper.java.maxmemory=64

Change that line to indicate the maximum amount of memory you wish the heap to use, and remove the "#" (currently commenting out the line), so that the line now reads:

wrapper.java.maxmemory=256

for example. Stop and restart the EngineServer service in your Windows Services, and the new heap size should take effect.

I believe any problems you might have with downloading large attachments should be resolved.

Hope that helps,

- Bryan Shumsky

Revelation Software

Hi Bob,

Its the version from april 2008.

Here is a part of the code:

Extension=FullFileName-1, "B."

• http://www.webmaster-toolkit.com/mime-types.shtml

Begin Case

	Case Extension _eqc "PDF"

		ContentType=application/pdf"

	Case Extension _eqc "XLS"

		ContentType=application/ms-excel"

	Case Extension _eqc "DOC"

		ContentType=application/msword"

	Case extension1, 3 _eqc 'htm'

		osread binary_Data from FullFileName else

                      binary_data='

		Return Binary_Data

	case extension _eqc 'bmp'

		contenttype=image/bmp"

End Case

osread binary_Data from FullFileName else binary_data='

content_length=len(binary_data)

If content_length=0 then

	httprequest=false$

End else

	image_type=jpeg'

	result='

	result := "Content-Type: " : ContentType : lf$

	result := "Content-Length: ": content_length: lf$

	result := lf$

	result := binary_Data

• Flag response as Binary data

	httprequest=true$

end

Return Result

It working perfect (thanks's Andrew McA), so I look at the timeout, because some of my clients can't download large pdf files.

Thanks

/Anders

Thank's Bryan,

/Anders

View this thread on the Works forum...