When a clustered application has many clones at runtime, every clone has an instance of the startup beans. The startup service invokes the startup bean instances of every clone. The startup beans instances of one clone are not aware of the instances of other clones, and do not synchronize the actions with instances of other clones. Therefore, you should take appropriate actions to avoid dead locks or data inconsistencies.