Huh... I remember slightly differently... because the 8080 for the old ADSAL couldn't coexist with the RESTCONF, which is why RESTCONF originally went on 8181... once ADSAL was deprecated, *then* RESTCONF shifted to the 8080 port, with 8181 retained for backward compatibility (I *think* I was the one to do all that work... but its a bit murky in my mind).
Ed On Wed, Aug 31, 2016 at 11:39 AM, Luis Gomez <ece...@gmail.com> wrote: > I think it is the other way around: 8181 is the "official" RESTCONF port > and 8080 was used before in ADSAL and kept for API backwards compatibility > reasons. > > On Aug 31, 2016, at 5:57 AM, Edward Warnicke <hagb...@gmail.com> wrote: > > 8080 is the primary port... 8181 was a historical artifact. > > Ed > > On Wed, Aug 31, 2016 at 3:18 AM, navin.kukr...@suse.com < > navin.kukr...@suse.com> wrote: > >> Hi, >> >> Why do we have two ports in etc/jetty.xml file? >> >> I installed Beryllium on a server but I am running another service on >> port 8080 and when I load dlux feature, it stays in graceperiod because >> port 8080 is unavailable. I completely removed 'addConnector' section for >> port 8080 from etc/jetty.xml file and it worked. >> >> Is port 8080 just a abckup port for web portal? >> >> Regards, >> Navin >> >> _______________________________________________ >> controller-dev mailing list >> controller-dev@lists.opendaylight.org >> https://lists.opendaylight.org/mailman/listinfo/controller-dev >> >> > _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/controller-dev > > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
