That is strange. You say the issue gets resolved when tomcat restarts? Do you know if the server "ldap.com.test.net" has a dynamic ip? I am guessing that this server has a dynamic IP and when you restart tomcat is able to route to this LDAP for 2 weeks or so. I am just guessing though.
Can you try moving the server name etc into a properties file instead of using <Resource ...> and see if this issue disappears?
Joined: Mar 06, 2009
Thanks for your reply. But I doubt how does it will resolve the problem if we move this ldap base property to a .properties file. Because we are using this <resource>.... </resource> configs as just like context. I have my own ldapfactory class where I'm reading this server.xml file and making a map and using that map in my authorisation class. Could please throw some more light on your point.