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

After Inplace upgrade of AEM from 6.3 to 6.5, Components are in a satisfied state

Avatar

Avatar
Validate 1
Level 1
Rohitash_Singh_
Level 1

Like

1 like

Total Posts

4 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Boost 1
View profile

Avatar
Validate 1
Level 1
Rohitash_Singh_
Level 1

Like

1 like

Total Posts

4 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Boost 1
View profile
Rohitash_Singh_
Level 1

13-11-2019

After Inplace upgrade of AEM from 6.3 to 6.5, Servlets as a component are in satisfied state in Felix console. Below is the error in logs.

13.11.2019 15:25:29.241 *ERROR* [FelixDispatchQueue] org.apache.sling.servlets.resolver FrameworkEvent ERROR (org.osgi.framework.ServiceException: Service factory returned null. (Component: com.isobar.sony.rewards.servlet.UniqueCodeCheckNameServlet (3755)))

org.osgi.framework.ServiceException: Service factory returned null. (Component: com.isobar.sony.rewards.servlet.UniqueCodeCheckNameServlet (3755))

at org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:381)

at org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:248)

at org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:350)

at org.apache.felix.framework.Felix.getService(Felix.java:3954)

at org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:450)

at org.apache.felix.scr.impl.manager.SingleRefPair.getServiceObject(SingleRefPair.java:86) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.inject.BindParameters.getServiceObject(BindParameters.java:47) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.inject.methods.BindMethod.getServiceObject(BindMethod.java:664) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.DependencyManager.getServiceObject(DependencyManager.java:2308) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.DependencyManager.doInvokeBindMethod(DependencyManager.java:1805) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.DependencyManager.invokeBindMethod(DependencyManager.java:1788) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.SingleComponentManager.invokeBindMethod(SingleComponentManager.java:435) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:325) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:294) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1216) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1137) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.trackAdding(ServiceTracker.java:944) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.track(ServiceTracker.java:880) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:1168) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.BundleComponentActivator$ListenerInfo.serviceChanged(BundleComponentActivator.java:125) [org.apache.felix.scr:2.1.16]

at org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)

at org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)

at org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)

at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4833)

at org.apache.felix.framework.Felix.registerService(Felix.java:3804)

at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:328)

at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:906) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:892) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:128) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:959) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:732) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.AbstractComponentManager.enableInternal(AbstractComponentManager.java:666) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.AbstractComponentManager.enable(AbstractComponentManager.java:432) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.manager.ConfigurableComponentHolder.enableComponents(ConfigurableComponentHolder.java:665) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.BundleComponentActivator.initialEnable(BundleComponentActivator.java:338) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:382) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.Activator.access$200(Activator.java:49) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.Activator$ScrExtension.start(Activator.java:264) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.AbstractExtender.createExtension(AbstractExtender.java:196) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:169) [org.apache.felix.scr:2.1.16]

at org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:49) [org.apache.felix.scr:2.1.16]

at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:488)

at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:420)

at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:232)

at org.osgi.util.tracker.BundleTracker$Tracked.bundleChanged(BundleTracker.java:450)

at org.apache.felix.framework.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:915)

at org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:834)

at org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:516)

at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4817)

at org.apache.felix.framework.Felix.startBundle(Felix.java:2336)

at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)

at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)

at org.apache.felix.webconsole.internal.core.InstallHelper.doRun(InstallHelper.java:67) [org.apache.felix.webconsole:4.3.8]

at org.apache.felix.webconsole.internal.core.BaseUpdateInstallHelper.doRun(BaseUpdateInstallHelper.java:99) [org.apache.felix.webconsole:4.3.8]

at org.apache.felix.webconsole.internal.core.BaseUpdateInstallHelper.run(BaseUpdateInstallHelper.java:171) [org.apache.felix.webconsole:4.3.8]

Is someone also encountered with the same issue after upgrade to AEM 6.5? Any help will be appreciated.

Replies

Avatar

Avatar
Coach
Employee
jbrar
Employee

Likes

380 likes

Total Posts

868 posts

Correct Reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile

Avatar
Coach
Employee
jbrar
Employee

Likes

380 likes

Total Posts

868 posts

Correct Reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile
jbrar
Employee

13-11-2019

Have you compiled the custom code with uber jar version 6.5.0.0 ?

Avatar

Avatar
Ignite 5
Level 2
bunny87948290
Level 2

Likes

4 likes

Total Posts

25 posts

Correct Reply

1 solution
Top badges earned
Ignite 5
Ignite 3
Ignite 1
Give Back 3
Give Back
View profile

Avatar
Ignite 5
Level 2
bunny87948290
Level 2

Likes

4 likes

Total Posts

25 posts

Correct Reply

1 solution
Top badges earned
Ignite 5
Ignite 3
Ignite 1
Give Back 3
Give Back
View profile
bunny87948290
Level 2

13-11-2019

Just curious, what are the steps performed for inplace upgrade from AEM 6.3 to 6.5 ? We are in the process of upgrading and would like to know more about the steps you took or plan you followed for this upgrade.

Avatar

Avatar
Coach
Employee
jbrar
Employee

Likes

380 likes

Total Posts

868 posts

Correct Reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile

Avatar
Coach
Employee
jbrar
Employee

Likes

380 likes

Total Posts

868 posts

Correct Reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile
jbrar
Employee

13-11-2019

1) Run Pre-Upgrade steps

2) Stop the 6.3 instance

3) Replace the jar as migration is not required when moving from 6.3 to 6.5

4) Unpack the jar and start the 6.5 instance.

More details at [1]

[1] Performing an In-Place Upgrade

Avatar

Avatar
Ignite 5
Level 2
bunny87948290
Level 2

Likes

4 likes

Total Posts

25 posts

Correct Reply

1 solution
Top badges earned
Ignite 5
Ignite 3
Ignite 1
Give Back 3
Give Back
View profile

Avatar
Ignite 5
Level 2
bunny87948290
Level 2

Likes

4 likes

Total Posts

25 posts

Correct Reply

1 solution
Top badges earned
Ignite 5
Ignite 3
Ignite 1
Give Back 3
Give Back
View profile
bunny87948290
Level 2

13-11-2019

Thanks. Did you have to do any code base update after the in place migration ? Document lists deploy upgraded code base.

Avatar

Avatar
Coach
Employee
jbrar
Employee

Likes

380 likes

Total Posts

868 posts

Correct Reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile

Avatar
Coach
Employee
jbrar
Employee

Likes

380 likes

Total Posts

868 posts

Correct Reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile
jbrar
Employee

13-11-2019

There are not many API that was changed from 6.3 to 6.5. So, compiling the custom code with uber jar version 6.5.0.0 should be enough.

Avatar

Avatar
Give Back 5
Employee
sunjot16
Employee

Likes

103 likes

Total Posts

164 posts

Correct Reply

50 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 25
Give Back 10
Give Back
View profile

Avatar
Give Back 5
Employee
sunjot16
Employee

Likes

103 likes

Total Posts

164 posts

Correct Reply

50 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 25
Give Back 10
Give Back
View profile
sunjot16
Employee

14-11-2019

In addition to JaideepBrar​ 's updates, if your components are using coralui 2, you should migrate your components to coralui 3.

The following document maybe helpful:

Legacy CoralUI 2 Components — Granite UI 1.0 documentation

There were some deprecated & removed features, which you can find here:

Deprecated and Removed Features - AEM 6.3

Deprecated and Removed Features  - AEM 6.4

Deprecated and Removed Features  - AEM 6.5