Production component issues

[nsvsrk]

Hi all,

Let us say my component works fine on Author, but fails on Publish.

What are all the ways to debug?

I am aware of debug logging and also monitoring network tab using Developer tools.

Is looking at the bundles in Felix to see whether bundle is active an option on Publish?

Appreciate all your responses,

Thanks,

RK.

[PRATHYUSHA_VP]

Few things to check -- 

• Check the replication is enabled to the publish environment and the queue is not blocked 
• Verify the same code is deployed in both environments

Thanks

[nsvsrk]

Thanks @PRATHYUSHA_VP .

The below are not possible in Publish?

debug logging

monitoring network tab using Developer tools.

Looking at the bundles in Felix to see whether bundle is active

What are all the debugging techniques we use on Author that could be and could not be used on Publish?

Thanks,

RK.

[AnkurAhlawat · Accepted solution]

Hello,

If you have setup Publish environment in your local and testing the changes then yes you can use any below mentioned approach

debug logging

monitoring network tab using Developer tools.

Looking at the bundles in Felix to see whether bundle is active

HowEver, if you are planning to test your publish changes on higher environment on AEMAsCloud instance then:-
1) You can set log level to debug and print your logs there.
2) You can monitor network tab to see basic network calls and encoded source files that are loaded.

3) OSGI console is not accessible but Using Admin console you can check bundle status.

If you are testing this on AEM 6.5 instance which is not on cloud and managed by AMS then you cannot check Felix console, until and unless you got access from Adobe.

[nsvsrk]

Thanks @AnkurAhlawat .

This is also a detailed explanation.

Thanks,

RK.

[BrianKasingli]

Hello there,

Here are some solid ways to debug when a component works on Author but fails on Publish in AEM as a Cloud Service:

1. Browser Developer Tools → Check Console and Network tabs for JS/CSS errors or 404s.
2. Review Logs → Download Publish logs from Cloud Manager and search for errors related to your component.
   • Typically you will find something useful here.
3. Developer Console (AEMaaCS) → Use it to check the status of OSGi bundles, Sling Models, and configurations. This is the AEMaaCS way to confirm whether everything is active (since Felix isn’t directly accessible).
4. Repository Browser (AEMaaCS) → check to see if configurations has been enabled correctly in the publishers content. 
5. Permissions → Verify the user or service account on Publish has access to the content and services your component depends on.
6. Dispatcher / CDN Layer → Ensure requests aren’t blocked or cached incorrectly before they reach Publish.
7. Error Pages → If you see 404/500 responses, confirm whether the error originates from AEM Publish or the dispatcher/security filters.

So yes — on AEMaaCS, checking bundle status via the Developer Console is a valid and very helpful step.

Hope this helps.

[nsvsrk]

Thanks @BrianKasingli .

This is a detailed explanation.

Thanks,

RK.

[BrianKasingli]

Yes indeed, these are the exact steps of what I use whenever debugging a problem in AEMaaCS.