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

toD endpoints exceeds the CamelMaximumEndpointCacheSize limit for CAMELCONTEXT

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • jboss-fuse-6.3
    • Camel
    • None
    • % %
    • -
    • Hide
      • download the attached bundle
      • start Fuse 6.3 R12 standalone karaf
      • deploy the bundle
      • check "****** Process "toD" ******" is logged 3 times
      • By JMX, access to EndpointRegistry under service category, and check "Maximum cache size" and "size" attributes. Although max cache size is 1, the size value is 3.
      Show
      download the attached bundle start Fuse 6.3 R12 standalone karaf deploy the bundle check "****** Process "toD" ******" is logged 3 times By JMX, access to EndpointRegistry under service category, and check "Maximum cache size" and "size" attributes. Although max cache size is 1, the size value is 3.

      toD has an option, cacheSize. With the default value 0, camel runtime will use CamelMaximumEndpointCacheSize for toD's cache.
      It seems like each toD EIP has it's own cacheSize counter, so if there are several toD endpoints with default cacheSize option, it's easy to exceeds the CamelMaximumEndpointCacheSize limit for CAMELCONTEXT.

      org.apache.camel.processor.SendDynamicProcessor.doStart() is the method to call ProducerCache() constructor and that will instantiate it's own maxCacheSize.

        1. camel-blueprint-1.0.0-SNAPSHOT.jar
          5 kB
        2. camel-core-2.17.0.redhat-630-SNAPSHOT.jar
          3.32 MB
        3. reproducer.zip
          14 kB

            rhn-support-dhawkins Duane Hawkins
            rhn-support-hfuruich Hisao Furuichi
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: