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

CXF Undertow Runtime has no Observability

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • None
    • fuse-7.6-GA
    • CXF
    • % %

      Migration from Fuse 6.3 to Fuse 7.6 on OpenShift is transitioning from Jetty to Undertow.

      During performance testing we found some issues using the default http configurations.

      1) No way to configure worker / io threads in Fuse 7.6 (this is being addressed in Fuse 7.7)

      2) The OpenShift container readiness / liveness probes also run on port 8181. If there are any downstream processing delays, requests build up on the worker queue which leads to the probes not running and the container getting killed

      To address that, we tested with the CXF undertow http engine on port 9001.

      1) We were able to tune the threading to optimal performance across their different services

      2) Readiness / liveness probes continue to run on port 8181 so they're not impacted by application traffic

      The issue is that the cxf undertow runtime does not seem to expose or allow anything to be discovered with Dynatrace. With the default http configuration, Dynatrace discovers all of their SOAP / REST endpoints and allows them to monitor requests, response time, errors etc..

      With the CXF Undertow Runtime, nothing is discovered by Dynatrace.

      Is there some implementation detail that would explain why the embedded runtime would lead to this lack of discovery?

            Unassigned Unassigned
            rhn-support-mrobson Matt Robson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: