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

Outbound-socket-binding configs don't propagate to domain server if socket-binding-group has no normal socket bindings

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 8.0.0.Alpha1
    • None
    • Management
    • None

      With a socket-binding-group config like the following, the outbound-socket-binding=mail-smtp:add op is not included in the list of boot ops sent to domain server.

          <socket-binding-groups>
              <socket-binding-group name="sockets1" default-interface="public">
                  <outbound-socket-binding name="mail-smtp">
                      <remote-destination host="localhost" port="1111"/>
                  </outbound-socket-binding>
              </socket-binding-group>
      

              bstansbe@redhat.com Brian Stansberry
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: