We are encountering a problem related to UserBrowser when the number of users in the User Directory are large. Right now, when we loaded 1000 users into the LDAP directory the following error is displayed on the browser: Error rendering Velocity template: /portlets/html/user-browser ..vm: Unable to find resource '/portlets/html/user-browser.vm' In addition, the following errors show up in velocity.log velocity.log:2003-03-26 16:00:47,411 - ResourceManager : found /portlets/html/user-browser.vm with loader org.apache.velocity.runtime.resource.loader.FileResourceLoader velocity.log:2003-03-26 16:00:47,412 - RHS of #set statement is null. Context will not be modified. /portl ets/html/user-browser.vm [line 10, column 1] velocity.log:2003-03-26 16:00:47,413 - RHS of #set statement is null. Context will not be modified. /portl ets/html/user-browser.vm [line 11, column 1] velocity.log:2003-03-26 16:00:47,416 - RHS of #set statement is null. Context will not be modified. /portl ets/html/user-browser.vm [line 12, column 1] velocity.log:2003-03-26 16:00:47,417 - Left side ($filter_type) of '==' operation has null value. If a ref erence, it may not be in the context. Operation not possible. /portlets/html/user-browser.vm [line 18, col umn 60] velocity.log:2003-03-26 16:00:47,417 - Left side ($filter_type) of '==' operation has null value. If a ref erence, it may not be in the context. Operation not possible. /portlets/html/user-browser.vm [line 19, col umn 60] We are using jetspeed1.4b3 version with IPlanet Directory Server 5.1 as Jetspeed User Repository. It seems to me that something is going wrong when the number of users exceed a certain limit/timeout. Is there any configurable parameter that governs this kind of limit? If not, is this a bug? If so, is there any this bug is fixable. We did not any see any problems when the number of users were around 900. Any hints in solving this problem are greatly appreciated. Thanks Prasad Kunchakarra [EMAIL PROTECTED]