I am running into what looks like the exact same problem with version 2.7.0. Is
there any chance that 2.7.0 missed the fix?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4207426#4207426
Reply to the post :
bdaw wrote : I improved the code a bit and with my test number of open
connections always remains low and related to poolingMaxsize. Could you try it
out?
|
http://anonsvn.jboss.org/repos/portal/modules/identity/branches/JBP_IDENTITY_BRANCH_1_0/
|
|
Ok I'll give it a try soon. I've
I improved the code a bit and with my test number of open connections always
remains low and related to poolingMaxsize. Could you try it out?
http://anonsvn.jboss.org/repos/portal/modules/identity/branches/JBP_IDENTITY_BRANCH_1_0/
View the original post :
btw. I'm not sure your take on TIME_WAIT is correct. Creating a connection is
costly so keeping the pool of open ones and reuse gives performance gain.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4145100#4145100
Reply to the post :
and one more thing for the configuration. You are right that timeout setting
for LDAPConnectionContext doesn't work. It seesm that these option must be
specified in java opts as you did:
http://java.sun.com/products/jndi/tutorial/ldap/connect/config.html
anonymous wrote : Note that these are
created http://jira.jboss.com/jira/browse/JBPORTAL-1996
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4145169#4145169
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4145169
___
This indeed looks like a bug. Could you create a JIRA with a patch and
reference to this thread?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4141948#4141948
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4141948
Ok, I will do that ASAP.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4141977#4141977
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4141977
___
jboss-user mailing list
Quick update:
Looking at the source the problem seems to be with method searchUsers in class
LDAPExtUserModuleImpl. I added some debugging to verify that
ldapContext.close() is been called - and it is.
Having pooling logging turned on I can see that even though ldapContext.close()
is called
Update 2:
I think I found at least one part of the code that is causing problems:
It is findUserByUserName(String userName) in LDAPExtUserModuleImpl (that uses
searchUsers).
I changed the code:
SearchResult res = (SearchResult)sr.iterator().next();
| Context ctx =
Thanks for the reply.
I tried with the following settings:
datasource
| nameLDAP/name
|
service-nameportal:service=Module,type=LDAPConnectionContext/service-name
| classorg.jboss.portal.identity.ldap.LDAPConnectionContext/class
| config
|
Portal uses standard JNDI pooling. For the JNDI configuration look here:
http://java.sun.com/products/jndi/tutorial/ldap/connect/pool.html
http://java.sun.com/products/jndi/tutorial/ldap/connect/config.html
Options set in ldap_identity-config.xml and standardidentity-config.xml are
mapped
12 matches
Mail list logo
