Announcement Announcement Module
Collapse
No announcement yet.
Task scheduler threads running for ever Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Task scheduler threads running for ever

    The task scheduler threads created for pollers dont seem to be destroyed when the application is undeployed from the server.

    I close the spring application context in the ServletContextListener.contextDestroyed() method.
    What else should be done to destroy these task scheduler threads?

  • #2
    Can you show how you've configured the TaskExecutor? The implementations provided by Spring are all also implementations of DisposableBean and have their destroy() methods called when the context is closed.

    Comment


    • #3
      hi Mark. thanks for your response.
      I believe task executor is not mandatory for a poller configuration. I haven't configured one.

      Here is my poller configuration:
      Code:
      	<si:chain input-channel="EmployeeUpdatedEventQ" output-channel="EmployeeUpdatedEventPubSubChnl">
      		<si:poller fixed-rate="30000" max-messages-per-poll="1">
      			<si:transactional transaction-manager="txManager" />
      		</si:poller>  
      		<si:filter ref="GlobalMsgSelector" />
      	</si:chain>

      Comment


      • #4
        Okay, and what are you polling from? What is on the other side of "EmployeeUpdatedEventQ"?

        Comment


        • #5
          Queue backed by a jdbc message store
          Here is the Q config:
          Code:
                  <jdbc:message-store id="EmployeeUpdatedEventMsgStore" data-source="GlobalMsgStoreDS" region="EMPLOYEE_UPD_EVNT" />
          
          	<si:channel id="EmployeeUpdatedEventQ">
          		<si:queue message-store="EmployeeUpdatedEventMsgStore" capacity="10" /> 
          	</si:channel>

          Comment

          Working...
          X