Problem with esearch

[MattPohl]

Hi All,

I am having a performance problem with Robert's esearch widget and was wondering if anyone has run into this. I have three services coded into the widget, two of them work great but the one service (which has a fairly large number of records) seems to get hung up during the first initial search search. I am using a user list as a selection method and when i select a name from the user list i get the "Loading" message with the spinning circle for a few seconds, than the circle goes away (like the search has completed), but the "Loading" message stays there and no results are ever returned. However, if I click on "Text Search" or "Graphical Search" and then click back to the "Results" table, the results are returned. This only happens the first time the a search is requested. if I keep the esearch widget open and preform another search, it works fine. Its because of this that I know the xml is correct, I am just hoping there is a way to get this to work when first opened. I could easily work with this, but some of our clients might have a hard time trying to use the workaround. Any help on this would be great.

Thanks,

Matt

[RobertScheitlin__GISP]

Matt,

   Not a lot to go one here... Even know you believe the SearchWidget.xml is correct you should post it for me to look at.

[MattPohl]

Hi Robert,

Thanks for getting back to me. I attached my esearch xml (with working services commented out). Also I attached two screen shots, one from when the search begins ("loading" meassage and spinning circle), and the other after the search has ended with not results returned (spinning circle gone, "loading" message still there). Like I said, I know the search is complete because if i click on the text or spatial search button and then go back and click on the results button, the results appear.

Thanks for looking into this.

Matt

[RobertScheitlin__GISP]

Matt,

   I have a couple of concerns:

1. upper(Lable) = upper('[value]') Also as you are using a userlist there is no need for the upper as your list should contain the exact value. i.e. Lable = '[value]' if Lable is correct. I don't see Lable listed in your returned fields though.


2. Next is what is up with all the space between the items in the userlist (i.e. ,    St. John (Little Canada),)? It should look like ,St. John (Little Canada),

[MattPohl]

Hi Robert,

I changed the expression to reflect your suggestion, and cleaned up the spaces in the user list (copy and paste error with that bi of a list), but still having the exact same results. Its strange it gets hung up just the first time. Like I said, if I preform the workaround, and keep the widget open I can clear the selection and preform a new one with no problems. Its just the first time the widget loads is when it gets hung up. The feature class that the service is queering is very large. roughly 250,000 records. Would this have anything to do with it?

Thanks again,

Matt

[RobertScheitlin__GISP]

Matt,

   My only other suggestion is to use a http utility like fiddler and see how long the response from your server is taking when the eSearch executes the query. Being that your service is secured I can not test this for you.

[MattPohl]

Hey Robert,

Fiddler posted back roughly a 8 second response time which to me is about right with that large of a dataset and consistent with the return times after using the workaround. Still hangs up when using the widget for the first time. Everything seems to be in order since it will work just fine after the first use. And it seems to me that its working the first time, just not returning the results. Any other thoughts on this one. Thanks for the help so far.

Matt

[MattPohl · Accepted solution]

Hi Robert,

Again thanks for giving me some suggestions on this one. Your help is always appreciated. I decided to start from scratch in an attempt to diagnosis the problem from the beginning and in doing so I upgraded the widget to Version 2.9.0 (previously on V2.5.1.2). Not sure if that is what did it or if it was just starting over with a new xml, but either way all services are now working as expected. Thanks again for a great widget.

Matt