Lot of SyncRequest from BES -- HELP!!

[stich86]

Hi guys,

after the upgrade to Zimbra 5.0.9, my mailbox.log print every second a lot of this messages caused by BES..

2008-08-25 15:39:10,575 INFO [btpool0-502] [name=1@mydomain.net;aname=besadmin@mydomain.net;mi d=11;ip=10.100.2.87;ua=ZimbraConnectorForBES/5.0.2582.5;] soap - SyncRequest
2008-08-25 15:39:10,933 INFO [btpool0-502] [name=2@mydomain.net;aname=besadmin@mydomain.net;mi d=13;ip=10.100.2.87;ua=ZimbraConnectorForBES/5.0.2582.5;] soap - SyncRequest
2008-08-25 15:39:11,917 INFO [btpool0-502] [name=3@mydomain.net;aname=besadmin@mydomain.net;mi d=14;ip=10.100.2.87;ua=ZimbraConnectorForBES/5.0.2582.5;] soap - SyncRequest
2008-08-25 15:39:11,972 INFO [btpool0-502] [name=4@mydomain.net;aname=besadmin@mydomain.net;mi d=23;ip=10.100.2.87;ua=ZimbraConnectorForBES/5.0.2582.5;] soap - SyncRequest
2008-08-25 15:39:12,028 INFO [btpool0-502] [name=5@mydomain.net;aname=besadmin@mydomain.net;mi d=24;ip=10.100.2.87;ua=ZimbraConnectorForBES/5.0.2582.5;] soap - SyncRequest
2008-08-25 15:39:12,091 INFO [btpool0-497] [name=6@mydomain.net;aname=besadmin@mydomain.net;mi d=36;ip=10.100.2.87;ua=ZimbraConnectorForBES/5.0.2582.5;] soap - SyncRequest
2008-08-25 15:39:12,240 INFO [btpool0-497] [name=7@mydomain.net;aname=besadmin@mydomain.net;mi d=17;ip=10.100.2.87;ua=ZimbraConnectorForBES/5.0.2582.5;] soap - SyncRequest
2008-08-25 15:39:12,328 INFO [btpool0-497] [name=8@mydomain.net;aname=besadmin@mydomain.net;mi d=28;ip=10.100.2.87;ua=ZimbraConnectorForBES/5.0.2582.5;] soap - SyncRequest
2008-08-25 15:39:13,007 INFO [btpool0-497] [name=9@mydomain.net;aname=besadmin@mydomain.net;mi d=8;ip=10.100.2.87;ua=ZimbraConnectorForBES/5.0.2582.5;] soap - SyncRequest
2008-08-25 15:39:13,212 INFO [btpool0-497] [name=10@mydomain.net;aname=besadmin@mydomain.net;m id=26;ip=10.100.2.87;ua=ZimbraConnectorForBES/5.0.2582.5;] soap - SyncRequest
2008-08-25 15:39:13,297 INFO [btpool0-497] [name=11@mydomain.net;aname=besadmin@mydomain.net;m id=9;ip=10.100.2.87;ua=ZimbraConnectorForBES/5.0.2582.5;] soap - SyncRequest
2008-08-25 15:39:13,347 INFO [btpool0-497] [name=12@mydomain.net;aname=besadmin@mydomain.net;m id=35;ip=10.100.2.87;ua=ZimbraConnectorForBES/5.0.2582.5;] soap - SyncRequest
2008-08-25 15:39:13,394 INFO [btpool0-497] [name=13@mydomain.net;aname=besadmin@mydomain.net;m id=19;ip=10.100.2.87;ua=ZimbraConnectorForBES/5.0.2582.5;] soap - SyncRequest
2008-08-25 15:39:13,447 INFO [btpool0-497] [name=14@mydomain.net;aname=besadmin@mydomain.net;m id=18;ip=10.100.2.87;ua=ZimbraConnectorForBES/5.0.2582.5;] soap - SyncRequest
2008-08-25 15:39:13,627 INFO [btpool0-497] [name=15@mydomain.net;aname=besadmin@mydomain.net;m id=12;ip=10.100.2.87;ua=ZimbraConnectorForBES/5.0.2582.5;] soap - SyncRequest
2008-08-25 15:39:14,171 INFO [btpool0-500] [name=16@mydomain.net;aname=besadmin@mydomain.net;m id=37;ip=10.100.2.87;ua=ZimbraConnectorForBES/5.0.2582.5;] soap - SyncRequest

what's up?!?

seems correlated to the same problem of other BES that cannot inizialiting the calendar, but the other two users on new BES doesn't have this error

please help me..

[alee]

Hi guys,

after the upgrade to Zimbra 5.0.9, my mailbox.log print every second a lot of this messages caused by BES..



what's up?!?

seems correlated to the same problem of other BES that cannot inizialiting the calendar, but the other two users on new BES doesn't have this error

please help me..

the mechanism used to issue sync requests on BES are through the waitset API. BES is notified by the server if a there is a change to one of the mailboxes that it is servicing. if that is the case, BES issues a sync request for that user. if you are seeing a lot of sync requests, it is because the accounts that BES is servicing are seeing a lot of changes.

if your other BES server is not seeing the same traffic, it is servicing less users or the usage patterns of the users are different.

[stich86]

the mechanism used to issue sync requests on BES are through the waitset API. BES is notified by the server if a there is a change to one of the mailboxes that it is servicing. if that is the case, BES issues a sync request for that user. if you are seeing a lot of sync requests, it is because the accounts that BES is servicing are seeing a lot of changes.

if your other BES server is not seeing the same traffic, it is servicing less users or the usage patterns of the users are different.

it's impossibile that all the users have a lot of change every second..

i've restarted all services on the old bes and this error disappear..

very strange