Show Table of Contents
4.4. CachedConnectionManager
The servlet container chapter described the cached connection manager, what it does, and how you can remove it. This section shows how to remove it from the EJB 3 container, and a short note about how you can remove it from the old EJB 2.x container as well. Note that the
minimalconfiguration does not contain the EJB 3 container.
The configuration for the cached connection manager, in the EJB 3 container, is
ejb3-interceptors-aop.xml, in the directory: JBOSS_EAP_DIST/jboss-as/server/<PROFILE>/deploy.
To remove the cached connection manager, comment or remove the following two lines from the configuration file.
<interceptor factory="org.jboss.ejb3.connectionmanager.CachedConnectionInterceptorFactory" scope="PER_CLASS"/> <interceptor-ref name="org.jboss.ejb3.connectionmanager.CachedConnectionInterceptorFactory"/>
The configuration of the EJB 2.x container is in
standardjboss.xml, in the directory: JBOSS_EAP_DIST/jboss-as/server/<PROFILE>/conf. Note that the minimal configuration, does not contain the EJB 2.x container.
To remove the cached connection manager, comment or remove the following line from each container configuration (there are many in the file).
<interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.