Backoffice - Unusable due to loading bar

[Former Member]

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?

[Former Member]

Hi,

It occurs sometimes and I just refresh the page. I don't know if it's a Hybris bug or because of my custom code. Hybris: 6.4

[Former Member · Accepted solution]

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>

[former_member625836]

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

[Former Member]

thanks for the detailed information on that!

[Former Member]

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

[Former Member]

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

[Former Member]

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.