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
BedrockMission!

Learn More

View all

Sign in to view all badges

AEM 6.3 Configuration bound to wrong bundle launchpad:resources/install/0/org.apache.sling.scripting.core-2.0.44.jar

Avatar

Avatar
Validate 1
Level 2
dbdigital04
Level 2

Likes

4 likes

Total Posts

21 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
dbdigital04
Level 2

Likes

4 likes

Total Posts

21 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
dbdigital04
Level 2

02-06-2018

Hi Community,

Want to share resolution of an issue I was facing with AEM 6.3 regarding wrong bundle binding causing components not working as expected.

Problem - Component configuration bound to launchpad:resources/install/0/org.apache.sling.scripting.core-2.0.44.jar where as per AEM 6.3 it should be unbound. Due to this wrong binding component doesn't get activated with correct OSGI config.

Cause - In our application code which is running fine on AEM 6.1, we were using

Configuration conf = sling.getService(org.osgi.service.cm.ConfigurationAdmin.class).getConfiguration(configName);

Whenever a page was loading, the above code is being executed. Above line return Configuration object which has bundle location set to some default value

launchpad:resources/install/0/org.apache.sling.scripting.core-2.0.44.jar

Fix- Set the bundle location to null in the code as follows. This will fix the problem.

Configuration conf = sling.getService(org.osgi.service.cm.ConfigurationAdmin.class).getConfiguration(configName);

if (null = conf) {

conf.setBundleLocation(null);

}

Cheers,

Deepak

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Level 2
dbdigital04
Level 2

Likes

4 likes

Total Posts

21 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
dbdigital04
Level 2

Likes

4 likes

Total Posts

21 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
dbdigital04
Level 2

02-06-2018

@chinnainturi

Above solution works for us. See if you have the same problem.

Answers (2)

Answers (2)

Avatar

Avatar
Level 1
saurabh_maggo
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile

Avatar
Level 1
saurabh_maggo
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile
saurabh_maggo
Level 1

01-06-2019

dbdigital04​: where exactly did you implemented this change in the service? Also, we are facing this issue for jcrinstall:/apps/install/aem.parent,core-x.y.z.jar

We are using ACS-Commons 'com.adobe.acs.commons.replication.dispatcher.impl.DispatcherFlushRulesImpl' to invalidate cache and this configuration somehow gets binded to an old jar version.

Avatar

Avatar
Validate 1
Level 2
dbdigital04
Level 2

Likes

4 likes

Total Posts

21 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
dbdigital04
Level 2

Likes

4 likes

Total Posts

21 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
dbdigital04
Level 2

03-06-2018

Just a little correct,

Fix- Set the bundle location to null in the code as follows. This will fix the problem.

Configuration conf = sling.getService(org.osgi.service.cm.ConfigurationAdmin.class).getConfiguration(configNam e);

if (null != conf) {

conf.setBundleLocation(null);

}