They must not define an http socket binding in the JDG app server's config (look in its standalone.xml and see). If it is true that they simply don't define that, its not a problem, the agent just doesn't collect data for it (I believe this is resource configuration property - it will just not get collected). Error message is just saying it can't find that resource property to collect. so look in the managed JDG server's standalone.xml's <socket-binding-group> section and I suspect you won't find "http" in the "standard-sockets". ----- Original Message ----- > Hello, > > Thomas asked me to take a look at how JDG 7 (based on EAP 7.0) worked along > with Hawkular and ManageIQ. > > I installed the Hawkular wildfly agent (on the JDG) and started it with: > > ./bin/standalone.sh -Djboss.socket.binding.port-offset=1000 > > and right after starting, when performing a discovery (i think) it throws the > following exception: > > ERROR [org.jboss.as.controller.management-operation] (Hawkular WildFly Agent > Full Discovery Scan-1) WFLYCTL0013: Operation ("read-attribute") failed - > address: ([ > ("socket-binding-group" => "standard-sockets"), > ("socket-binding" => "http") > > Aside from that exception It seems to be working well with hawkular-services > and ManageIQ. I could do deployments, undeploy, create datasources, stop the > server, and so on. > I'm not sure if the discovery process ends unexpectedly with that exception > or if it continues. > Anyone know if this could affect discovery of other resources ? > > I attached a minimal server.log of JDG as i didn't see anything relevant on > Hawkular-services console. > > Thanks, > Josejulio. > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev

So do we need to fix the agent or the agent configuration to not spit that error message ? Or do we need to add the http socket for some reason ?

What do we lose from ManageIQ pov ?

Thomas On Wed, Nov 9, 2016 at 7:05 PM, Josejulio Martinez Magana < jmartine(a)redhat.com&gt; wrote: > You are right, an http socket is not defined on the standalone.xml. > > Thanks. > > On Wed, Nov 9, 2016 at 11:59 AM, John Mazzitelli <mazz(a)redhat.com&gt; > wrote: > >> They must not define an http socket binding in the JDG app server's >> config (look in its standalone.xml and see). If it is true that they >> simply >> don't define that, its not a problem, the agent just doesn't collect >> data >> for it (I believe this is resource configuration property - it will >> just >> not get collected). Error message is just saying it can't find that >> resource property to collect. >> >> so look in the managed JDG server's standalone.xml's >> <socket-binding-group> section and I suspect you won't find "http" >> in the >> "standard-sockets". >> >> ----- Original Message ----- >>> Hello, >>> >>> Thomas asked me to take a look at how JDG 7 (based on EAP 7.0) >>> worked >> along >>> with Hawkular and ManageIQ. >>> >>> I installed the Hawkular wildfly agent (on the JDG) and started it >>> with: >>> >>> ./bin/standalone.sh -Djboss.socket.binding.port-offset=1000 >>> >>> and right after starting, when performing a discovery (i think) it >> throws the >>> following exception: >>> >>> ERROR [org.jboss.as.controller.management-operation] (Hawkular >>> WildFly >> Agent >>> Full Discovery Scan-1) WFLYCTL0013: Operation ("read-attribute") >>> failed >> - >>> address: ([ >>> ("socket-binding-group" => "standard-sockets"), >>> ("socket-binding" => "http") >>> >>> Aside from that exception It seems to be working well with >> hawkular-services >>> and ManageIQ. I could do deployments, undeploy, create datasources, >> stop the >>> server, and so on. >>> I'm not sure if the discovery process ends unexpectedly with that >> exception >>> or if it continues. >>> Anyone know if this could affect discovery of other resources ? >>> >>> I attached a minimal server.log of JDG as i didn't see anything >> relevant on >>> Hawkular-services console. >>> >>> Thanks, >>> Josejulio. >>> >>> _______________________________________________ >>> hawkular-dev mailing list >>> hawkular-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hawkular-dev >>> >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev