That's correct. The plan is to remove by Final once we make sure that various tools and ides are using the new http upgrade mechanism. Sent from my iPhone On Jan 8, 2014, at 11:21 AM, Filippe Costa Spolti <filippespolti(a)gmail.com <mailto:filippespolti@gmail.com>> wrote: > Hello guys. > > Let me ask something. > > In the WildFly announcements says that the remoting port was > deprecated, but in WFLY CR1 the port still present. > Here: http://wildfly.org/news/2013/12/21/WildFly8-CR1-Released/ > > But when i start the standalone mode the port 9990 appears: > > [root@wfly_tests ~]# netstat -anp | grep java > tcp 0 0 127.0.0.1:9999 0.0.0.0:* > LISTEN 3070/java > tcp 0 0 192.168.11.109:8080 0.0.0.0:* > LISTEN 3070/java > tcp 0 0 127.0.0.1:9990 0.0.0.0:* > LISTEN 3070/java > > This port will be removed only in the Final version? > > -- > Regards, > ______________________________________ > Filippe Costa Spolti > Linux User n°515639 - http://counter.li.org/ > filippespolti(a)gmail.com > "Be yourself" > <linkedin.png> > <http://www.linkedin.com/pub/filippe-costa-spolti/67/985/575> > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/wildfly-dev

Hi, JMX connectivity is currently supported over the remoting port. How will JMX clients be able to connect when the remoting port goes away?

Thanks, Thomas Le 08/01/2014 18:27, Jason Greene a écrit : > That's correct. The plan is to remove by Final once we make sure that > various tools and ides are using the new http upgrade mechanism. > > Sent from my iPhone > > On Jan 8, 2014, at 11:21 AM, Filippe Costa Spolti > <filippespolti(a)gmail.com <mailto:filippespolti@gmail.com>> wrote: > >> Hello guys. >> >> Let me ask something. >> >> In the WildFly announcements says that the remoting port was >> deprecated, but in WFLY CR1 the port still present. >> Here: http://wildfly.org/news/2013/12/21/WildFly8-CR1-Released/ >> >> But when i start the standalone mode the port 9990 appears: >> >> [root@wfly_tests ~]# netstat -anp | grep java >> tcp 0 0 127.0.0.1:9999 0.0.0.0:* >> LISTEN 3070/java >> tcp 0 0 192.168.11.109:8080 0.0.0.0:* >> LISTEN 3070/java >> tcp 0 0 127.0.0.1:9990 0.0.0.0:* >> LISTEN 3070/java >> >> This port will be removed only in the Final version? >> >> -- >> Regards, >> ______________________________________ >> Filippe Costa Spolti >> Linux User n°515639 - http://counter.li.org/ >> filippespolti(a)gmail.com >> "Be yourself" >> <linkedin.png> >> <http://www.linkedin.com/pub/filippe-costa-spolti/67/985/575> >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/wildfly-dev > > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

Le 09/01/2014 13:51, Darran Lofthouse a écrit : > On 09/01/14 12:35, Thomas Segismont wrote: >> Hi, >> >> JMX connectivity is currently supported over the remoting port. How will >> JMX clients be able to connect when the remoting port goes away? > > Over the HTTP port with a HTTP Upgrade, overall just a slight change in > the URL used to establish the connection from the end users perspective. Great! Is this documented somewhere in the wiki? Or maybe not yet implemented? I found https://docs.jboss.org/author/display/WFLY8/JMX+subsystem+configuration but it only refers to the remoting port solution. Thomas