Not able to replicate through crx/de after code deployment , it is giving 500 internal server error when trying to replicate using crx/de. | Community
Skip to main content
B
Bipsa
December 26, 2024
Solved

Not able to replicate through crx/de after code deployment , it is giving 500 internal server error when trying to replicate using crx/de.

  • December 26, 2024
  • 1 reply
  • 573 views

Attaching screenshot for reference. 

Repro steps

  • After deploying custom code on an instance, the instance restarts and a nullpointer exception occurs at "java.lang.NullPointerException: null
      at com.day.cq.replication.impl.ReplicatorImpl.getReplicationStatus(ReplicatorImpl.java:288) [com.day.cq.cq-replication:6.2.86.CQ650-B0007]" in CRXDE
  • When we try to reproduce the same on a vanilla instance, the issue doesn't occur unless we do a soft restart and deploy the core bundle of our custom code again. 

Note : after every deployment instance is getting restarted and issue mainly occurs after deploying core bundle and this is happening in all the AEM environment's (local . dev , uat e.t.c)

Below are the steps tried so far to resolve the issue 

  • Removed imports and exports in the core pom which could also be imported by core components
  • Removed RepositoryInitializer from ui.config
  • We also tried removing Environment Indicator bundle from ACS commons
  • Decoupled/Removed other custom code dependencies
  • Tried removing references of core components in poms

Still issue occures .

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Pranay_M

Hi @bipsa,


I believe this is a known issue and has already been fixed in the Forms SP22 release. I would request you try upgrading your environment to SP22 and validate the use case to see if you get the same issue. 

If you still see the issue, please raise a support case via the Experience League portal to investigate the issue further.

 

Thanks
Pranay

1 reply

P
Adobe Employee
Pranay_MAdobe EmployeeAccepted solution
Adobe Employee
January 7, 2025

Hi @bipsa,


I believe this is a known issue and has already been fixed in the Forms SP22 release. I would request you try upgrading your environment to SP22 and validate the use case to see if you get the same issue. 

If you still see the issue, please raise a support case via the Experience League portal to investigate the issue further.

 

Thanks
Pranay

Khushwant_Singh
Adobe Employee
Khushwant_SinghAdobe Employee
Adobe Employee
January 13, 2025

@bipsa, did yoy try @pranay_m 's suggetion? Did it resolve the issue? 

P
Adobe Employee
Pranay_MAdobe Employee
Adobe Employee
January 13, 2025

Hi @khushwant_singh,

 

This issue has already been fixed in SP22, and I have validated the use case.

Thanks
Pranay

Terms & ConditionsAccessibility statement

Loading footer...