I think I partially narrowed down the cause of BAD JSON. The bandwidth. I said partially because sometimes I can't replicate it yet I was succeeded to do so just few seconds before.You see, instead of placing in DMZ part of my network's firewall, I placed Zimbra server in a remote colocation rack. I was starting to aware of bandwidth problem when it occured to me that it happened ocassionally when I use HSDPA modem. So, I built a test machine, connected to a multi-homed machine with linux bridge and CBQ traffic control, and that bridge connected to my laptop which act as requestor.My unconfirmed result is BAD JSON RESPONSE sometimes appeared when I instructed CBQ script to choke bandwidth down to 40Kbps and sometimes even 50kbps. I was using Advanced Mode of Zimbra Web client. But it was so sporadic that just few seconds after BAD JSON RESPONSE appeared, I was unable to replicate that error anymore. It left me scratching my head.Based on that partially successful (or partially failed) test, I tried to avoid BAD JSON error by placing traffic QoS based on my Zimbra's IP address for my network users. I think that this is (partially) solve questions from my original thread.  |