search doesn't work for me in SWA - exception in swa.log

Discuss the Scalix web client

Moderators: ScalixSupport, admin

struempelix
Posts: 16
Joined: Thu Jan 18, 2007 10:17 am

Postby struempelix » Fri Apr 20, 2007 8:01 am

Hi Subir,
I issued "sxmkindex -r 00:00:00" and 6271 messages were processed. But unfortunately it's still not working.
It might be interesting for you to know that nothing happens after pressing the search mail button. The "Searching...." stays forever.

thanks,
jens

ScalixSupport
Scalix
Scalix
Posts: 5503
Joined: Thu Mar 25, 2004 8:15 pm

Postby ScalixSupport » Fri Apr 20, 2007 8:46 am

Hi!

As you have mentioned there are about 6500 files to be indexed, I would like you to edit the
values in /var/opt/scalix/??/sis/sis.properties file for:
index.max.queue.size=8000
search.max.results=8000

Also set swa.search.maxresults=10000, in /var/opt/scalix/??/webmail/swa.properties file.

Restart scalix-tomcat service, to see if the issue gets resolved. If it still doesn't work, run
sxmkindex command I gave you earlier and try again.

Thanks,
Subir

struempelix
Posts: 16
Joined: Thu Jan 18, 2007 10:17 am

Postby struempelix » Fri Apr 20, 2007 10:07 am

Hello Subir,
did all that, but still no success.

I see some I/O exceptions in catalina.out everytime I try to search as well:

Code: Select all

INFO: I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
20.04.2007 15:01:03 org.apache.commons.httpclient.HttpMethodDirector executeWith
Retry


You mentioned earlier that I should check apache access and error logs. Should there something in the access log when I issue a search?

I'll try to replicate the problem on a vmware test instance this weekend, but I can remember that I had the same issue with it.

Thanks,
jens

ScalixSupport
Scalix
Scalix
Posts: 5503
Joined: Thu Mar 25, 2004 8:15 pm

Postby ScalixSupport » Mon Apr 23, 2007 2:41 am

Hi Jens,

I see you don't have

Code: Select all

# Defines in Seconds how long a SOAP request will remain in the current, uncomplete
# readyState (= 1, 2, or 3) before we force a timeout
swa.soap.soapRequestTimeout=60

in your swa.properties, save and exit, restart scalix-tomcat and try searching again.

If search do not work still, you should run the installer and reconfigure:
[1] Scalix DB
[2] Scalix Tomcat
[3] Scalix Messaging Services
[4] Scalix Management Agent
[5] Scalix Web Access
[6] Scalix Management Services
[7] Scalix Search and Index Service
[8] Scalix Mobile Client

I am sure this should help.

Thanks,
Subir

struempelix
Posts: 16
Joined: Thu Jan 18, 2007 10:17 am

Postby struempelix » Mon Apr 23, 2007 3:41 am

Hi Subir,
I tried to reproduce the problem on my testing vmware deployment but I couldn't. Means Search is working there!!

I'll do a diff between all config files and hope to find the issue there.

BTW, swa.soap.soapRequestTimeout=60 is configured in swa.properties.

Anyway, thanks a lot for your great support!!!

Cheers,
jens


Return to “Scalix Web Access”



Who is online

Users browsing this forum: No registered users and 0 guests