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

Old “remote://“ protocol is hard coded RemoteDomainConnectionService

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • None
    • None
    • None
    • None

    Description

      Email conversation on wildfly-dev:

      http://lists.jboss.org/pipermail/wildfly-dev/2014-May/002157.html

      > 1). Why the following entry is still referring to 9999 ? Shouldn't it be 9990 ?
      >
      > <domain-controller>
      > <remote host="10.211.55.7" port="9999"/>
      > </domain-controller>
      >
      > FTR it only works with 9999, not with 9990.
      >
      > Domain Controller shows the message:
      >
      > [Host Controller] 15:36:22,811 INFO [org.jboss.as.domain] (Host
      > Controller Service Threads - 28) JBAS010918: Registered remote slave
      > host "slave", WildFly 8.1.0.CR2 “Kenny”
      It looks like we hardcode the old “remote://“ protocol in RemoteDomainConnectionService rather than the new http-remoting protocol, so it is a bug. I am not sure if that is something we should attempt to negotiate explicitly, or to make the <remote> element take a ‘protocol’ attribute?

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              arungupta_jira Arun Gupta (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: