We are using Lotus Notes LDAP custom for our authentication. Lately, around 12:30 p.m. to 1 p.m., no one can log in - it just hangs and does note error out. The query load at that time is fairly low and I have not found any processes running consistently during this time period for this duration.
Windows 2003 server, BO clustered environment, Tomcat memory 512/1024, each server has 4GB RAM
During this time period, only about 25 scheduled reports are running including a simple 3 second report we use for monitoring. This report takes 5 minutes during this “slow” time period. The database it is accessing is not under load and responds well.
I will check the timeout settings but during that time period I have verified that there are zero logins which means that there is not a long list
of users trying to get in all at once.
As info, our LDAP has been problematic from the start but never an issue like this before.
NEW INFO: When this issue occurs, the primary CMS iin the cluster is running constantly at 100% of one CPU or higher. When the issue stops occurring, the following message appears in WCA log:
This is coming from someone who doesn’t do LDAP but does Windows AD, so I apologize if this doesn’t apply.
Does BOE update your authentication automatically at that specific time? I don’t see what version you’re running but I think 3.1 can be set up to update at a specific time. I’m fairly certain XIr2 can’t be scheduled.
Good thought - it does seem like some internal BO process run amok. We are XI R2 which I believe does updates after a preset number of hours of “idle time” or if you manually hit the update button in CMC>Authentication>LDAP. Our environment is busy all throughout the day. It occurs “almost” every day at about 12:34 p.m. My next test will be to disable schedules at 12 or 12:15 p.m. to see if a certain scheduled report is causing havoc with the system.