-
Type:
Bug
-
Status: Resolved
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 5.4.2, 5.5
-
Fix Version/s: 5.4.2-HF17, 5.5.0-HF03, 5.6-RC1, 5.6
-
Component/s: Core
As this time, the repository initialization is done by the first opening session in a temporary tx. As described in NXP-8862, this doesn't work.
We need a separated tx, for being sure that concurrent transaction will get the new documents at the time they will be able to open the repository. We can't spawn a new tx as the calling session will not get in return the documents.
As long as we don't support suspend/resume tx, we need to control the repository initialization in the framework bootstrap.
This can be done by introducing a start level onto runtime components, and let the runtime call-backing the component for the application started event in the proper order.
We're thinking about to implement the repository initialization handling into the core repository component.
