Exception when starting CachePreloaderService

[Former Member]

Dear Portal Specialists

We upgraded our portal to NW 7.0 EHP1 SPS 3 and want to enable Navigation Cache and the CachePreloaderService.

So first i enabled the Navigation Cache and then i configured the CachePreloaderService.

Run on startup: true

Users to preload: [Administrator:2:false:en_US,en] (i also tried custom values)

When i go to the node to restart the service, i receive the following error:

Server 1991650:Error in the listener class com.sap.ip.portal.admin.portalanywhere.QueryHandler during the process of handleTopic.

I can find other threads about the same error message, but those are about custom services or services that had to be deployed.

Does anybody know this problem and knows how to solve it?

Thank you very much and best regards

Martin

[anja_engelhardt2 · Accepted solution]

Hi Martin,

the cache preloader service was designed not to work when the portal is up, because of the reason that the navigation engine cannot know when all the connectors is up, and because of that the cache

preloader might not work.

Did you tried to restart the portal completely?

Cheers,

Anja

[Former Member · Accepted solution]

Dear Anja

thank you very much for your fast reply!

You were correct, restarting the portal seems to start the Preloader Service correctly (i checked the navigation cache and saw all the roles there from the user defined in the preload service)

So that is implemented successfully.

However, the reason why we wanted to configure the navigation cache and the Preloader Service was poor performance in combination with FPN (remote delta link)

Displaying the navigation can take up to a minute when a user has lots of FPN content (and this on productive environment!!)

Are Preloader Service and Navigation Cache not the right answers to this prolbem?

I got an OSS open regarding this issue, but reproduction is not that easy and it will be hard that we get support from there i think.

Thank you very much for your help.

Best Regards

Martin

[Former Member · Accepted solution]

Dear Martin,

we switched to 7.01 SP2 because of the same problem --> very bad performance in combination with FPN. The only difference is that we use Remote Role Assignment.

We also configured the Preloader Service but it doesn't work for FPN roles. Displaying the navigation after the FPN RRA cache was deleted can take a long time... Have you configured the SLGP service? Caching System IDs is described in the following blog () and helped us a lot.

Do you already have an answer of sap? Will they enlarge the preloader service for FPN?

I'm looking forward to hearing from you.

Best regards,

Sandra

[Former Member · Accepted solution]

Dear Sandra

Thank you for your reply.

How bad was the performance in your case?

What was the behavior of it (was it slow for every click or only once a day, for each user or only the first who loaded it?)

We are not 100% sure about that, that is why i ask.

We enabled SLGP and the problem only came later. So it does not seem to help in our case.

Do you recommend remote role assignment instead of remote delta link?

We do the remote delta links on workset level, but i have to check with my colleagues why we don't use remote role assignment (i don't see any reason)

Our call at SAP is still open. Up to now there were mainly questions but no answers.

Once it sounded like they were working on a solution but i'm not too confident about this yet.

I'll post it here, if i have any news.

Best Regards

Martin

[Former Member · Accepted solution]

Dear Martin,

performance is still very bad each time the RRA cache is empty (because the cache lifetime expired or we had to clear it manually because of the problems described at note 1282293). At System Administration --> Federated Portal --> Myself As Content Consumer --> Cache Management we set the lifetime to 600000 seconds. What is your value here? Have you tried to synchronize the Remote Delta Link Content? Does it show any effect on performance?

Every time the Remote Cache in our consumer portal is empty it takes up to minutes to navigate through the folders and subfolders in the detailed navigation which are received from our producer portal. After clicking through all the navigation items for the first time, I guess that the SLGP service works and for the next 600000 seconds performance is not that bad. The cache is shared with all users and the languages we configured at [OptimizerC|http://help.sap.com/saphelp_nw70/helpdata/en/43/222eaf0bb93fece10000000a11466f/frameset.htm] service.

I would not recommend RRA. Honestly we often thought about switching to Remote Delta Links, but we see problems with content updating and additional work on our consumer portal. Which kind of content do you receive from your producer portal? We share BI reports. Today we have almost 50 remote roles. The more it get the worse is our performance. Since we are on 7.01 SP2 we had many problems with nullPointerExceptions (note [1282293|https://websmp130.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?sap-params=bnVtbT0xMjgyMjkzJnNtcHNydj0%3d]]). Finally, we got a correction for SP2 last week.

May you describe the behaviour of your portal? Is it slow for every click?

I really hope SAP works on all those problems!

Best regards,

Sandra

[Former Member · Accepted solution]

Dear Sandra

thank you very much for the detailled infos!

Following some responses and some more questions:

We set the FPN Cache validity to 43'200 = 12 h

We think about changing that. But this will have influence on our transport process for our BI systems, so we first have to think about it.

The navigation is not slow on every click. We also assume that it is only slow when cache expired. But since we have 8 server nodes, this behavior is not that easy to really verify.

Usually only the loading of the first opening of the detail navigation is slow, but opening the subfolders is not slow.

However, from time to time it is also slow to open subfolders.

I don't understand the functionality of the synchronize button exactly.

It seems that it loads the current info from the systems and caches it. (the message after it is finished sais that the cache got renewed.)

So my conclusion is, that if the system gets restarted, and we click this button, we don't have to expect bad performance. Is this correct?

You write about opening all the navigation structure after cache expired, is this necessary? How are you doing this (did you find a way for automation?)

We did a test, of the synchronizing, but we have to do more tests.

Do you recommend to load all content or only the changed content (first radio button option to chose from)

We did not configure the OptimizerC service.

According to SAP help it is only used for RRA but not for RDL. So this does not help in our case.

We also connected BI Systems with FPN (except from one iview from CE)

We also have problem with the synchronization from time to time, so RDL is not the perfect solution.

Can you tell me, if you have 32 of 64bit servers?

I got a recommendation from SAP to set the Pcd.Xfs.Cache.HardReferenceLimit to 500 instead of 100 (Note 905211)

But we have only 32bit servers (will be replaced one day) so we have some concerns to set 500. Do you have any experience with this setting?

Thank you very much and best Regards

Martin