Page 1 of 1
SWA is not reliable
Posted: Tue Nov 30, 2010 11:08 am
by joako
What needs to be done to make SWA reliable? I get constant errors and issues like server timed out messages, XML response messages basically I can't keep SWA open all day in one session.
Re: SWA is not reliable
Posted: Tue Nov 30, 2010 4:50 pm
by fkienker
Try upping your Java memory settings in /etc/opt/scalix-tomcat/scalix-tomcat.conf. This solved these issues for us.
Re: SWA is not reliable
Posted: Tue Nov 30, 2010 7:01 pm
by sgreen
Fkienker, what do you have yours set to?
Re: SWA is not reliable
Posted: Tue Nov 30, 2010 7:26 pm
by fkienker
Using Scalix 11.4.6 on a Dell PowerEdge 2650 with 4 Gb of RAM memory and CentOS 5.5, these settings seem to work best:
JAVA_OPTS="-server -Djava.net.preferIPv4Stack=true -Xms1536m -Xmx1536m"
Going higher than 1536m causes subtle and annoying problems with Scalix WebAccess.
Also, upping the txqueuelen to 5000 helps a lot. Use something like:
/sbin/ifconfig eth0 txqueuelen 5000
to set it so you can try it out. If it helps, add it to something which will survive reboots. On CentOS or RHEL this is the /etc/rc.local file.
Best regards,
Fred
Re: SWA is not reliable
Posted: Wed Dec 01, 2010 2:44 pm
by sgreen
thanks, hopefully this makes the users who use webmail a little happier.
Sadly moving the execs to that mail server which shall not be named, the lag of outlook 2010 support and not stable BES and activesync support forced our hand. Hopefully we can one day move them back. For me on my Droid 1 activesync works great, so it seems highly dependent on the client implementation.
Re: SWA is not reliable
Posted: Thu Dec 02, 2010 12:38 am
by joako
Well I increase the memory from the default and I still get timed out errors. If I do nothing, not even click ok on the massage the folder eventually loads.
Re: SWA is not reliable
Posted: Thu Dec 02, 2010 9:52 am
by BaldBoy
Most of the times the slowness is related to how swa retrieves messages from the mailstore.
In my experience all performance issues were bound to improper functioning of the Postgres backend.
Have you examined your /var/opt/scalix/xx/tomcat/logs/scalix-swa.log for errors ?
Re: SWA is not reliable
Posted: Thu Dec 02, 2010 4:10 pm
by joako
So what is the correct way to configure Postges and the mail store? Right now I have everything at the default.
Re: SWA is not reliable
Posted: Fri Dec 03, 2010 5:18 am
by BaldBoy
Postgres "should" be set by default ... but sometimes it happens it gets misconfigured.
Please post here any error you find in the /var/opt/scalix/xx/tomcat/logs/scalix-swa.log
Re: SWA is not reliable
Posted: Fri Dec 03, 2010 8:24 pm
by joako
I am seeing messages such as:
2010-12-03 19:19:01,140 ERROR [HttpRequestHandler.sendResponse:294] ip: (ip unavailable); username: andrew@joako.net; message: Failed Response
Could not write SOAP response: org.apache.catalina.connector.ClientAbortException: null
at com.oddpost.soap.SoapResponseImpl.flushAndHandleException(SoapResponseImpl.java:371)
at com.oddpost.soap.SoapResponseImpl.send(SoapResponseImpl.java:350)
at com.oddpost.server.HttpRequestHandler.sendResponse(HttpRequestHandler.java:292)
at com.oddpost.server.HttpRequestHandler.handleRequest(HttpRequestHandler.java:263)
at com.oddpost.server.SoapServlet.doPost(SoapServlet.java:44)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:70)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at com.oddpost.server.filter.HttpConfFilter.doFilter(HttpConfFilter.java:181)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
... skipping the last 18 lines as irrelevant...
Caused by: ClientAbortException: java.net.SocketException: Broken pipe
at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:370)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:432)
at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:321)
at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:295)
at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:98)
at com.oddpost.soap.SoapResponseImpl.flush(SoapResponseImpl.java:312)
at com.oddpost.soap.SoapResponseImpl.flushAndHandleException(SoapResponseImpl.java:359)
... 31 more
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:538)
at org.apache.jk.common.JkInputStream.doWrite(JkInputStream.java:162)
at org.apache.coyote.Response.doWrite(Response.java:560)
at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:365)
... 37 more
But they don't seem related to a Postgress or mailstore misconfiguration.
Re: SWA is not reliable
Posted: Sat Dec 04, 2010 1:01 pm
by BaldBoy
I'd suggest you the reading of this thread: http://www.scalix.com/forums/viewtopic.php?t=11436
(same error as yours).
Probably your configuration is pointing to 127.0.0.1 instead of the IP address of ethernet adapter.
Regards.
Re: SWA is not reliable
Posted: Tue Dec 07, 2010 5:58 pm
by echelon
Is it slow for everyone, or just for people with extremely large numbers of e-mails in the top-level of the inbox.
Re: SWA is not reliable
Posted: Fri Jun 10, 2011 6:36 am
by stefano
joako,
i have the same issue. Have you solved it ?
thank you
Stefano
Re: SWA is not reliable
Posted: Thu Jun 16, 2011 9:28 pm
by joako123
I haven't seen it recently, but the data integretiy issues persist.