Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-6473

Message 'Can't find asset: com.atlassian.servicedesk/banner.json' should be suppressed when there are no customisations in Customer Portal

    • 103
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      When a customer portal is being loaded up, JSD always try to load the banner image for a customised portal. This happens to all portals regardless they are customised or not.

      If there is no customisation, the following message is logged

      /servicedesk/customer/portal/3 [c.a.j.p.assets.impl.AssetStorageManagerImpl] Can't find asset: com.atlassian.servicedesk/banner.json: Path does not exist

      Although this can be safely ignored, it indicates that JSD doesn't even check for any customisations before loading anything.

      Suggestion

      • Include a check before loading any customizations
      • Change the message to something less dramatic

      Workaround

      Configure logging package com.atlassian.jira.plugins.assets.impl with WARN level to make sure the message doesn't get logged.

      For permanent logging change, update the log4j.properties file:

            [JSDSERVER-6473] Message 'Can't find asset: com.atlassian.servicedesk/banner.json' should be suppressed when there are no customisations in Customer Portal

            9.19 still brings the issue.

            And note:

            NOTE

            Putting a specific log type to disable is NOT a proper workaround.

            This is just burying my head in the sand so I won't see the problem anymore, even though it's still appearing in the background.

            Thanks

             

            Best: Peter

            Peter Cselotei - Lupus Consulting Zrt. added a comment - 9.19 still brings the issue. And note: NOTE Putting a specific log type to disable is NOT a proper workaround. This is just burying my head in the sand so I won't see the problem anymore, even though it's still appearing in the background. Thanks   Best: Peter

            i have the same message after upgrade to 9.12.13 and portal isn't loaded we have blank page 

            Nairi salma added a comment - i have the same message after upgrade to 9.12.13 and portal isn't loaded we have blank page 

            Urmo Luts added a comment - - edited

            2023 we still have this problem. Will there be any fix?

            2023-05-19 11:13:40,993+0300 https-jsse-nio-8443-exec-19 url: /servicedesk/customer/portal/1, /rest/servicedesk/1/customer/pages/portal/1; user: urmol INFO urmol 673x163612x1 19ekk3b 172.21.0.42,10.0.9.229 /servicedesk/customer/portal/1 [c.a.j.p.assets.impl.AssetStorageManagerImpl] Can't find asset: com.atlassian.servicedesk/banner.json: Path does not exist

            Urmo Luts added a comment - - edited 2023 we still have this problem. Will there be any fix? 2023-05-19 11:13:40,993+0300 https-jsse-nio-8443-exec-19 url: /servicedesk/customer/portal/1, / rest /servicedesk/1/customer/pages/portal/1; user: urmol INFO urmol 673x163612x1 19ekk3b 172.21.0.42,10.0.9.229 /servicedesk/customer/portal/1 [c.a.j.p.assets.impl.AssetStorageManagerImpl] Can't find asset: com.atlassian.servicedesk/banner.json: Path does not exist

            Exatel added a comment -

            Exactly what is the cause?

            Exatel added a comment - Exactly what is the cause?

            What is the cause?

            Gonchik Tsymzhitov added a comment - What is the cause?

            David Chan added a comment - - edited

            For permanent logging change, update the log4j.properties file:

            David Chan added a comment - - edited For permanent logging change, update the log4j.properties file: https://confluence.atlassian.com/adminjiraserver0713/logging-and-profiling-964983962.html Add: log4j.logger.com.atlassian.jira.plugins.assets.impl = WARN, filelog log4j.additivity.com.atlassian.plugin.classloader = false Restart

            I have the same message after upgrade  Jira Service Desk to version  4.4.2

            Lukasz Sieniu added a comment - I have the same message after upgrade  Jira Service Desk to version  4.4.2

              c8bcca445054 Benjamin Suess
              aharith Akmal Harith (Inactive)
              Votes:
              177 Vote for this issue
              Watchers:
              104 Start watching this issue

                Created:
                Updated:
                Resolved: