Announcement Announcement Module
No announcement yet.
DefaultMessageListenerContainer and HibernateTransactionManager Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • DefaultMessageListenerContainer and HibernateTransactionManager

    Is it ok to use a HibernateTransactionManager within a DMLC on Webshpere

    Things work fine in my development setup but when deployed on unix boxes things work for a while and then the whole app hangs, requiring a reboot. If I take out the 'transactionManager' and 'sessionTransacted' property out of the equation the listener works just fine. I have some data to persist in the database (My app uses hibernate 3.0)

    here is my config,

    <bean id="transactionManager" class="org.springframework.orm.hibernate3.Hibernat eTransactionManager">
    <property name="sessionFactory"><ref bean="sessionFactory"/></property>

    <bean id="mxContractStatusListener" class=" istener" />

    <bean id="jmsContainer" class="org.springframework.jms.listener.DefaultMes sageListenerContainer102">
    <property name="connectionFactory" ref="jmsConnectionFactory"/>
    <property name="destinationName" value="jms/efpMxContractStatusReq" />
    <property name="destinationResolver" ref="jmsDestinationResolver"/>
    <property name="concurrentConsumers" value="1"/>
    <property name="maxConcurrentConsumers" value="1"/>
    <property name="cacheLevel" value="0"/>
    <property name="taskExecutor" ref="listenerTaskExecutor" />
    <property name="sessionTransacted" value="true"/>
    <property name="transactionManager" ref="transactionManager" />
    <property name="messageListener" ref="mxContractStatusListener" />
    Last edited by prempower; Oct 31st, 2008, 11:50 AM.