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

Share the life-cycle management of the JCo server connections among multiple instances of the SAP Camel component

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Closed
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: jboss-fuse-6.2.1, jboss-fuse-6.3
    • Fix Version/s: fuse-7.0
    • Component/s: Camel
    • Labels:
      None
    • Environment:

      n/a

      Description

      "There is indeed a restriction on a JCo server connection in that it can only be used in a single Camel context. The reason for this is that the lifecycle of an underlying JCo server connection is managed by an SAP Camel component instance. JCo server connections need to be started, stopped, released and monitored by a single entity and this is done by the SAP Camel component. Since each Camel context has a distinct instance of a SAP Camel component, multiple instances of an SAP Camel component in distinct Camel contexts can not manage the same server connection and the component specifically prevents this. Thus routes with SAP server endpoints using a specific JCo server connection need to be restricted to a single Camel context."

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                wcollins William Collins
                Reporter:
                roddiekieley Roddie Kieley
                Tester:
                Jan Bouska
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: