Uploaded image for project: 'Spring Integration'
  1. Spring Integration
  2. INT-4189

JMSOutbound Gateway Does Not Terminate all replyListener Container Threads

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Works as Designed
    • Affects Version/s: 2.2.7
    • Fix Version/s: None
    • Component/s: JMS Support
    • Environment:
      10 server cluster...Window Server...JBoss EAP 5.2

      Description

      We have an application with around 75 partitioned steps spread around 100 jobs. Our configuration for the outbound gateway is:

      <int-jms:outbound-gateway 
          id="outbound-gateway_1"
          auto-startup="true" 
          connection-factory="jmsConnectionFactory"
          request-channel="jms.requests_1"
          request-destination="jms.requestsQueue"
          reply-channel="jms.reply_1"
          reply-destination="jms.repliesQueue"
          receive-timeout="${timeout}"
          correlation-key="JMSCorrelationID" >
          <int-jms:reply-listener receive-timeout="1000"/>
      </int-jms:outbound-gateway>
      

      When autostart="true" we see the replyListener thread for each outbound gateway. To remove this extra load and resource consumption, we change to autostart="false" and added a step listener for the partitioned step the start and stop the gateway in the beforeStep and afterStep methods. At server startup the replyListener threads are not there as expected. They appear during step execution but are not removed after the call to stop on the outbound gateway (even after waiting a prolonged period).

      Is something else needed to cleanup the replyListener?

        Attachments

          Activity

            People

            Assignee:
            grussell Gary Russell
            Reporter:
            mjrother Mike Rother
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: