Users can't enter site in Share for a short period of time?

[gronfelt]

I'm running Community 3.2 with multi-tenancy enabled and from time to time my users can't enter specific sites in Share. The problem first appeared yesterday and after a few tries during 5-10 minutes everything seemed to work. Now the situation is the same again, this morning our users could not enter some sites, after 5-10 minutes everything works as normal.

Sites created after the problem first appeared yesterday is no problem, only older sites.

The logs show nothing at all.

The problem occurred about the same time of day today and yesterday, is it possible that some sort of periodic maintenance procedure is causing this (either in Alfresco or in the hosting Linux system)?

[steve]

Hello,
How many logged in users are there when you see this problem?

Thanks,

Steve

[gronfelt]

The system where we have seen this issue is currently only used for testing, we have had a maximum of 2-4 concurrent users at any given time.

[paolo]

Same for us. We have maximum 1/3 users at the same time.

[kevinr]

OK thanks, we have reproduced the issue in house.

Kev

[dward]

OK, the problem was basically down to RemoteStore.hasDocument returning false when it received a non status 200 HTTP response from a web script. This caused StoreModelObjectPersister to cache the non-existence of a site page so that future requests for it were redirected to the root dashboard. I have changed it to throw an IOException in the event of an error response, so that errors are propagated properly and invalid results aren't cached.

And as for why it was getting non status 200 responses for the site dashboard. This was because the required authentication for the remoteavm GET webscript had been changed from "none" to "guest" (for multi-tenancy purposes). This prevented the WebscriptNTLMAuthenticationFilter from querying authentication information for a page before it was accessed and also meant that on a web session expiry the cached incorrect hasDocument result would remain. We have changed the required access back to "none", and have added extra code for the MT case that escalates it back to guest if required (MT and NTLM are incompatible anyway).

A fix has been checked into HEAD. I tried it on revision 15801.

[jtp]

So to get this fix we'll have to build from HEAD if possible or wait for another release?

[mikeh]

So to get this fix we'll have to build from HEAD if possible or wait for another release?

Yes, quickest would be to build from HEAD. Or keep an eye on the nightly build server. That latter only gets updated if all unit tests pass, so "nightly" isn't particularly accurate during periods of intense development (like now for the RM module).

Thanks,
Mike

[jriker1]

I'm on revision 15994 and getting an issue with the passthru user defined as an admin in the properties file that it can't render the dashboard for the user.  Is this related?  For some reason works fine in production at the moment but not development.  Changing the user back to non admin doesn't help.  Getting errors about "Unable to retrieve object: page.title.user~<network id here>~dashboard ".

Also get in the logs:

Unable to process tag and commit output
The problematic instruction:
———-
==> user-directive region [on line 10, column 7 in org/alfresco/dashboard.ftl]
in user-directive templateBody [on line 7, column 1 in org/alfresco/dashboard.ftl]
———-

Again not sure if it's related to this thread, however seemed to be an issue with loading the user's desktop template so thought it may be.

JR