Question

I have the following config.

<bean id="abcManager" parent="TxProxyTemplate">
    <property name="target">
        <bean class="com.x.y.AbcManagerImpl">
          <property name="abcDAO" ref="abcDAO"/>
          <property name="xyzManager" ref="xyzManager"/>
        </bean>
    </property>
</bean>

<bean id="xyzManager" parent="TxProxyTemplate">
    <property name="target">
        <bean class="com.x.y.XyzManagerImpl">
          <property name="abcDAO" ref="abcDAO"/>
          <property name="anotherManager" ref="anotherManager"/>
        </bean>
    </property>
</bean>

<bean id="anotherManager" parent="TxProxyTemplate">
    <property name="target">
      <bean class="com.x.y.AnotherManagerImpl">
        <property name="abcDAO" ref="abcDAO"/>
        <property name="oneMoreManager" ref="oneMoreManager"/>
      </bean>
    </property>
</bean>

What is the issue with the following configuration? will having the same DAO at the different levels cause concurency issues?

We found that we get lots of weblogic connection releases when we have high load.

How is this related to the connection release issue?

We use Hibernate for DAO operations.

Answer 1

First, analyse the logs to see when spring creates and closes transactions.
Set the logger for org.springframework.transaction to DEBUG for this.

Next my guess is you need to examine your @Transactional annotations (which I assume you use on your managers (=services?). Make sure the propagation is set correctly because this might be related to your issue (hard to say without seeing your manager’s code of course).