Zimbra 8.0.2 very slow webui after upgrade from 7.1.x

Hello all,
i have upgrade our zimbra server with the latest 8.0.2 version 2 weeks ago.

Before this upgrade, all work fine.
After upgrade, the webui was very slow, with many error message, wheeling mouse cursor, and 503 error message.

Exemple:
Server error:
Code d'erreur : CSFE_SVC_ERROR Method: NoOpRequest Détails :HTTP response status 503


My zimbra version:
8.0.2_GA_5569.FOSS SLES 11 SP2
Running on XenServer.
VM with 2 processors, 4GB RAM.

We have about 50 account on this server.

Any idea? Same problem? Many thanks and best regards.


EDIT:
A new error occured in the webui:

Une erreur réseau s'est produite.
method: [unknown]
msg: system failure: error while proxying request to target server: HTTP/1.1 503 Service Unavailable
code: service.FAILURE
detail: soap:Receiver
trace: qtp1290340102-1405:http://192.168.1.14:80/service/soap/...062e8049df55f9
request:

Body: {
MsgActionRequest: {
_jsns: "urn:zimbraMail",
action: {
id: "532649",
l: "2d238739-7dde-464c-8c07-ace516138b5a:61805",
op: "move"
}
}
},
Header: {
context: {
_jsns: "urn:zimbra",
account: {
_content: "myuser@mydomain.com",
by: "name"
},
authToken: "(removed)",
notify: {
seq: 129
},
session: {
_content: 1651,
id: 1651
},
userAgent: {
name: "ZimbraWebClient - FF18 (Mac)",
version: "8.0.2_GA_5569"
}
}
}

Auto-reply :)

I have found this.
http://www.zimbra.com/forums/announc...1-8-0-2-a.html

I will try a few days and report status here.

Did you have any luck?

Yes, the soap error was resolved.

But, i have a new problem, same that the high cpu java usage in 7.1.x, it's really strange and i can't find a solution for this.

I have no log, or i can't found it.. But, in the webui, i have a wheeling wheel, and if i try to read, move, delete a message, that take very long time.

If i make a top: i have two instance of java process with 20% processor.

This is my java localconfig:

zmlocalconfig | grep java
javamail_imap_debug = false
javamail_imap_enable_starttls = true
javamail_imap_test_timeout = 20
javamail_imap_timeout = 60
javamail_pop3_debug = false
javamail_pop3_enable_starttls = true
javamail_pop3_test_timeout = 20
javamail_pop3_timeout = 60
javamail_smtp_debug = false
javamail_smtp_enable_starttls = true
javamail_smtp_timeout = 60
javamail_zparser = true
javamail_zsmtp = true
mailboxd_java_heap_new_size_percent = 25
mailboxd_java_heap_size = 1024
mailboxd_java_options = -server -Djava.awt.headless=true -Dsun.net.inetaddr.ttl=60 -XX:+UseConcMarkSweepGC -XX:PermSize=128m -XX:MaxPermSize=128m -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCApplicationStoppedTime -XX:-OmitStackTraceInFastThrow -Djava.net.preferIPv4Stack=true
mailboxd_truststore = /opt/zimbra/java/jre/lib/security/cacerts
spnego_java_options = -Djava.security.krb5.conf=${mailboxd_directory}/etc/krb5.ini -Djava.security.auth.login.config=${mailboxd_direct ory}/etc/spnego.conf -Djavax.security.auth.useSubjectCredsOnly=false
zimbra_java_home = /opt/zimbra/java
zimbra_java_path = java
zimbra_zmjava_java_ext_dirs =
zimbra_zmjava_java_library_path =
zimbra_zmjava_options = -Xmx256m -Djava.net.preferIPv4Stack=true


Any idea? Would you like other log?..

Many thanks for your help and best regards.

Auto-reply one more time :)

I have solve this by changing the mailboxd_java_options as follow:

mailboxd_java_options = -server -Djava.awt.headless=true -Dsun.net.inetaddr.ttl=60 -XX:+UseConcMarkSweepGC -XX:PermSize=196m -XX:MaxPermSize=350m -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCApplicationStoppedTime -XX:-OmitStackTraceInFastThrow -Djava.net.preferIPv4St