D
dbeavon
Guest
I agree that trimming is remote ABL brokers is important. In some respects, the brokers act like glorified "shared memory" ABL sessions. The big difference is that they do time-slicing* to handle proxied requests on behalf of a "client/server" ABL session. (*in OE 12 it will change to multi-threading) By trimming brokers (eg. after an inactivity period, or after a specified lifetime period has elapsed) it clears out any latent cruft that may have accumulated in the broker process over time. We have noticed issues that would have been mitigated by trimming ABL brokers regularly. For example this bug ( knowledgebase.progress.com/.../raw-transfer-statement-failed-due-to-stale-schema-for-table-abc ) only takes place because of ABL remote brokers that refuse to recognize an "online" schema change. Every other type of OpenEdge client picks up the schema changes, but not the pre-existing ABL brokers for some reason. The bug is scheduled to be fixed one day, but it has been about a year since I reported it. Trimming ABL brokers after a specified lifetime would be very handy. After that lifetime expired, the broker could be flagged, and any new clients would be directed to go to another one.
Continue reading...
Continue reading...