Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-21259

EAP 7.4 migration: for multiple ejb remoting connectors, they should be in connectors

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 7.4.0.Beta
    • Documentation, EJB
    • None
    • 3
    • False
    • False
    • Undefined

      By default there is 1 remoting connector http-remoting-connector.
      If you add another connector such as the legacy-remoting-connector , those connectors should be listed in the 'remote' 'connectors' element of the ejb3 subsystem. By default it only had a connector-ref and did not allow specifying multiple connectors.

              <subsystem xmlns="urn:jboss:domain:ejb3:8.0">
                  ...
                  <remote cluster="ejb" connectors="http-remoting-connector" thread-pool-name="default">
                      <channel-creation-options>
                          <option name="MAX_OUTBOUND_MESSAGES" value="1234" type="remoting"/>
                      </channel-creation-options>
                  </remote>
      ...
              <subsystem xmlns="urn:jboss:domain:remoting:4.0">
                  <connector name="legacy-remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>
                  <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
              </subsystem>
      
              </subsystem>
      ....
      

      Setting the connectors to http-remoting-connector , legacy-remoting-connector :

      /subsystem=ejb3/service=remote:write-attribute(name=connectors, value=[http-remoting-connector, legacy-remoting-connector])
      

              ncbaratta Nicole Baratta
              rhn-support-bmaxwell Brad Maxwell
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: