Grouper Developers Forum

[Joy Veronneau <>]

Hi,

Related to our monster group of 190K members... we are thinking that  
we might need some sort of protection in the UI so that people are not  
allowed to use huge groups like this as part of a composite group.  It  
would work ok for the grouperdb, but when LDAPpc got around to  
updating the directory... well, maybe not so good..

Interested in your thoughts-

Joy

> Question 2.
>
> Our current AuthZ system has one monster group of 190K members.  I  
> have found that LDAPpc can not sync a group of this size, and fails  
> with the error "Broken pipe".  I am new to the Java/JNDI/DB  
> landscape, but the problem appears to be ...
>
> You can pile 200K hasMember entries into a BasicAttribute, but when  
> you hand that to createSubcontext, it goes boom, and not with any  
> exception which createSubcontext throws.
>
> I do not know the exact max size a BasicAttribute can be before  
> createSubcontext barfs, but my tests show it is somewhere around 95K  
> hasMember entries.  I am using Java version 1.5.0_07.
>
> I can keep appending, using modifyAttributes, after an initial write  
> of 95K entries, so I can get all the entries in there, but not using  
> LDAPpc.  Once they are all in there, a sync with LDAPpc should work,  
> as only the deltas will get used.
>
> I am curious to know if anyone else run into this situation, and if  
> so what solution was used.