Constant Timeouts on IMS5.2p1

Constant Timeouts on IMS5.2p1

We currently have a major issue with IMS5.2p1 running with IDS5.1. Users who make IMAP connections keep getting asked for their username and password every so often. Also a lot of them get a message saying their IMAP connection has timed out. This happens with pretty much all clients including MS Outlook, Outlook Express, Netscape Messenger and Evolution. Has anyone else seen this problem before, and can someone please help me eradicate it.

Thanks

Ali

[524 byte] By [ALI-ABEDI] at [2007-11-25 9:03:21]
# 1
One thing to check is make sure that your ldap connection timeout is set to 0 (unlimited). If imap loses it's ldap connection the user will have to log back in.You can check this in the console.
navin504 at 2007-7-1 16:00:14 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 2
Thanks for your reply, where can I find this using the command line on solaris?Thanks in advance..
ALI-ABEDI at 2007-7-1 16:00:14 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 3

You cant really access it via command line editor. Since the directory now stores its config info in ldap you would either need to use the java console to change it, or go into the ldap directory and under cn=config make sure that nsslapd-idletimeout is set to 0

You can do this with ldapsearch or using an ldap browser

navin504 at 2007-7-1 16:00:14 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 4
Thanks a lot for that.. will try it asap.
ALI-ABEDI at 2007-7-1 16:00:14 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 5
Unfortunately, this is already set to 0 for my ldap replicas and my ldap master.
ALI-ABEDI at 2007-7-1 16:00:14 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 6

Three things to ckeck:

1. Do you have a firewall between your server and clients? If so, it may be set to close idle connections too agressively.

2. Is the IMAP idle timeout set to something other than 30 minutes on your server? It should be left at 30.

3. You wouldn't by chance be using Resonate for load balancing?

Brian Williams at 2007-7-1 16:00:14 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 7

I have experienced the exact same issue. The problem was in the firewall. Since the mail server is in the DMZ and the clients are on the LAN side, all traffic passes through the firewall.

I discovered that the firewall had a timeout of 5 minutes! This of course overrode any setting in iMS with regard to timeouts. Changing the firewall's value to something more realistic solved the problem.

--Joel

Joel Miles at 2007-7-1 16:00:14 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...