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.