Article

Appserver becomes unstable after receiving lock table overflow error 915

« Go Back

Information

 
Article Number000011811
EnvironmentProgress 9.1D
Progress 9.1B
Progress 9.1C
OpenEdge 10.0x
All Supported Operating Systems
Question/Problem Description
Appserver becomes unstable after receiving lock table overflow error 915
Lock table overflow, increase -L on server (915)
SYSTEM ERROR: ixfil called during resyncing (1062)
SYSTEM ERROR: rmmak called during resyncing (1068)
Begin transaction backout. (2252)
Transaction backout completed. (2253)
AppServer process dies with error 1062 reported in the server log file
AppServer process crashes
Stack trace reads:

RaiseException
utcore
drexit
msgout
msgnCB
msgCB
dsmFatalMsgnCallBack
cxCreateIndex
dsmObjectCreate
proixfc
fdixfilc
scget_ttblfild
rnreloc
rnproc_entry
rninterpret
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement NumberOE00095300
Cause
When an application causes a lock table overflow, the AppServer improperly handled the condition and became unstable as a result.
Resolution
Upgrade to Progress 9.1E or later or OpenEdge 10.1A or later. The AppServer will return to being useful again for the next call, once the client in question is forcibly disconnected from the AppServer session. This is because locktable overflow is considered a serious application error.

A temporary workaround is to correct the coding errors reported prior to the error 1062 and in case error 915 is reported as well, to increase the -L database startup parameter.
Workaround
Notes
It is possible to temporarily workaround a lock table overflow error by increasing the -L parameter. However, getting such an error is considered to be a serious application design (i.e. transaction scoping) error. To avoid this happening in the first instance, investigate downscoping transactions that the identified user was running, so that -L on the lock table is not exceeded past what would be a reasonable -L setting for the particular application's design.
Raising the STOP condition while manipulating the temp-table's buffer(s) causes the AppServer to crash. The STOP condition could be triggered by reaching the Lock Table size, or by coding errors.
Attachment 
Last Modified Date9/13/2015 5:41 AM


Feedback
 
Did this article resolve your question/issue?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025