Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

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

Avatar

Level 2

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

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

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.

View solution in original post

5 Replies

Avatar

Community Advisor

@hptarora 

Yeah, this is a known issue whenever you hit mvn clean install -PautoInstallBundle command. AEM shows the blank screen in edit mode and this mainly because the project bundle goes to the installed state. To overcome this problem just wait for 5-10 min to activate the project bundle from the installed state. If this does not solve the problem then go to http://localhost:4502/system/console/bundles and then project bundle, then action and click on the active button (Play icon). It will restart and activate the project bundle.

Avatar

Community Advisor

Hi @hptarora 

 

Are you running AEM 6.5 on JDK 11? Or this is on JDK 8?

 

If it's on JDK 11

Please update the below line in sling.properties file:

from sling.bootdelegation.sun=sun.*,com.sun.*

to sling.bootdelegation.sun=sun.*,com.sun.*,jdk.internal.reflect,jdk.internal.reflect.*

 

Thanks!

 

Avatar

Community Advisor

Please update the below line in sling.properties file:

from sling.bootdelegation.sun=sun.*,com.sun.*

to sling.bootdelegation.sun=sun.*,com.sun.*,jdk.internal.reflect,jdk.internal.reflect.*

 

Restart the instance once.

Thanks!

Avatar

Correct answer by
Employee Advisor

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.