Dotnetnuke Version:04.08.02

DMX-Version: 04.02.01

We have see an little Bad Effect with the Search-Results in DMX on our Portal.

When we activate any Caching Feature in DNN and we wait a Day or two we becoms no Results in the DMX-Search.

We have deaktivate the caching = No Effect

We have restart the Webapp = Now works perfect

After a Day or 2 the Results is empty and we made the same procedure with identical Results

We deaktiviate the caching from dnn complete the Search works over any Days without any Problem but the DNN is without caching very slow.

Have you a Tip for us Peter, the Compression is only a little Help for the Performance?

Best regards!

Hi Guido,

So, if I understand correctly:

With caching = DMX search not working after a couple of days AND
Without caching = DMX search keeps on working.
Correct?

Second question: is it only the search in the DMX Ajax UI affected or also the search on the Search Results page (if you installed this)?

Peter

Hi Peter,

yes you understand correctly!

We use only the UI-Search in this Portal and no DNN Search!!

Best Regards

Guido

 

Hi Guido,

I'm left guessing here because there's not much caching going on in the search logic. But what might help is to see what happens in the DMX_SearchResults table in SQL. What happens after those 2 days? Do you see any results filling up in there upon a search?

Peter

Hi Peter,

i will made on Monday a copy from the Portal and DB and separate this as Copy under a separate Hostheader for Tests. We cannot active the Caching and Testing on the Production-System.

I send a info to you when we have complete the Test-System.

Guido

 

Hi Peter,

sorry for the long Delay but my Customer priorize other projects and we have must disable the caching from DNN since the latest Problems. Now my Customers will now here a Solution from us for this Problem.

We have today create a Copy from the Portal, activate the caching and now we see the same Effect on the Copied CMS.

We test the Search the UI refreshed in the Background but no Results are displayed.

We have looked in the Table DMX_SearchResults and we see here Entries.

We have upgraded the CMS-COPY to DNN 04.09.03 but here is the same Effect!

What can we do as next to come to a solution?

Guido

 

Hi Guido,

Your best bet is to find out if the caching also affects the ajax calls. So what you can do is to use something like Fillder to have a look at the traffic between client and server when you do your search. There will be a refresh of the Grid1 in there somewhere. In that refesh it calls for the search results. This call should then lead to an SQL call to retrieve the contents from the database. You should be able to see that with the SQL profiler. Now there are several scenarios:

1. The refresh does not lead to a call to the database for the search results. This means the Ajax call is being cached. You'll need to disable caching calls to Ajax.
2. The SQL runs but returns no results. This means there is a problem with the search logic or session ID. Carefully check the SQL to determine why no results were returned.
3. The SQL runs and returns results. Now we have determined that somewhere in the downstream something is wrong. I have no explanation for this scenario.

Peter

Hi Peter!

We check this tomorrow.

One stupid Question from me, how i can disable caching to Ajax in DNN?

Best regards

Guido

Hi Guido,

I'm not sure. There shouldn't be any caching in Ajax. I don't know how I could enable it anywhere, nor how to disable it. Ajax means there is a postback behind the scenes, and my code will run. I don't include any caching in the response. I included it in the list above because theoretically it might cause the issue. And I tried to enumerate every possiblity.

Peter

Hi Peter,

we have made any Tests today and now followed Result.

* Start Network-Monitor on the Websystem
* Start a Search in the UI
* We see that the Browser made a Post to the Webserver with the Search-Paramters and further informations.
* We see also that your DMX communicate with SQL-Server (Delete Serach-Result with specified ID), followed by many Inserts in the SearchResults-Table.
* But no Results are displayed

* We have another Client test the same and here are displayed the Results!?

* We check as next the search with Lucene-Syntax (schultyp:ahs) and have here also no Results.When we search with luke is all ok.
* As next we reindex the portal and made a additional Test after completing but we see here also no Results!

Very interesting Effect:

*we have logged in for the reindexing from other System and logged otu after the reindexing and see on this System theh Results, in the same time we test this from 2 other and this Clients cannot see Results.

* We will reproduce the Effect and made a Login from a System was cannot see the Results, logged out and search but here also no Results displayed, we close the Browser start a new Browser made a search but no Results are visible.

* We have also tested to set "Ajax-Enabled in DNN 4.9.3" to not activated nut we have here no better Results.

* By our last Test we use the "Restart Application" in DNN and now we see the Results also on Machines what have see this not before!

What we can do no to come to a solution?

Best Regards

Guido

 

Hi Guido,

OK, let's look closer at this. The indexing itself is not an issue, I believe and you won't need to reindex. What I take from your account is that what happens is:
1. The DELETE call is made to the database to clear old search results
2. The search results are then filled with search results. This means search is actually working!
And then nothing happens any more.

One question: you do not see an SQL call to retrieve records for DMX_SearchResults after step 2?

Peter