I started having some problems we had deployed search and profiles and all was working smooth all of a sudden out of no where we started having these massive stalls.
Lets say that you go to search it would take 10-30 seconds for the search to list whats in it. Same thing with profiles. I then noticed that parcels in the same sim if you flew over there there would be this massive lag.
I started to look at the region console and then I noticed it would say JOpenSimSearch etc and then after a while it would say it again then all of a sudden the lag would stop. This wasn't just happening in one region but all regions even in regions on other servers.
Like I said originally everything was doing well, we hadn't made any changes or anything this just started happening one day. I rebooted the entire grid and even the machines hoping it would help. When I removed Jopensimsearch and profiles from the sims and disabled in the setup there is no more any problems. Even things like searching for a region on the map would stall the whole region for everyone. If I turn of jopensim search no stalling no problems.
Any ideas what could be causing this? I am a bit bummed because it was all working so well in the beginning.
Other things in world are super fast even communication to the database I also notice if I go to joomla admin panel and everything loads so fast but anything jopensim related takes forever to load.
Hope to find a solution - thanks all!
Ps, I have checked the hardware all looks fine no slowness no hard drive issues no network issues etc I even defragged the database hoping it would help.
Wanted to update you all - I found the problem there are a ton of urls that the JOpenSim wants to go to that are wrong this looks like it is a mistake with the jopensim files I had to go in there and fix the issue and this solved it and performance is now phenomenal.
I'm happy you could solve your issue Could you please specify a bit more, what kind of invalid urls have been where and what jOpenSim files are involved there?
In case this is a bug, I would like to fix it for the next release