System Exceptions

System exceptions are error conditions that are raised automatically by the system; for example, a lock exception or an integrity violation.

A 1092 (Object not available) exception may be raised during an exception handling operation if you are trying to access the object that caused the exception and that object is not yet read into cache.

If this exception is raised, fix your application code so that objects that cause an exception during their access (usually lock operations) are not referenced.

There is more sensitivity in a "dirty" read of uncommitted changes to a persistent object when both processes run in the same node, because dirty reads are detected inside the common node while dirty reads across nodes are detected on the server node. Processes that share the same node are therefore likely to get more dirty read exceptions. Use lock exception handling in your code to deal with dirty read situations that may occur.

For details about sharing uncommitted persistent objects, see "Sharing Uncommitted Persistent Objects", in Chapter 1. For details about dirty reads, see "JADE Object Manager Distributed Processing", in Chapter 1 of the JADE Object Manager Guide.