I have spent some time this morning trying to gather more information. Previous to your post, it hadn’'t occured to me to check the cpu utilization on the windows box running the Jive server. I was maily concerned about the cpu on our Netware server. I will add that, today, I have been able to add users to newly created groups without any problems.
This morning, for the purpose of testing, I created a new group called Test. This group is set to show in all users’’ rosters. I added an ldap user to this group. This particular user has never logged into the jive server to do instant messaging. The group sets up and is displayed correctly in users’’ rosters.
When I try to delete the group using the admin console, the cpu utilization on the jive server / windows box jumps to and stays around 50-55%. The cpu utilization on the ldap / novell server jumps up to 15-20%. Both servers continue with this utilization until I stop the jive messenger service.
In your post, you asked if the procedure is just taking too long to complete, or if it never stops. In reality, I guess I don’‘t know if it would ever stop. In my testing this morning, I gave it about four minutes before I finally killed the service. In my mind, if it hasn’‘t stopped by then, it’'s not going to until something catastrophic happens.
I turned on debug output on the jive server while I attempted to delete the group. The output is this:
.03.17 10:35:56 Creating a DirContext in LdapManager.getContext()…
2005.03.17 10:35:56 Created hashtable with context values, attempting to create context…
2005.03.17 10:35:56 … context created successfully, returning.
2005.03.17 10:40:43 Creating a DirContext in LdapManager.getContext()…
2005.03.17 10:40:43 Created hashtable with context values, attempting to create context…
2005.03.17 10:40:43 … context created successfully, returning.
What you see above just repeats from 10:35:56 to 10:40:43. I can see in the info.log that at 10:40:43 the jive server halted (when I killed the service). One thing I noted was that I didn’'t hit the delete button in the browser until 10:36:25 (jive server time). However, there seems to be no difference in the debug output beginning at that time.
I don’'t know of a way to actually see the queries that are being made against the ldap server, short of packet sniffing. Anything else you can suggest before having to go that far?