The solutions described in
Solutions for a single listener/AOR and
Solutions for a multi-region EJB server are
not the only possibilities. Another approach, for example, is to:
- Use non-default TRANIDs for the request processors associated with the
beans to be updated. (In other words, segregate your enterprise beans by CorbaServer
and transaction ID in the way previously suggested.)
- Disable the request processor transactions, or put the transactions into
a transaction class and reduce the TCLASS limit to zero.
- When all instances of the beans have been destroyed or passivated, install
the updated versions of the deployed JAR files in one of the ways described
for the other solutions.