Skip to Content
author's profile photo Former Member
Former Member

Backoffice - Unusable due to loading bar

On our test environments, the backoffice sometimes is not usable.

When clicking on a typenode in the explorer tree the loading bar shows up and counts up to 100%, but i never see any search results. When now selecting any other type in the explorer tree, the search seems to be performed successfully, since i see the search results, but they are hidden behind a transparent layer, that still shows the 100% loading bar (see attachment).

Due to this layer i am not able to select any entry in the list browser, which makes the backoffice unusable.

This issue occours occasionally on all environments. The product cockpit is also affected by this.

We are running version 6.4.0.7. When looking at the dev tools in the browser i can see one call per second to the endpoint /zkau responded by the following JSON object:

 {rs: [], rid: 191}

Where the rid is increasing by 1 with every call. Did anyone ever face this issue?

alt text

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • Posted on Apr 03, 2018 at 10:27 AM

    This is a known 6.4 issue. But there is a workaround. We can diasble the async loading in the collection browser, thus the overlay will no longer be displayed. This can be done either via orchestrator mode or add the following in your_ext_name-backoffice-widgets.xml

     <widget-extension widgetId="hmc2list"> 
             <setting key="asyncLoading" type="Boolean">false</setting>
     </widget-extension>
     <widget-extension widgetId="pcmbackoffice-collectionBrowser-browser">
             <setting key="asyncLoading" type="Boolean">false</setting>
     </widget-extension>
    
    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 07, 2019 at 08:13 AM

    I think it is been resolved in the patch version of Hybris 6.6.0.10.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 07, 2019 at 10:03 AM

    Hi all,

    The issue have been fixed in 1811 and backported to: 1808.2, 6.7.0.7, 6.6.0.10, 6.5.0.14, 6.4.0.17. So either you can use one of those versions or just set asynchLoading setting of Collection Browser to false as a workaround.

    Cheers, Jacek

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Mar 14, 2018 at 02:37 PM

    It is most possible with data issues, too large data in some types, etc. If it is happening for OOTB accelerator code, please create a product ticket. I say this because, when there are upwards of several million records for some types, it does slow down (again defining appropriate keys may help). Unless you give specifics it is hard to pinpoint exact issue.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 06, 2019 at 12:20 PM

    Is there an update on this issue - we also face it on version 6.6?

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.