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

CXF fix from support case didn't port well to EAP 7.1.3 (regression introduced)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • fuse-7.0.1
    • CXF
    • None
    • % %
    • Hide

      The same use cases used for ENTESB-9102 should still be valid.

      Show
      The same use cases used for ENTESB-9102 should still be valid.

      The customer had been using Fuse 6.4, but reported an issue with JMS transport clean-up [1]. The fix provided (cxf-rt-transports-jms-3.1.5-redhat-630347-08.jar) solved the issue.

      The customer has since upgraded to Fuse 7.1, with a base of EAP 7.1.3 (resulting in use of cxf-rt-transports-jms-3.1.13.redhat-1.jar) and the problem is back.

      Analysis reveals the method 'sendExchange()' is not the same between the two jars. (It appears the code that improved prior base to 3.1.5 is still there in 3.1.13. The problem may be in the additional code that is also present.

      [1] https://issues.jboss.org/browse/ENTESB-9102

      ------------------------- Secondary issue ------------------------------------------------------

      Downloading the source for the EAP patch [2], it does not appear this source matches the jar from the patch [3]

      [2] https://maven.repository.redhat.com/ga/org/apache/cxf/cxf-rt-transports-jms/3.1.13.redhat-1/cxf-rt-transports-jms-3.1.13.redhat-1-sources.jar

      [3] https://maven.repository.redhat.com/ga/org/apache/cxf/cxf-rt-transports-jms/3.1.13.redhat-1/cxf-rt-transports-jms-3.1.13.redhat-1.jar

            yfang@redhat.com Freeman(Yue) Fang
            rhn-support-rick Rick Wagner
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: