Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-3148

Camel pooled threads never die when defined in SwitchYard

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • jboss-fuse-6.3
    • None
    • SwitchYard
    • None
    • (As observed in Fuse Service Works 6.0GA). Please make sure this is not present in Fuse 6.2.

    • Hide
      • Deploy the enclosed sample application, change the file binding to something friendly for your machine.
      • Take a thread dump right after application deployment. Grep it for the thread name (i.e. jstack $PID | grep I048)
      • Note the threads. See the name 'I048' assigned in the RouteBuilder.
      • Drop a few files, see the thread count go up. Note the 'KeepAliveTime' param set on the profile. Set this to whatever you'd like, it seems not to change anything.
      • Undeploy the SwitchYard app. Continue monitoring with jstack, the custom threads keep on waiting on condition.
      Show
      Deploy the enclosed sample application, change the file binding to something friendly for your machine. Take a thread dump right after application deployment. Grep it for the thread name (i.e. jstack $PID | grep I048) Note the threads. See the name 'I048' assigned in the RouteBuilder. Drop a few files, see the thread count go up. Note the 'KeepAliveTime' param set on the profile. Set this to whatever you'd like, it seems not to change anything. Undeploy the SwitchYard app. Continue monitoring with jstack, the custom threads keep on waiting on condition.
    • 6.3 Sprint 4 (Mar 28 - Apr 29)

      SwitchYard/Camel users wish to make use of a custom thread pool to handle Wiretap messages.

      They find the thread pool works as they would like, but there is a complication. The threads never seem to go away, even when the application that defined the custom pool is undeployed.

              tcunning@redhat.com Thomas Cunningham
              rhn-support-rick Rick Wagner
              Stefan Veres Stefan Veres (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: