I'm getting the following error when I tried to open a widows application which was written in PROGRESS 9.1 4GL.
Both Front end and back end written in PROGRESS 9.1 4GL.
Error -
"Insufficient stack space. Increase the -s startup parameter. 31986 bytes are needed, Only 31984 are available. (8035)"
This error is occurring only when loading the application.
I found that this error occurs when application trying to retrieve all the users information and some system information from the database (PROGRESS 9.1).
I can open the application without any problem when I delete some of the system information.
If I re-enter the deleted information them I'm getting the same error again.
Could you please explain how I can fix this issue?
Re: Insufficient stack space. Increase the -s startup parameter. 31986 bytes are need
Have you tried doing what the message says and increasing -s?
Why you get it depends on what your code is doing. Just guessing but I'd start for looking at places where you are appending data to strings. If you are creating strings that are potentially thousands of bytes long that could be your problem.
The startup parameters are case-sensitive so there is a difference between -S and -s. -S is the servicename or portnumber that is used to connect to the database. -s is the stacksize. If the -s is not in the pf file then you can simply add it there.
Re: Insufficient stack space. Increase the -s startup parameter. 31986 bytes are need
As RKR says parameters are case sensitive. The .pf file that you found is likely to be the one that clients use so add "-s 48" to it (-s is measured in kilobytes).
You mentioned that this has been working for years and stopped working recently and that you have a work-around that involves deleting some data. You might want to take a look at the data that is going into this process and determine if, perhaps, an invalid or unreasonably long value has been introduced somewhere. For instance -- perhaps a string that is assumed to be 30 characters long because it has a display format of x(30) has an actual size of 30k due to being imported in a manner that does not enforce the assumed size limit? (Keep in mind that in Progress all fields are variable length -- formats are not constraints on storage -- they are for display purposes.)
Re: Insufficient stack space. Increase the -s startup parameter. 31986 bytes are need
Hi RKR and Tom Bascom
Thanks for the support.
I tried to set -s parameter as you explained. Though I set the -s parameter I'm getting the same error when I tried to open the application. I have restarted database and the app broker after changing the .pf file.
but it didn't solve the issue. .Pf file contents
I tried to set -s parameter as you explained. Though I set the -s parameter I'm getting the same error when I tried to open the application. I have restarted database and the app broker after changing the .pf file.
but it didn't solve the issue. .Pf file contents
You get the same values in the warning or are the values now different ? If the values are higher you can try to increase the value of -s to a much higher number. The maximum size of -s is limited by the available memory on your system. If the values are the same then you will have to look if the application is actually using this pf file. I think however that looking into the data as Tom mentioned might be a better solution.
Quote from the helpfiles.
Progress recomments setting the size of -s to 128
Note: It is recommended that the -s session startup parameter be set to 128. Setting this startup parameter to a smaller value may result in runtime errors in some environments.
I used this file for the startup of the application as well after doing the above changes.
It worked when I used one .pf file without using 2 .pf files.
I wanted to check whether is this issue exists because of there are 2 .pf files.
I simply removed the -s 128 parameter from the file and then restarted my PC.
Then also I didn't get the error.
I'm wondering whether it is because there are 2 .pf files.
Could you please let me know what can be the reasons for this?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
