"Repeatable Read" for drools-jpa-persistence

[totempole]

An application-scoped entitymanager (singleton) is shared by all clients in drools-jpa-persistence. When the entitymanager joins a JTA transaction in one thread, before that transaction ends, it may be invoked on entityManager.joinTransaction() in another thread for a different JTA transaction. Assuming the same knowledge session instance is updated in two transactions. Is "Repeatable Read" applied to the knowledge session or entitymanager? If not, the knowledge session would have blended changes from different transactions. It is still an issue even the two transactions update two distinct knowledge sessions. Can anybody confirm the behavior of drools under this circumstance?

[totempole]

Any thoughts？