Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-5741

Intermittent "The CacheManager has been shut down. It can no longer be used." in JBWS testsuite

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.1.0.DR11
    • 7.0.2.CR1, 7.1.0.DR2
    • Web Services
    • None
    • Hide

      just run the upstream testsuite, eg:
      mvn -Pwildfly1000 integration-test

      Show
      just run the upstream testsuite, eg: mvn -Pwildfly1000 integration-test

      After upgrade to JBWS 5.1.5.Final & CXF 3.1.6 intermittent failures started to occur on client side within these tests from JBossWS testsuite:
      MultipleClientsSignEncryptTestCase
      WSSecurityPolicyExamples21xTestCase
      WSSecurityPolicyExamples22xTestCase
      WSSecurityPolicyExamples23xTestCase

      Example stacktrace:

      javax.xml.ws.soap.SOAPFaultException: The CacheManager has been shut down. It can no longer be used.
	at net.sf.ehcache.CacheManager.checkStatus(CacheManager.java:1623)
	at net.sf.ehcache.CacheManager.addCacheIfAbsent(CacheManager.java:1939)
	at org.apache.cxf.ws.security.tokenstore.EHCacheTokenStore.<init>(EHCacheTokenStore.java:66)
	at org.apache.cxf.ws.security.tokenstore.EHCacheTokenStoreFactory.newTokenStore(EHCacheTokenStoreFactory.java:37)
	at org.apache.cxf.ws.security.tokenstore.TokenStoreUtils.getTokenStore(TokenStoreUtils.java:57)
	at org.apache.cxf.ws.security.wss4j.policyhandlers.AbstractBindingBuilder.getTokenStore(AbstractBindingBuilder.java:323)
	at org.apache.cxf.ws.security.wss4j.policyhandlers.SymmetricBindingHandler.<init>(SymmetricBindingHandler.java:99)
	at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessageInternal(PolicyBasedWSS4JOutInterceptor.java:187)
	at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:109)
	at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:96)
	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
	at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514)
	at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423)
	at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324)
	at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277)
	at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
	at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139)
	at com.sun.proxy.$Proxy271.sayHello(Unknown Source)
	at org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples22xTestCase.test224(WSSecurityPolicyExamples22xTestCase.java:188)

      It is very rare to reproduce indicating some sort of race condition, probably in CXF/WSS4J integration.
      I noticed it is present also in upstream CI runs, eg.:
      http://jbossws-qa.jboss.org:8180/jenkins/job/CXF-CORE-AS-10.0.0/10/testReport/
      http://jbossws-qa.jboss.org:8180/jenkins/job/CXF-CORE-AS-11.0.0/6/testReport/

              rhn-support-asoldano Alessio Soldano
              jbliznak@redhat.com Jan Blizňák
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: