Localhost AEM throws error: Use 'service.ranking:Integer' as the key | Community
Skip to main content
A
Aaron_Dempwolff
Level 4
February 18, 2025
Solved

Localhost AEM throws error: Use 'service.ranking:Integer' as the key

  • February 18, 2025
  • 3 replies
  • 1354 views

Hello friends, I have a Brightcove third party that when I was using my old version of AEM on localhost I could build the project locally with no problems, but now that I upgraded my local AEM both the JDK and SDK I get the following error now

[ERROR] The analyser found the following errors for author and publish :
[ERROR] [configurations-basic] Configuration org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended~brightcove_admin: Service.ranking is not of type Integer. Use 'service.ranking:Integer' as the key. (com.tfs:aem-tfs-project.all:0.0.1-SNAPSHOT|com.coresecure:brightcove.all:6.1.10|com.coresecure:brightcove.ui.config:6.1.10)

The versions of the update are the next one:

JDK: Oracle JDK 21.0.6

SDK: AEM SDK v2025.1.19149.20250116T154450Z-250100

I modified the file of the configuration:

org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-brightcove_admin.cfg.json

With the next code:

{
  "service.ranking:Integer": "0",
  "user.mapping": [
      "brightcove.core:brightcoveWrite=[brightcove_admin]"
  ]
}
And even with that still happend the same issue, what can else I can do?

I even tried to do the next modifications and still not working:
"service.ranking:Integer": "0"

"service.ranking": "0"

"service.ranking:Integer": 0

"service.ranking": 0
    Best answer by chaudharynick

    Hi @aaron_dempwolff 

     

    Can you let me know the reason for keeping the ranking of this service? Are there multiple similar Brightcove services already present? since this is going to be unique you can simply remove the service.ranking from here.

     

    Please refer to https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/security/best-practices-for-sling-service-user-mapping-and-service-user-definition for best practices.

    3 replies

    AmitVishwakarma
    Community Advisor
    AmitVishwakarmaCommunity Advisor
    Community Advisor
    February 18, 2025

    1. Try changing the config format: If you're using a .cfg.json file, switch to a .config file instead, as AEM might interpret it better.

    2. Check for any formatting issues in your JSON and ensure the service config is correct.

    3. Restart AEM and clear the OSGi cache to reload the configuration.

    4. Check compatibility between your new AEM version and the Brightcove integration (make sure the version you're using is compatible with AEM 2025). 

    5. Directly set the integer without quotes:

    { "service.ranking:Integer": 0, "user.mapping": [ "brightcove.core:brightcoveWrite=[brightcove_admin]" ] }

    6. Ensure AEM is actually refreshing the configuration after changes. Sometimes AEM caches configurations, so after modifying the files, restarting the AEM instance and clearing the OSGi cache is key.

      A
      Anil_Chennapragada
      Level 4
      February 19, 2025

      hi @aaron_dempwolff ,

      Hope you have already found the solution for the same. If not please check the below link and the example class below if it helps

       

       

       

        konstantyn_diachenko
        Community Advisor
        konstantyn_diachenkoCommunity Advisor
        Community Advisor
        February 19, 2025

        Small note: it's possible to define service.ranking property in the @Component annotation when you manage this component code. However, @aaron_dempwolff is talking about creating of OSGi configuration for Sling OOTB OSGi component. It is impossible to modify java code for that service.

        Kostiantyn Diachenko, Community Advisor, Certified Senior AEM Developer, creator of free AEM VLT Tool, maintainer of AEM Tools plugin.
          chaudharynick
          chaudharynickAccepted solution
          Level 4
          February 20, 2025

          Hi @aaron_dempwolff 

           

          Can you let me know the reason for keeping the ranking of this service? Are there multiple similar Brightcove services already present? since this is going to be unique you can simply remove the service.ranking from here.

           

          Please refer to https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/security/best-practices-for-sling-service-user-mapping-and-service-user-definition for best practices.

            kartheekd203042
            kartheekd203042
            Level 3
            August 28, 2025
            Thanks all - we did face the same issue with the latest SDK and JDK 21 - though this solves the issue it does require us to modify the connector config and re-package.
             
            We are facing sync issues with the latest connector cloud version as well. - https://github.com/brightcove/Adobe-AEM-Brightcove-Connector/releases/tag/6.1.10-cloud
             
            I am posting here in case anyone else can report a set of issues with the brightcove connector that can collectively help make the connector compatible with JDK 21 and latest SDK by Brigthcove team maintaining the connector.
            Terms & ConditionsAccessibility statement

            Loading footer...