Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > General Zimbra > Announcements

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 03-10-2006, 11:50 AM
Zimbra Employee
 
Posts: 4,792
Default New developer builds

Just pushed new developer builds for all the platforms. Lots of little fixes and updates from the past 2 weeks. These builds have had little/no QA and are not an *official* release. We are running it as our internal mail currently.

The *big* change in this release is a new IMAP implementation based on Java NIO. This no longer requires 1 thread per connection. It also re-enabled IMAP IDLE which makes push email to mobile clients much faster.

IMAP NIO is off by default. To enable it please run:

$ tomcat stop
$ zmlocalconfig -e nio_imap_enable=true
$ tomcat start

Please let us know if you see any problems with this new IMAP impl.
__________________
Bugzilla - Wiki - Downloads - Offline Client
Reply With Quote
  #2 (permalink)  
Old 03-10-2006, 12:53 PM
Zimbra Consultant & Moderator
 
Posts: 20,314
Default

Another flawless upgrade, well done.

It seems to be a bit more snappy for response in the UI using FF, I guess there's some performance enhancements in there?

I've enabled IMAP NIO on my server, just out of interest what benefit does it give? The Mail Queue statistics look interesting in the Admin UI, will that be fully implemented in the next official release?
__________________
Regards


Bill

Last edited by phoenix; 03-10-2006 at 12:56 PM..
Reply With Quote
  #3 (permalink)  
Old 03-10-2006, 01:43 PM
Zimbra Employee
 
Posts: 4,792
Default

Yes the server has a few tweaks to speed up conversation loading and some popular queries(is:unread). We are always trying to find ways to cache and speed up the JS code. So you'll see fixes to that in most releases.

NIO removes the limitation that the current IMAP has which every connection takes it's own thread. Using NIO we now can handle multiple connections in a single thread. So for huge deployments 100's or 1000's of users will see much better memory usage (ie less). If you've only got a 10's of user's you may not see a huge difference. Of course the fact that IMAP IDLE is now back on.

NOTE: It seems under certain cases the new code will still lock-up with IMAP IDLE. We are looking at that now.
__________________
Bugzilla - Wiki - Downloads - Offline Client
Reply With Quote
  #4 (permalink)  
Old 03-11-2006, 05:12 PM
Former Zimbran
 
Posts: 5,606
Default dev build status

I noticed that you mentioned that there might be some bugs in the code that causes freezing.

Any updates?
Reply With Quote
  #5 (permalink)  
Old 03-11-2006, 06:15 PM
Zimbra Employee
 
Posts: 4,792
Default

It appears to be a rare case, again related to IMAP idle. If your worried about it just leave NIO off. It will be fixed in the next build.
__________________
Bugzilla - Wiki - Downloads - Offline Client
Reply With Quote
  #6 (permalink)  
Old 03-13-2006, 03:00 PM
Senior Member
 
Posts: 66
Default

Is the FC4 version missing the zmstatuslog, zmdisklog, and zmqueuelog files? I didn't have time to download another version to check but I was getting error emails saying they were missing. They are also being emailed to zimbra@mydomain.com account (which doesn't exist). I copied them from a backup (ga 160) and everything seems to be ok now.
Reply With Quote
  #7 (permalink)  
Old 03-13-2006, 03:03 PM
Zimbra Employee
 
Posts: 2,103
Default

Probably a bug - check the crontab, which is probably looking for them in /opt/zimbra/bin, and change that to libexec, which is where they should now be.
Reply With Quote
  #8 (permalink)  
Old 03-13-2006, 03:12 PM
Senior Member
 
Posts: 66
Default

Quote:
Originally Posted by marcmac
Probably a bug - check the crontab, which is probably looking for them in /opt/zimbra/bin, and change that to libexec, which is where they should now be.
That's what it was and the files were in libexec. All good now Thanks
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.