Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-12190

Reintroduce EJB over HTTP/HTTPS capability with HTTP Loadbalancer - server to server config

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 21.0.0.Beta1, 21.0.0.Final
    • None
    • EJB
    • None

    Description

      Wildfly/EAP added EJB over HTTP through load balancer, but we missed adding the ability to configure this server to server in the standalone.xml remoting subsystem like the other EJB server to server configs.

      The remoting outbound connection would need an http option , currently it only allows http*-remoting, remote and remote+http*.

       /subsystem=remoting/remote-outbound-connection=remote-ejb-connection:write-attribute(name=protocol,
value=)
http-remoting  https-remoting  remote  remote+http  remote+https

      Also, Undertow defaults to http://host:8080/wildfly-services for the provider URL to be used, the remote-outbound-configuration for http would need to be able to accept the path, as the path can be configured to a different path from wildfly-services. It might be good to default to wildfly-services if no path is specified.

      /subsystem=undertow/server=default-server/host=default-host/setting=http-invoker:write-attribute(name=path,value=ejbOverHttp)

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-13878 Add transformer and subsystem test coverage for EJB over HTTP discovery configuration

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. WEJBHTTP-34 Implement discovery for EJB over HTTP

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) EJBCLIENT-364 Enable EJB-over-HTTP invocation from standalone client

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-13492 Upgrade Wildfly HTTP Client to 1.1.2.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-13654 Upgrade wildfly-http-client to 1.1.2.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-12184 WFTC is not integrated with http-client and transaction propagation does not work for server to server ejb over HTTP calls

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              tadamski@redhat.com Tomasz Adamski
              rhn-support-bmaxwell Brad Maxwell
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: