Scalix Forums

Recently upgraded this site to 11.4.5 and some users are having issues when accessing their folders with webmail. I logged on and experienced it myself. I was opening a folder with about 1000 messages, it only showed some of them and then I hit Send & Receive All a few times then I got a popup that said there was a server connection error with an OK button only, clicked that and it kept popping up every few seconds for a while. I went out of the folder, into an empty folder, back to the original folder and all the items were displayed eventually... took a few minutes to display them all.

In the logs I found this scalix-api.log:

2009-08-28 15:35:18,337 WARN [PlatformDispatcherServlet.service:86] Problem pro
cessing request method=GET URI=/api/user@international.com.au/mailbox/Inb
ox%202008%20archive
ClientAbortException: java.net.SocketException: Broken pipe
at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffe
r.java:366)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:432)
at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:347)
at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.ja
va:392)
at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:38
1)
at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputSt
ream.java:89)
at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(Unknown Source)
at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(Unknown Source)
at sun.nio.cs.StreamEncoder.write(Unknown Source)
at java.io.OutputStreamWriter.write(Unknown Source)
at java.io.Writer.write(Unknown Source)
at org.apache.xml.serialize.Printer.printText(Unknown Source)

....etc to
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:537)

But there was only one of these errors but I saw loads of the popup warning box.

In the scalix.swa.log I get:
2009-08-28 15:35:09,874 WARN [SoapMail.fetchMessageHeaders:1420] Reverting to IMA
P to fetch headers because the platform failed with status 500 for request /vankat
@international.com.au/mailbox/Inbox%202008%20archive?uids=1334,1333,1332,1331
,1330,1329,1328 ....
2009-08-28 15:35:18,214 WARN [FailedResponseException.<init>:28] Could not write
SOAP response
ClientAbortException: java.net.SocketException: Broken pipe
at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.
java:366)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:432)
at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:347)
at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java
:392)
at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:381)
at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStre
am.java:89)
at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStre
am.java:83)
at com.oddpost.soap.SoapResponseImpl.serializeElementListToStream(SoapResp
onseImpl.java:204)
at com.oddpost.soap.SoapResponseImpl.flush(SoapResponseImpl.java:292)
at com.oddpost.soap.SoapResponseImpl.flushAndHandleException(SoapResponseI
mpl.java:359)

Any suggestions what is the issue or anyone else seen this, fixed this?

Check that Postgres is running correctly. If this is not the case, the mobile client will fail completely, so it's easy to test.

Alternatively, you can try to clear the user's IMAP cache as well.