S
shaske1
Guest
Although the 4GL client provides various logging options to record the creation and deletion of dynamic objects, we are finding in certain circumstances that it is very difficult to identify which specific client might be responsible for non-reproducible/production-only bugs where a server process runs out of index cursors. We also recognize that static queries may use index cursors and that resource usage is virtually invisible. For those reasons, we would propose a VST field to keep track of the current number of open cursors on _connect. Alternatively this might be a column in an appropriately promon screen. It may also be useful to know the count of index cursors from _server -- though that number could be calculated and so is less necessary. A complete solution might record the high water mark per server to help indicate when certain code might be approaching the limit slowly. We recognize additional overhead may not be worth it. Again, simply having a _connect counter would significantly improve the ability to localize such issues when they occur.
Continue reading...
Continue reading...