동시 환경의 Ehcache ReentrantReadWriteLock

Question

ehcache 2.1.0 라이브러리가있는 Websphere 7.x의 생산적인 환경에서 문제점이 있습니다. 웹 컨테이너의 스레드는 모두 캐시에서 상담 또는 삽입을 기다리고 있습니다. 프로그래밍 특별한 무관

이

NULL 
3XMTHREADINFO  "WebContainer : 11" J9VMThread:0x00000000C7C10300, j9thread_t:0x0000010043913FB0, java/lang/Thread:0x00000000507623F0, state:P, prio=5 
sun.misc.Unsafe.park(Native Method) 
java.util.concurrent.locks.LockSupport.park(LockSupport.java:182) 
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:822) <2> 
java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:907) 
net.sf.ehcache.store.compound.Segment.put(Segment.java:402) 
net.sf.ehcache.store.compound.CompoundStore.put(CompoundStore.java:132) 
net.sf.ehcache.Cache.putInternal(Cache.java:1247) <2> 
org.springframework.cache.ehcache.EhCacheCache.put(EhCacheCache.java:70) 
xxx.yyy.fac.security.userdetails.GaiaLdapAuthoritiesPopulator.putElementCache(GaiaLdapAuthoritiesPopulator.java:466) <4> 
xxx.yyy.dgtp.gaiafrontend.core.filters.preauth.GaiaGrantedAuthoritiesWebAuthenticationDetails.buildDetails(GaiaGrantedAuthoritiesWebAuthenticationDetails.java:32) <1> 
org.springframework.security.web.authentication.preauth.AbstractPreAuthenticatedProcessingFilter.doAuthenticate(AbstractPreAuthenticatedProcessingFilter.java:114) <1> 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) 
org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) 
org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) 
org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:184) <1> 
org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) <1> 
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) 
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:125) 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:322) 
xxx.yyy.dgtp.gaiafrontend.core.web.filters.JsonDeserializerFilter.doFilterChain(JsonDeserializerFilter.java:109) <1> 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) 
xxx.yyy.dgtp.gaiafrontend.core.filters.userinfo.UserInfoFilter.followWithTheRequestChain(UserInfoFilter.java:106) <1> 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) 
xxx.yyy.dgtp.gaia.commons.web.filters.RequestResponseWrapperFilter.doFilter(RequestResponseWrapperFilter.java:69) 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) 
org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:83) 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) 
xxx.yyy.dgtp.gaiafrontend.core.web.filters.ResponseHeadersFilter.doFilter(ResponseHeadersFilter.java:55) 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) 
org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:184) <1> 
org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) <1> 
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) 
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:125) 
org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) 
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) 
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:125) <1> 
com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908) 
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:939) <1> 
com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:181) 
com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3994) 
com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276) 
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:945) 
com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592) 
com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:191) 
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:453) <3> 
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214) <1> 
com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175) 
com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) 
com.ibm.io.async.AsyncChannelFuture$1.run(AsyncChannelFuture.java:205) 
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1660)  

내가 캐시에 넣어으로 Ehcache에 추상화 계층 및 얻을 수있는 코드 /로 스프링을 사용

이

모든 웹 컨테이너 스레드가 대기하고있는 순간에 덤프입니다.

다음과 같이 캐시의 구성은 다음과 같습니다

@Bean 
    public EhCacheManagerFactoryBean cacheFactoryBean() { 

     EhCacheManagerFactoryBean ehCacheManagerFactoryBean = new EhCacheManagerFactoryBean(); 
     ehCacheManagerFactoryBean.setConfigLocation(new ClassPathResource("gaia-cache-ldap.xml")); 
     return ehCacheManagerFactoryBean; 

    } 

    @Bean 
    public CacheManager cacheManagerLdap() { 
     CacheManager cacheManager = new EhCacheCacheManager(cacheFactoryBean().getObject()); 
     return cacheManager; 

    } 

캐시에 액세스 할 수있는 코드 :

private void getMemberOfRecursive(String group, ConcurrentMap<String, String> groupsCollector) { 

     if (group != null) { 
      if (existInCache(group)) { 
       log.debug("Group: {} exist in cache. No query executing", group); 
       groupsCollector.put(group, group); 
       Set<String> groups = (Set<String>) getElementCache(group).get(); 
       for (String newGroup : groups) { 
        getMemberOfRecursive(newGroup, groupsCollector); 
       } 
      } else { 
       String cn = getCnFromDn(group); 
       String filter = MessageFormat.format(getFilterGroupRecursive(), cn); 
       String baseDN = group.substring(group.indexOf(",") + 1); 
       groupsCollector.put(group, group); 

       log.debug("Executing recursive query with baseDN: {} " + 
         " and filter {}: ", baseDN, filter); 
       Set<String> groups = 
         getLdapTemplate().searchForSingleAttributeValues(
           baseDN, filter, new String[]{}, getRetrievesAttributes()); 
       putElementCache(group, groups); 
       for (String newGroup : groups) { 
        getMemberOfRecursive(newGroup, groupsCollector); 
       } 
      } 

     } 

으로 Ehcache 설정 파일 : 마지막으로

<ehcache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  xsi:noNamespaceSchemaLocation="ehcache.xsd" updateCheck="false" monitoring="autodetect"  dynamicConfig="true"> 
    <diskStore path="java.io.tmpdir" /> 
    <defaultCache maxElementsInMemory="3000" eternal="false" timeToIdleSeconds="1200" 
        timeToLiveSeconds="1200" overflowToDisk="true" maxElementsOnDisk="10000" 
        diskPersistent="false" diskExpiryThreadIntervalSeconds="120" 
        memoryStoreEvictionPolicy="LRU"/> 
    <cache name="groupsldap" maxElementsInMemory="3000" eternal="true" overflowToDisk="false" 
      memoryStoreEvictionPolicy="LRU"/> 

</ehcache> 

Answer 1

, 그것은이었다 생산 오류를 재현 할 수 있습니다. 이 오류는 적어도 Active Directory 그룹의 사용자에게 있었던 상호 그룹과 관련이있는 것으로 보입니다. 지난 주에 캐시를 사용하지 않고이 오류를 건너 뛴 덕분에 더 자세히 분석 할 수있었습니다.이 경우 대기 상태의 스레드로 ldap 연결 풀이 고갈되는 stackoverflowerror가 관찰되었습니다.

일단이 문제로 인해 이전에 방문한 그룹을 제거하는 픽스가 발견되면 이번에는 캐시를 사용하여 로컬 테스트에서 재현되었으며 웹 컨테이너의 스레드 풀을 비헤이비어로 포화시켜야합니다 생산에서 발견 된 것과 유사합니다.