Resolution:
PROBLEM:
-------------

If your application acquires ENVIRONMENT Scope storage in a Peer Server session (e.g. via Trigger Rule on a Remote Table), this storage is never released. Additionally, since references to this storage in @MAP are removed, the acquired storage is rendered non-addressable which may cause your application to acquire a new piece of storage on each iteration. Depending on the size of storage thus acquired and the usage frequency of this application, the Peer Sever Execution Environment (EE) Address Space may eventually suffer a Short-on-Storage condition.


AFFECTED RELEASES:
----------------------------

TIBCO Object Service Broker 5.0 and 5.2


SOLUTION:
--------------

Defect Issue JIRA-1459 has been raised and the problem will be resolved via a future Hot Fix.

Until a fix is available, if you must use Environment-Scope storage in Peer Server sessions, you may want to consider 'remembering' the address of the acquired ENVIRONMENT-Scope storage via an EES Table parameterized by LTERM. This will allow you to reuse the storage that you have already acquired rather than acquiring a new block on every iteration of your Peer Server application.