Qiang has a very good description about tests. I am exploring how unsyncPC can
work in cluster env. Especially, how to make joinTx in test2 (instance2) to take care the data in test1 (instance1)?
On 4/17/2013 7:39 PM, Qiang Liu wrote:
> Hi Mitesh
> Ethan and I have discussed this test cases together before, and I can give a brief description for it:
> 1. The first request is sent to Instance 1, the EJB tries to persist Employee 1 and Employee 2 with not joining transaction, and then flush PC. An expected exception is caught.
> 2. The second request is sent to Instance 2, the EJB tries to persist Employee 3 and Emploee4 after join transaction. Even the flush is not invoked, the entities will be persisted to DB when the transaction is committed. But, since this is difference instance from Step 1, Employee 1 and Employee 2 will not be persisted to DB in this step.
> 3. The third request is sent to Instance 1, the EBJ tries to persist Employee 5 and Employee 6 without joining transaction, as it doesn't invoke the flush method, all the entities will not be persisted to DB. But, here the test case expects Employee 1 involved in PC in Step 1 will be persisted to DB in Step 2. Since the EM and PC will not be synced between instances in cluster env, so the test3 will not pass.