Project bundles does not start after couple of builds on local AEM instance

Avatar

Avatar
Boost 1
Level 1
hptarora
Level 1

Like

1 like

Total Posts

20 posts

Correct reply

0 solutions
Top badges earned
Boost 1
Validate 1
View profile

Avatar
Boost 1
Level 1
hptarora
Level 1

Like

1 like

Total Posts

20 posts

Correct reply

0 solutions
Top badges earned
Boost 1
Validate 1
View profile
hptarora
Level 1

28-04-2021

Hi,

 

I have AEM 6.5 local instance. After couple of builds, it stops loading pages in edit mode and after checking bundles I found that project bundle not started and has couple service showing in red.

Sometimes restarting the local AEM instance solves the problem but sometime it just get stuck and I have to re setup local instance.

 

Any help on why it happens and how to solve it.

 

Thanks

View Entire Topic

Avatar

Avatar
Affirm 50
Employee
markus_bulla_adobe
Employee

Likes

152 likes

Total Posts

141 posts

Correct reply

66 solutions
Top badges earned
Affirm 50
Boost 100
Applaud 25
Affirm 25
Boost 50
View profile

Avatar
Affirm 50
Employee
markus_bulla_adobe
Employee

Likes

152 likes

Total Posts

141 posts

Correct reply

66 solutions
Top badges earned
Affirm 50
Boost 100
Applaud 25
Affirm 25
Boost 50
View profile
markus_bulla_adobe
Employee

29-04-2021

Hi @hptarora!

 

If your project bundle is not able to resolve all required dependencies/services it will not be able to start.

Please check the services that are marked in red on the detail view of your bundle and make sure that the according services are available. Once all required dependencies are available, the bundle should be able to start. You may also try to start the bundle manually through Web Console (/system/console/bundles). If it fails (e. g. due to missing dependencies) this will throw an exception, so please check your error.log for the stacktrace.

 

Are these your own, custom services or are these services from the product/framework?
Could you share a screenshot of the missing services and a stacktrace from an unsuccessful attempt to start the bundle?

 

If your bundle/services have mandatory dependencies to other, volatile services this may lead to issues if not done right.