Weblogic does not cache LDAP

I have a web application configured using JSF 2.1 and JEE 6 running on a WebLogic 12.1.2 server with open access for authentication. I noticed that loading any page in the application causes several BIND requests for LDAP - every time!

I read most of the material and set up the LDAP provider in Weblogic, so almost any cache that I could find is activated. In particular, I installed

  • [x] Cache Enabled
  • Cache Size: 10240
  • TTL Cache: 300
  • GUID Attribute: entryUUID

I also double-checked that the entryUUID attribute exists. I'm not very knowledgeable about either WebLogic or LDAP, but I read almost any page on setting up the cache, but there are still as many LDAP requests (yes, I restarted the servers after the changes.)

I would appreciate any help, understanding or wild suggestions as to what might be causing or how I can debug this problem further. I'm not too sure which configuration files to join, but if something is needed, I am happy to provide it.

LDAP queries are as follows:

# journalctl -u slapd # … many of these … Sep 16 23:06:03 server.org slapd[15038]: daemon: read active on 13 Sep 16 23:06:03 server.org slapd[15038]: daemon: epoll: listen=7 active_threads=0 tvp=zero Sep 16 23:06:03 server.org slapd[15038]: daemon: epoll: listen=8 active_threads=0 tvp=zero Sep 16 23:06:03 server.org slapd[15038]: conn=1109 op=32 BIND anonymous mech=implicit ssf=0 Sep 16 23:06:03 server.org slapd[15038]: conn=1109 op=32 BIND dn="tpid=NQ00000013,ou=people,dc=de,dc=foobiz,dc=com" method=128 Sep 16 23:06:03 server.org slapd[15038]: conn=1109 op=32 BIND dn="tpid=NQ00000013,ou=people,dc=de,dc=foobiz,dc=com" mech=SIMPLE ssf=0 Sep 16 23:06:03 server.org slapd[15038]: conn=1109 op=32 RESULT tag=97 err=0 text= Sep 16 23:06:03 server.org slapd[15038]: daemon: activity on 1 descriptor Sep 16 23:06:03 server.org slapd[15038]: daemon: activity on: 
+6
source share
1 answer

I figured out the problem and WebLogic is not to blame. Our application seems to use the rather complex concept of calling remote EJBs, where it creates its own proxy, saves JNDI information, and does a JNDI lookup every time the method is called.

Therefore, even bean caching would not help. Of course, this bypasses any caching mechanisms and thus leads to several LDAP connections with each request.

+1
source

All Articles