I also think this might be related to deleting the bundle cache while the system still runs. If you want a clean startup then you should delete the karaf data dir while the system is stopped. This also deletes the installed karaf features though. So to get your system up automatically you must configure your features as boot features.
If you save all your configs in the etc dir then deleting the data dir will still preserve configuration. Christian Am Mi., 19. Dez. 2018 um 12:44 Uhr schrieb Dheeraj Guntupalli < reindh...@gmail.com>: > Hello All, > > We are using Karaf 4.1.7, aries-jpa 2.7.0, h2 db in our application. We > use multiple persistence units, multiple h2 db files within our > application. We observed that when we have multiple h2 db files, and when > we restart Karaf after deleting the bundle cache a couple or more times we > see this issue "Waiting for JpaTemplate". > > We are able to reproduce this issue frequently, and when this issue > occurs, the JPA Template services are missing in the OSGi service registry. > We feel it is related to bundle/service startup/registration timing. Once > the bundle cache is built and it works, it will also work on subsequent > startups as long as the bundle cache isn’t deleted. > > The persistence bundle creates the JpaTemplate service by providing the > persistence unit, but also consumes it in the DAO services. Possibly the > required waiting time before the input data sources become available can > trigger the issue. > > Has anyone faced this issue earlier, or could give any pointers on how > to resolve this. Please let us know if you need more info. > > > Thanks & regards, > > Dheeraj > -- -- Christian Schneider http://www.liquid-reality.de Computer Scientist http://www.adobe.com
