If your bean uses bean-to-bean communication with the same transaction
id within the same AOR, setting MAXACTIVE to one will result in the communication
not working. This is because the execution of the second transaction will
be suspended waiting for a slot in which to execute, and the original bean
will then experience a “timeout” condition. The way to avoid this
is to take one of the following actions:
- Use REQUESTMODELs to specify a unique transaction id for each bean.
- Allow all create methods to use CIRP ( the default transaction id), and
use REQUESTMODELs to define a unique transaction id for each set of business
methods.
Note: When a bean is running inside a request processor, CICS® will only utilize
requestmodels (and therefore start a new CICS transaction under the new transaction
ID) if a remote method call made by that bean cannot be satisfied in the current
request processor. A method call cannot be satisfied locally in the current
request processor if:
- The transaction attributes of the method being called require a different
transaction context
- The bean being called is in a different CorbaServer