Messaging server "testing" config directory instance
So I'm noticing a lot of binds and searches from Messaging to it's config DS instance and was just curious as to if there's a pattern? My production box seems to test anywhere from every minute to as long as 4 minutes apart, however a test box (at the same patch level as prod) it only tests every 10 minutes (or right along with msprobe). The prod box has the same configutil for msprobe so I can't figure out why the prod messaging is continuously doing this:
[06/Feb/2007:09:44:59 -0500] conn=1504753 op=0 msgId=1 - BIND dn="cn=msg-config, cn=Sun ONE Messaging Suite, cn=Server Group, cn=mail.domain.edu, ou=domain.edu, o=NetscapeRoot" method=128 version=2
[06/Feb/2007:09:44:59 -0500] conn=1504753 op=0 msgId=1 - RESULT err=0 tag=97 nentries=0 etime=0 dn="cn=msg-config,cn=sun one messaging suite,cn=server group,cn=mail.domain.edu,ou=domain.edu,o=netscaperoot"
[06/Feb/2007:09:44:59 -0500] conn=1504753 op=1 msgId=2 - SRCH base="cn=configuration,cn=msg-config,cn=sun one messaging suite,cn=server group,cn=mail.domain.edu,ou=domain.edu,o=netscaperoot" scope=2 filter="(objectClass=*)" attrs=ALL
[06/Feb/2007:09:44:59 -0500] conn=1504753 op=1 msgId=2 - RESULT err=0 tag=101 nentries=39 etime=0
[06/Feb/2007:09:44:59 -0500] conn=1504753 op=2 msgId=3 - UNBIND
[06/Feb/2007:09:44:59 -0500] conn=1504753 op=2 msgId=-1 - closing - U1
[06/Feb/2007:09:44:59 -0500] conn=1504753 op=-1 msgId=-1 - closed.
Sure there's a LOT more traffic to production than test, but I wasn't aware that it was traffic dependent. This is also a backend store - the two front ends we have which are config'd for MMP/MEM do not look for the config ds other than at startu/shutdown.
Version:
Sun Java(tm) System Messaging Server 6.2-7.05 (built Sep 5 2006)
libimta.so 6.2-7.05 (built 12:18:44, Sep 5 2006)
Is this typical? Is this configurable to stop it from checking so frequently/sporadically? Is this something I need to worry about?
