From theute at redhat.com Wed Oct 11 12:28:18 2017 From: theute at redhat.com (Thomas Heute) Date: Wed, 11 Oct 2017 16:28:18 +0000 Subject: [Hawkular-dev] New Hawkular Blog Post: Hawkular Alerts in ManageIQ Message-ID: <59de46a239eff_7a888f13301476a@mini-queue-05.resque.ife.mail> New Hawkular blog post from noreply at hawkular.org (Edgar Hern?ndez): http://ift.tt/2ygxRgx Hawkular project includes an alerting module that can be used to send notifications when certain conditions are met. The alerting module is bundled in Hawkular Middleware Manager (aka. Hawkular Services) ManageIQ also has alerting capabilities and Hawkular Middleware Manager integrates to it. Once Hawkular is added as a provider, ManageIQ alerting features can be used to monitor servers managed by Hawkular. ManageIQ alerting terminology In ManageIQ, two terms are used: Alert Defines the which type of infrastructure item should be monitored, the conditions and the actions to take when the conditions are met. Alert profile It is a relation between a set of alerts and a set of infrastructure items. The set of alerts in the profile will all be applied to the set of infrastructure items. If any of the infrastructure items met the conditions in one of the alerts, the actions of the alert will run. ManageIQ has support for several types of infrastructure items, but Hawkular Middleware Manager supports only a subset of them. Middleware servers are an example of infrastructure items that are supported by Hawkular. Hawkular alerting terminology Hawkular?s alerting module has several kinds of objects (and terms). The two objects that are relevant from a ManageIQ perspective are: Group trigger Defines the set of conditions that should be met to fire an alert or an event. A group trigger is a template and no alert nor events will be fired until a member is added to it. Group member It?s an association of a group trigger with the actual data to be evaluated. Internally to Hawkular, group members are managed instances of group triggers. Changes to the group trigger are pushed down to the members. Currently, ManageIQ creates group triggers that raise events (not alerts) and polls Hawkular to catch the events and run configured actions, if needed. Terminology relationships When a user creates a ManageIQ alert, a Hawkular group trigger is created in the background. From then, any changes to the ManageIQ alert are replicated to the associated Hawkular group trigger until the alert is deleted, which causes the group trigger to also be deleted. While ManageIQ alerts have a direct relation with Hawkular group triggers, ManageIQ alert profiles are a little bit more complicated. For each alert in a ManageIQ profile, one Hawkular group member is created for each infrastructure item in the profile. This means that nothing is created in Hawkular if: The alert profile is empty (has no alerts nor infrastructure items) The alert profile has alerts but has no infrastructure items The alert profile has infrastructure items but has no alerts If a ManageIQ alert profile has one alert and has assigned multiple infrastructure items, then the relevant Hawkular group trigger will have as many members as infrastructure items are in the ManageIQ alert profile. If a ManageIQ alert profile has multiple alerts and has assigned only one infrastructure item, then each Hawkular group trigger will have one member. With these two examples, you should be able to guess what will happen if the ManageIQ alert profile has a set of alerts and a set of infrastructure items. Creating ManageIQ alerts Alerts are created by navigating to Control > Explorer > Alerts. In the alerts tree, select the All alerts folder. This will enable the Add a New Alert option under the Configuration button. In the form to create/edit an alert, be sure to select Middleware server in the Based On field. Currently, this is the only infrastructure item supported by Hawkular. If you choose something else, the alert won?t be managed by Hawkular. All other options can be filled as desired. When the alert is created, it will be available in the control explorer and will be available to be included in an alert profile. In the background, a Hawkular group trigger is also created. Creating an alert profile Alert profiles are created by navigating to Control > Explorer > Alert Profiles. In the alerts tree, select the Middleware server Alert Profiles item. This will enable the Add a Middleware Server Alert Profile option under the Configuration button. In the form to create/edit an alert profile, write a description and select the desired alerts to evaluate. At least, one alert is required to be able to create the alert profile. When the alert profile is created, it will be available in the control explorer which will also list the alerts contained in the profile. Nothing will be created in Hawkular because when the profile is created it is still not assigned to middleware servers. Assigning middleware servers to an alert profile To assign middleware servers to an alert profile, select the desired profile in the control explorer. In the toolbar, use the Edit assignments for this Alert Profile options under the Configuration button. This will show the assignments page. An alert profile can be assigned to specific middleware servers or to all inventoried middleware servers (The Enterprise). Once you have chosen the desired middleware servers (or the enterprise) and changes are saved, the view page of the alert will be displayed again. In the background, Hawkular group members will be created to make effective the configuration and alerts should start triggering. Viewing alerts in the timeline The timeline of ManageIQ Hawkular provider will log events if the configuration of an alert is enabled to show timeline events. Hawkular?s provider timeline can be accessed through the summary page of the provider, under the Monitoring menu: If the alert has enabled the standard Show on Timeline configuration, the options to query the events are: Event type: Management Events Category: Alarm/Status Change/Errors Conclusion ManageIQ and Hawkular, albeit being two independent projects, they can be connected together to complement each other features. In this post is discussed how the alerting integration works and how to configure a basic alert. At the time of writing, ManageIQ supports only Middleware Servers as targets and, also, only a limited set of metrics is available to configure alerts. There is ongoing work to provide a wider range of metrics and this is expected to be available in following versions. from Hawkular Blog -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171011/829a6c99/attachment-0001.html From mazz at redhat.com Thu Oct 12 10:01:18 2017 From: mazz at redhat.com (John Mazzitelli) Date: Thu, 12 Oct 2017 10:01:18 -0400 (EDT) Subject: [Hawkular-dev] need design decisions to be made for server-side config of agent In-Reply-To: <1016633585.28625833.1507816847264.JavaMail.zimbra@redhat.com> Message-ID: <482123703.28625912.1507816878698.JavaMail.zimbra@redhat.com> I added this comment to a JIRA: https://issues.jboss.org/browse/HAWKULAR-1261?focusedCommentId=13476371&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13476371 This is to discuss how we want things to work wrt the agent pulling down configuration from the server. This is going to require me to rip up parts of the agent and i want to avoid doing unnecessary work because it will not be trivial. Thus, I need to know how we want it to work before I do anything. Please enter your comments in that JIRA. Or we can discuss in #hawkular. From mwringe at redhat.com Thu Oct 12 14:17:01 2017 From: mwringe at redhat.com (Matthew Wringe) Date: Thu, 12 Oct 2017 14:17:01 -0400 Subject: [Hawkular-dev] need design decisions to be made for server-side config of agent In-Reply-To: <482123703.28625912.1507816878698.JavaMail.zimbra@redhat.com> References: <1016633585.28625833.1507816847264.JavaMail.zimbra@redhat.com> <482123703.28625912.1507816878698.JavaMail.zimbra@redhat.com> Message-ID: Can we maybe get something like a google doc started for this? I find that can be a bit easier to collaborate on than with just the jira. It might also be good to reserve a time to have a call to discuss this over bluejeans. As far as I can tell, the plan isn't to have server side configurations (like you would with a pull model) but instead to continue to have client side configurations but have the server be able to push out updates to the client. Will this require a new component to expose REST endpoints at the server level? or are we planning on reusing an existing component? Are we going to be able to have individual configurations per server, or are we lumping things into server types (eg all EAP7 instances have the same configuration) On Thu, Oct 12, 2017 at 10:01 AM, John Mazzitelli wrote: > I added this comment to a JIRA: > > https://issues.jboss.org/browse/HAWKULAR-1261?focusedCommentId=13476371& > page=com.atlassian.jira.plugin.system.issuetabpanels: > comment-tabpanel#comment-13476371 > > This is to discuss how we want things to work wrt the agent pulling down > configuration from the server. > > This is going to require me to rip up parts of the agent and i want to > avoid doing unnecessary work because it will not be trivial. Thus, I need > to know how we want it to work before I do anything. > > Please enter your comments in that JIRA. > > Or we can discuss in #hawkular. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171012/c1c56a8d/attachment.html From mazz at redhat.com Thu Oct 12 15:18:39 2017 From: mazz at redhat.com (John Mazzitelli) Date: Thu, 12 Oct 2017 15:18:39 -0400 (EDT) Subject: [Hawkular-dev] need design decisions to be made for server-side config of agent In-Reply-To: References: <1016633585.28625833.1507816847264.JavaMail.zimbra@redhat.com> <482123703.28625912.1507816878698.JavaMail.zimbra@redhat.com> Message-ID: <386794691.28697570.1507835919238.JavaMail.zimbra@redhat.com> > It might also be good to reserve a time to have a call to discuss this over > bluejeans. > > As far as I can tell, the plan isn't to have server side configurations > (like you would with a pull model) but instead to continue to have client > side configurations but have the server be able to push out updates to the > client. The idea isn't a "push from server to agent", rather its the agent pulling its config from the server. > Will this require a new component to expose REST endpoints at the server > level? or are we planning on reusing an existing component? We already have something in place today: https://github.com/hawkular/hawkular-commons/blob/mwm-wildfly/hawkular-inventory-parent/hawkular-inventory-service/src/main/java/org/hawkular/inventory/handlers/InventoryHandlers.java#L78-L94 > Are we going to be able to have individual configurations per server, or > are we lumping things into server types (eg all EAP7 instances have the > same configuration) Preferably we are going to be grouping config based on server type. I mention an example in the JIRA comment: These server-side configuration files are centrally located and will define types for all servers to be managed. There is not going to be one uber file. There will be two files per server kind (two files because one is for jmx exporter, the other is for our agent). e.g. EAP-7.0.0-Final-jmx-exporter.yaml EAP-7.0.0-Final-inventory.yaml Fuse-1.1.0-RC2-jmx-exporter.yaml Fuse-1.1.0-RC2-inventory.yaml So when EAP 7.1 is released, we'll just add two new files to the central location on the server and the agent can start downloading those to managed EAP 7.1 servers. From jshaughn at redhat.com Thu Oct 12 17:20:22 2017 From: jshaughn at redhat.com (Jay Shaughnessy) Date: Thu, 12 Oct 2017 17:20:22 -0400 Subject: [Hawkular-dev] need design decisions to be made for server-side config of agent In-Reply-To: <386794691.28697570.1507835919238.JavaMail.zimbra@redhat.com> References: <1016633585.28625833.1507816847264.JavaMail.zimbra@redhat.com> <482123703.28625912.1507816878698.JavaMail.zimbra@redhat.com> <386794691.28697570.1507835919238.JavaMail.zimbra@redhat.com> Message-ID: On 10/12/2017 3:18 PM, John Mazzitelli wrote: >> It might also be good to reserve a time to have a call to discuss this over >> bluejeans. >> >> As far as I can tell, the plan isn't to have server side configurations >> (like you would with a pull model) but instead to continue to have client >> side configurations but have the server be able to push out updates to the >> client. > The idea isn't a "push from server to agent", rather its the agent pulling its config from the server. When you say, "As far as I can tell, the plan isn't to have server side configurations",? where is that coming from? ? It's true that in the past we had agent-side config, but it has been a while now that we've planned on going to a centralized config, to avoid unnecessary complexity and to minimize the need to update agents.? Anyway, as Mazz points out, the mechanism is already there to serve up the files.? I just wanted to make sure there isn't a change in plan, or a doc, that I'm not aware of. >> Will this require a new component to expose REST endpoints at the server >> level? or are we planning on reusing an existing component? > We already have something in place today: > > https://github.com/hawkular/hawkular-commons/blob/mwm-wildfly/hawkular-inventory-parent/hawkular-inventory-service/src/main/java/org/hawkular/inventory/handlers/InventoryHandlers.java#L78-L94 > >> Are we going to be able to have individual configurations per server, or >> are we lumping things into server types (eg all EAP7 instances have the >> same configuration) > Preferably we are going to be grouping config based on server type. I mention an example in the JIRA comment: > > These server-side configuration files are centrally located and will define types for all servers to be managed. There is not going to be one uber file. There will be two files per server kind (two files because one is for jmx exporter, the other is for our agent). > > e.g. > EAP-7.0.0-Final-jmx-exporter.yaml > EAP-7.0.0-Final-inventory.yaml > Fuse-1.1.0-RC2-jmx-exporter.yaml > Fuse-1.1.0-RC2-inventory.yaml > > So when EAP 7.1 is released, we'll just add two new files to the central location on the server and the agent can start downloading those to managed EAP 7.1 servers. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From jtakvori at redhat.com Fri Oct 13 03:03:30 2017 From: jtakvori at redhat.com (Joel Takvorian) Date: Fri, 13 Oct 2017 09:03:30 +0200 Subject: [Hawkular-dev] need design decisions to be made for server-side config of agent In-Reply-To: References: <1016633585.28625833.1507816847264.JavaMail.zimbra@redhat.com> <482123703.28625912.1507816878698.JavaMail.zimbra@redhat.com> <386794691.28697570.1507835919238.JavaMail.zimbra@redhat.com> Message-ID: Just adding here, that the new model (as it is currently defined) makes it mandatory to have unique resource type definition per server ; that is, the resource types definitions cannot vary from an agent to another. Technically speaking, it doesn't have feedId. On Thu, Oct 12, 2017 at 11:20 PM, Jay Shaughnessy wrote: > > > On 10/12/2017 3:18 PM, John Mazzitelli wrote: > >> It might also be good to reserve a time to have a call to discuss this > over > >> bluejeans. > >> > >> As far as I can tell, the plan isn't to have server side configurations > >> (like you would with a pull model) but instead to continue to have > client > >> side configurations but have the server be able to push out updates to > the > >> client. > > The idea isn't a "push from server to agent", rather its the agent > pulling its config from the server. > > When you say, "As far as I can tell, the plan isn't to have server side > configurations", where is that coming from? It's true that in the > past we had agent-side > config, but it has been a while now that we've planned on going to a > centralized config, to avoid unnecessary complexity and to minimize the > need to update > agents. Anyway, as Mazz points out, the mechanism is already there to > serve up the files. I just wanted to make sure there isn't a change in > plan, or a doc, that > I'm not aware of. > > > >> Will this require a new component to expose REST endpoints at the server > >> level? or are we planning on reusing an existing component? > > We already have something in place today: > > > > https://github.com/hawkular/hawkular-commons/blob/mwm- > wildfly/hawkular-inventory-parent/hawkular-inventory- > service/src/main/java/org/hawkular/inventory/handlers/ > InventoryHandlers.java#L78-L94 > > > >> Are we going to be able to have individual configurations per server, or > >> are we lumping things into server types (eg all EAP7 instances have the > >> same configuration) > > Preferably we are going to be grouping config based on server type. I > mention an example in the JIRA comment: > > > > These server-side configuration files are centrally located and will > define types for all servers to be managed. There is not going to be one > uber file. There will be two files per server kind (two files because one > is for jmx exporter, the other is for our agent). > > > > e.g. > > EAP-7.0.0-Final-jmx-exporter.yaml > > EAP-7.0.0-Final-inventory.yaml > > Fuse-1.1.0-RC2-jmx-exporter.yaml > > Fuse-1.1.0-RC2-inventory.yaml > > > > So when EAP 7.1 is released, we'll just add two new files to the central > location on the server and the agent can start downloading those to managed > EAP 7.1 servers. > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171013/8031ed91/attachment-0001.html From jshaughn at redhat.com Mon Oct 16 17:07:00 2017 From: jshaughn at redhat.com (Jay Shaughnessy) Date: Mon, 16 Oct 2017 17:07:00 -0400 Subject: [Hawkular-dev] need design decisions to be made for server-side config of agent In-Reply-To: References: <1016633585.28625833.1507816847264.JavaMail.zimbra@redhat.com> <482123703.28625912.1507816878698.JavaMail.zimbra@redhat.com> <386794691.28697570.1507835919238.JavaMail.zimbra@redhat.com> Message-ID: <905f1260-b918-17fc-cc6f-96ddbc610ab6@redhat.com> Actually, the resource types are global across [hawkular] servers as well, right?? We'd likely use the same agent config files across multiple server instances. On 10/13/2017 3:03 AM, Joel Takvorian wrote: > Just adding here, that the new model (as it is currently defined) > makes it mandatory to have unique resource type definition per server > ; that is, the resource types definitions cannot vary from an agent to > another. > Technically speaking, it doesn't have feedId. > > On Thu, Oct 12, 2017 at 11:20 PM, Jay Shaughnessy > wrote: > > > > On 10/12/2017 3:18 PM, John Mazzitelli wrote: > >> It might also be good to reserve a time to have a call to > discuss this over > >> bluejeans. > >> > >> As far as I can tell, the plan isn't to have server side > configurations > >> (like you would with a pull model) but instead to continue to > have client > >> side configurations but have the server be able to push out > updates to the > >> client. > > The idea isn't a "push from server to agent", rather its the > agent pulling its config from the server. > > When you say, "As far as I can tell, the plan isn't to have server > side > configurations",? where is that coming from? ? It's true that in the > past we had agent-side > config, but it has been a while now that we've planned on going to a > centralized config, to avoid unnecessary complexity and to > minimize the > need to update > agents.? Anyway, as Mazz points out, the mechanism is already there to > serve up the files.? I just wanted to make sure there isn't a > change in > plan, or a doc, that > I'm not aware of. > > > >> Will this require a new component to expose REST endpoints at > the server > >> level? or are we planning on reusing an existing component? > > We already have something in place today: > > > > > https://github.com/hawkular/hawkular-commons/blob/mwm-wildfly/hawkular-inventory-parent/hawkular-inventory-service/src/main/java/org/hawkular/inventory/handlers/InventoryHandlers.java#L78-L94 > > > > >> Are we going to be able to have individual configurations per > server, or > >> are we lumping things into server types (eg all EAP7 instances > have the > >> same configuration) > > Preferably we are going to be grouping config based on server > type. I mention an example in the JIRA comment: > > > > These server-side configuration files are centrally located and > will define types for all servers to be managed. There is not > going to be one uber file. There will be two files per server kind > (two files because one is for jmx exporter, the other is for our > agent). > > > > e.g. > > EAP-7.0.0-Final-jmx-exporter.yaml > > EAP-7.0.0-Final-inventory.yaml > > Fuse-1.1.0-RC2-jmx-exporter.yaml > > Fuse-1.1.0-RC2-inventory.yaml > > > > So when EAP 7.1 is released, we'll just add two new files to the > central location on the server and the agent can start downloading > those to managed EAP 7.1 servers. > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171016/f1e4e8d0/attachment.html From mazz at redhat.com Tue Oct 17 17:07:09 2017 From: mazz at redhat.com (John Mazzitelli) Date: Tue, 17 Oct 2017 17:07:09 -0400 (EDT) Subject: [Hawkular-dev] h-services / travis / jenkins/torii In-Reply-To: <623013758.29580006.1508274007318.JavaMail.zimbra@redhat.com> Message-ID: <236413736.29581223.1508274429767.JavaMail.zimbra@redhat.com> I updated H-Services to push out the docker image to Docker hub. I need someone to review/merge: https://github.com/hawkular/hawkular-services/pull/200 You'll see the docker image up on docker hub here: https://hub.docker.com/r/hawkular/hawkular-services/tags/ How it works is if someone merges a PR into master branch then docker-dist mvn module will be built with the maven goal of docker:build and the resulting image will be pushed to docker hub with docker tag of "latest". Right now the branch hawkular-1259 is special - travis will also push the docker image when we merge into that branch (with a docker tag of hawkular-1259). Once we get back onto master, I will take out that special stuff so we only release "latest" image from master. What I need is: whoever (Juca?) has the magic keys to jenkins on that internal RH machine, turn off the pushing of the image to docker hub. This way we have all the code that does it out in the open on github not in some internal private machine. I don't know if we still care about keeping that internal Jenkins integration job running that does the releases. If I knew exactly what it does, I could try to get travis to do that too (I have a feeling it will be more involved than the docker hub thing, so maybe we keep it). However, right now, that Jenkins job is always failing so I have no idea what good it is doing for us right now anyway (it's always failing on the hawkular-1259 branch). From mazz at redhat.com Wed Oct 25 09:30:05 2017 From: mazz at redhat.com (John Mazzitelli) Date: Wed, 25 Oct 2017 09:30:05 -0400 (EDT) Subject: [Hawkular-dev] how to play with jmx exporter In-Reply-To: <853051090.31723979.1508938117709.JavaMail.zimbra@redhat.com> Message-ID: <1913375003.31728996.1508938205640.JavaMail.zimbra@redhat.com> If you want to test with jmx exporter, here's three lines of code you can add to the very bottom of your Hawkular Services distro's standalone.conf file: ---- wget http://central.maven.org/maven2/io/prometheus/jmx/jmx_prometheus_javaagent/0.10/jmx_prometheus_javaagent-0.10.jar unzip -o -j $JBOSS_HOME/modules/system/layers/hawkular/org/hawkular/nest/main/deployments/hawkular-inventory-service.war WEB-INF/classes/wildfly-10-jmx-exporter.yml JAVA_OPTS="$JAVA_OPTS -javaagent:$JBOSS_HOME/bin/jmx_prometheus_javaagent-0.10.jar=9779:$JBOSS_HOME/bin/wildfly-10-jmx-exporter.yml" ---- Then just run the server normally. Once up, you can see the metrics at http://localhost:9779/metrics [this email was sent on October 25 at 9:30am EDT] From jgodoy at redhat.com Thu Oct 26 16:25:41 2017 From: jgodoy at redhat.com (Jerczey Godoy) Date: Thu, 26 Oct 2017 17:25:41 -0300 Subject: [Hawkular-dev] Hawkular APM 0.14.4 + external Elastic Search Message-ID: Hello , I got the email list from irc.freenode #hawkular We are attempting to make the events data (from agents) persistent, we expect the external elastic search allows to have some sort of persistance if there is a failure of the APM itself. We checked the embedded elastic, and if the APM (wilfly) goes down, the data from previous events does not remain. So, we expected that an external elastic could suffice this , we used this rpm wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-5.6.3.rpm and on the same host we set up the APM 0.14 distrbution we pointed the standalone.conf with the following configuration: export HAWKULAR_APM_ELASTICSEARCH_CLUSTER="elasticsearch" export HAWKULAR_APM_ELASTICSEARCH_HOSTS="localhost:9200" unfortunately, this throws an error starting the APM *15:54:37,520 SEVERE [org.hawkular.apm.server.elasticsearch.ElasticsearchBootstrap] (ServerService Thread Pool -- 91) Failed to initialise Elasticsearch: org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: []* *16:25:16,525 INFO [org.elasticsearch.client.transport] (elasticsearch[Jaren][generic][T#2]) [Jaren] failed to get node info for [#transport#-1][cllnxHawkular][inet[localhost/127.0.0.1:9300]], disconnecting...: org.elasticsearch.transport.NodeDisconnectedException: [][inet[localhost/127.0.0.1:9300]][cluster:monitor/nodes/info] disconnected* is there a configuration for the elastic search ? does the external elasticsearch able to make the data persistent ? Any comment/help is very appreciated! Thanks! -- JERCZEY GODOY MIDDLEWARE CONSULTANT RHCJA Red Hat Chile Avenida Apoquindo 2827, Piso 7. Santiago, Chile. JGodoy at RedHat.com M: 975791358 IM: @jerczey TRIED. TESTED. TRUSTED. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171026/3ef43a5b/attachment-0001.html From mazz at redhat.com Thu Oct 26 17:48:08 2017 From: mazz at redhat.com (John Mazzitelli) Date: Thu, 26 Oct 2017 17:48:08 -0400 (EDT) Subject: [Hawkular-dev] change to inventory metric model to store Prometheus info In-Reply-To: <29791849.32773994.1509054200254.JavaMail.zimbra@redhat.com> Message-ID: <1542975970.32777555.1509054488489.JavaMail.zimbra@redhat.com> I *think* I'm almost at the point where our inventory is able to store Prometheus metric data (metric family name and labels) in our inventory. Once done, you need only query inventory to get a resource's metric data and from there you will get the Prometheus metric family+labels so you know what you need to ask Prometheus for. Currently, there is no place in our Metric domain object in inventory for this information. Right now I am putting it in that generic properties: // don't copy properties - we are using the inventory properties for P labels right now //m.getProperties().forEach((k, v) -> mb.property(k, v.toString())); // map to the Prometheus metric timeseries mb.property("hawkular.metric.family", m.getMetricFamily()); mb.properties(m.getMetricLabels()); The object "m" is the agent's own Metric object that has a generic properties map. Right now I don't think we store anything in there so that commented portion of the code is no big deal at the moment. But notice the metric family name and the metric labels are all in the same generic properties for the inventory Metric object (that's what mb is). I don't like this. It means who ever queries inventory has to strip out the "hawkular.metric.family" key from the metric generic properties - the rest of the map are the real labels. I think we should make these first-class attributes in the inventory model: mb.metricFamily(m.getMetricFamily()) mb.metricLabels(m.getMetricLabels()) Thoughts? (looking at you Joel :-) [ps. this email was sent at 5:48pm on October 26, 2017] From mazz at redhat.com Thu Oct 26 23:07:45 2017 From: mazz at redhat.com (John Mazzitelli) Date: Thu, 26 Oct 2017 23:07:45 -0400 (EDT) Subject: [Hawkular-dev] jmx exporter - com.sun classes used In-Reply-To: <814257212.32859795.1509073297319.JavaMail.zimbra@redhat.com> Message-ID: <407496306.32860037.1509073665032.JavaMail.zimbra@redhat.com> Take a look at Prometheus's HTTPServer class: https://github.com/prometheus/client_java/blob/master/simpleclient_httpserver/src/main/java/io/prometheus/client/exporter/HTTPServer.java#L22-L24 This Prometheus HTTPServer class is what jmx exporter uses for its metrics endpoint - see: https://github.com/prometheus/jmx_exporter/blob/master/jmx_prometheus_javaagent/src/main/java/io/prometheus/jmx/JavaAgent.java#L8 https://github.com/prometheus/jmx_exporter/blob/master/jmx_prometheus_httpserver/src/main/java/io/prometheus/jmx/WebServer.java#L7 Since it uses com.sun.net.httpserver classes under the covers, I'll assume this rules out support for, say, IBM's JVM (does IBM's JRE implement these?). I think this is available on OpenJDK but didn't check to make 100% sure. From jtakvori at redhat.com Fri Oct 27 03:04:04 2017 From: jtakvori at redhat.com (Joel Takvorian) Date: Fri, 27 Oct 2017 09:04:04 +0200 Subject: [Hawkular-dev] change to inventory metric model to store Prometheus info In-Reply-To: <1542975970.32777555.1509054488489.JavaMail.zimbra@redhat.com> References: <29791849.32773994.1509054200254.JavaMail.zimbra@redhat.com> <1542975970.32777555.1509054488489.JavaMail.zimbra@redhat.com> Message-ID: Go on :-) Using the props map was just easier in hawkular-1259 but now we're at a step where we can design a model more specific to prometheus. Are all metric labels needed for inventory? Or is it just a subset? There's also something that needs to be done to distinguish availability metrics (I think Lucas was adding a "tag" field in the model, indexed, allowing to query for metrics tagged "availability" ... Lucas do you confirm?). Are we able to recognize avail metrics from the agent, or is it something that must be hard-coded somewhere for explicit family name? I fear that having both "tags" and "labels" on the model can be quite confusing, but on the other hand we don't want to index all P labels in ispn. On Thu, Oct 26, 2017 at 11:48 PM, John Mazzitelli wrote: > I *think* I'm almost at the point where our inventory is able to store > Prometheus metric data (metric family name and labels) in our inventory. > Once done, you need only query inventory to get a resource's metric data > and from there you will get the Prometheus metric family+labels so you know > what you need to ask Prometheus for. > > Currently, there is no place in our Metric domain object in inventory for > this information. Right now I am putting it in that generic properties: > > // don't copy properties - we are using the inventory properties > for P labels right now > //m.getProperties().forEach((k, v) -> mb.property(k, > v.toString())); > > // map to the Prometheus metric timeseries > mb.property("hawkular.metric.family", m.getMetricFamily()); > mb.properties(m.getMetricLabels()); > > The object "m" is the agent's own Metric object that has a generic > properties map. Right now I don't think we store anything in there so that > commented portion of the code is no big deal at the moment. > > But notice the metric family name and the metric labels are all in the > same generic properties for the inventory Metric object (that's what mb is). > > I don't like this. It means who ever queries inventory has to strip out > the "hawkular.metric.family" key from the metric generic properties - the > rest of the map are the real labels. > > I think we should make these first-class attributes in the inventory model: > > mb.metricFamily(m.getMetricFamily()) > mb.metricLabels(m.getMetricLabels()) > > Thoughts? (looking at you Joel :-) > > [ps. this email was sent at 5:48pm on October 26, 2017] > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171027/3a5fdb13/attachment.html From lponce at redhat.com Fri Oct 27 03:08:20 2017 From: lponce at redhat.com (Lucas Ponce) Date: Fri, 27 Oct 2017 09:08:20 +0200 Subject: [Hawkular-dev] change to inventory metric model to store Prometheus info In-Reply-To: <1542975970.32777555.1509054488489.JavaMail.zimbra@redhat.com> References: <29791849.32773994.1509054200254.JavaMail.zimbra@redhat.com> <1542975970.32777555.1509054488489.JavaMail.zimbra@redhat.com> Message-ID: On Thu, Oct 26, 2017 at 11:48 PM, John Mazzitelli wrote: > I *think* I'm almost at the point where our inventory is able to store > Prometheus metric data (metric family name and labels) in our inventory. > Once done, you need only query inventory to get a resource's metric data > and from there you will get the Prometheus metric family+labels so you know > what you need to ask Prometheus for. > > Currently, there is no place in our Metric domain object in inventory for > this information. Right now I am putting it in that generic properties: > > // don't copy properties - we are using the inventory properties > for P labels right now > //m.getProperties().forEach((k, v) -> mb.property(k, > v.toString())); > > // map to the Prometheus metric timeseries > mb.property("hawkular.metric.family", m.getMetricFamily()); > mb.properties(m.getMetricLabels()); > > The object "m" is the agent's own Metric object that has a generic > properties map. Right now I don't think we store anything in there so that > commented portion of the code is no big deal at the moment. > > But notice the metric family name and the metric labels are all in the > same generic properties for the inventory Metric object (that's what mb is). > > I don't like this. It means who ever queries inventory has to strip out > the "hawkular.metric.family" key from the metric generic properties - the > rest of the map are the real labels. > > I think we should make these first-class attributes in the inventory model: > > mb.metricFamily(m.getMetricFamily()) > mb.metricLabels(m.getMetricLabels()) > > Thoughts? (looking at you Joel :-) > I am not Joel, but jumping here, as we have thought on this too. Do we want to split the Prometheus model ? I mean, what if we consider a metricId also opaque, and we know that in P8S is a combination of , at the end of the day, is a string and it is unique. I ask this, because if we expose the details, it will be tempted to start manipulating IDs in other layers, and perhaps that will create technical debt. So a metricId = "api_http_requests_total{method='POST', handler='/messages'}" stored in the inventory will simplify tasks in other layers as we can maintain the abstraction we are using today: get_resource(resourceId).get_metric_id(metricId) Or, I don't know if we can combine, maintaining an opaque metricId to continue the model, and adding family and labels as properties/context in those use cases are necessary. > > [ps. this email was sent at 5:48pm on October 26, 2017] > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171027/edc0a1b2/attachment.html From hrupp at redhat.com Fri Oct 27 04:26:55 2017 From: hrupp at redhat.com (Heiko Rupp) Date: Fri, 27 Oct 2017 10:26:55 +0200 Subject: [Hawkular-dev] jmx exporter - com.sun classes used In-Reply-To: <407496306.32860037.1509073665032.JavaMail.zimbra@redhat.com> References: <814257212.32859795.1509073297319.JavaMail.zimbra@redhat.com> <407496306.32860037.1509073665032.JavaMail.zimbra@redhat.com> Message-ID: That package is indeed problematic. And may be even more so in the future on JDK9+ with the module system, where modules like this may be totally encapsulated away. On Fri, Oct 27, 2017 at 5:07 AM, John Mazzitelli wrote: > Take a look at Prometheus's HTTPServer class: > > https://github.com/prometheus/client_java/blob/master/ > simpleclient_httpserver/src/main/java/io/prometheus/ > client/exporter/HTTPServer.java#L22-L24 > > This Prometheus HTTPServer class is what jmx exporter uses for its metrics > endpoint - see: > > https://github.com/prometheus/jmx_exporter/blob/master/jmx_ > prometheus_javaagent/src/main/java/io/prometheus/jmx/JavaAgent.java#L8 > https://github.com/prometheus/jmx_exporter/blob/master/jmx_ > prometheus_httpserver/src/main/java/io/prometheus/jmx/WebServer.java#L7 > > Since it uses com.sun.net.httpserver classes under the covers, I'll assume > this rules out support for, say, IBM's JVM (does IBM's JRE implement > these?). I think this is available on OpenJDK but didn't check to make 100% > sure. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -- Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 14, D-85630 Grasbrunn Handelsregister: Amtsgericht M?nchen HRB 153243 Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171027/e1e825e6/attachment-0001.html From mazz at redhat.com Fri Oct 27 04:50:33 2017 From: mazz at redhat.com (John Mazzitelli) Date: Fri, 27 Oct 2017 04:50:33 -0400 (EDT) Subject: [Hawkular-dev] change to inventory metric model to store Prometheus info In-Reply-To: References: <29791849.32773994.1509054200254.JavaMail.zimbra@redhat.com> <1542975970.32777555.1509054488489.JavaMail.zimbra@redhat.com> Message-ID: <1846526460.32930699.1509094233400.JavaMail.zimbra@redhat.com> > I mean, what if we consider a metricId also opaque, and we know that in P8S > is a combination of , at the end of the day, is a > string and it is unique. > > I ask this, because if we expose the details, it will be tempted to start > manipulating IDs in other layers, and perhaps that will create technical > debt. Just thinking off the top of my head, Prometheus's "family{labels}" ID is not to be considered opaque. It is important, I think, that clients understand these because it is how you query in Prometheus. For example, to get a group (aggregate) metric value, you could query on just a subset of labels thus aggregating over the labels you did not specify. For example, if there is: http_requests_time{method="POST", app="my.war"} = 1.0 http_requests_time{method="POST", app="another.war"} = 1.2 http_requests_time{method="GET", app="my.war"} = 0.5 http_requests_time{method="GET", app="another.war"} = 0.6 A client (MiQ UI?) can aggregate the GET request times across all apps by knowing it only queries with the method label, like "average( http_requests_time{method="GET"} )" So therefore P metric IDs (family+labels) are not opaque - clients need to understand them a bit. From lponce at redhat.com Fri Oct 27 05:30:02 2017 From: lponce at redhat.com (Lucas Ponce) Date: Fri, 27 Oct 2017 11:30:02 +0200 Subject: [Hawkular-dev] change to inventory metric model to store Prometheus info In-Reply-To: <1846526460.32930699.1509094233400.JavaMail.zimbra@redhat.com> References: <29791849.32773994.1509054200254.JavaMail.zimbra@redhat.com> <1542975970.32777555.1509054488489.JavaMail.zimbra@redhat.com> <1846526460.32930699.1509094233400.JavaMail.zimbra@redhat.com> Message-ID: On Fri, Oct 27, 2017 at 10:50 AM, John Mazzitelli wrote: > > I mean, what if we consider a metricId also opaque, and we know that in > P8S > > is a combination of , at the end of the day, is a > > string and it is unique. > > > > I ask this, because if we expose the details, it will be tempted to start > > manipulating IDs in other layers, and perhaps that will create technical > > debt. > > Just thinking off the top of my head, Prometheus's "family{labels}" ID is > not to be considered opaque. It is important, I think, that clients > understand these because it is how you query in Prometheus. > > For example, to get a group (aggregate) metric value, you could query on > just a subset of labels thus aggregating over the labels you did not > specify. > > For example, if there is: > > http_requests_time{method="POST", app="my.war"} = 1.0 > http_requests_time{method="POST", app="another.war"} = 1.2 > http_requests_time{method="GET", app="my.war"} = 0.5 > http_requests_time{method="GET", app="another.war"} = 0.6 > > A client (MiQ UI?) can aggregate the GET request times across all apps by > knowing it only queries with the method label, like "average( > http_requests_time{method="GET"} )" > > So therefore P metric IDs (family+labels) are not opaque - clients need to > understand them a bit. > MiQ today provides an abstraction layer (which is not perfect, but it helps) to map miq identifiers used in MiQ reports and charts and native metrics identifiers. Like this: https://github.com/ManageIQ/manageiq/blob/master/product/live_metrics/middleware_server.yaml https://github.com/ManageIQ/manageiq/blob/master/product/live_metrics/middleware_datasource.yaml So, a report in MiQ is defined with this miq identifiers https://github.com/ManageIQ/manageiq/blob/master/product/charts/miq_reports/vim_perf_realtime_middleware_server.yaml The way we define the mapping between inventory and prometheus will have an important impact in MiQ code as it will be needed to change most of today's logic https://github.com/ManageIQ/manageiq-providers-hawkular/blob/master/app/models/manageiq/providers/hawkular/middleware_manager/live_metrics_capture.rb https://github.com/ManageIQ/manageiq-providers-hawkular/blob/master/app/models/manageiq/providers/hawkular/middleware_manager/alert_profile_manager.rb https://github.com/ManageIQ/manageiq/blob/master/app/models/middleware_performance.rb So, I'm just thinking loud with the new inventory how this will be translated, as I guess we will still need a metric_id at least to define the mapping, even we get benefits of the metricNames/Labels to perform specific calculations. In summary, I think we will need a metric_id (but perhaps the identifier of the inventory could be enough). -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171027/7d49db60/attachment.html From theute at redhat.com Fri Oct 27 07:55:52 2017 From: theute at redhat.com (Thomas Heute) Date: Fri, 27 Oct 2017 13:55:52 +0200 Subject: [Hawkular-dev] Hawkular APM 0.14.4 + external Elastic Search In-Reply-To: References: Message-ID: Just a note that Hawkular APM is no longer in development, our efforts are now aimed toward Jaeger. If you still need help with Hawkular APM, Gary may have some tips. Thomas On Thu, Oct 26, 2017 at 10:25 PM, Jerczey Godoy wrote: > Hello , I got the email list from irc.freenode #hawkular > > > We are attempting to make the events data (from agents) persistent, we > expect the external elastic search allows to have some sort of persistance > if there is a failure of the APM itself. > We checked the embedded elastic, and if the APM (wilfly) goes down, the > data from previous events does not remain. > > > So, we expected that an external elastic could suffice this , > we used this rpm wget https://artifacts.elastic.co/ > downloads/elasticsearch/elasticsearch-5.6.3.rpm and on the same host we > set up the APM 0.14 distrbution > we pointed the standalone.conf with the following configuration: > > > export HAWKULAR_APM_ELASTICSEARCH_CLUSTER="elasticsearch" > export HAWKULAR_APM_ELASTICSEARCH_HOSTS="localhost:9200" > > > unfortunately, this throws an error starting the APM > > *15:54:37,520 SEVERE > [org.hawkular.apm.server.elasticsearch.ElasticsearchBootstrap] > (ServerService Thread Pool -- 91) Failed to initialise Elasticsearch: > org.elasticsearch.client.transport.NoNodeAvailableException: None of the > configured nodes are available: []* > > > *16:25:16,525 INFO [org.elasticsearch.client.transport] > (elasticsearch[Jaren][generic][T#2]) [Jaren] failed to get node info for > [#transport#-1][cllnxHawkular][inet[localhost/127.0.0.1:9300 > ]], disconnecting...: > org.elasticsearch.transport.NodeDisconnectedException: > [][inet[localhost/127.0.0.1 > :9300]][cluster:monitor/nodes/info] disconnected* > > > > is there a configuration for the elastic search ? > does the external elasticsearch able to make the data persistent ? > > Any comment/help is very appreciated! > > Thanks! > > > -- > > JERCZEY GODOY > > MIDDLEWARE CONSULTANT RHCJA > > Red Hat Chile > > Avenida Apoquindo 2827, Piso 7. Santiago, Chile. > > JGodoy at RedHat.com M: 975791358 IM: @jerczey > > > TRIED. TESTED. TRUSTED. > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171027/6f719448/attachment.html From jpkroehling at redhat.com Fri Oct 27 08:11:29 2017 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Fri, 27 Oct 2017 14:11:29 +0200 Subject: [Hawkular-dev] Hawkular APM 0.14.4 + external Elastic Search In-Reply-To: References: Message-ID: On 10/26/2017 10:25 PM, Jerczey Godoy wrote: > So, we expected that an external elastic could suffice this , > we used this rpm wget > https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-5.6.3.rpm > and on the same host we set up the APM 0.14 distrbution > we pointed the standalone.conf with the following configuration: Could you try the same version that we used for the last APM version? Looks like it was 1.7.1. If it works, then there's something definitely incompatible with 5.6.3. > Any comment/help is very appreciated! I just to reinforce what Thomas said in a previous email on this thread that Hawkular APM is no longer being developed. Please, see this: http://www.hawkular.org/blog/2017/04/19/hawkular-apm-jaeger.html - Juca. From jshaughn at redhat.com Fri Oct 27 09:30:02 2017 From: jshaughn at redhat.com (Jay Shaughnessy) Date: Fri, 27 Oct 2017 09:30:02 -0400 Subject: [Hawkular-dev] change to inventory metric model to store Prometheus info In-Reply-To: References: <29791849.32773994.1509054200254.JavaMail.zimbra@redhat.com> <1542975970.32777555.1509054488489.JavaMail.zimbra@redhat.com> <1846526460.32930699.1509094233400.JavaMail.zimbra@redhat.com> Message-ID: <95d61d16-9157-3c15-8bcd-e2ea940fecfe@redhat.com> I agree with Lucas that a unique ID will help the existing model we have for the provider.? P doesn't care about this because it is designed around the slice-and-dice grouping of querying against the metric name and a subset of labels.? We do care because we need to identify the singleton time series (TS) for a metric name on a resource.? That equates to the set of key-value pairs that uniquely identify the TS.? I don't have a problem with merging the two suggestions.? We could have explicit, immutable fields for [family] name (String) and labels (Map).? We could also have an id (perhaps a hash of these two fields)? By keeping the name and label (keyset) available, we would have more flexibility for potentially using the metrics easily is some other sort of aggregation. On 10/27/2017 5:30 AM, Lucas Ponce wrote: > > > On Fri, Oct 27, 2017 at 10:50 AM, John Mazzitelli > wrote: > > > I mean, what if we consider a metricId also opaque, and we know > that in P8S > > is a combination of , at the end of the > day, is a > > string and it is unique. > > > > I ask this, because if we expose the details, it will be tempted > to start > > manipulating IDs in other layers, and perhaps that will create > technical > > debt. > > Just thinking off the top of my head, Prometheus's > "family{labels}" ID is not to be considered opaque. It is > important, I think, that clients understand these because it is > how you query in Prometheus. > > For example, to get a group (aggregate) metric value, you could > query on just a subset of labels thus aggregating over the labels > you did not specify. > > For example, if there is: > > http_requests_time{method="POST", app="my.war"} = 1.0 > http_requests_time{method="POST", app="another.war"} = 1.2 > http_requests_time{method="GET", app="my.war"} = 0.5 > http_requests_time{method="GET", app="another.war"} = 0.6 > > A client (MiQ UI?) can aggregate the GET request times across all > apps by > knowing it only queries with the method label, like "average( > http_requests_time{method="GET"} )" > > So therefore P metric IDs (family+labels) are not opaque - clients > need to understand them a bit. > > > > MiQ today provides an abstraction layer (which is not perfect, but it > helps) to map miq identifiers used in MiQ reports and charts and > native metrics identifiers. > > Like this: > > https://github.com/ManageIQ/manageiq/blob/master/product/live_metrics/middleware_server.yaml > https://github.com/ManageIQ/manageiq/blob/master/product/live_metrics/middleware_datasource.yaml > > So, a report in MiQ is defined with this miq identifiers > > https://github.com/ManageIQ/manageiq/blob/master/product/charts/miq_reports/vim_perf_realtime_middleware_server.yaml > > > The way we define the mapping between inventory and prometheus will > have an important impact in MiQ code as it will be needed to change > most of today's logic > > https://github.com/ManageIQ/manageiq-providers-hawkular/blob/master/app/models/manageiq/providers/hawkular/middleware_manager/live_metrics_capture.rb > https://github.com/ManageIQ/manageiq-providers-hawkular/blob/master/app/models/manageiq/providers/hawkular/middleware_manager/alert_profile_manager.rb > https://github.com/ManageIQ/manageiq/blob/master/app/models/middleware_performance.rb > > So, I'm just thinking loud with the new inventory how this will be > translated, as I guess we will still need a metric_id at least to > define the mapping, even we get benefits of the metricNames/Labels to > perform specific calculations. > > > In summary, I think we will need a metric_id (but perhaps the > identifier of the inventory could be enough). > > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171027/b7113350/attachment-0001.html From mwringe at redhat.com Fri Oct 27 10:30:58 2017 From: mwringe at redhat.com (Matthew Wringe) Date: Fri, 27 Oct 2017 10:30:58 -0400 Subject: [Hawkular-dev] jmx exporter - com.sun classes used In-Reply-To: References: <814257212.32859795.1509073297319.JavaMail.zimbra@redhat.com> <407496306.32860037.1509073665032.JavaMail.zimbra@redhat.com> Message-ID: I think the com.sun.* classes will work with OpenJDK (at least the JMX exporter works fine when using OpenJDK) As to whether it will work with other JVMs is another question. Is this part of the code we are forking anyways? I assume since we need to make other modifications here to support https, we might as well update this section as well. On Fri, Oct 27, 2017 at 4:26 AM, Heiko Rupp wrote: > That package is indeed problematic. And may be even more so in the future > on JDK9+ with the module system, where modules like this may be totally > encapsulated away. > > On Fri, Oct 27, 2017 at 5:07 AM, John Mazzitelli wrote: > >> Take a look at Prometheus's HTTPServer class: >> >> https://github.com/prometheus/client_java/blob/master/simple >> client_httpserver/src/main/java/io/prometheus/client/ >> exporter/HTTPServer.java#L22-L24 >> >> This Prometheus HTTPServer class is what jmx exporter uses for its >> metrics endpoint - see: >> >> https://github.com/prometheus/jmx_exporter/blob/master/jmx_p >> rometheus_javaagent/src/main/java/io/prometheus/jmx/JavaAgent.java#L8 >> https://github.com/prometheus/jmx_exporter/blob/master/jmx_p >> rometheus_httpserver/src/main/java/io/prometheus/jmx/WebServer.java#L7 >> >> Since it uses com.sun.net.httpserver classes under the covers, I'll >> assume this rules out support for, say, IBM's JVM (does IBM's JRE implement >> these?). I think this is available on OpenJDK but didn't check to make 100% >> sure. >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> > > > > -- > Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, > Werner-von-Siemens-Ring 14, D-85630 Grasbrunn > Handelsregister: Amtsgericht M?nchen HRB 153243 > Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, > Eric Shander > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171027/d9c0d29d/attachment.html From mazz at redhat.com Fri Oct 27 10:56:46 2017 From: mazz at redhat.com (John Mazzitelli) Date: Fri, 27 Oct 2017 10:56:46 -0400 (EDT) Subject: [Hawkular-dev] jmx exporter - com.sun classes used In-Reply-To: References: <814257212.32859795.1509073297319.JavaMail.zimbra@redhat.com> <407496306.32860037.1509073665032.JavaMail.zimbra@redhat.com> Message-ID: <1657798305.33140599.1509116206868.JavaMail.zimbra@redhat.com> > I think the com.sun.* classes will work with OpenJDK (at least the JMX > exporter works fine when using OpenJDK) > > As to whether it will work with other JVMs is another question. Is this > part of the code we are forking anyways? I assume since we need to make > other modifications here to support https, we might as well update this > section as well. We are using it in our forked class here: https://github.com/jmazzitelli/hawkular-agent/blob/remove-h-metrics/hawkular-agent-core/src/main/java/org/hawkular/agent/monitor/prometheus/WebServer.java#L47 Unfortunately, the way they coded up this class, it can't be subclasses and overridden. We'd have to write our own and integrate the jmx exporter stuff ourselves. Means we'll be writing a bit more code, but, yeah, once we start implementing the https stuff, we can do it all at once. > > On Fri, Oct 27, 2017 at 4:26 AM, Heiko Rupp wrote: > > > That package is indeed problematic. And may be even more so in the future > > on JDK9+ with the module system, where modules like this may be totally > > encapsulated away. > > > > On Fri, Oct 27, 2017 at 5:07 AM, John Mazzitelli wrote: > > > >> Take a look at Prometheus's HTTPServer class: > >> > >> https://github.com/prometheus/client_java/blob/master/simple > >> client_httpserver/src/main/java/io/prometheus/client/ > >> exporter/HTTPServer.java#L22-L24 > >> > >> This Prometheus HTTPServer class is what jmx exporter uses for its > >> metrics endpoint - see: > >> > >> https://github.com/prometheus/jmx_exporter/blob/master/jmx_p > >> rometheus_javaagent/src/main/java/io/prometheus/jmx/JavaAgent.java#L8 > >> https://github.com/prometheus/jmx_exporter/blob/master/jmx_p > >> rometheus_httpserver/src/main/java/io/prometheus/jmx/WebServer.java#L7 > >> > >> Since it uses com.sun.net.httpserver classes under the covers, I'll > >> assume this rules out support for, say, IBM's JVM (does IBM's JRE > >> implement > >> these?). I think this is available on OpenJDK but didn't check to make > >> 100% > >> sure. > >> _______________________________________________ > >> hawkular-dev mailing list > >> hawkular-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/hawkular-dev > >> > > > > > > > > -- > > Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, > > Werner-von-Siemens-Ring 14, D-85630 Grasbrunn > > Handelsregister: Amtsgericht M?nchen HRB 153243 > > Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, > > Eric Shander > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > From mazz at redhat.com Fri Oct 27 17:54:51 2017 From: mazz at redhat.com (John Mazzitelli) Date: Fri, 27 Oct 2017 17:54:51 -0400 (EDT) Subject: [Hawkular-dev] javaagent and domain mode Message-ID: <923728418.33384735.1509141291848.JavaMail.zimbra@redhat.com> Who has successfully run the Java Agent in a WildFly host controller (i.e. domain mode)?? I can't seem to get this to work [1] - its the agent's wildfly distro (a wildfly+agent distro) with a new domain.conf file so you can use this distro to test the agent in domain mode, but it isn't working. Getting the typical class not found errors for the logging stuff (I really hate this problem). Anyone have ideas what is wrong and how to fix? [1] https://github.com/hawkular/hawkular-agent/pull/384/files From jmartine at redhat.com Fri Oct 27 23:19:39 2017 From: jmartine at redhat.com (Josejulio Martinez Magana) Date: Sat, 28 Oct 2017 03:19:39 +0000 Subject: [Hawkular-dev] javaagent and domain mode In-Reply-To: <923728418.33384735.1509141291848.JavaMail.zimbra@redhat.com> References: <923728418.33384735.1509141291848.JavaMail.zimbra@redhat.com> Message-ID: I got it working, is in a docker image on the agent repository. See: https://github.com/hawkular/hawkular-agent/pull/382/files I had to use wildfly 11.0.0. It appears you are missing the jboss.host.server-excluded-properties El El vie, 27 de octubre de 2017 a la(s) 17:55, John Mazzitelli < mazz at redhat.com> escribi?: > Who has successfully run the Java Agent in a WildFly host controller (i.e. > domain mode)?? > > I can't seem to get this to work [1] - its the agent's wildfly distro (a > wildfly+agent distro) with a new domain.conf file so you can use this > distro to test the agent in domain mode, but it isn't working. Getting the > typical class not found errors for the logging stuff (I really hate this > problem). > > Anyone have ideas what is wrong and how to fix? > > [1] https://github.com/hawkular/hawkular-agent/pull/384/files > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171028/6ae4ca01/attachment.html From mazz at redhat.com Sat Oct 28 16:10:43 2017 From: mazz at redhat.com (John Mazzitelli) Date: Sat, 28 Oct 2017 16:10:43 -0400 (EDT) Subject: [Hawkular-dev] javaagent and domain mode In-Reply-To: References: <923728418.33384735.1509141291848.JavaMail.zimbra@redhat.com> Message-ID: <196825021.33871624.1509221443532.JavaMail.zimbra@redhat.com> Thanks. Got it working by forcing the distro to build with WildFly 11 and using that server-excluded-properties feature. ----- Original Message ----- > I got it working, is in a docker image on the agent repository. > > See: https://github.com/hawkular/hawkular-agent/pull/382/files > > I had to use wildfly 11.0.0. > It appears you are missing the jboss.host.server-excluded-properties > > El El vie, 27 de octubre de 2017 a la(s) 17:55, John Mazzitelli < > mazz at redhat.com> escribi?: > > > Who has successfully run the Java Agent in a WildFly host controller (i.e. > > domain mode)?? > > > > I can't seem to get this to work [1] - its the agent's wildfly distro (a > > wildfly+agent distro) with a new domain.conf file so you can use this > > distro to test the agent in domain mode, but it isn't working. Getting the > > typical class not found errors for the logging stuff (I really hate this > > problem). > > > > Anyone have ideas what is wrong and how to fix? > > > > [1] https://github.com/hawkular/hawkular-agent/pull/384/files > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > From mazz at redhat.com Sun Oct 29 08:30:26 2017 From: mazz at redhat.com (John Mazzitelli) Date: Sun, 29 Oct 2017 08:30:26 -0400 (EDT) Subject: [Hawkular-dev] agent can now link prometheus metrics in inventory In-Reply-To: <1104416817.33960920.1509279211909.JavaMail.zimbra@redhat.com> Message-ID: <2136050331.33961361.1509280226122.JavaMail.zimbra@redhat.com> The agent in branch hawkular-1275 can now link Prometheus metric family names/labels into hawkular inventory (at least, it looks like its working :-) You will see metrics in inventory that look like the below examples - notice the general props on the metrics now contain Prometheus metric labels - there is one extra property called "hawkular.metric.family" and that is, obviously, the Prometheus metric family name. The rest are Prometheus metric labels. We need to change this, I think. We should have first-class fields on the inventory Metric object for "String metricFamily" and "Map metricLabels". But for now, we are using general properties. So for example, to query the "Pool Create Count" metric data from Prometheus for the Stateless Session EJB resource called "InventoryServiceIspn" you look up its metric metadata in hawkular inventory, see the following metadata I show below, and then you know have to query this in Prometheus: wildfly_ejb_pool_create_count{deployment=hawkular-inventory-service.war, name=InventoryServiceIspn, feed-id=mazzlap} We do not have unique metric IDs being stored yet. We should figure out if we really need them before we store more data in inventory. Also, the JMX exporter does not actually put the feed-id label on metrics - that will be the job of the Prometheus server and its scrape definition. But we know it will need to be there, so inventory will specify it. { "name": "Pool Create Count", "type": "Pool Create Count", "unit": "NONE", "properties": { "feed-id": "mazzlap", "name": "InventoryServiceIspn", "type": "stateless-session", "hawkular.metric.family": "wildfly_ejb_pool_create_count", "deployment": "hawkular-inventory-service.war" } Here's other examples you will see in inventory: { "name": "Max Active Sessions", "type": "Max Active Sessions", "unit": "NONE", "properties": { "feed-id": "mazzlap", "hawkular.metric.family": "wildfly_deployment_max_active_sessions", "deployment": "hawkular-inventory-service.war" } { "name": "Heap Used", "type": "Heap Used", "unit": "BYTES", "properties": { "area": "heap", "feed-id": "mazzlap", "hawkular.metric.family": "jvm_memory_bytes_used" } From mazz at redhat.com Sun Oct 29 21:03:54 2017 From: mazz at redhat.com (John Mazzitelli) Date: Sun, 29 Oct 2017 21:03:54 -0400 (EDT) Subject: [Hawkular-dev] possible bug in inventory server In-Reply-To: <131097386.34268802.1509322878797.JavaMail.zimbra@redhat.com> Message-ID: <2081173691.34285872.1509325434574.JavaMail.zimbra@redhat.com> This agent itest error on travis just happened to me locally. After looking at it, I think it is a bug in inventory REST server. I'll try to explain as briefly as I can. In this particular itest [B] it creates datasources in WildFly, checks that they exist in h-inventory, removes those datasources from WildFly, and checks that they no longer exist in h-inventory. For some reason, after it is removed from WildFly and inventory, a REST query to inventory says it is still there (even though a previous, different, query said it was not there). Here's what I see: 1. "testXaDs" is an XA datasource that is created in Wildfly and the agent stored it in inventory. A "get all resources" inventory REST query "hawkular/inventory/resources?feedId=itest-rest-feed" shows it exists in inventory: testXaDs id: itest-rest-feed~Local DMR~/subsystem=datasources/xa-data-source=testXaDs parent: itest-rest-feed~Local DMR~~ type: XA Datasource 2. The test then removes that datasource from WildFly (the itest asserts via a DMR query that it is gone from WildFly). Then, making that same inventory REST query "hawkular/inventory/resources?feedId=itest-rest-feed" that "testXaDs" is not in the list - it is gone from inventory based on that "get all resources" query. This is good and expected. We see the datasource successfully removed from inventory after WildFly deleted it. 3. But then the itest queries inventory using a different REST URL (filtered on type ID): "/hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource" and this time I GET RESULTS back saying that "testXaDs" resource is still there! Even though the "get all resources" query said it was not there. This is the call here [C] which ends up at this inventory REST request [D]. Who wants to investigate the inventory service to see if I'm right that there is a bug here? If there is no bug in inventory, the only other option is it's a bug in the itest code, but I checked and everything looks good to me there. I can't see a problem in the itest code. And the fact this is intermittent (passes sometimes, fails sometimes) tells me there is something sinister going on in the inventory server (i.e. if it is a problem in the test code, you would think it would always fail). ~~~~~~~~~~ [D] https://github.com/hawkular/hawkular-agent/blob/hawkular-1275/hawkular-agent-itest-util/src/main/java/org/hawkular/agent/itest/util/ITestHelper.java#L93 [C] https://github.com/hawkular/hawkular-agent/blob/hawkular-1275/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/src/test/java/org/hawkular/agent/ws/test/DatasourceCommandITest.java#L377 [B] https://github.com/hawkular/hawkular-agent/blob/hawkular-1275/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/src/test/java/org/hawkular/agent/ws/test/DatasourceCommandITest.java [A] Here's the full output from the test along with the itest assertion error stack trace. There is a lot of junk, but in short, it shows the XA datasource called "testXaDs" is in inventory, then the test deletes it, we see "testXaDs" is no longer in inventory (that print out of the inventory list comes from query results of that "get all resources" REST query), but a query to inventory REST API filtering on typeId says it is still there. Doesn't happen all the time, happens half the time in travis and just happened locally to me. ===== Got code 200 and message [OK] retries: http://127.0.0.1:8080/hawkular/inventory/resources?feedId=itest-rest-feed&typeId=Datasource [Invoker 211968962] Invoking @AfterMethod AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] [Invoker 211968962] Invoking @BeforeMethod AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] [Invoker 211968962] Invoking org.hawkular.agent.ws.test.DatasourceCommandITest.testRemoveXaDatasource Got code 200 and message [OK] retries: http://127.0.0.1:8080/hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource Got code 200 and message [OK] retries: http://127.0.0.1:8080/hawkular/inventory/resources?feedId=itest-rest-feed ALL RESOURCES IN HAWKULAR INVENTORY: 67 ===== testXaDs exists and will be removed ===== --- Hawkular Java Agent id: itest-rest-feed~Local JMX~org.hawkular:type=hawkular-javaagent parent: null type: Hawkular Java Agent --- JMX [Local JMX] MemoryPool Metaspace id: itest-rest-feed~Local JMX~java.lang:name=Metaspace,type=MemoryPool parent: itest-rest-feed~Local JMX~java.lang:type=Runtime type: Memory Pool MBean --- Processor [3] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/PROCESSOR=3 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Processor --- JMX [Remote JMX] MemoryPool PS Old Gen id: itest-rest-feed~Remote JMX~java.lang:name=PS Old Gen,type=MemoryPool parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime type: Memory Pool MBean --- jolokia-war.war id: itest-rest-feed~Local DMR~/deployment=jolokia-war.war parent: itest-rest-feed~Local DMR~~ type: Deployment --- hawkular-alerts id: itest-rest-feed~Local DMR~/subsystem=infinispan/cache-container=hawkular-alerts parent: itest-rest-feed~Local DMR~/subsystem=infinispan type: Infinispan Cache Container --- DLQ id: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default/jms-queue=DLQ parent: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default type: JMS Queue --- InventoryServiceIspn id: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war/subsystem=ejb3/stateless-session-bean=InventoryServiceIspn parent: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war type: Stateless Session EJB --- ajp id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets/socket-binding=ajp parent: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets type: Socket Binding --- mail-smtp id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=mail-smtp parent: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets type: Remote Destination Outbound Socket Binding --- https id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets/socket-binding=https parent: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets type: Socket Binding --- management-https id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets/socket-binding=management-https parent: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets type: Socket Binding --- InventoryStats id: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war/subsystem=ejb3/singleton-bean=InventoryStats parent: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war type: Singleton EJB --- testXaDs id: itest-rest-feed~Local DMR~/subsystem=datasources/xa-data-source=testXaDs parent: itest-rest-feed~Local DMR~~ type: XA Datasource --- File Store [/dev/mapper/fedora_mazzwork-home] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/FILE_STORE=/dev/mapper/fedora_mazzwork-home parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_File Store --- Memory id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/MEMORY=Memory parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Memory --- Processor [2] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/PROCESSOR=2 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Processor --- File Store [/dev/sda1] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/FILE_STORE=/dev/sda1 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_File Store --- JMX [Remote JMX] MemoryPool Code Cache id: itest-rest-feed~Remote JMX~java.lang:name=Code Cache,type=MemoryPool parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime type: Memory Pool MBean --- JMX [Remote JMX] MemoryPool Metaspace id: itest-rest-feed~Remote JMX~java.lang:name=Metaspace,type=MemoryPool parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime type: Memory Pool MBean --- JMX [Remote JMX] MemoryPool PS Survivor Space id: itest-rest-feed~Remote JMX~java.lang:name=PS Survivor Space,type=MemoryPool parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime type: Memory Pool MBean --- txn-recovery-environment id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets/socket-binding=txn-recovery-environment parent: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets type: Socket Binding --- default id: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default parent: itest-rest-feed~Local DMR~~ type: Messaging Server --- Infinispan id: itest-rest-feed~Local DMR~/subsystem=infinispan parent: itest-rest-feed~Local DMR~~ type: Infinispan --- jolokia-agent id: itest-rest-feed~Local DMR~/deployment=jolokia-war.war/subsystem=undertow/servlet=jolokia-agent parent: itest-rest-feed~Local DMR~/deployment=jolokia-war.war type: Servlet --- hawkular-inventory-ui.war id: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-ui.war parent: itest-rest-feed~Local DMR~~ type: Deployment --- hawkular-services id: itest-rest-feed~Local DMR~/subsystem=infinispan/cache-container=hawkular-services parent: itest-rest-feed~Local DMR~/subsystem=infinispan type: Infinispan Cache Container --- web id: itest-rest-feed~Local DMR~/subsystem=infinispan/cache-container=web parent: itest-rest-feed~Local DMR~/subsystem=infinispan type: Infinispan Cache Container --- management-http id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets/socket-binding=management-http parent: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets type: Socket Binding --- JMX [Local JMX] MemoryPool PS Survivor Space id: itest-rest-feed~Local JMX~java.lang:name=PS Survivor Space,type=MemoryPool parent: itest-rest-feed~Local JMX~java.lang:type=Runtime type: Memory Pool MBean --- JMX [Local JMX] MemoryPool PS Eden Space id: itest-rest-feed~Local JMX~java.lang:name=PS Eden Space,type=MemoryPool parent: itest-rest-feed~Local JMX~java.lang:type=Runtime type: Memory Pool MBean --- JMX [Local JMX] MemoryPool Code Cache id: itest-rest-feed~Local JMX~java.lang:name=Code Cache,type=MemoryPool parent: itest-rest-feed~Local JMX~java.lang:type=Runtime type: Memory Pool MBean --- Processor [7] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/PROCESSOR=7 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Processor --- Processor [1] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/PROCESSOR=1 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Processor --- txn-status-manager id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets/socket-binding=txn-status-manager parent: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets type: Socket Binding --- ejb id: itest-rest-feed~Local DMR~/subsystem=infinispan/cache-container=ejb parent: itest-rest-feed~Local DMR~/subsystem=infinispan type: Infinispan Cache Container --- h2 id: itest-rest-feed~Local DMR~/subsystem=datasources/jdbc-driver=h2 parent: itest-rest-feed~Local DMR~~ type: JDBC Driver --- File Store [tmpfs] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/FILE_STORE=tmpfs parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_File Store --- Processor [0] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/PROCESSOR=0 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Processor --- Processor [6] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/PROCESSOR=6 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Processor --- JMX [Remote JMX] MemoryPool PS Eden Space id: itest-rest-feed~Remote JMX~java.lang:name=PS Eden Space,type=MemoryPool parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime type: Memory Pool MBean --- JMX [Remote JMX][Runtime] id: itest-rest-feed~Remote JMX~java.lang:type=Runtime parent: null type: Runtime MBean --- JMX [Local JMX] MemoryPool PS Old Gen id: itest-rest-feed~Local JMX~java.lang:name=PS Old Gen,type=MemoryPool parent: itest-rest-feed~Local JMX~java.lang:type=Runtime type: Memory Pool MBean --- HawkularQueue id: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default/jms-topic=HawkularQueue parent: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default type: JMS Topic --- Local DMR id: itest-rest-feed~Local DMR~~ parent: null type: WildFly Server --- HawkularTopic id: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default/jms-topic=HawkularTopic parent: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default type: JMS Topic --- hawkular-command-gateway-war.war id: itest-rest-feed~Local DMR~/deployment=hawkular-command-gateway-war.war parent: itest-rest-feed~Local DMR~~ type: Deployment --- hibernate id: itest-rest-feed~Local DMR~/subsystem=infinispan/cache-container=hibernate parent: itest-rest-feed~Local DMR~/subsystem=infinispan type: Infinispan Cache Container --- HawkularCommandEvent id: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default/jms-topic=HawkularCommandEvent parent: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default type: JMS Topic --- File Store [/dev/mapper/fedora_mazzwork-root] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/FILE_STORE=/dev/mapper/fedora_mazzwork-root parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_File Store --- Processor [5] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/PROCESSOR=5 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Processor --- JMX [Local JMX][Runtime] id: itest-rest-feed~Local JMX~java.lang:type=Runtime parent: null type: Runtime MBean --- JMX [Local JMX] MemoryPool Compressed Class Space id: itest-rest-feed~Local JMX~java.lang:name=Compressed Class Space,type=MemoryPool parent: itest-rest-feed~Local JMX~java.lang:type=Runtime type: Memory Pool MBean --- server id: itest-rest-feed~Local DMR~/subsystem=infinispan/cache-container=server parent: itest-rest-feed~Local DMR~/subsystem=infinispan type: Infinispan Cache Container --- standard-sockets id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets parent: itest-rest-feed~Local DMR~~ type: Socket Binding Group --- hawkular-inventory-service.war id: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war parent: itest-rest-feed~Local DMR~~ type: Deployment --- JMX [Remote JMX] MemoryPool Compressed Class Space id: itest-rest-feed~Remote JMX~java.lang:name=Compressed Class Space,type=MemoryPool parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime type: Memory Pool MBean --- File Store [/] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/FILE_STORE=~ parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_File Store --- itest-rest-feed_OperatingSystem id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem parent: null type: Platform_Operating System --- Processor [4] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/PROCESSOR=4 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Processor --- ExampleDS id: itest-rest-feed~Local DMR~/subsystem=datasources/data-source=ExampleDS parent: itest-rest-feed~Local DMR~~ type: Datasource --- ExpiryQueue id: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default/jms-queue=ExpiryQueue parent: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default type: JMS Queue --- org.hawkular.inventory.handlers.InventoryApp id: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war/subsystem=undertow/servlet=org.hawkular.inventory.handlers.InventoryApp parent: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war type: Servlet --- http id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets/socket-binding=http parent: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets type: Socket Binding --- Transaction Manager id: itest-rest-feed~Local DMR~/subsystem=transactions parent: itest-rest-feed~Local DMR~~ type: Transaction Manager --- InventoryConfig id: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war/subsystem=ejb3/singleton-bean=InventoryConfig parent: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war type: Singleton EJB --- HawkularInventoryChanges id: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default/jms-topic=HawkularInventoryChanges parent: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default type: JMS Topic ===== Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener onOpen FINE: WebSocket opened 20:13:29,091 INFO [org.hawkular.cmdgw.command.ws.server.UIClientWebSocket] (default task-42) HAWKFEEDCOMM000013: WebSocket session [Hgf9Zznsx_y9U14uaHPPWIPuSarLogLgugUCweVK] opened for endpoint [/ui/ws] Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener handle FINE: Received message[0] from WebSocket: [ActualMessage [type=application/vnd.okhttp.websocket+text; charset=utf-8, body=WelcomeResponse={"sessionId":"Hgf9Zznsx_y9U14uaHPPWIPuSarLogLgugUCweVK"}]] Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener handle FINE: Message[0]: [PASSED] Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$MessageAnswer$1 run FINE: Sending over WebSocket: RemoveDatasourceRequest={"authentication":{"username":"itest-rest","password":"itest-rest-password"}, "feedId":"itest-rest-feed","resourceId":"itest-rest-feed~Local DMR~/subsystem=datasources/xa-data-source=testXaDs"} Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$MessageAnswer$1 run FINE: No sleep configured 20:13:29,102 INFO [org.hawkular.cmdgw.command.ws.server.AbstractGatewayWebSocket] (default task-43) HAWKFEEDCOMM000014: Received message [org.hawkular.cmdgw.api.RemoveDatasourceRequest] from WebSocket session [Hgf9Zznsx_y9U14uaHPPWIPuSarLogLgugUCweVK] of [/ui/ws] Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener handle FINE: Received message[1] from WebSocket: [ActualMessage [type=application/vnd.okhttp.websocket+text; charset=utf-8, body=GenericSuccessResponse={"message":"The request has been forwarded to feed [itest-rest-feed] (MessageId=ID:27f779d9-bd07-11e7-a03b-55f35baba5f1)"}]] Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener handle FINE: Message[1]: [PASSED] Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$ExpectedEvent scheduleAnswer FINE: No answer to send for message[1] 20:13:29,108 INFO [org.hawkular.agent.monitor.cmd.AbstractDMRResourcePathCommand] (OkHttp http://127.0.0.1:8080/...) HAWKAGENT010065: Received request to perform [Remove] on a [Datasource] given by inventory path [itest-rest-feed~Local DMR~/subsystem=datasources/xa-data-source=testXaDs] 20:13:29,150 INFO [org.hawkular.cmdgw.command.ws.server.AbstractGatewayWebSocket] (default task-47) HAWKFEEDCOMM000014: Received message [org.hawkular.cmdgw.api.RemoveDatasourceResponse] from WebSocket session [AQNPLng4hq-vgfGOOo53kVpLuQjVcKvzXAzwqPS3] of [/feed/{feedId}] Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener handle FINE: Received message[2] from WebSocket: [ActualMessage [type=application/vnd.okhttp.websocket+text; charset=utf-8, body=RemoveDatasourceResponse={"feedId":"itest-rest-feed","resourceId":"itest-rest-feed~Local DMR~/subsystem=datasources/xa-data-source=testXaDs","destinationSessionId":"Hgf9Zznsx_y9U14uaHPPWIPuSarLogLgugUCweVK","status":"OK","message":"Performed [Remove] on a [Datasource] given by Feed Id [itest-rest-feed] Resource Id [itest-rest-feed~Local DMR~/subsystem=datasources/xa-data-source=testXaDs]","serverRefreshIndicator":"RELOAD-REQUIRED"}]] Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener handle FINE: Message[2]: [PASSED] Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$Answer$1 lambda$schedule$0 FINE: About to send manual close Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$Answer$1 lambda$schedule$0 FINE: Close sent 20:13:29,156 INFO [org.hawkular.cmdgw.command.ws.server.UIClientWebSocket] (default task-44) HAWKFEEDCOMM000015: WebSocket session [Hgf9Zznsx_y9U14uaHPPWIPuSarLogLgugUCweVK] of [/ui/ws] closed. Reason=[CloseReason[1000,OK]] Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener handle FINE: Received message[3] from WebSocket: [ActualClose [code=1000, reason=OK]] Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener handle FINE: Message[3]: [PASSED] Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$ExpectedEvent scheduleAnswer FINE: No answer to send for message[3] Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener handle FINE: Message[3] was the last expected message, sending close. Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener close FINE: Closing the websocket Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener shutDownExecutor FINE: Shutting down the executor Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener shutDownExecutor FINE: Executor shut down Got code 200 and message [OK] retries: http://127.0.0.1:8080/hawkular/inventory/resources?feedId=itest-rest-feed ALL RESOURCES IN HAWKULAR INVENTORY: 66 ===== testXaDs deleted, should be out of inventory ===== --- Hawkular Java Agent id: itest-rest-feed~Local JMX~org.hawkular:type=hawkular-javaagent parent: null type: Hawkular Java Agent --- JMX [Local JMX] MemoryPool Metaspace id: itest-rest-feed~Local JMX~java.lang:name=Metaspace,type=MemoryPool parent: itest-rest-feed~Local JMX~java.lang:type=Runtime type: Memory Pool MBean --- Processor [3] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/PROCESSOR=3 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Processor --- JMX [Remote JMX] MemoryPool PS Old Gen id: itest-rest-feed~Remote JMX~java.lang:name=PS Old Gen,type=MemoryPool parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime type: Memory Pool MBean --- jolokia-war.war id: itest-rest-feed~Local DMR~/deployment=jolokia-war.war parent: itest-rest-feed~Local DMR~~ type: Deployment --- hawkular-alerts id: itest-rest-feed~Local DMR~/subsystem=infinispan/cache-container=hawkular-alerts parent: itest-rest-feed~Local DMR~/subsystem=infinispan type: Infinispan Cache Container --- DLQ id: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default/jms-queue=DLQ parent: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default type: JMS Queue --- InventoryServiceIspn id: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war/subsystem=ejb3/stateless-session-bean=InventoryServiceIspn parent: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war type: Stateless Session EJB --- ajp id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets/socket-binding=ajp parent: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets type: Socket Binding --- mail-smtp id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=mail-smtp parent: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets type: Remote Destination Outbound Socket Binding --- https id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets/socket-binding=https parent: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets type: Socket Binding --- management-https id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets/socket-binding=management-https parent: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets type: Socket Binding --- InventoryStats id: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war/subsystem=ejb3/singleton-bean=InventoryStats parent: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war type: Singleton EJB --- File Store [/dev/mapper/fedora_mazzwork-home] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/FILE_STORE=/dev/mapper/fedora_mazzwork-home parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_File Store --- Memory id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/MEMORY=Memory parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Memory --- Processor [2] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/PROCESSOR=2 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Processor --- File Store [/dev/sda1] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/FILE_STORE=/dev/sda1 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_File Store --- JMX [Remote JMX] MemoryPool Code Cache id: itest-rest-feed~Remote JMX~java.lang:name=Code Cache,type=MemoryPool parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime type: Memory Pool MBean --- JMX [Remote JMX] MemoryPool Metaspace id: itest-rest-feed~Remote JMX~java.lang:name=Metaspace,type=MemoryPool parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime type: Memory Pool MBean --- JMX [Remote JMX] MemoryPool PS Survivor Space id: itest-rest-feed~Remote JMX~java.lang:name=PS Survivor Space,type=MemoryPool parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime type: Memory Pool MBean --- txn-recovery-environment id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets/socket-binding=txn-recovery-environment parent: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets type: Socket Binding --- default id: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default parent: itest-rest-feed~Local DMR~~ type: Messaging Server --- Infinispan id: itest-rest-feed~Local DMR~/subsystem=infinispan parent: itest-rest-feed~Local DMR~~ type: Infinispan --- jolokia-agent id: itest-rest-feed~Local DMR~/deployment=jolokia-war.war/subsystem=undertow/servlet=jolokia-agent parent: itest-rest-feed~Local DMR~/deployment=jolokia-war.war type: Servlet --- hawkular-inventory-ui.war id: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-ui.war parent: itest-rest-feed~Local DMR~~ type: Deployment --- hawkular-services id: itest-rest-feed~Local DMR~/subsystem=infinispan/cache-container=hawkular-services parent: itest-rest-feed~Local DMR~/subsystem=infinispan type: Infinispan Cache Container --- web id: itest-rest-feed~Local DMR~/subsystem=infinispan/cache-container=web parent: itest-rest-feed~Local DMR~/subsystem=infinispan type: Infinispan Cache Container --- management-http id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets/socket-binding=management-http parent: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets type: Socket Binding --- JMX [Local JMX] MemoryPool PS Survivor Space id: itest-rest-feed~Local JMX~java.lang:name=PS Survivor Space,type=MemoryPool parent: itest-rest-feed~Local JMX~java.lang:type=Runtime type: Memory Pool MBean --- JMX [Local JMX] MemoryPool PS Eden Space id: itest-rest-feed~Local JMX~java.lang:name=PS Eden Space,type=MemoryPool parent: itest-rest-feed~Local JMX~java.lang:type=Runtime type: Memory Pool MBean --- JMX [Local JMX] MemoryPool Code Cache id: itest-rest-feed~Local JMX~java.lang:name=Code Cache,type=MemoryPool parent: itest-rest-feed~Local JMX~java.lang:type=Runtime type: Memory Pool MBean --- Processor [7] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/PROCESSOR=7 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Processor --- Processor [1] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/PROCESSOR=1 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Processor --- txn-status-manager id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets/socket-binding=txn-status-manager parent: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets type: Socket Binding --- ejb id: itest-rest-feed~Local DMR~/subsystem=infinispan/cache-container=ejb parent: itest-rest-feed~Local DMR~/subsystem=infinispan type: Infinispan Cache Container --- h2 id: itest-rest-feed~Local DMR~/subsystem=datasources/jdbc-driver=h2 parent: itest-rest-feed~Local DMR~~ type: JDBC Driver --- File Store [tmpfs] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/FILE_STORE=tmpfs parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_File Store --- Processor [0] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/PROCESSOR=0 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Processor --- Processor [6] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/PROCESSOR=6 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Processor --- JMX [Remote JMX] MemoryPool PS Eden Space id: itest-rest-feed~Remote JMX~java.lang:name=PS Eden Space,type=MemoryPool parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime type: Memory Pool MBean --- JMX [Remote JMX][Runtime] id: itest-rest-feed~Remote JMX~java.lang:type=Runtime parent: null type: Runtime MBean --- JMX [Local JMX] MemoryPool PS Old Gen id: itest-rest-feed~Local JMX~java.lang:name=PS Old Gen,type=MemoryPool parent: itest-rest-feed~Local JMX~java.lang:type=Runtime type: Memory Pool MBean --- HawkularQueue id: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default/jms-topic=HawkularQueue parent: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default type: JMS Topic --- Local DMR id: itest-rest-feed~Local DMR~~ parent: null type: WildFly Server --- HawkularTopic id: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default/jms-topic=HawkularTopic parent: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default type: JMS Topic --- hawkular-command-gateway-war.war id: itest-rest-feed~Local DMR~/deployment=hawkular-command-gateway-war.war parent: itest-rest-feed~Local DMR~~ type: Deployment --- hibernate id: itest-rest-feed~Local DMR~/subsystem=infinispan/cache-container=hibernate parent: itest-rest-feed~Local DMR~/subsystem=infinispan type: Infinispan Cache Container --- HawkularCommandEvent id: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default/jms-topic=HawkularCommandEvent parent: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default type: JMS Topic --- File Store [/dev/mapper/fedora_mazzwork-root] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/FILE_STORE=/dev/mapper/fedora_mazzwork-root parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_File Store --- Processor [5] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/PROCESSOR=5 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Processor --- JMX [Local JMX][Runtime] id: itest-rest-feed~Local JMX~java.lang:type=Runtime parent: null type: Runtime MBean --- JMX [Local JMX] MemoryPool Compressed Class Space id: itest-rest-feed~Local JMX~java.lang:name=Compressed Class Space,type=MemoryPool parent: itest-rest-feed~Local JMX~java.lang:type=Runtime type: Memory Pool MBean --- server id: itest-rest-feed~Local DMR~/subsystem=infinispan/cache-container=server parent: itest-rest-feed~Local DMR~/subsystem=infinispan type: Infinispan Cache Container --- standard-sockets id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets parent: itest-rest-feed~Local DMR~~ type: Socket Binding Group --- hawkular-inventory-service.war id: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war parent: itest-rest-feed~Local DMR~~ type: Deployment --- JMX [Remote JMX] MemoryPool Compressed Class Space id: itest-rest-feed~Remote JMX~java.lang:name=Compressed Class Space,type=MemoryPool parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime type: Memory Pool MBean --- File Store [/] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/FILE_STORE=~ parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_File Store --- itest-rest-feed_OperatingSystem id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem parent: null type: Platform_Operating System --- Processor [4] id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem/PROCESSOR=4 parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest-feed_OperatingSystem type: Platform_Processor --- ExampleDS id: itest-rest-feed~Local DMR~/subsystem=datasources/data-source=ExampleDS parent: itest-rest-feed~Local DMR~~ type: Datasource --- ExpiryQueue id: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default/jms-queue=ExpiryQueue parent: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default type: JMS Queue --- org.hawkular.inventory.handlers.InventoryApp id: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war/subsystem=undertow/servlet=org.hawkular.inventory.handlers.InventoryApp parent: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war type: Servlet --- http id: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets/socket-binding=http parent: itest-rest-feed~Local DMR~/socket-binding-group=standard-sockets type: Socket Binding --- Transaction Manager id: itest-rest-feed~Local DMR~/subsystem=transactions parent: itest-rest-feed~Local DMR~~ type: Transaction Manager --- InventoryConfig id: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war/subsystem=ejb3/singleton-bean=InventoryConfig parent: itest-rest-feed~Local DMR~/deployment=hawkular-inventory-service.war type: Singleton EJB --- HawkularInventoryChanges id: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default/jms-topic=HawkularInventoryChanges parent: itest-rest-feed~Local DMR~/subsystem=messaging-activemq/server=default type: JMS Topic ===== 20:13:29,186 ERROR [org.hawkular.agent.monitor.storage.HawkularStorageAdapter] (OkHttp http://127.0.0.1:8080/...) HAWKAGENT010083: Failed to store notification: {"type":"RESOURCE_ADDED","properties":{"resourceId":"itest-rest-feed~Local DMR~~","feedId":"itest-rest-feed","resourceType":"WildFly Server"}}: java.io.IOException: status-code=[405], reason=[Method Not Allowed], url=[http://127.0.0.1:8080/hawkular/api/notification] at org.hawkular.agent.monitor.storage.HawkularStorageAdapter$1.onResponse(HawkularStorageAdapter.java:116) at okhttp3.shaded.RealCall$AsyncCall.execute(RealCall.java:126) at okhttp3.shaded.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Got code 200 and message [OK] retries: http://127.0.0.1:8080/hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource Got code 200 and message [OK] retries: http://127.0.0.1:8080/hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource Got code 200 and message [OK] retries: http://127.0.0.1:8080/hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource Got code 200 and message [OK] retries: http://127.0.0.1:8080/hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource Got code 200 and message [OK] retries: http://127.0.0.1:8080/hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource Got code 200 and message [OK] retries: http://127.0.0.1:8080/hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource Got code 200 and message [OK] retries: http://127.0.0.1:8080/hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource Got code 200 and message [OK] retries: http://127.0.0.1:8080/hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource Got code 200 and message [OK] retries: http://127.0.0.1:8080/hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource Got code 200 and message [OK] retries: http://127.0.0.1:8080/hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource [Invoker 211968962] Invoking @AfterMethod AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] ===== Invoked methods AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 StandaloneWildFlyITest.testAgent()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 StandaloneWildFlyITest.datasourcesAddedToInventory()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 StandaloneWildFlyITest.operationParameters()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 StandaloneWildFlyITest.socketBindingGroupsInInventory()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 StandaloneWildFlyITest.machineId()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 StandaloneWildFlyITest.resourceConfig()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.ExecuteOperationCommandITest at 77e4c80f] 2011482127 ExecuteOperationCommandITest.testExecuteAgentDiscoveryScan()[pri:0, instance:org.hawkular.agent.ws.test.ExecuteOperationCommandITest at 77e4c80f] 2011482127 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.ExecuteOperationCommandITest at 77e4c80f] 2011482127 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 StandaloneDeployApplicationITest.testAddDeployment()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 StandaloneDeployApplicationITest.testDisableDeployment()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 StandaloneDeployApplicationITest.testEnableDeployment()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 StandaloneDeployApplicationITest.testRestartDeployment()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 StandaloneDeployApplicationITest.testLocalAndRemoteJMXOperations()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 StandaloneDeployApplicationITest.testUndeploy()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITest at 351d0846] 891095110 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.ExportJdrCommandITest at 176d53b2] 393040818 ExportJdrCommandITest.exportJdrCommand()[pri:0, instance:org.hawkular.agent.ws.test.ExportJdrCommandITest at 176d53b2] 393040818 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.ExportJdrCommandITest at 176d53b2] 393040818 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 DatasourceCommandITest.testAddDatasource()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 DatasourceCommandITest.testAddXaDatasource()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 DatasourceCommandITest.testUpdateDatasource()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 DatasourceCommandITest.testUpdateXaDatasource()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 DatasourceCommandITest.testRemoveDatasource()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 DatasourceCommandITest.testRemoveXaDatasource()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] 1147258851 ===== Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/Surefire suite/Surefire test.html Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/Surefire suite/Surefire test.xml PASSED: testAgent PASSED: datasourcesAddedToInventory PASSED: operationParameters PASSED: socketBindingGroupsInInventory PASSED: machineId PASSED: resourceConfig PASSED: testExecuteAgentDiscoveryScan PASSED: testAddDeployment PASSED: testDisableDeployment PASSED: testEnableDeployment PASSED: testRestartDeployment PASSED: testLocalAndRemoteJMXOperations PASSED: testUndeploy PASSED: exportJdrCommand PASSED: testAddDatasource PASSED: testAddXaDatasource PASSED: testUpdateDatasource PASSED: testUpdateXaDatasource PASSED: testRemoveDatasource FAILED: testRemoveXaDatasource java.lang.AssertionError: Resource [type=XA Datasource, containing=testXaDs] still found after 10 attempts. at org.hawkular.agent.itest.util.ITestHelper.waitForNoResourceContaining(ITestHelper.java:167) at org.hawkular.agent.ws.test.DatasourceCommandITest.testRemoveXaDatasource(DatasourceCommandITest.java:381) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86) at org.testng.internal.Invoker.invokeMethod(Invoker.java:643) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112) at org.testng.TestRunner.privateRun(TestRunner.java:782) at org.testng.TestRunner.run(TestRunner.java:632) at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) at org.testng.SuiteRunner.run(SuiteRunner.java:268) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) at org.testng.TestNG.run(TestNG.java:1064) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:132) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:147) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) SKIPPED: testEnableStatistics java.lang.Throwable: Method StatisticsControlCommandITest.testEnableStatistics()[pri:0, instance:org.hawkular.agent.ws.test.StatisticsControlCommandITest at 4450d156] depends on not successfully finished methods in group "DatasourceCommandITest" at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1037) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112) at org.testng.TestRunner.privateRun(TestRunner.java:782) at org.testng.TestRunner.run(TestRunner.java:632) at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) at org.testng.SuiteRunner.run(SuiteRunner.java:268) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) at org.testng.TestNG.run(TestNG.java:1064) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:132) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:147) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) SKIPPED: testDisableStatistics java.lang.Throwable: Method StatisticsControlCommandITest.testDisableStatistics()[pri:0, instance:org.hawkular.agent.ws.test.StatisticsControlCommandITest at 4450d156] depends on not successfully finished methods at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1037) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112) at org.testng.TestRunner.privateRun(TestRunner.java:782) at org.testng.TestRunner.run(TestRunner.java:632) at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) at org.testng.SuiteRunner.run(SuiteRunner.java:268) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) at org.testng.TestNG.run(TestNG.java:1064) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:132) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:147) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) SKIPPED: testEnableStatisticsSubset java.lang.Throwable: Method StatisticsControlCommandITest.testEnableStatisticsSubset()[pri:0, instance:org.hawkular.agent.ws.test.StatisticsControlCommandITest at 4450d156] depends on not successfully finished methods at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1037) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112) at org.testng.TestRunner.privateRun(TestRunner.java:782) at org.testng.TestRunner.run(TestRunner.java:632) at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) at org.testng.SuiteRunner.run(SuiteRunner.java:268) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) at org.testng.TestNG.run(TestNG.java:1064) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:132) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:147) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) SKIPPED: testAddJdbcDriver java.lang.Throwable: Method JdbcDriverCommandITest.testAddJdbcDriver()[pri:0, instance:org.hawkular.agent.ws.test.JdbcDriverCommandITest at 731f8236] depends on not successfully finished methods in group "StatisticsControlCommandITest" at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1037) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112) at org.testng.TestRunner.privateRun(TestRunner.java:782) at org.testng.TestRunner.run(TestRunner.java:632) at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) at org.testng.SuiteRunner.run(SuiteRunner.java:268) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) at org.testng.TestNG.run(TestNG.java:1064) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:132) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:147) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) SKIPPED: testRemoveJdbcDriver java.lang.Throwable: Method JdbcDriverCommandITest.testRemoveJdbcDriver()[pri:0, instance:org.hawkular.agent.ws.test.JdbcDriverCommandITest at 731f8236] depends on not successfully finished methods at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1037) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112) at org.testng.TestRunner.privateRun(TestRunner.java:782) at org.testng.TestRunner.run(TestRunner.java:632) at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) at org.testng.SuiteRunner.run(SuiteRunner.java:268) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) at org.testng.TestNG.run(TestNG.java:1064) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:132) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:147) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) SKIPPED: testImmutableUpdate java.lang.Throwable: Method ImmutableITest.testImmutableUpdate()[pri:0, instance:org.hawkular.agent.ws.test.ImmutableITest at 1b68b9a4] depends on not successfully finished methods in group "JdbcDriverCommandITest" at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1037) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112) at org.testng.TestRunner.privateRun(TestRunner.java:782) at org.testng.TestRunner.run(TestRunner.java:632) at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) at org.testng.SuiteRunner.run(SuiteRunner.java:268) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) at org.testng.TestNG.run(TestNG.java:1064) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:132) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:147) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) =============================================== Surefire test Tests run: 26, Failures: 1, Skips: 6 =============================================== =============================================== Surefire suite Total tests run: 26, Failures: 1, Skips: 6 =============================================== Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/testng-failed.xml Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/Surefire suite/testng-failed.xml [TestNG] Time taken by [FailedReporter passed=0 failed=0 skipped=0]: 7 ms Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire suite/toc.html Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire suite/Surefire test.properties Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire suite/index.html Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire suite/main.html Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire suite/groups.html Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire suite/classes.html Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire suite/reporter-output.html Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire suite/methods-not-run.html Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire suite/testng.xml.html Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/old/index.html [TestNG] Time taken by org.testng.reporters.SuiteHTMLReporter at 396e2f39: 9 ms Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/junitreports/TEST-org.hawkular.agent.ws.test.StandaloneDeployApplicationITest.xml Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/junitreports/TEST-org.hawkular.agent.ws.test.ExportJdrCommandITest.xml Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/junitreports/TEST-org.hawkular.agent.ws.test.ImmutableITest.xml Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/junitreports/TEST-org.hawkular.agent.ws.test.ExecuteOperationCommandITest.xml Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/junitreports/TEST-org.hawkular.agent.ws.test.DatasourceCommandITest.xml Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/junitreports/TEST-org.hawkular.agent.ws.test.StatisticsControlCommandITest.xml Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/junitreports/TEST-org.hawkular.agent.ws.test.StandaloneWildFlyITest.xml Creating /home/mazz/source/hawkular-agent/hawkular-javaagent-itest-parent/hawkular-javaagent-all-itests/hawkular-javaagent-cmdgw-itest/target/failsafe-reports/junitreports/TEST-org.hawkular.agent.ws.test.JdbcDriverCommandITest.xml [TestNG] Time taken by org.testng.reporters.JUnitReportReporter at 2eda0940: 7 ms [TestNG] Time taken by org.testng.reporters.jq.Main at 7e0e6aa2: 61 ms [TestNG] Time taken by org.testng.reporters.XMLReporter at 2e3fc542: 6 ms [TestNG] Time taken by org.testng.reporters.EmailableReporter2 at 704d6e83: 7 ms Tests run: 26, Failures: 1, Errors: 0, Skipped: 6, Time elapsed: 103.303 sec <<< FAILURE! - in TestSuite testRemoveXaDatasource(org.hawkular.agent.ws.test.DatasourceCommandITest) Time elapsed: 50.287 sec <<< FAILURE! java.lang.AssertionError: Resource [type=XA Datasource, containing=testXaDs] still found after 10 attempts. at org.hawkular.agent.ws.test.DatasourceCommandITest.testRemoveXaDatasource(DatasourceCommandITest.java:381) Results : Failed tests: DatasourceCommandITest.testRemoveXaDatasource:381 Resource [type=XA Datasource, containing=testXaDs] still found after 10 attempts. Tests run: 26, Failures: 1, Errors: 0, Skipped: 6 From jtakvori at redhat.com Mon Oct 30 03:43:55 2017 From: jtakvori at redhat.com (Joel Takvorian) Date: Mon, 30 Oct 2017 08:43:55 +0100 Subject: [Hawkular-dev] agent can now link prometheus metrics in inventory In-Reply-To: <2136050331.33961361.1509280226122.JavaMail.zimbra@redhat.com> References: <1104416817.33960920.1509279211909.JavaMail.zimbra@redhat.com> <2136050331.33961361.1509280226122.JavaMail.zimbra@redhat.com> Message-ID: Nice! It looks like from these example, fields "name" and "type" could be merged into one, are they always identical? On Sun, Oct 29, 2017 at 1:30 PM, John Mazzitelli wrote: > The agent in branch hawkular-1275 can now link Prometheus metric family > names/labels into hawkular inventory (at least, it looks like its working > :-) > > You will see metrics in inventory that look like the below examples - > notice the general props on the metrics now contain Prometheus metric > labels - there is one extra property called "hawkular.metric.family" and > that is, obviously, the Prometheus metric family name. The rest are > Prometheus metric labels. We need to change this, I think. We should have > first-class fields on the inventory Metric object for "String metricFamily" > and "Map metricLabels". But for now, we are using general > properties. > > So for example, to query the "Pool Create Count" metric data from > Prometheus for the Stateless Session EJB resource called > "InventoryServiceIspn" you look up its metric metadata in hawkular > inventory, see the following metadata I show below, and then you know have > to query this in Prometheus: > > wildfly_ejb_pool_create_count{deployment=hawkular-inventory-service.war, > name=InventoryServiceIspn, feed-id=mazzlap} > > We do not have unique metric IDs being stored yet. We should figure out if > we really need them before we store more data in inventory. > Also, the JMX exporter does not actually put the feed-id label on metrics > - that will be the job of the Prometheus server and its scrape definition. > But we know it will need to be there, so inventory will specify it. > > { > "name": "Pool Create Count", > "type": "Pool Create Count", > "unit": "NONE", > "properties": { > "feed-id": "mazzlap", > "name": "InventoryServiceIspn", > "type": "stateless-session", > "hawkular.metric.family": "wildfly_ejb_pool_create_count", > "deployment": "hawkular-inventory-service.war" > } > > Here's other examples you will see in inventory: > > { > "name": "Max Active Sessions", > "type": "Max Active Sessions", > "unit": "NONE", > "properties": { > "feed-id": "mazzlap", > "hawkular.metric.family": "wildfly_deployment_max_ > active_sessions", > "deployment": "hawkular-inventory-service.war" > } > > { > "name": "Heap Used", > "type": "Heap Used", > "unit": "BYTES", > "properties": { > "area": "heap", > "feed-id": "mazzlap", > "hawkular.metric.family": "jvm_memory_bytes_used" > } > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171030/730f66e1/attachment.html From lponce at redhat.com Mon Oct 30 03:47:30 2017 From: lponce at redhat.com (Lucas Ponce) Date: Mon, 30 Oct 2017 08:47:30 +0100 Subject: [Hawkular-dev] possible bug in inventory server In-Reply-To: <2081173691.34285872.1509325434574.JavaMail.zimbra@redhat.com> References: <131097386.34268802.1509322878797.JavaMail.zimbra@redhat.com> <2081173691.34285872.1509325434574.JavaMail.zimbra@redhat.com> Message-ID: Let me take a look. It sounds weird but we can discard if there is anything wrong with the backend. On Mon, Oct 30, 2017 at 2:03 AM, John Mazzitelli wrote: > This agent itest error on travis just happened to me locally. After > looking at it, I think it is a bug in inventory REST server. > > I'll try to explain as briefly as I can. > > In this particular itest [B] it creates datasources in WildFly, checks > that they exist in h-inventory, removes those datasources from WildFly, and > checks that they no longer exist in h-inventory. > > For some reason, after it is removed from WildFly and inventory, a REST > query to inventory says it is still there (even though a previous, > different, query said it was not there). > > Here's what I see: > > 1. "testXaDs" is an XA datasource that is created in Wildfly and the agent > stored it in inventory. A "get all resources" inventory REST query > "hawkular/inventory/resources?feedId=itest-rest-feed" shows it exists in > inventory: > > testXaDs > id: itest-rest-feed~Local DMR~/subsystem=datasources/xa- > data-source=testXaDs > parent: itest-rest-feed~Local DMR~~ > type: XA Datasource > > 2. The test then removes that datasource from WildFly (the itest asserts > via a DMR query that it is gone from WildFly). Then, making that same > inventory REST query "hawkular/inventory/resources?feedId=itest-rest-feed" > that "testXaDs" is not in the list - it is gone from inventory based on > that "get all resources" query. This is good and expected. We see the > datasource successfully removed from inventory after WildFly deleted it. > > 3. But then the itest queries inventory using a different REST URL > (filtered on type ID): "/hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource" > and this time I GET RESULTS back saying that "testXaDs" resource is still > there! Even though the "get all resources" query said it was not there. > This is the call here [C] which ends up at this inventory REST request [D]. > > Who wants to investigate the inventory service to see if I'm right that > there is a bug here? If there is no bug in inventory, the only other option > is it's a bug in the itest code, but I checked and everything looks good to > me there. I can't see a problem in the itest code. And the fact this is > intermittent (passes sometimes, fails sometimes) tells me there is > something sinister going on in the inventory server (i.e. if it is a > problem in the test code, you would think it would always fail). > > ~~~~~~~~~~ > > [D] https://github.com/hawkular/hawkular-agent/blob/hawkular- > 1275/hawkular-agent-itest-util/src/main/java/org/ > hawkular/agent/itest/util/ITestHelper.java#L93 > > [C] https://github.com/hawkular/hawkular-agent/blob/hawkular- > 1275/hawkular-javaagent-itest-parent/hawkular-javaagent-all- > itests/hawkular-javaagent-cmdgw-itest/src/test/java/org/ > hawkular/agent/ws/test/DatasourceCommandITest.java#L377 > > [B] https://github.com/hawkular/hawkular-agent/blob/hawkular- > 1275/hawkular-javaagent-itest-parent/hawkular-javaagent-all- > itests/hawkular-javaagent-cmdgw-itest/src/test/java/org/ > hawkular/agent/ws/test/DatasourceCommandITest.java > > [A] Here's the full output from the test along with the itest assertion > error stack trace. There is a lot of junk, but in short, it shows the XA > datasource called "testXaDs" is in inventory, then the test deletes it, we > see "testXaDs" is no longer in inventory (that print out of the inventory > list comes from query results of that "get all resources" REST query), but > a query to inventory REST API filtering on typeId says it is still there. > Doesn't happen all the time, happens half the time in travis and just > happened locally to me. > > ===== > > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=Datasource > [Invoker 211968962] Invoking @AfterMethod AbstractITest.after()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > [Invoker 211968962] Invoking @BeforeMethod AbstractITest.before()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > [Invoker 211968962] Invoking org.hawkular.agent.ws.test. > DatasourceCommandITest.testRemoveXaDatasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed > ALL RESOURCES IN HAWKULAR INVENTORY: 67 > ===== > testXaDs exists and will be removed > ===== > --- > Hawkular Java Agent > id: itest-rest-feed~Local JMX~org.hawkular:type= > hawkular-javaagent > parent: null > type: Hawkular Java Agent > --- > JMX [Local JMX] MemoryPool Metaspace > id: itest-rest-feed~Local JMX~java.lang:name=Metaspace, > type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > Processor [3] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=3 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > JMX [Remote JMX] MemoryPool PS Old Gen > id: itest-rest-feed~Remote JMX~java.lang:name=PS Old > Gen,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > jolokia-war.war > id: itest-rest-feed~Local DMR~/deployment=jolokia-war.war > parent: itest-rest-feed~Local DMR~~ > type: Deployment > --- > hawkular-alerts > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=hawkular-alerts > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > DLQ > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-queue=DLQ > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Queue > --- > InventoryServiceIspn > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war/subsystem=ejb3/stateless-session-bean= > InventoryServiceIspn > parent: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > type: Stateless Session EJB > --- > ajp > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=ajp > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > mail-smtp > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/remote-destination-outbound-socket-binding=mail-smtp > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Remote Destination Outbound Socket Binding > --- > https > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=https > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > management-https > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=management-https > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > InventoryStats > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war/subsystem=ejb3/singleton-bean=InventoryStats > parent: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > type: Singleton EJB > --- > testXaDs > id: itest-rest-feed~Local DMR~/subsystem=datasources/xa- > data-source=testXaDs > parent: itest-rest-feed~Local DMR~~ > type: XA Datasource > --- > File Store [/dev/mapper/fedora_mazzwork-home] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=/dev/mapper/fedora_mazzwork-home > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > Memory > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/MEMORY=Memory > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Memory > --- > Processor [2] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=2 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > File Store [/dev/sda1] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=/dev/sda1 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > JMX [Remote JMX] MemoryPool Code Cache > id: itest-rest-feed~Remote JMX~java.lang:name=Code > Cache,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Remote JMX] MemoryPool Metaspace > id: itest-rest-feed~Remote JMX~java.lang:name=Metaspace, > type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Remote JMX] MemoryPool PS Survivor Space > id: itest-rest-feed~Remote JMX~java.lang:name=PS Survivor > Space,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > txn-recovery-environment > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=txn-recovery-environment > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > default > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > parent: itest-rest-feed~Local DMR~~ > type: Messaging Server > --- > Infinispan > id: itest-rest-feed~Local DMR~/subsystem=infinispan > parent: itest-rest-feed~Local DMR~~ > type: Infinispan > --- > jolokia-agent > id: itest-rest-feed~Local DMR~/deployment=jolokia-war. > war/subsystem=undertow/servlet=jolokia-agent > parent: itest-rest-feed~Local DMR~/deployment=jolokia-war.war > type: Servlet > --- > hawkular-inventory-ui.war > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-ui.war > parent: itest-rest-feed~Local DMR~~ > type: Deployment > --- > hawkular-services > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=hawkular-services > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > web > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=web > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > management-http > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=management-http > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > JMX [Local JMX] MemoryPool PS Survivor Space > id: itest-rest-feed~Local JMX~java.lang:name=PS Survivor > Space,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Local JMX] MemoryPool PS Eden Space > id: itest-rest-feed~Local JMX~java.lang:name=PS Eden > Space,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Local JMX] MemoryPool Code Cache > id: itest-rest-feed~Local JMX~java.lang:name=Code > Cache,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > Processor [7] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=7 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > Processor [1] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=1 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > txn-status-manager > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=txn-status-manager > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > ejb > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=ejb > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > h2 > id: itest-rest-feed~Local DMR~/subsystem=datasources/ > jdbc-driver=h2 > parent: itest-rest-feed~Local DMR~~ > type: JDBC Driver > --- > File Store [tmpfs] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=tmpfs > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > Processor [0] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=0 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > Processor [6] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=6 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > JMX [Remote JMX] MemoryPool PS Eden Space > id: itest-rest-feed~Remote JMX~java.lang:name=PS Eden > Space,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Remote JMX][Runtime] > id: itest-rest-feed~Remote JMX~java.lang:type=Runtime > parent: null > type: Runtime MBean > --- > JMX [Local JMX] MemoryPool PS Old Gen > id: itest-rest-feed~Local JMX~java.lang:name=PS Old > Gen,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > HawkularQueue > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-topic=HawkularQueue > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Topic > --- > Local DMR > id: itest-rest-feed~Local DMR~~ > parent: null > type: WildFly Server > --- > HawkularTopic > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-topic=HawkularTopic > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Topic > --- > hawkular-command-gateway-war.war > id: itest-rest-feed~Local DMR~/deployment=hawkular- > command-gateway-war.war > parent: itest-rest-feed~Local DMR~~ > type: Deployment > --- > hibernate > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=hibernate > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > HawkularCommandEvent > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-topic=HawkularCommandEvent > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Topic > --- > File Store [/dev/mapper/fedora_mazzwork-root] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=/dev/mapper/fedora_mazzwork-root > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > Processor [5] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=5 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > JMX [Local JMX][Runtime] > id: itest-rest-feed~Local JMX~java.lang:type=Runtime > parent: null > type: Runtime MBean > --- > JMX [Local JMX] MemoryPool Compressed Class Space > id: itest-rest-feed~Local JMX~java.lang:name=Compressed Class > Space,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > server > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=server > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > standard-sockets > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > parent: itest-rest-feed~Local DMR~~ > type: Socket Binding Group > --- > hawkular-inventory-service.war > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > parent: itest-rest-feed~Local DMR~~ > type: Deployment > --- > JMX [Remote JMX] MemoryPool Compressed Class Space > id: itest-rest-feed~Remote JMX~java.lang:name=Compressed Class > Space,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > File Store [/] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=~ > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > itest-rest-feed_OperatingSystem > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > parent: null > type: Platform_Operating System > --- > Processor [4] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=4 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > ExampleDS > id: itest-rest-feed~Local DMR~/subsystem=datasources/ > data-source=ExampleDS > parent: itest-rest-feed~Local DMR~~ > type: Datasource > --- > ExpiryQueue > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-queue=ExpiryQueue > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Queue > --- > org.hawkular.inventory.handlers.InventoryApp > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war/subsystem=undertow/servlet=org.hawkular.inventory. > handlers.InventoryApp > parent: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > type: Servlet > --- > http > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=http > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > Transaction Manager > id: itest-rest-feed~Local DMR~/subsystem=transactions > parent: itest-rest-feed~Local DMR~~ > type: Transaction Manager > --- > InventoryConfig > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war/subsystem=ejb3/singleton-bean=InventoryConfig > parent: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > type: Singleton EJB > --- > HawkularInventoryChanges > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-topic=HawkularInventoryChanges > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Topic > ===== > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > onOpen > FINE: WebSocket opened > 20:13:29,091 INFO [org.hawkular.cmdgw.command.ws.server.UIClientWebSocket] > (default task-42) HAWKFEEDCOMM000013: WebSocket session [Hgf9Zznsx_ > y9U14uaHPPWIPuSarLogLgugUCweVK] opened for endpoint [/ui/ws] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Received message[0] from WebSocket: [ActualMessage > [type=application/vnd.okhttp.websocket+text; charset=utf-8, > body=WelcomeResponse={"sessionId":"Hgf9Zznsx_ > y9U14uaHPPWIPuSarLogLgugUCweVK"}]] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Message[0]: [PASSED] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$MessageAnswer$1 > run > FINE: Sending over WebSocket: RemoveDatasourceRequest={" > authentication":{"username":"itest-rest","password":"itest-rest-password"}, > "feedId":"itest-rest-feed","resourceId":"itest-rest-feed~Local > DMR~/subsystem=datasources/xa-data-source=testXaDs"} > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$MessageAnswer$1 > run > FINE: No sleep configured > 20:13:29,102 INFO [org.hawkular.cmdgw.command.ws.server.AbstractGatewayWebSocket] > (default task-43) HAWKFEEDCOMM000014: Received message > [org.hawkular.cmdgw.api.RemoveDatasourceRequest] from WebSocket session > [Hgf9Zznsx_y9U14uaHPPWIPuSarLogLgugUCweVK] of [/ui/ws] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Received message[1] from WebSocket: [ActualMessage > [type=application/vnd.okhttp.websocket+text; charset=utf-8, > body=GenericSuccessResponse={"message":"The request has been forwarded to > feed [itest-rest-feed] (MessageId=ID:27f779d9-bd07- > 11e7-a03b-55f35baba5f1)"}]] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Message[1]: [PASSED] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$ExpectedEvent > scheduleAnswer > FINE: No answer to send for message[1] > 20:13:29,108 INFO [org.hawkular.agent.monitor.cmd. > AbstractDMRResourcePathCommand] (OkHttp http://127.0.0.1:8080/...) > HAWKAGENT010065: Received request to perform [Remove] on a [Datasource] > given by inventory path [itest-rest-feed~Local > DMR~/subsystem=datasources/xa-data-source=testXaDs] > 20:13:29,150 INFO [org.hawkular.cmdgw.command.ws.server.AbstractGatewayWebSocket] > (default task-47) HAWKFEEDCOMM000014: Received message > [org.hawkular.cmdgw.api.RemoveDatasourceResponse] from WebSocket session > [AQNPLng4hq-vgfGOOo53kVpLuQjVcKvzXAzwqPS3] of [/feed/{feedId}] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Received message[2] from WebSocket: [ActualMessage > [type=application/vnd.okhttp.websocket+text; charset=utf-8, > body=RemoveDatasourceResponse={"feedId":"itest-rest-feed"," > resourceId":"itest-rest-feed~Local DMR~/subsystem=datasources/xa- > data-source=testXaDs","destinationSessionId":"Hgf9Zznsx_ > y9U14uaHPPWIPuSarLogLgugUCweVK","status":"OK","message":"Performed > [Remove] on a [Datasource] given by Feed Id [itest-rest-feed] Resource Id > [itest-rest-feed~Local DMR~/subsystem=datasources/xa- > data-source=testXaDs]","serverRefreshIndicator":"RELOAD-REQUIRED"}]] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Message[2]: [PASSED] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$Answer$1 > lambda$schedule$0 > FINE: About to send manual close > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$Answer$1 > lambda$schedule$0 > FINE: Close sent > 20:13:29,156 INFO [org.hawkular.cmdgw.command.ws.server.UIClientWebSocket] > (default task-44) HAWKFEEDCOMM000015: WebSocket session [Hgf9Zznsx_ > y9U14uaHPPWIPuSarLogLgugUCweVK] of [/ui/ws] closed. > Reason=[CloseReason[1000,OK]] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Received message[3] from WebSocket: [ActualClose [code=1000, > reason=OK]] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Message[3]: [PASSED] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$ExpectedEvent > scheduleAnswer > FINE: No answer to send for message[3] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Message[3] was the last expected message, sending close. > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > close > FINE: Closing the websocket > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > shutDownExecutor > FINE: Shutting down the executor > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > shutDownExecutor > FINE: Executor shut down > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed > ALL RESOURCES IN HAWKULAR INVENTORY: 66 > ===== > testXaDs deleted, should be out of inventory > ===== > --- > Hawkular Java Agent > id: itest-rest-feed~Local JMX~org.hawkular:type= > hawkular-javaagent > parent: null > type: Hawkular Java Agent > --- > JMX [Local JMX] MemoryPool Metaspace > id: itest-rest-feed~Local JMX~java.lang:name=Metaspace, > type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > Processor [3] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=3 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > JMX [Remote JMX] MemoryPool PS Old Gen > id: itest-rest-feed~Remote JMX~java.lang:name=PS Old > Gen,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > jolokia-war.war > id: itest-rest-feed~Local DMR~/deployment=jolokia-war.war > parent: itest-rest-feed~Local DMR~~ > type: Deployment > --- > hawkular-alerts > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=hawkular-alerts > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > DLQ > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-queue=DLQ > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Queue > --- > InventoryServiceIspn > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war/subsystem=ejb3/stateless-session-bean= > InventoryServiceIspn > parent: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > type: Stateless Session EJB > --- > ajp > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=ajp > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > mail-smtp > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/remote-destination-outbound-socket-binding=mail-smtp > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Remote Destination Outbound Socket Binding > --- > https > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=https > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > management-https > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=management-https > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > InventoryStats > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war/subsystem=ejb3/singleton-bean=InventoryStats > parent: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > type: Singleton EJB > --- > File Store [/dev/mapper/fedora_mazzwork-home] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=/dev/mapper/fedora_mazzwork-home > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > Memory > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/MEMORY=Memory > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Memory > --- > Processor [2] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=2 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > File Store [/dev/sda1] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=/dev/sda1 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > JMX [Remote JMX] MemoryPool Code Cache > id: itest-rest-feed~Remote JMX~java.lang:name=Code > Cache,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Remote JMX] MemoryPool Metaspace > id: itest-rest-feed~Remote JMX~java.lang:name=Metaspace, > type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Remote JMX] MemoryPool PS Survivor Space > id: itest-rest-feed~Remote JMX~java.lang:name=PS Survivor > Space,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > txn-recovery-environment > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=txn-recovery-environment > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > default > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > parent: itest-rest-feed~Local DMR~~ > type: Messaging Server > --- > Infinispan > id: itest-rest-feed~Local DMR~/subsystem=infinispan > parent: itest-rest-feed~Local DMR~~ > type: Infinispan > --- > jolokia-agent > id: itest-rest-feed~Local DMR~/deployment=jolokia-war. > war/subsystem=undertow/servlet=jolokia-agent > parent: itest-rest-feed~Local DMR~/deployment=jolokia-war.war > type: Servlet > --- > hawkular-inventory-ui.war > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-ui.war > parent: itest-rest-feed~Local DMR~~ > type: Deployment > --- > hawkular-services > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=hawkular-services > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > web > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=web > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > management-http > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=management-http > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > JMX [Local JMX] MemoryPool PS Survivor Space > id: itest-rest-feed~Local JMX~java.lang:name=PS Survivor > Space,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Local JMX] MemoryPool PS Eden Space > id: itest-rest-feed~Local JMX~java.lang:name=PS Eden > Space,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Local JMX] MemoryPool Code Cache > id: itest-rest-feed~Local JMX~java.lang:name=Code > Cache,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > Processor [7] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=7 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > Processor [1] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=1 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > txn-status-manager > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=txn-status-manager > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > ejb > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=ejb > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > h2 > id: itest-rest-feed~Local DMR~/subsystem=datasources/ > jdbc-driver=h2 > parent: itest-rest-feed~Local DMR~~ > type: JDBC Driver > --- > File Store [tmpfs] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=tmpfs > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > Processor [0] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=0 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > Processor [6] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=6 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > JMX [Remote JMX] MemoryPool PS Eden Space > id: itest-rest-feed~Remote JMX~java.lang:name=PS Eden > Space,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Remote JMX][Runtime] > id: itest-rest-feed~Remote JMX~java.lang:type=Runtime > parent: null > type: Runtime MBean > --- > JMX [Local JMX] MemoryPool PS Old Gen > id: itest-rest-feed~Local JMX~java.lang:name=PS Old > Gen,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > HawkularQueue > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-topic=HawkularQueue > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Topic > --- > Local DMR > id: itest-rest-feed~Local DMR~~ > parent: null > type: WildFly Server > --- > HawkularTopic > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-topic=HawkularTopic > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Topic > --- > hawkular-command-gateway-war.war > id: itest-rest-feed~Local DMR~/deployment=hawkular- > command-gateway-war.war > parent: itest-rest-feed~Local DMR~~ > type: Deployment > --- > hibernate > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=hibernate > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > HawkularCommandEvent > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-topic=HawkularCommandEvent > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Topic > --- > File Store [/dev/mapper/fedora_mazzwork-root] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=/dev/mapper/fedora_mazzwork-root > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > Processor [5] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=5 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > JMX [Local JMX][Runtime] > id: itest-rest-feed~Local JMX~java.lang:type=Runtime > parent: null > type: Runtime MBean > --- > JMX [Local JMX] MemoryPool Compressed Class Space > id: itest-rest-feed~Local JMX~java.lang:name=Compressed Class > Space,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > server > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=server > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > standard-sockets > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > parent: itest-rest-feed~Local DMR~~ > type: Socket Binding Group > --- > hawkular-inventory-service.war > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > parent: itest-rest-feed~Local DMR~~ > type: Deployment > --- > JMX [Remote JMX] MemoryPool Compressed Class Space > id: itest-rest-feed~Remote JMX~java.lang:name=Compressed Class > Space,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > File Store [/] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=~ > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > itest-rest-feed_OperatingSystem > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > parent: null > type: Platform_Operating System > --- > Processor [4] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=4 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > ExampleDS > id: itest-rest-feed~Local DMR~/subsystem=datasources/ > data-source=ExampleDS > parent: itest-rest-feed~Local DMR~~ > type: Datasource > --- > ExpiryQueue > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-queue=ExpiryQueue > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Queue > --- > org.hawkular.inventory.handlers.InventoryApp > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war/subsystem=undertow/servlet=org.hawkular.inventory. > handlers.InventoryApp > parent: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > type: Servlet > --- > http > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=http > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > Transaction Manager > id: itest-rest-feed~Local DMR~/subsystem=transactions > parent: itest-rest-feed~Local DMR~~ > type: Transaction Manager > --- > InventoryConfig > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war/subsystem=ejb3/singleton-bean=InventoryConfig > parent: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > type: Singleton EJB > --- > HawkularInventoryChanges > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-topic=HawkularInventoryChanges > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Topic > ===== > 20:13:29,186 ERROR [org.hawkular.agent.monitor.storage.HawkularStorageAdapter] > (OkHttp http://127.0.0.1:8080/...) HAWKAGENT010083: Failed to store > notification: {"type":"RESOURCE_ADDED","properties":{"resourceId":"itest-rest-feed~Local > DMR~~","feedId":"itest-rest-feed","resourceType":"WildFly Server"}}: > java.io.IOException: status-code=[405], reason=[Method Not Allowed], url=[ > http://127.0.0.1:8080/hawkular/api/notification] > at org.hawkular.agent.monitor.storage.HawkularStorageAdapter$1. > onResponse(HawkularStorageAdapter.java:116) > at okhttp3.shaded.RealCall$AsyncCall.execute(RealCall.java:126) > at okhttp3.shaded.internal.NamedRunnable.run( > NamedRunnable.java:32) > at java.util.concurrent.ThreadPoolExecutor.runWorker( > ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > [Invoker 211968962] Invoking @AfterMethod AbstractITest.after()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > ===== Invoked methods > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > StandaloneWildFlyITest.testAgent()[pri:0, instance:org.hawkular.agent. > ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > StandaloneWildFlyITest.datasourcesAddedToInventory()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] > 577405636 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > StandaloneWildFlyITest.operationParameters()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] > 577405636 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > StandaloneWildFlyITest.socketBindingGroupsInInventory()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] > 577405636 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > StandaloneWildFlyITest.machineId()[pri:0, instance:org.hawkular.agent. > ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > StandaloneWildFlyITest.resourceConfig()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] > 577405636 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > ExecuteOperationCommandITest at 77e4c80f] 2011482127 > ExecuteOperationCommandITest.testExecuteAgentDiscoveryScan()[pri:0, > instance:org.hawkular.agent.ws.test.ExecuteOperationCommandITest at 77e4c80f] > 2011482127 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > ExecuteOperationCommandITest at 77e4c80f] 2011482127 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > StandaloneDeployApplicationITest.testAddDeployment()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITe > st at 351d0846] 891095110 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > StandaloneDeployApplicationITest.testDisableDeployment()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITe > st at 351d0846] 891095110 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > StandaloneDeployApplicationITest.testEnableDeployment()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITe > st at 351d0846] 891095110 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > StandaloneDeployApplicationITest.testRestartDeployment()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITe > st at 351d0846] 891095110 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > StandaloneDeployApplicationITest.testLocalAndRemoteJMXOperations()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITe > st at 351d0846] 891095110 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > StandaloneDeployApplicationITest.testUndeploy()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITe > st at 351d0846] 891095110 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > AbstractITest.before()[pri:0, instance:org.hawkular.agent. > ws.test.ExportJdrCommandITest at 176d53b2] 393040818 > ExportJdrCommandITest.exportJdrCommand()[pri:0, > instance:org.hawkular.agent.ws.test.ExportJdrCommandITest at 176d53b2] > 393040818 > AbstractITest.after()[pri:0, instance:org.hawkular.agent. > ws.test.ExportJdrCommandITest at 176d53b2] 393040818 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > DatasourceCommandITest.testAddDatasource()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > 1147258851 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > DatasourceCommandITest.testAddXaDatasource()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > 1147258851 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > DatasourceCommandITest.testUpdateDatasource()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > 1147258851 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > DatasourceCommandITest.testUpdateXaDatasource()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > 1147258851 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > DatasourceCommandITest.testRemoveDatasource()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > 1147258851 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > DatasourceCommandITest.testRemoveXaDatasource()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > 1147258851 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > ===== > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/Surefire suite/Surefire > test.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/Surefire suite/Surefire > test.xml > PASSED: testAgent > PASSED: datasourcesAddedToInventory > PASSED: operationParameters > PASSED: socketBindingGroupsInInventory > PASSED: machineId > PASSED: resourceConfig > PASSED: testExecuteAgentDiscoveryScan > PASSED: testAddDeployment > PASSED: testDisableDeployment > PASSED: testEnableDeployment > PASSED: testRestartDeployment > PASSED: testLocalAndRemoteJMXOperations > PASSED: testUndeploy > PASSED: exportJdrCommand > PASSED: testAddDatasource > PASSED: testAddXaDatasource > PASSED: testUpdateDatasource > PASSED: testUpdateXaDatasource > PASSED: testRemoveDatasource > FAILED: testRemoveXaDatasource > java.lang.AssertionError: Resource [type=XA Datasource, > containing=testXaDs] still found after 10 attempts. > at org.hawkular.agent.itest.util.ITestHelper. > waitForNoResourceContaining(ITestHelper.java:167) > at org.hawkular.agent.ws.test.DatasourceCommandITest. > testRemoveXaDatasource(DatasourceCommandITest.java:381) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke( > NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.testng.internal.MethodInvocationHelper.invokeMethod( > MethodInvocationHelper.java:86) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:643) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820) > at org.testng.internal.Invoker.invokeTestMethods(Invoker. > java:1128) > at org.testng.internal.TestMethodWorker.invokeTestMethods( > TestMethodWorker.java:129) > at org.testng.internal.TestMethodWorker.run( > TestMethodWorker.java:112) > at org.testng.TestRunner.privateRun(TestRunner.java:782) > at org.testng.TestRunner.run(TestRunner.java:632) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) > at org.testng.SuiteRunner.run(SuiteRunner.java:268) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker. > java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) > at org.testng.TestNG.run(TestNG.java:1064) > at org.apache.maven.surefire.testng.TestNGExecutor.run( > TestNGExecutor.java:132) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > executeMulti(TestNGDirectoryTestSuite.java:193) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > execute(TestNGDirectoryTestSuite.java:94) > at org.apache.maven.surefire.testng.TestNGProvider.invoke( > TestNGProvider.java:147) > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > SKIPPED: testEnableStatistics > java.lang.Throwable: Method StatisticsControlCommandITest.testEnableStatistics()[pri:0, > instance:org.hawkular.agent.ws.test.StatisticsControlCommandITest at 4450d156] > depends on not successfully finished methods in group > "DatasourceCommandITest" > at org.testng.internal.Invoker.invokeTestMethods(Invoker. > java:1037) > at org.testng.internal.TestMethodWorker.invokeTestMethods( > TestMethodWorker.java:129) > at org.testng.internal.TestMethodWorker.run( > TestMethodWorker.java:112) > at org.testng.TestRunner.privateRun(TestRunner.java:782) > at org.testng.TestRunner.run(TestRunner.java:632) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) > at org.testng.SuiteRunner.run(SuiteRunner.java:268) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker. > java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) > at org.testng.TestNG.run(TestNG.java:1064) > at org.apache.maven.surefire.testng.TestNGExecutor.run( > TestNGExecutor.java:132) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > executeMulti(TestNGDirectoryTestSuite.java:193) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > execute(TestNGDirectoryTestSuite.java:94) > at org.apache.maven.surefire.testng.TestNGProvider.invoke( > TestNGProvider.java:147) > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > SKIPPED: testDisableStatistics > java.lang.Throwable: Method StatisticsControlCommandITest.testDisableStatistics()[pri:0, > instance:org.hawkular.agent.ws.test.StatisticsControlCommandITest at 4450d156] > depends on not successfully finished methods > at org.testng.internal.Invoker.invokeTestMethods(Invoker. > java:1037) > at org.testng.internal.TestMethodWorker.invokeTestMethods( > TestMethodWorker.java:129) > at org.testng.internal.TestMethodWorker.run( > TestMethodWorker.java:112) > at org.testng.TestRunner.privateRun(TestRunner.java:782) > at org.testng.TestRunner.run(TestRunner.java:632) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) > at org.testng.SuiteRunner.run(SuiteRunner.java:268) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker. > java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) > at org.testng.TestNG.run(TestNG.java:1064) > at org.apache.maven.surefire.testng.TestNGExecutor.run( > TestNGExecutor.java:132) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > executeMulti(TestNGDirectoryTestSuite.java:193) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > execute(TestNGDirectoryTestSuite.java:94) > at org.apache.maven.surefire.testng.TestNGProvider.invoke( > TestNGProvider.java:147) > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > SKIPPED: testEnableStatisticsSubset > java.lang.Throwable: Method StatisticsControlCommandITest. > testEnableStatisticsSubset()[pri:0, instance:org.hawkular.agent.ws.test. > StatisticsControlCommandITest at 4450d156] depends on not successfully > finished methods > at org.testng.internal.Invoker.invokeTestMethods(Invoker. > java:1037) > at org.testng.internal.TestMethodWorker.invokeTestMethods( > TestMethodWorker.java:129) > at org.testng.internal.TestMethodWorker.run( > TestMethodWorker.java:112) > at org.testng.TestRunner.privateRun(TestRunner.java:782) > at org.testng.TestRunner.run(TestRunner.java:632) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) > at org.testng.SuiteRunner.run(SuiteRunner.java:268) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker. > java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) > at org.testng.TestNG.run(TestNG.java:1064) > at org.apache.maven.surefire.testng.TestNGExecutor.run( > TestNGExecutor.java:132) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > executeMulti(TestNGDirectoryTestSuite.java:193) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > execute(TestNGDirectoryTestSuite.java:94) > at org.apache.maven.surefire.testng.TestNGProvider.invoke( > TestNGProvider.java:147) > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > SKIPPED: testAddJdbcDriver > java.lang.Throwable: Method JdbcDriverCommandITest.testAddJdbcDriver()[pri:0, > instance:org.hawkular.agent.ws.test.JdbcDriverCommandITest at 731f8236] > depends on not successfully finished methods in group " > StatisticsControlCommandITest" > at org.testng.internal.Invoker.invokeTestMethods(Invoker. > java:1037) > at org.testng.internal.TestMethodWorker.invokeTestMethods( > TestMethodWorker.java:129) > at org.testng.internal.TestMethodWorker.run( > TestMethodWorker.java:112) > at org.testng.TestRunner.privateRun(TestRunner.java:782) > at org.testng.TestRunner.run(TestRunner.java:632) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) > at org.testng.SuiteRunner.run(SuiteRunner.java:268) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker. > java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) > at org.testng.TestNG.run(TestNG.java:1064) > at org.apache.maven.surefire.testng.TestNGExecutor.run( > TestNGExecutor.java:132) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > executeMulti(TestNGDirectoryTestSuite.java:193) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > execute(TestNGDirectoryTestSuite.java:94) > at org.apache.maven.surefire.testng.TestNGProvider.invoke( > TestNGProvider.java:147) > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > SKIPPED: testRemoveJdbcDriver > java.lang.Throwable: Method JdbcDriverCommandITest.testRemoveJdbcDriver()[pri:0, > instance:org.hawkular.agent.ws.test.JdbcDriverCommandITest at 731f8236] > depends on not successfully finished methods > at org.testng.internal.Invoker.invokeTestMethods(Invoker. > java:1037) > at org.testng.internal.TestMethodWorker.invokeTestMethods( > TestMethodWorker.java:129) > at org.testng.internal.TestMethodWorker.run( > TestMethodWorker.java:112) > at org.testng.TestRunner.privateRun(TestRunner.java:782) > at org.testng.TestRunner.run(TestRunner.java:632) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) > at org.testng.SuiteRunner.run(SuiteRunner.java:268) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker. > java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) > at org.testng.TestNG.run(TestNG.java:1064) > at org.apache.maven.surefire.testng.TestNGExecutor.run( > TestNGExecutor.java:132) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > executeMulti(TestNGDirectoryTestSuite.java:193) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > execute(TestNGDirectoryTestSuite.java:94) > at org.apache.maven.surefire.testng.TestNGProvider.invoke( > TestNGProvider.java:147) > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > SKIPPED: testImmutableUpdate > java.lang.Throwable: Method ImmutableITest.testImmutableUpdate()[pri:0, > instance:org.hawkular.agent.ws.test.ImmutableITest at 1b68b9a4] depends on > not successfully finished methods in group "JdbcDriverCommandITest" > at org.testng.internal.Invoker.invokeTestMethods(Invoker. > java:1037) > at org.testng.internal.TestMethodWorker.invokeTestMethods( > TestMethodWorker.java:129) > at org.testng.internal.TestMethodWorker.run( > TestMethodWorker.java:112) > at org.testng.TestRunner.privateRun(TestRunner.java:782) > at org.testng.TestRunner.run(TestRunner.java:632) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) > at org.testng.SuiteRunner.run(SuiteRunner.java:268) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker. > java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) > at org.testng.TestNG.run(TestNG.java:1064) > at org.apache.maven.surefire.testng.TestNGExecutor.run( > TestNGExecutor.java:132) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > executeMulti(TestNGDirectoryTestSuite.java:193) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > execute(TestNGDirectoryTestSuite.java:94) > at org.apache.maven.surefire.testng.TestNGProvider.invoke( > TestNGProvider.java:147) > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > > =============================================== > Surefire test > Tests run: 26, Failures: 1, Skips: 6 > =============================================== > > > =============================================== > Surefire suite > Total tests run: 26, Failures: 1, Skips: 6 > =============================================== > > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/testng-failed.xml > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/Surefire > suite/testng-failed.xml > [TestNG] Time taken by [FailedReporter passed=0 failed=0 skipped=0]: 7 ms > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire suite/toc.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire suite/Surefire > test.properties > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire > suite/index.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire suite/main.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire > suite/groups.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire > suite/classes.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire > suite/reporter-output.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire > suite/methods-not-run.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire > suite/testng.xml.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/index.html > [TestNG] Time taken by org.testng.reporters.SuiteHTMLReporter at 396e2f39: 9 > ms > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/junitreports/ > TEST-org.hawkular.agent.ws.test.StandaloneDeployApplicationITest.xml > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/junitreports/ > TEST-org.hawkular.agent.ws.test.ExportJdrCommandITest.xml > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/junitreports/ > TEST-org.hawkular.agent.ws.test.ImmutableITest.xml > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/junitreports/ > TEST-org.hawkular.agent.ws.test.ExecuteOperationCommandITest.xml > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/junitreports/ > TEST-org.hawkular.agent.ws.test.DatasourceCommandITest.xml > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/junitreports/ > TEST-org.hawkular.agent.ws.test.StatisticsControlCommandITest.xml > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/junitreports/ > TEST-org.hawkular.agent.ws.test.StandaloneWildFlyITest.xml > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/junitreports/ > TEST-org.hawkular.agent.ws.test.JdbcDriverCommandITest.xml > [TestNG] Time taken by org.testng.reporters.JUnitReportReporter at 2eda0940: > 7 ms > [TestNG] Time taken by org.testng.reporters.jq.Main at 7e0e6aa2: 61 ms > [TestNG] Time taken by org.testng.reporters.XMLReporter at 2e3fc542: 6 ms > [TestNG] Time taken by org.testng.reporters.EmailableReporter2 at 704d6e83: > 7 ms > Tests run: 26, Failures: 1, Errors: 0, Skipped: 6, Time elapsed: 103.303 > sec <<< FAILURE! - in TestSuite > testRemoveXaDatasource(org.hawkular.agent.ws.test.DatasourceCommandITest) > Time elapsed: 50.287 sec <<< FAILURE! > java.lang.AssertionError: Resource [type=XA Datasource, > containing=testXaDs] still found after 10 attempts. > at org.hawkular.agent.ws.test.DatasourceCommandITest. > testRemoveXaDatasource(DatasourceCommandITest.java:381) > > > Results : > > Failed tests: > DatasourceCommandITest.testRemoveXaDatasource:381 Resource [type=XA > Datasource, containing=testXaDs] still found after 10 attempts. > > Tests run: 26, Failures: 1, Errors: 0, Skipped: 6 > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171030/19bb1881/attachment-0001.html From jtakvori at redhat.com Mon Oct 30 03:49:25 2017 From: jtakvori at redhat.com (Joel Takvorian) Date: Mon, 30 Oct 2017 08:49:25 +0100 Subject: [Hawkular-dev] possible bug in inventory server In-Reply-To: <2081173691.34285872.1509325434574.JavaMail.zimbra@redhat.com> References: <131097386.34268802.1509322878797.JavaMail.zimbra@redhat.com> <2081173691.34285872.1509325434574.JavaMail.zimbra@redhat.com> Message-ID: The description would correspond to an non-updated index table after removal. I hit this case previously when the server was killed and then restarted, but it must be different here. On Mon, Oct 30, 2017 at 2:03 AM, John Mazzitelli wrote: > This agent itest error on travis just happened to me locally. After > looking at it, I think it is a bug in inventory REST server. > > I'll try to explain as briefly as I can. > > In this particular itest [B] it creates datasources in WildFly, checks > that they exist in h-inventory, removes those datasources from WildFly, and > checks that they no longer exist in h-inventory. > > For some reason, after it is removed from WildFly and inventory, a REST > query to inventory says it is still there (even though a previous, > different, query said it was not there). > > Here's what I see: > > 1. "testXaDs" is an XA datasource that is created in Wildfly and the agent > stored it in inventory. A "get all resources" inventory REST query > "hawkular/inventory/resources?feedId=itest-rest-feed" shows it exists in > inventory: > > testXaDs > id: itest-rest-feed~Local DMR~/subsystem=datasources/xa- > data-source=testXaDs > parent: itest-rest-feed~Local DMR~~ > type: XA Datasource > > 2. The test then removes that datasource from WildFly (the itest asserts > via a DMR query that it is gone from WildFly). Then, making that same > inventory REST query "hawkular/inventory/resources?feedId=itest-rest-feed" > that "testXaDs" is not in the list - it is gone from inventory based on > that "get all resources" query. This is good and expected. We see the > datasource successfully removed from inventory after WildFly deleted it. > > 3. But then the itest queries inventory using a different REST URL > (filtered on type ID): "/hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource" > and this time I GET RESULTS back saying that "testXaDs" resource is still > there! Even though the "get all resources" query said it was not there. > This is the call here [C] which ends up at this inventory REST request [D]. > > Who wants to investigate the inventory service to see if I'm right that > there is a bug here? If there is no bug in inventory, the only other option > is it's a bug in the itest code, but I checked and everything looks good to > me there. I can't see a problem in the itest code. And the fact this is > intermittent (passes sometimes, fails sometimes) tells me there is > something sinister going on in the inventory server (i.e. if it is a > problem in the test code, you would think it would always fail). > > ~~~~~~~~~~ > > [D] https://github.com/hawkular/hawkular-agent/blob/hawkular- > 1275/hawkular-agent-itest-util/src/main/java/org/ > hawkular/agent/itest/util/ITestHelper.java#L93 > > [C] https://github.com/hawkular/hawkular-agent/blob/hawkular- > 1275/hawkular-javaagent-itest-parent/hawkular-javaagent-all- > itests/hawkular-javaagent-cmdgw-itest/src/test/java/org/ > hawkular/agent/ws/test/DatasourceCommandITest.java#L377 > > [B] https://github.com/hawkular/hawkular-agent/blob/hawkular- > 1275/hawkular-javaagent-itest-parent/hawkular-javaagent-all- > itests/hawkular-javaagent-cmdgw-itest/src/test/java/org/ > hawkular/agent/ws/test/DatasourceCommandITest.java > > [A] Here's the full output from the test along with the itest assertion > error stack trace. There is a lot of junk, but in short, it shows the XA > datasource called "testXaDs" is in inventory, then the test deletes it, we > see "testXaDs" is no longer in inventory (that print out of the inventory > list comes from query results of that "get all resources" REST query), but > a query to inventory REST API filtering on typeId says it is still there. > Doesn't happen all the time, happens half the time in travis and just > happened locally to me. > > ===== > > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=Datasource > [Invoker 211968962] Invoking @AfterMethod AbstractITest.after()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > [Invoker 211968962] Invoking @BeforeMethod AbstractITest.before()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > [Invoker 211968962] Invoking org.hawkular.agent.ws.test. > DatasourceCommandITest.testRemoveXaDatasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed > ALL RESOURCES IN HAWKULAR INVENTORY: 67 > ===== > testXaDs exists and will be removed > ===== > --- > Hawkular Java Agent > id: itest-rest-feed~Local JMX~org.hawkular:type= > hawkular-javaagent > parent: null > type: Hawkular Java Agent > --- > JMX [Local JMX] MemoryPool Metaspace > id: itest-rest-feed~Local JMX~java.lang:name=Metaspace, > type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > Processor [3] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=3 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > JMX [Remote JMX] MemoryPool PS Old Gen > id: itest-rest-feed~Remote JMX~java.lang:name=PS Old > Gen,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > jolokia-war.war > id: itest-rest-feed~Local DMR~/deployment=jolokia-war.war > parent: itest-rest-feed~Local DMR~~ > type: Deployment > --- > hawkular-alerts > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=hawkular-alerts > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > DLQ > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-queue=DLQ > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Queue > --- > InventoryServiceIspn > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war/subsystem=ejb3/stateless-session-bean= > InventoryServiceIspn > parent: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > type: Stateless Session EJB > --- > ajp > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=ajp > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > mail-smtp > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/remote-destination-outbound-socket-binding=mail-smtp > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Remote Destination Outbound Socket Binding > --- > https > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=https > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > management-https > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=management-https > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > InventoryStats > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war/subsystem=ejb3/singleton-bean=InventoryStats > parent: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > type: Singleton EJB > --- > testXaDs > id: itest-rest-feed~Local DMR~/subsystem=datasources/xa- > data-source=testXaDs > parent: itest-rest-feed~Local DMR~~ > type: XA Datasource > --- > File Store [/dev/mapper/fedora_mazzwork-home] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=/dev/mapper/fedora_mazzwork-home > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > Memory > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/MEMORY=Memory > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Memory > --- > Processor [2] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=2 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > File Store [/dev/sda1] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=/dev/sda1 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > JMX [Remote JMX] MemoryPool Code Cache > id: itest-rest-feed~Remote JMX~java.lang:name=Code > Cache,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Remote JMX] MemoryPool Metaspace > id: itest-rest-feed~Remote JMX~java.lang:name=Metaspace, > type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Remote JMX] MemoryPool PS Survivor Space > id: itest-rest-feed~Remote JMX~java.lang:name=PS Survivor > Space,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > txn-recovery-environment > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=txn-recovery-environment > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > default > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > parent: itest-rest-feed~Local DMR~~ > type: Messaging Server > --- > Infinispan > id: itest-rest-feed~Local DMR~/subsystem=infinispan > parent: itest-rest-feed~Local DMR~~ > type: Infinispan > --- > jolokia-agent > id: itest-rest-feed~Local DMR~/deployment=jolokia-war. > war/subsystem=undertow/servlet=jolokia-agent > parent: itest-rest-feed~Local DMR~/deployment=jolokia-war.war > type: Servlet > --- > hawkular-inventory-ui.war > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-ui.war > parent: itest-rest-feed~Local DMR~~ > type: Deployment > --- > hawkular-services > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=hawkular-services > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > web > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=web > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > management-http > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=management-http > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > JMX [Local JMX] MemoryPool PS Survivor Space > id: itest-rest-feed~Local JMX~java.lang:name=PS Survivor > Space,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Local JMX] MemoryPool PS Eden Space > id: itest-rest-feed~Local JMX~java.lang:name=PS Eden > Space,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Local JMX] MemoryPool Code Cache > id: itest-rest-feed~Local JMX~java.lang:name=Code > Cache,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > Processor [7] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=7 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > Processor [1] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=1 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > txn-status-manager > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=txn-status-manager > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > ejb > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=ejb > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > h2 > id: itest-rest-feed~Local DMR~/subsystem=datasources/ > jdbc-driver=h2 > parent: itest-rest-feed~Local DMR~~ > type: JDBC Driver > --- > File Store [tmpfs] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=tmpfs > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > Processor [0] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=0 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > Processor [6] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=6 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > JMX [Remote JMX] MemoryPool PS Eden Space > id: itest-rest-feed~Remote JMX~java.lang:name=PS Eden > Space,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Remote JMX][Runtime] > id: itest-rest-feed~Remote JMX~java.lang:type=Runtime > parent: null > type: Runtime MBean > --- > JMX [Local JMX] MemoryPool PS Old Gen > id: itest-rest-feed~Local JMX~java.lang:name=PS Old > Gen,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > HawkularQueue > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-topic=HawkularQueue > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Topic > --- > Local DMR > id: itest-rest-feed~Local DMR~~ > parent: null > type: WildFly Server > --- > HawkularTopic > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-topic=HawkularTopic > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Topic > --- > hawkular-command-gateway-war.war > id: itest-rest-feed~Local DMR~/deployment=hawkular- > command-gateway-war.war > parent: itest-rest-feed~Local DMR~~ > type: Deployment > --- > hibernate > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=hibernate > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > HawkularCommandEvent > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-topic=HawkularCommandEvent > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Topic > --- > File Store [/dev/mapper/fedora_mazzwork-root] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=/dev/mapper/fedora_mazzwork-root > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > Processor [5] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=5 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > JMX [Local JMX][Runtime] > id: itest-rest-feed~Local JMX~java.lang:type=Runtime > parent: null > type: Runtime MBean > --- > JMX [Local JMX] MemoryPool Compressed Class Space > id: itest-rest-feed~Local JMX~java.lang:name=Compressed Class > Space,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > server > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=server > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > standard-sockets > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > parent: itest-rest-feed~Local DMR~~ > type: Socket Binding Group > --- > hawkular-inventory-service.war > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > parent: itest-rest-feed~Local DMR~~ > type: Deployment > --- > JMX [Remote JMX] MemoryPool Compressed Class Space > id: itest-rest-feed~Remote JMX~java.lang:name=Compressed Class > Space,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > File Store [/] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=~ > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > itest-rest-feed_OperatingSystem > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > parent: null > type: Platform_Operating System > --- > Processor [4] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=4 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > ExampleDS > id: itest-rest-feed~Local DMR~/subsystem=datasources/ > data-source=ExampleDS > parent: itest-rest-feed~Local DMR~~ > type: Datasource > --- > ExpiryQueue > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-queue=ExpiryQueue > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Queue > --- > org.hawkular.inventory.handlers.InventoryApp > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war/subsystem=undertow/servlet=org.hawkular.inventory. > handlers.InventoryApp > parent: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > type: Servlet > --- > http > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=http > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > Transaction Manager > id: itest-rest-feed~Local DMR~/subsystem=transactions > parent: itest-rest-feed~Local DMR~~ > type: Transaction Manager > --- > InventoryConfig > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war/subsystem=ejb3/singleton-bean=InventoryConfig > parent: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > type: Singleton EJB > --- > HawkularInventoryChanges > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-topic=HawkularInventoryChanges > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Topic > ===== > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > onOpen > FINE: WebSocket opened > 20:13:29,091 INFO [org.hawkular.cmdgw.command.ws.server.UIClientWebSocket] > (default task-42) HAWKFEEDCOMM000013: WebSocket session [Hgf9Zznsx_ > y9U14uaHPPWIPuSarLogLgugUCweVK] opened for endpoint [/ui/ws] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Received message[0] from WebSocket: [ActualMessage > [type=application/vnd.okhttp.websocket+text; charset=utf-8, > body=WelcomeResponse={"sessionId":"Hgf9Zznsx_ > y9U14uaHPPWIPuSarLogLgugUCweVK"}]] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Message[0]: [PASSED] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$MessageAnswer$1 > run > FINE: Sending over WebSocket: RemoveDatasourceRequest={" > authentication":{"username":"itest-rest","password":"itest-rest-password"}, > "feedId":"itest-rest-feed","resourceId":"itest-rest-feed~Local > DMR~/subsystem=datasources/xa-data-source=testXaDs"} > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$MessageAnswer$1 > run > FINE: No sleep configured > 20:13:29,102 INFO [org.hawkular.cmdgw.command.ws.server.AbstractGatewayWebSocket] > (default task-43) HAWKFEEDCOMM000014: Received message > [org.hawkular.cmdgw.api.RemoveDatasourceRequest] from WebSocket session > [Hgf9Zznsx_y9U14uaHPPWIPuSarLogLgugUCweVK] of [/ui/ws] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Received message[1] from WebSocket: [ActualMessage > [type=application/vnd.okhttp.websocket+text; charset=utf-8, > body=GenericSuccessResponse={"message":"The request has been forwarded to > feed [itest-rest-feed] (MessageId=ID:27f779d9-bd07- > 11e7-a03b-55f35baba5f1)"}]] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Message[1]: [PASSED] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$ExpectedEvent > scheduleAnswer > FINE: No answer to send for message[1] > 20:13:29,108 INFO [org.hawkular.agent.monitor.cmd. > AbstractDMRResourcePathCommand] (OkHttp http://127.0.0.1:8080/...) > HAWKAGENT010065: Received request to perform [Remove] on a [Datasource] > given by inventory path [itest-rest-feed~Local > DMR~/subsystem=datasources/xa-data-source=testXaDs] > 20:13:29,150 INFO [org.hawkular.cmdgw.command.ws.server.AbstractGatewayWebSocket] > (default task-47) HAWKFEEDCOMM000014: Received message > [org.hawkular.cmdgw.api.RemoveDatasourceResponse] from WebSocket session > [AQNPLng4hq-vgfGOOo53kVpLuQjVcKvzXAzwqPS3] of [/feed/{feedId}] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Received message[2] from WebSocket: [ActualMessage > [type=application/vnd.okhttp.websocket+text; charset=utf-8, > body=RemoveDatasourceResponse={"feedId":"itest-rest-feed"," > resourceId":"itest-rest-feed~Local DMR~/subsystem=datasources/xa- > data-source=testXaDs","destinationSessionId":"Hgf9Zznsx_ > y9U14uaHPPWIPuSarLogLgugUCweVK","status":"OK","message":"Performed > [Remove] on a [Datasource] given by Feed Id [itest-rest-feed] Resource Id > [itest-rest-feed~Local DMR~/subsystem=datasources/xa- > data-source=testXaDs]","serverRefreshIndicator":"RELOAD-REQUIRED"}]] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Message[2]: [PASSED] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$Answer$1 > lambda$schedule$0 > FINE: About to send manual close > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$Answer$1 > lambda$schedule$0 > FINE: Close sent > 20:13:29,156 INFO [org.hawkular.cmdgw.command.ws.server.UIClientWebSocket] > (default task-44) HAWKFEEDCOMM000015: WebSocket session [Hgf9Zznsx_ > y9U14uaHPPWIPuSarLogLgugUCweVK] of [/ui/ws] closed. > Reason=[CloseReason[1000,OK]] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Received message[3] from WebSocket: [ActualClose [code=1000, > reason=OK]] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Message[3]: [PASSED] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$ExpectedEvent > scheduleAnswer > FINE: No answer to send for message[3] > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > handle > FINE: Message[3] was the last expected message, sending close. > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > close > FINE: Closing the websocket > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > shutDownExecutor > FINE: Shutting down the executor > Oct 29, 2017 8:13:29 PM org.hawkular.cmdgw.ws.test.TestWebSocketClient$TestListener > shutDownExecutor > FINE: Executor shut down > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed > ALL RESOURCES IN HAWKULAR INVENTORY: 66 > ===== > testXaDs deleted, should be out of inventory > ===== > --- > Hawkular Java Agent > id: itest-rest-feed~Local JMX~org.hawkular:type= > hawkular-javaagent > parent: null > type: Hawkular Java Agent > --- > JMX [Local JMX] MemoryPool Metaspace > id: itest-rest-feed~Local JMX~java.lang:name=Metaspace, > type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > Processor [3] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=3 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > JMX [Remote JMX] MemoryPool PS Old Gen > id: itest-rest-feed~Remote JMX~java.lang:name=PS Old > Gen,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > jolokia-war.war > id: itest-rest-feed~Local DMR~/deployment=jolokia-war.war > parent: itest-rest-feed~Local DMR~~ > type: Deployment > --- > hawkular-alerts > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=hawkular-alerts > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > DLQ > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-queue=DLQ > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Queue > --- > InventoryServiceIspn > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war/subsystem=ejb3/stateless-session-bean= > InventoryServiceIspn > parent: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > type: Stateless Session EJB > --- > ajp > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=ajp > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > mail-smtp > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/remote-destination-outbound-socket-binding=mail-smtp > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Remote Destination Outbound Socket Binding > --- > https > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=https > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > management-https > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=management-https > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > InventoryStats > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war/subsystem=ejb3/singleton-bean=InventoryStats > parent: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > type: Singleton EJB > --- > File Store [/dev/mapper/fedora_mazzwork-home] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=/dev/mapper/fedora_mazzwork-home > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > Memory > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/MEMORY=Memory > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Memory > --- > Processor [2] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=2 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > File Store [/dev/sda1] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=/dev/sda1 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > JMX [Remote JMX] MemoryPool Code Cache > id: itest-rest-feed~Remote JMX~java.lang:name=Code > Cache,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Remote JMX] MemoryPool Metaspace > id: itest-rest-feed~Remote JMX~java.lang:name=Metaspace, > type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Remote JMX] MemoryPool PS Survivor Space > id: itest-rest-feed~Remote JMX~java.lang:name=PS Survivor > Space,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > txn-recovery-environment > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=txn-recovery-environment > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > default > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > parent: itest-rest-feed~Local DMR~~ > type: Messaging Server > --- > Infinispan > id: itest-rest-feed~Local DMR~/subsystem=infinispan > parent: itest-rest-feed~Local DMR~~ > type: Infinispan > --- > jolokia-agent > id: itest-rest-feed~Local DMR~/deployment=jolokia-war. > war/subsystem=undertow/servlet=jolokia-agent > parent: itest-rest-feed~Local DMR~/deployment=jolokia-war.war > type: Servlet > --- > hawkular-inventory-ui.war > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-ui.war > parent: itest-rest-feed~Local DMR~~ > type: Deployment > --- > hawkular-services > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=hawkular-services > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > web > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=web > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > management-http > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=management-http > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > JMX [Local JMX] MemoryPool PS Survivor Space > id: itest-rest-feed~Local JMX~java.lang:name=PS Survivor > Space,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Local JMX] MemoryPool PS Eden Space > id: itest-rest-feed~Local JMX~java.lang:name=PS Eden > Space,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Local JMX] MemoryPool Code Cache > id: itest-rest-feed~Local JMX~java.lang:name=Code > Cache,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > Processor [7] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=7 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > Processor [1] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=1 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > txn-status-manager > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=txn-status-manager > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > ejb > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=ejb > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > h2 > id: itest-rest-feed~Local DMR~/subsystem=datasources/ > jdbc-driver=h2 > parent: itest-rest-feed~Local DMR~~ > type: JDBC Driver > --- > File Store [tmpfs] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=tmpfs > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > Processor [0] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=0 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > Processor [6] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=6 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > JMX [Remote JMX] MemoryPool PS Eden Space > id: itest-rest-feed~Remote JMX~java.lang:name=PS Eden > Space,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > JMX [Remote JMX][Runtime] > id: itest-rest-feed~Remote JMX~java.lang:type=Runtime > parent: null > type: Runtime MBean > --- > JMX [Local JMX] MemoryPool PS Old Gen > id: itest-rest-feed~Local JMX~java.lang:name=PS Old > Gen,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > HawkularQueue > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-topic=HawkularQueue > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Topic > --- > Local DMR > id: itest-rest-feed~Local DMR~~ > parent: null > type: WildFly Server > --- > HawkularTopic > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-topic=HawkularTopic > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Topic > --- > hawkular-command-gateway-war.war > id: itest-rest-feed~Local DMR~/deployment=hawkular- > command-gateway-war.war > parent: itest-rest-feed~Local DMR~~ > type: Deployment > --- > hibernate > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=hibernate > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > HawkularCommandEvent > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-topic=HawkularCommandEvent > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Topic > --- > File Store [/dev/mapper/fedora_mazzwork-root] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=/dev/mapper/fedora_mazzwork-root > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > Processor [5] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=5 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > JMX [Local JMX][Runtime] > id: itest-rest-feed~Local JMX~java.lang:type=Runtime > parent: null > type: Runtime MBean > --- > JMX [Local JMX] MemoryPool Compressed Class Space > id: itest-rest-feed~Local JMX~java.lang:name=Compressed Class > Space,type=MemoryPool > parent: itest-rest-feed~Local JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > server > id: itest-rest-feed~Local DMR~/subsystem=infinispan/ > cache-container=server > parent: itest-rest-feed~Local DMR~/subsystem=infinispan > type: Infinispan Cache Container > --- > standard-sockets > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > parent: itest-rest-feed~Local DMR~~ > type: Socket Binding Group > --- > hawkular-inventory-service.war > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > parent: itest-rest-feed~Local DMR~~ > type: Deployment > --- > JMX [Remote JMX] MemoryPool Compressed Class Space > id: itest-rest-feed~Remote JMX~java.lang:name=Compressed Class > Space,type=MemoryPool > parent: itest-rest-feed~Remote JMX~java.lang:type=Runtime > type: Memory Pool MBean > --- > File Store [/] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/FILE_STORE=~ > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_File Store > --- > itest-rest-feed_OperatingSystem > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > parent: null > type: Platform_Operating System > --- > Processor [4] > id: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem/PROCESSOR=4 > parent: itest-rest-feed~platform~/OPERATING_SYSTEM=itest-rest- > feed_OperatingSystem > type: Platform_Processor > --- > ExampleDS > id: itest-rest-feed~Local DMR~/subsystem=datasources/ > data-source=ExampleDS > parent: itest-rest-feed~Local DMR~~ > type: Datasource > --- > ExpiryQueue > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-queue=ExpiryQueue > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Queue > --- > org.hawkular.inventory.handlers.InventoryApp > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war/subsystem=undertow/servlet=org.hawkular.inventory. > handlers.InventoryApp > parent: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > type: Servlet > --- > http > id: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets/socket-binding=http > parent: itest-rest-feed~Local DMR~/socket-binding-group= > standard-sockets > type: Socket Binding > --- > Transaction Manager > id: itest-rest-feed~Local DMR~/subsystem=transactions > parent: itest-rest-feed~Local DMR~~ > type: Transaction Manager > --- > InventoryConfig > id: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war/subsystem=ejb3/singleton-bean=InventoryConfig > parent: itest-rest-feed~Local DMR~/deployment=hawkular- > inventory-service.war > type: Singleton EJB > --- > HawkularInventoryChanges > id: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default/jms-topic=HawkularInventoryChanges > parent: itest-rest-feed~Local DMR~/subsystem=messaging- > activemq/server=default > type: JMS Topic > ===== > 20:13:29,186 ERROR [org.hawkular.agent.monitor.storage.HawkularStorageAdapter] > (OkHttp http://127.0.0.1:8080/...) HAWKAGENT010083: Failed to store > notification: {"type":"RESOURCE_ADDED","properties":{"resourceId":"itest-rest-feed~Local > DMR~~","feedId":"itest-rest-feed","resourceType":"WildFly Server"}}: > java.io.IOException: status-code=[405], reason=[Method Not Allowed], url=[ > http://127.0.0.1:8080/hawkular/api/notification] > at org.hawkular.agent.monitor.storage.HawkularStorageAdapter$1. > onResponse(HawkularStorageAdapter.java:116) > at okhttp3.shaded.RealCall$AsyncCall.execute(RealCall.java:126) > at okhttp3.shaded.internal.NamedRunnable.run( > NamedRunnable.java:32) > at java.util.concurrent.ThreadPoolExecutor.runWorker( > ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > Got code 200 and message [OK] retries: http://127.0.0.1:8080/ > hawkular/inventory/resources?feedId=itest-rest-feed&typeId=XA%20Datasource > [Invoker 211968962] Invoking @AfterMethod AbstractITest.after()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > ===== Invoked methods > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > StandaloneWildFlyITest.testAgent()[pri:0, instance:org.hawkular.agent. > ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > StandaloneWildFlyITest.datasourcesAddedToInventory()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] > 577405636 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > StandaloneWildFlyITest.operationParameters()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] > 577405636 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > StandaloneWildFlyITest.socketBindingGroupsInInventory()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] > 577405636 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > StandaloneWildFlyITest.machineId()[pri:0, instance:org.hawkular.agent. > ws.test.StandaloneWildFlyITest at 226a82c4] 577405636 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > StandaloneWildFlyITest.resourceConfig()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneWildFlyITest at 226a82c4] > 577405636 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneWildFlyITest at 226a82c4] 577405636 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > ExecuteOperationCommandITest at 77e4c80f] 2011482127 > ExecuteOperationCommandITest.testExecuteAgentDiscoveryScan()[pri:0, > instance:org.hawkular.agent.ws.test.ExecuteOperationCommandITest at 77e4c80f] > 2011482127 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > ExecuteOperationCommandITest at 77e4c80f] 2011482127 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > StandaloneDeployApplicationITest.testAddDeployment()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITe > st at 351d0846] 891095110 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > StandaloneDeployApplicationITest.testDisableDeployment()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITe > st at 351d0846] 891095110 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > StandaloneDeployApplicationITest.testEnableDeployment()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITe > st at 351d0846] 891095110 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > StandaloneDeployApplicationITest.testRestartDeployment()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITe > st at 351d0846] 891095110 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > StandaloneDeployApplicationITest.testLocalAndRemoteJMXOperations()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITe > st at 351d0846] 891095110 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > StandaloneDeployApplicationITest.testUndeploy()[pri:0, > instance:org.hawkular.agent.ws.test.StandaloneDeployApplicationITe > st at 351d0846] 891095110 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > StandaloneDeployApplicationITest at 351d0846] 891095110 > AbstractITest.before()[pri:0, instance:org.hawkular.agent. > ws.test.ExportJdrCommandITest at 176d53b2] 393040818 > ExportJdrCommandITest.exportJdrCommand()[pri:0, > instance:org.hawkular.agent.ws.test.ExportJdrCommandITest at 176d53b2] > 393040818 > AbstractITest.after()[pri:0, instance:org.hawkular.agent. > ws.test.ExportJdrCommandITest at 176d53b2] 393040818 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > DatasourceCommandITest.testAddDatasource()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > 1147258851 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > DatasourceCommandITest.testAddXaDatasource()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > 1147258851 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > DatasourceCommandITest.testUpdateDatasource()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > 1147258851 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > DatasourceCommandITest.testUpdateXaDatasource()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > 1147258851 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > DatasourceCommandITest.testRemoveDatasource()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > 1147258851 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > AbstractITest.before()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > DatasourceCommandITest.testRemoveXaDatasource()[pri:0, > instance:org.hawkular.agent.ws.test.DatasourceCommandITest at 4461c7e3] > 1147258851 > AbstractITest.after()[pri:0, instance:org.hawkular.agent.ws.test. > DatasourceCommandITest at 4461c7e3] 1147258851 > ===== > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/Surefire suite/Surefire > test.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/Surefire suite/Surefire > test.xml > PASSED: testAgent > PASSED: datasourcesAddedToInventory > PASSED: operationParameters > PASSED: socketBindingGroupsInInventory > PASSED: machineId > PASSED: resourceConfig > PASSED: testExecuteAgentDiscoveryScan > PASSED: testAddDeployment > PASSED: testDisableDeployment > PASSED: testEnableDeployment > PASSED: testRestartDeployment > PASSED: testLocalAndRemoteJMXOperations > PASSED: testUndeploy > PASSED: exportJdrCommand > PASSED: testAddDatasource > PASSED: testAddXaDatasource > PASSED: testUpdateDatasource > PASSED: testUpdateXaDatasource > PASSED: testRemoveDatasource > FAILED: testRemoveXaDatasource > java.lang.AssertionError: Resource [type=XA Datasource, > containing=testXaDs] still found after 10 attempts. > at org.hawkular.agent.itest.util.ITestHelper. > waitForNoResourceContaining(ITestHelper.java:167) > at org.hawkular.agent.ws.test.DatasourceCommandITest. > testRemoveXaDatasource(DatasourceCommandITest.java:381) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke( > NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.testng.internal.MethodInvocationHelper.invokeMethod( > MethodInvocationHelper.java:86) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:643) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820) > at org.testng.internal.Invoker.invokeTestMethods(Invoker. > java:1128) > at org.testng.internal.TestMethodWorker.invokeTestMethods( > TestMethodWorker.java:129) > at org.testng.internal.TestMethodWorker.run( > TestMethodWorker.java:112) > at org.testng.TestRunner.privateRun(TestRunner.java:782) > at org.testng.TestRunner.run(TestRunner.java:632) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) > at org.testng.SuiteRunner.run(SuiteRunner.java:268) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker. > java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) > at org.testng.TestNG.run(TestNG.java:1064) > at org.apache.maven.surefire.testng.TestNGExecutor.run( > TestNGExecutor.java:132) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > executeMulti(TestNGDirectoryTestSuite.java:193) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > execute(TestNGDirectoryTestSuite.java:94) > at org.apache.maven.surefire.testng.TestNGProvider.invoke( > TestNGProvider.java:147) > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > SKIPPED: testEnableStatistics > java.lang.Throwable: Method StatisticsControlCommandITest.testEnableStatistics()[pri:0, > instance:org.hawkular.agent.ws.test.StatisticsControlCommandITest at 4450d156] > depends on not successfully finished methods in group > "DatasourceCommandITest" > at org.testng.internal.Invoker.invokeTestMethods(Invoker. > java:1037) > at org.testng.internal.TestMethodWorker.invokeTestMethods( > TestMethodWorker.java:129) > at org.testng.internal.TestMethodWorker.run( > TestMethodWorker.java:112) > at org.testng.TestRunner.privateRun(TestRunner.java:782) > at org.testng.TestRunner.run(TestRunner.java:632) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) > at org.testng.SuiteRunner.run(SuiteRunner.java:268) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker. > java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) > at org.testng.TestNG.run(TestNG.java:1064) > at org.apache.maven.surefire.testng.TestNGExecutor.run( > TestNGExecutor.java:132) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > executeMulti(TestNGDirectoryTestSuite.java:193) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > execute(TestNGDirectoryTestSuite.java:94) > at org.apache.maven.surefire.testng.TestNGProvider.invoke( > TestNGProvider.java:147) > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > SKIPPED: testDisableStatistics > java.lang.Throwable: Method StatisticsControlCommandITest.testDisableStatistics()[pri:0, > instance:org.hawkular.agent.ws.test.StatisticsControlCommandITest at 4450d156] > depends on not successfully finished methods > at org.testng.internal.Invoker.invokeTestMethods(Invoker. > java:1037) > at org.testng.internal.TestMethodWorker.invokeTestMethods( > TestMethodWorker.java:129) > at org.testng.internal.TestMethodWorker.run( > TestMethodWorker.java:112) > at org.testng.TestRunner.privateRun(TestRunner.java:782) > at org.testng.TestRunner.run(TestRunner.java:632) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) > at org.testng.SuiteRunner.run(SuiteRunner.java:268) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker. > java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) > at org.testng.TestNG.run(TestNG.java:1064) > at org.apache.maven.surefire.testng.TestNGExecutor.run( > TestNGExecutor.java:132) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > executeMulti(TestNGDirectoryTestSuite.java:193) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > execute(TestNGDirectoryTestSuite.java:94) > at org.apache.maven.surefire.testng.TestNGProvider.invoke( > TestNGProvider.java:147) > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > SKIPPED: testEnableStatisticsSubset > java.lang.Throwable: Method StatisticsControlCommandITest. > testEnableStatisticsSubset()[pri:0, instance:org.hawkular.agent.ws.test. > StatisticsControlCommandITest at 4450d156] depends on not successfully > finished methods > at org.testng.internal.Invoker.invokeTestMethods(Invoker. > java:1037) > at org.testng.internal.TestMethodWorker.invokeTestMethods( > TestMethodWorker.java:129) > at org.testng.internal.TestMethodWorker.run( > TestMethodWorker.java:112) > at org.testng.TestRunner.privateRun(TestRunner.java:782) > at org.testng.TestRunner.run(TestRunner.java:632) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) > at org.testng.SuiteRunner.run(SuiteRunner.java:268) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker. > java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) > at org.testng.TestNG.run(TestNG.java:1064) > at org.apache.maven.surefire.testng.TestNGExecutor.run( > TestNGExecutor.java:132) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > executeMulti(TestNGDirectoryTestSuite.java:193) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > execute(TestNGDirectoryTestSuite.java:94) > at org.apache.maven.surefire.testng.TestNGProvider.invoke( > TestNGProvider.java:147) > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > SKIPPED: testAddJdbcDriver > java.lang.Throwable: Method JdbcDriverCommandITest.testAddJdbcDriver()[pri:0, > instance:org.hawkular.agent.ws.test.JdbcDriverCommandITest at 731f8236] > depends on not successfully finished methods in group " > StatisticsControlCommandITest" > at org.testng.internal.Invoker.invokeTestMethods(Invoker. > java:1037) > at org.testng.internal.TestMethodWorker.invokeTestMethods( > TestMethodWorker.java:129) > at org.testng.internal.TestMethodWorker.run( > TestMethodWorker.java:112) > at org.testng.TestRunner.privateRun(TestRunner.java:782) > at org.testng.TestRunner.run(TestRunner.java:632) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) > at org.testng.SuiteRunner.run(SuiteRunner.java:268) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker. > java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) > at org.testng.TestNG.run(TestNG.java:1064) > at org.apache.maven.surefire.testng.TestNGExecutor.run( > TestNGExecutor.java:132) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > executeMulti(TestNGDirectoryTestSuite.java:193) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > execute(TestNGDirectoryTestSuite.java:94) > at org.apache.maven.surefire.testng.TestNGProvider.invoke( > TestNGProvider.java:147) > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > SKIPPED: testRemoveJdbcDriver > java.lang.Throwable: Method JdbcDriverCommandITest.testRemoveJdbcDriver()[pri:0, > instance:org.hawkular.agent.ws.test.JdbcDriverCommandITest at 731f8236] > depends on not successfully finished methods > at org.testng.internal.Invoker.invokeTestMethods(Invoker. > java:1037) > at org.testng.internal.TestMethodWorker.invokeTestMethods( > TestMethodWorker.java:129) > at org.testng.internal.TestMethodWorker.run( > TestMethodWorker.java:112) > at org.testng.TestRunner.privateRun(TestRunner.java:782) > at org.testng.TestRunner.run(TestRunner.java:632) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) > at org.testng.SuiteRunner.run(SuiteRunner.java:268) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker. > java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) > at org.testng.TestNG.run(TestNG.java:1064) > at org.apache.maven.surefire.testng.TestNGExecutor.run( > TestNGExecutor.java:132) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > executeMulti(TestNGDirectoryTestSuite.java:193) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > execute(TestNGDirectoryTestSuite.java:94) > at org.apache.maven.surefire.testng.TestNGProvider.invoke( > TestNGProvider.java:147) > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > SKIPPED: testImmutableUpdate > java.lang.Throwable: Method ImmutableITest.testImmutableUpdate()[pri:0, > instance:org.hawkular.agent.ws.test.ImmutableITest at 1b68b9a4] depends on > not successfully finished methods in group "JdbcDriverCommandITest" > at org.testng.internal.Invoker.invokeTestMethods(Invoker. > java:1037) > at org.testng.internal.TestMethodWorker.invokeTestMethods( > TestMethodWorker.java:129) > at org.testng.internal.TestMethodWorker.run( > TestMethodWorker.java:112) > at org.testng.TestRunner.privateRun(TestRunner.java:782) > at org.testng.TestRunner.run(TestRunner.java:632) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) > at org.testng.SuiteRunner.run(SuiteRunner.java:268) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker. > java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) > at org.testng.TestNG.run(TestNG.java:1064) > at org.apache.maven.surefire.testng.TestNGExecutor.run( > TestNGExecutor.java:132) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > executeMulti(TestNGDirectoryTestSuite.java:193) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite. > execute(TestNGDirectoryTestSuite.java:94) > at org.apache.maven.surefire.testng.TestNGProvider.invoke( > TestNGProvider.java:147) > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > > =============================================== > Surefire test > Tests run: 26, Failures: 1, Skips: 6 > =============================================== > > > =============================================== > Surefire suite > Total tests run: 26, Failures: 1, Skips: 6 > =============================================== > > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/testng-failed.xml > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/Surefire > suite/testng-failed.xml > [TestNG] Time taken by [FailedReporter passed=0 failed=0 skipped=0]: 7 ms > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire suite/toc.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire suite/Surefire > test.properties > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire > suite/index.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire suite/main.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire > suite/groups.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire > suite/classes.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire > suite/reporter-output.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire > suite/methods-not-run.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/Surefire > suite/testng.xml.html > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/old/index.html > [TestNG] Time taken by org.testng.reporters.SuiteHTMLReporter at 396e2f39: 9 > ms > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/junitreports/ > TEST-org.hawkular.agent.ws.test.StandaloneDeployApplicationITest.xml > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/junitreports/ > TEST-org.hawkular.agent.ws.test.ExportJdrCommandITest.xml > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/junitreports/ > TEST-org.hawkular.agent.ws.test.ImmutableITest.xml > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/junitreports/ > TEST-org.hawkular.agent.ws.test.ExecuteOperationCommandITest.xml > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/junitreports/ > TEST-org.hawkular.agent.ws.test.DatasourceCommandITest.xml > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/junitreports/ > TEST-org.hawkular.agent.ws.test.StatisticsControlCommandITest.xml > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/junitreports/ > TEST-org.hawkular.agent.ws.test.StandaloneWildFlyITest.xml > Creating /home/mazz/source/hawkular-agent/hawkular-javaagent- > itest-parent/hawkular-javaagent-all-itests/hawkular- > javaagent-cmdgw-itest/target/failsafe-reports/junitreports/ > TEST-org.hawkular.agent.ws.test.JdbcDriverCommandITest.xml > [TestNG] Time taken by org.testng.reporters.JUnitReportReporter at 2eda0940: > 7 ms > [TestNG] Time taken by org.testng.reporters.jq.Main at 7e0e6aa2: 61 ms > [TestNG] Time taken by org.testng.reporters.XMLReporter at 2e3fc542: 6 ms > [TestNG] Time taken by org.testng.reporters.EmailableReporter2 at 704d6e83: > 7 ms > Tests run: 26, Failures: 1, Errors: 0, Skipped: 6, Time elapsed: 103.303 > sec <<< FAILURE! - in TestSuite > testRemoveXaDatasource(org.hawkular.agent.ws.test.DatasourceCommandITest) > Time elapsed: 50.287 sec <<< FAILURE! > java.lang.AssertionError: Resource [type=XA Datasource, > containing=testXaDs] still found after 10 attempts. > at org.hawkular.agent.ws.test.DatasourceCommandITest. > testRemoveXaDatasource(DatasourceCommandITest.java:381) > > > Results : > > Failed tests: > DatasourceCommandITest.testRemoveXaDatasource:381 Resource [type=XA > Datasource, containing=testXaDs] still found after 10 attempts. > > Tests run: 26, Failures: 1, Errors: 0, Skipped: 6 > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171030/70c6275a/attachment-0001.html From jtakvori at redhat.com Mon Oct 30 05:06:36 2017 From: jtakvori at redhat.com (Joel Takvorian) Date: Mon, 30 Oct 2017 10:06:36 +0100 Subject: [Hawkular-dev] agent can now link prometheus metrics in inventory In-Reply-To: References: <1104416817.33960920.1509279211909.JavaMail.zimbra@redhat.com> <2136050331.33961361.1509280226122.JavaMail.zimbra@redhat.com> Message-ID: BTW, +1 for dedicated fields in Metric model. That will avoid mixing labels and properties, which would be error-prone on client side for rebuilding the full ID. I've created a JIRA for that: https://issues.jboss.org/browse/HAWKULAR-1311 On Mon, Oct 30, 2017 at 8:43 AM, Joel Takvorian wrote: > Nice! > > It looks like from these example, fields "name" and "type" could be merged > into one, are they always identical? > > On Sun, Oct 29, 2017 at 1:30 PM, John Mazzitelli wrote: > >> The agent in branch hawkular-1275 can now link Prometheus metric family >> names/labels into hawkular inventory (at least, it looks like its working >> :-) >> >> You will see metrics in inventory that look like the below examples - >> notice the general props on the metrics now contain Prometheus metric >> labels - there is one extra property called "hawkular.metric.family" and >> that is, obviously, the Prometheus metric family name. The rest are >> Prometheus metric labels. We need to change this, I think. We should have >> first-class fields on the inventory Metric object for "String metricFamily" >> and "Map metricLabels". But for now, we are using general >> properties. >> >> So for example, to query the "Pool Create Count" metric data from >> Prometheus for the Stateless Session EJB resource called >> "InventoryServiceIspn" you look up its metric metadata in hawkular >> inventory, see the following metadata I show below, and then you know have >> to query this in Prometheus: >> >> wildfly_ejb_pool_create_count{deployment=hawkular-inventory-service.war, >> name=InventoryServiceIspn, feed-id=mazzlap} >> >> We do not have unique metric IDs being stored yet. We should figure out >> if we really need them before we store more data in inventory. >> Also, the JMX exporter does not actually put the feed-id label on metrics >> - that will be the job of the Prometheus server and its scrape definition. >> But we know it will need to be there, so inventory will specify it. >> >> { >> "name": "Pool Create Count", >> "type": "Pool Create Count", >> "unit": "NONE", >> "properties": { >> "feed-id": "mazzlap", >> "name": "InventoryServiceIspn", >> "type": "stateless-session", >> "hawkular.metric.family": "wildfly_ejb_pool_create_count", >> "deployment": "hawkular-inventory-service.war" >> } >> >> Here's other examples you will see in inventory: >> >> { >> "name": "Max Active Sessions", >> "type": "Max Active Sessions", >> "unit": "NONE", >> "properties": { >> "feed-id": "mazzlap", >> "hawkular.metric.family": "wildfly_deployment_max_active >> _sessions", >> "deployment": "hawkular-inventory-service.war" >> } >> >> { >> "name": "Heap Used", >> "type": "Heap Used", >> "unit": "BYTES", >> "properties": { >> "area": "heap", >> "feed-id": "mazzlap", >> "hawkular.metric.family": "jvm_memory_bytes_used" >> } >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171030/f9eebba4/attachment.html From jtakvori at redhat.com Mon Oct 30 05:37:21 2017 From: jtakvori at redhat.com (Joel Takvorian) Date: Mon, 30 Oct 2017 10:37:21 +0100 Subject: [Hawkular-dev] Separate maven build of Inventory UI Message-ID: Hi, While I'm really glad that inventory has an embedded UI, very helpful while testing and debugging, it's a bit sad that it involves nodejs/npm build triggered during the maven build of hawkular-commons (build time is more than tripled). For Hawkular Metrics UI we use a separate repo (hawkular-ui) for the build: all npm/nodejs build stuff happens there. On hawkular-metrics side, before preparing the WAR, the webapp is pulled using maven SCM plugin. What do you think, can we have a similar process here? (I'd volunteer to do it) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171030/aaf6df4e/attachment.html From lponce at redhat.com Mon Oct 30 05:53:55 2017 From: lponce at redhat.com (Lucas Ponce) Date: Mon, 30 Oct 2017 10:53:55 +0100 Subject: [Hawkular-dev] Separate maven build of Inventory UI In-Reply-To: References: Message-ID: On Mon, Oct 30, 2017 at 10:37 AM, Joel Takvorian wrote: > Hi, > > While I'm really glad that inventory has an embedded UI, very helpful > while testing and debugging, it's a bit sad that it involves nodejs/npm > build triggered during the maven build of hawkular-commons (build time is > more than tripled). > > For Hawkular Metrics UI we use a separate repo (hawkular-ui) for the > build: all npm/nodejs build stuff happens there. On hawkular-metrics side, > before preparing the WAR, the webapp is pulled using maven SCM plugin. > > What do you think, can we have a similar process here? (I'd volunteer to > do it) > As the UI is a development helper, I guess it can go a different repo (I don't think it has testing by itself). But if potentially needs to grow (and additions and tests are necessary) then should be under the CI and perhaps it should be used a separate profile (-Pui) or similar to let travis to build it. Both solutions sound good to me, so it is a matter of what people prefer to do. Lucas > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171030/dc07dfd6/attachment.html From jtakvori at redhat.com Mon Oct 30 05:55:55 2017 From: jtakvori at redhat.com (Joel Takvorian) Date: Mon, 30 Oct 2017 10:55:55 +0100 Subject: [Hawkular-dev] Separate maven build of Inventory UI In-Reply-To: References: Message-ID: Yes, I'd like a profile-based solution as well. On Mon, Oct 30, 2017 at 10:53 AM, Lucas Ponce wrote: > > > On Mon, Oct 30, 2017 at 10:37 AM, Joel Takvorian > wrote: > >> Hi, >> >> While I'm really glad that inventory has an embedded UI, very helpful >> while testing and debugging, it's a bit sad that it involves nodejs/npm >> build triggered during the maven build of hawkular-commons (build time is >> more than tripled). >> >> For Hawkular Metrics UI we use a separate repo (hawkular-ui) for the >> build: all npm/nodejs build stuff happens there. On hawkular-metrics side, >> before preparing the WAR, the webapp is pulled using maven SCM plugin. >> >> What do you think, can we have a similar process here? (I'd volunteer to >> do it) >> > > As the UI is a development helper, I guess it can go a different repo (I > don't think it has testing by itself). > > But if potentially needs to grow (and additions and tests are necessary) > then should be under the CI and perhaps it should be used a separate > profile (-Pui) or similar to let travis to build it. > > Both solutions sound good to me, so it is a matter of what people prefer > to do. > > Lucas > > >> >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> >> > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171030/27601c99/attachment.html From jtakvori at redhat.com Mon Oct 30 08:15:36 2017 From: jtakvori at redhat.com (Joel Takvorian) Date: Mon, 30 Oct 2017 13:15:36 +0100 Subject: [Hawkular-dev] possible bug in inventory server In-Reply-To: References: <131097386.34268802.1509322878797.JavaMail.zimbra@redhat.com> <2081173691.34285872.1509325434574.JavaMail.zimbra@redhat.com> Message-ID: I've seen the same error just once (out of 5 or 6 tries), and, coincidentally, had the same error notified "Failed to store notification: {"type":"RESOURCE_ADDED" etc." with "MethodNotAllowed" at the very same moment, that is, just when the testRemoveXaDatasource test runs. That's maybe a trail to investigate, maybe it betrays some server-side malfunction. I don't know if it's possible to see server-side logs during agent itests, but it would probably help. I don't know why this error happens. When I run tests successfully, I also see from times to times this error, but it's distributed randomly in tests, and fortunately or not (rather not), tests pass. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171030/e9024649/attachment-0001.html From jtakvori at redhat.com Mon Oct 30 13:17:25 2017 From: jtakvori at redhat.com (Joel Takvorian) Date: Mon, 30 Oct 2017 18:17:25 +0100 Subject: [Hawkular-dev] possible bug in inventory server In-Reply-To: References: <131097386.34268802.1509322878797.JavaMail.zimbra@redhat.com> <2081173691.34285872.1509325434574.JavaMail.zimbra@redhat.com> Message-ID: Some update, here is the latest logs I got while the test failed: https://paste.fedoraproject.org/paste/Yy8CuDvgqzX1RazON6Cmag I haven't time to dig further today, but see in the middle that lovely stack trace: *18:01:59,012 ERROR [org.infinispan.transaction.impl.TransactionCoordinator] (default task-35) ISPN000255: Error while processing prepare: org.infinispan.transaction.WriteSkewException: Write skew detected on key itest-rest-feed~Local DMR~/subsystem=datasources/xa-data-source=testXaDs for transaction TransactionImple < ac, BasicAction: 0:ffffc0a8000c:-5784e282:59f75acd:b4 status: ActionStatus.RUNNING >* * at org.infinispan.transaction.impl.WriteSkewHelper.performWriteSkewCheckAndReturnNewVersions(WriteSkewHelper.java:66)* * at org.infinispan.interceptors.locking.ClusteringDependentLogic$AbstractClusteringDependentLogic.clusteredCreateNewVersionsAndCheckForWriteSkews(ClusteringDependentLogic.java:261)* I have no idea why it wasn't displayed before, and it is now. On Mon, Oct 30, 2017 at 1:15 PM, Joel Takvorian wrote: > I've seen the same error just once (out of 5 or 6 tries), and, > coincidentally, had the same error notified "Failed to store > notification: {"type":"RESOURCE_ADDED" etc." with "MethodNotAllowed" at > the very same moment, that is, just when the testRemoveXaDatasource test > runs. > That's maybe a trail to investigate, maybe it betrays some server-side > malfunction. I don't know if it's possible to see server-side logs during > agent itests, but it would probably help. I don't know why this error > happens. > > When I run tests successfully, I also see from times to times this error, > but it's distributed randomly in tests, and fortunately or not (rather > not), tests pass. > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171030/299dae29/attachment.html From lponce at redhat.com Mon Oct 30 13:25:42 2017 From: lponce at redhat.com (Lucas Ponce) Date: Mon, 30 Oct 2017 18:25:42 +0100 Subject: [Hawkular-dev] possible bug in inventory server In-Reply-To: References: <131097386.34268802.1509322878797.JavaMail.zimbra@redhat.com> <2081173691.34285872.1509325434574.JavaMail.zimbra@redhat.com> Message-ID: That's interesting. I haven't got that trace, yes, it seems the indexmanager failed, still trying to get the same one. On Mon, Oct 30, 2017 at 6:17 PM, Joel Takvorian wrote: > Some update, here is the latest logs I got while the test failed: > https://paste.fedoraproject.org/paste/Yy8CuDvgqzX1RazON6Cmag > > I haven't time to dig further today, but see in the middle that lovely > stack trace: > > *18:01:59,012 ERROR > [org.infinispan.transaction.impl.TransactionCoordinator] (default task-35) > ISPN000255: Error while processing prepare: > org.infinispan.transaction.WriteSkewException: Write skew detected on key > itest-rest-feed~Local DMR~/subsystem=datasources/xa-data-source=testXaDs > for transaction TransactionImple < ac, BasicAction: > 0:ffffc0a8000c:-5784e282:59f75acd:b4 status: ActionStatus.RUNNING >* > * at > org.infinispan.transaction.impl.WriteSkewHelper.performWriteSkewCheckAndReturnNewVersions(WriteSkewHelper.java:66)* > * at > org.infinispan.interceptors.locking.ClusteringDependentLogic$AbstractClusteringDependentLogic.clusteredCreateNewVersionsAndCheckForWriteSkews(ClusteringDependentLogic.java:261)* > > I have no idea why it wasn't displayed before, and it is now. > > On Mon, Oct 30, 2017 at 1:15 PM, Joel Takvorian > wrote: > >> I've seen the same error just once (out of 5 or 6 tries), and, >> coincidentally, had the same error notified "Failed to store >> notification: {"type":"RESOURCE_ADDED" etc." with "MethodNotAllowed" at >> the very same moment, that is, just when the testRemoveXaDatasource test >> runs. >> That's maybe a trail to investigate, maybe it betrays some server-side >> malfunction. I don't know if it's possible to see server-side logs during >> agent itests, but it would probably help. I don't know why this error >> happens. >> >> When I run tests successfully, I also see from times to times this error, >> but it's distributed randomly in tests, and fortunately or not (rather >> not), tests pass. >> > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171030/2a050f59/attachment.html From lponce at redhat.com Mon Oct 30 13:39:35 2017 From: lponce at redhat.com (Lucas Ponce) Date: Mon, 30 Oct 2017 18:39:35 +0100 Subject: [Hawkular-dev] possible bug in inventory server In-Reply-To: References: <131097386.34268802.1509322878797.JavaMail.zimbra@redhat.com> <2081173691.34285872.1509325434574.JavaMail.zimbra@redhat.com> Message-ID: Well, in details it means that is trying to write/delete at same key and it failed, and then probably the indexmanager was not updated. Did you get that trace also in the server.log as well ? On Mon, Oct 30, 2017 at 6:25 PM, Lucas Ponce wrote: > That's interesting. > I haven't got that trace, yes, it seems the indexmanager failed, still > trying to get the same one. > > On Mon, Oct 30, 2017 at 6:17 PM, Joel Takvorian > wrote: > >> Some update, here is the latest logs I got while the test failed: >> https://paste.fedoraproject.org/paste/Yy8CuDvgqzX1RazON6Cmag >> >> I haven't time to dig further today, but see in the middle that lovely >> stack trace: >> >> *18:01:59,012 ERROR [org.infinispan.transaction.im >> pl.TransactionCoordinator] (default >> task-35) ISPN000255: Error while processing prepare: >> org.infinispan.transaction.WriteSkewException: Write skew detected on key >> itest-rest-feed~Local DMR~/subsystem=datasources/xa-data-source=testXaDs >> for transaction TransactionImple < ac, BasicAction: >> 0:ffffc0a8000c:-5784e282:59f75acd:b4 status: ActionStatus.RUNNING >* >> * at >> org.infinispan.transaction.impl.WriteSkewHelper.performWriteSkewCheckAndReturnNewVersions(WriteSkewHelper.java:66)* >> * at >> org.infinispan.interceptors.locking.ClusteringDependentLogic$AbstractClusteringDependentLogic.clusteredCreateNewVersionsAndCheckForWriteSkews(ClusteringDependentLogic.java:261)* >> >> I have no idea why it wasn't displayed before, and it is now. >> >> On Mon, Oct 30, 2017 at 1:15 PM, Joel Takvorian >> wrote: >> >>> I've seen the same error just once (out of 5 or 6 tries), and, >>> coincidentally, had the same error notified "Failed to store >>> notification: {"type":"RESOURCE_ADDED" etc." with "MethodNotAllowed" at >>> the very same moment, that is, just when the testRemoveXaDatasource test >>> runs. >>> That's maybe a trail to investigate, maybe it betrays some server-side >>> malfunction. I don't know if it's possible to see server-side logs during >>> agent itests, but it would probably help. I don't know why this error >>> happens. >>> >>> When I run tests successfully, I also see from times to times this >>> error, but it's distributed randomly in tests, and fortunately or not >>> (rather not), tests pass. >>> >> >> >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171030/08a4e675/attachment.html From lponce at redhat.com Mon Oct 30 14:01:17 2017 From: lponce at redhat.com (Lucas Ponce) Date: Mon, 30 Oct 2017 19:01:17 +0100 Subject: [Hawkular-dev] possible bug in inventory server In-Reply-To: References: <131097386.34268802.1509322878797.JavaMail.zimbra@redhat.com> <2081173691.34285872.1509325434574.JavaMail.zimbra@redhat.com> Message-ID: Ok, I spot a potential problem. I will prepare a better test in commons to deal with it. On Mon, Oct 30, 2017 at 6:39 PM, Lucas Ponce wrote: > Well, in details it means that is trying to write/delete at same key and > it failed, and then probably the indexmanager was not updated. > > Did you get that trace also in the server.log as well ? > > On Mon, Oct 30, 2017 at 6:25 PM, Lucas Ponce wrote: > >> That's interesting. >> I haven't got that trace, yes, it seems the indexmanager failed, still >> trying to get the same one. >> >> On Mon, Oct 30, 2017 at 6:17 PM, Joel Takvorian >> wrote: >> >>> Some update, here is the latest logs I got while the test failed: >>> https://paste.fedoraproject.org/paste/Yy8CuDvgqzX1RazON6Cmag >>> >>> I haven't time to dig further today, but see in the middle that lovely >>> stack trace: >>> >>> *18:01:59,012 ERROR [org.infinispan.transaction.im >>> pl.TransactionCoordinator] (default >>> task-35) ISPN000255: Error while processing prepare: >>> org.infinispan.transaction.WriteSkewException: Write skew detected on key >>> itest-rest-feed~Local DMR~/subsystem=datasources/xa-data-source=testXaDs >>> for transaction TransactionImple < ac, BasicAction: >>> 0:ffffc0a8000c:-5784e282:59f75acd:b4 status: ActionStatus.RUNNING >* >>> * at >>> org.infinispan.transaction.impl.WriteSkewHelper.performWriteSkewCheckAndReturnNewVersions(WriteSkewHelper.java:66)* >>> * at >>> org.infinispan.interceptors.locking.ClusteringDependentLogic$AbstractClusteringDependentLogic.clusteredCreateNewVersionsAndCheckForWriteSkews(ClusteringDependentLogic.java:261)* >>> >>> I have no idea why it wasn't displayed before, and it is now. >>> >>> On Mon, Oct 30, 2017 at 1:15 PM, Joel Takvorian >>> wrote: >>> >>>> I've seen the same error just once (out of 5 or 6 tries), and, >>>> coincidentally, had the same error notified "Failed to store >>>> notification: {"type":"RESOURCE_ADDED" etc." with "MethodNotAllowed" >>>> at the very same moment, that is, just when the testRemoveXaDatasource test >>>> runs. >>>> That's maybe a trail to investigate, maybe it betrays some server-side >>>> malfunction. I don't know if it's possible to see server-side logs during >>>> agent itests, but it would probably help. I don't know why this error >>>> happens. >>>> >>>> When I run tests successfully, I also see from times to times this >>>> error, but it's distributed randomly in tests, and fortunately or not >>>> (rather not), tests pass. >>>> >>> >>> >>> _______________________________________________ >>> hawkular-dev mailing list >>> hawkular-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hawkular-dev >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171030/a7e710ba/attachment-0001.html From mwringe at redhat.com Mon Oct 30 14:29:49 2017 From: mwringe at redhat.com (Matthew Wringe) Date: Mon, 30 Oct 2017 14:29:49 -0400 Subject: [Hawkular-dev] Separate maven build of Inventory UI In-Reply-To: References: Message-ID: I think another question is will we ever want to include things outside of inventory? Would having a UI to help with development/testing also be useful for other pieces of Hawkular Services? I think using a separate repo (possibly re-using the hawkular-ui repo) could be a good idea here, and then bringing it into Hawkular Services if a profile is activated. On Mon, Oct 30, 2017 at 5:55 AM, Joel Takvorian wrote: > Yes, I'd like a profile-based solution as well. > > On Mon, Oct 30, 2017 at 10:53 AM, Lucas Ponce wrote: > >> >> >> On Mon, Oct 30, 2017 at 10:37 AM, Joel Takvorian >> wrote: >> >>> Hi, >>> >>> While I'm really glad that inventory has an embedded UI, very helpful >>> while testing and debugging, it's a bit sad that it involves nodejs/npm >>> build triggered during the maven build of hawkular-commons (build time is >>> more than tripled). >>> >>> For Hawkular Metrics UI we use a separate repo (hawkular-ui) for the >>> build: all npm/nodejs build stuff happens there. On hawkular-metrics side, >>> before preparing the WAR, the webapp is pulled using maven SCM plugin. >>> >>> What do you think, can we have a similar process here? (I'd volunteer to >>> do it) >>> >> >> As the UI is a development helper, I guess it can go a different repo (I >> don't think it has testing by itself). >> >> But if potentially needs to grow (and additions and tests are necessary) >> then should be under the CI and perhaps it should be used a separate >> profile (-Pui) or similar to let travis to build it. >> >> Both solutions sound good to me, so it is a matter of what people prefer >> to do. >> >> Lucas >> >> >>> >>> _______________________________________________ >>> hawkular-dev mailing list >>> hawkular-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hawkular-dev >>> >>> >> >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> >> > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171030/63f0f845/attachment.html From jgodoy at redhat.com Tue Oct 31 10:57:44 2017 From: jgodoy at redhat.com (Jerczey Godoy) Date: Tue, 31 Oct 2017 11:57:44 -0300 Subject: [Hawkular-dev] Hawkular APM 0.14.4 + external Elastic Search In-Reply-To: References: Message-ID: Thanks everyone for the reply We managed to persist data by installing the ES 1.7.6 version. These act as a cluster with the embedded APM's ES. We assume that persistence is achieved as long as the master node is targeted to the independent ES service. best regards! On Thu, Oct 26, 2017 at 5:25 PM, Jerczey Godoy wrote: > Hello , I got the email list from irc.freenode #hawkular > > > We are attempting to make the events data (from agents) persistent, we > expect the external elastic search allows to have some sort of persistance > if there is a failure of the APM itself. > We checked the embedded elastic, and if the APM (wilfly) goes down, the > data from previous events does not remain. > > > So, we expected that an external elastic could suffice this , > we used this rpm wget https://artifacts.elastic.co/ > downloads/elasticsearch/elasticsearch-5.6.3.rpm and on the same host we > set up the APM 0.14 distrbution > we pointed the standalone.conf with the following configuration: > > > export HAWKULAR_APM_ELASTICSEARCH_CLUSTER="elasticsearch" > export HAWKULAR_APM_ELASTICSEARCH_HOSTS="localhost:9200" > > > unfortunately, this throws an error starting the APM > > *15:54:37,520 SEVERE > [org.hawkular.apm.server.elasticsearch.ElasticsearchBootstrap] > (ServerService Thread Pool -- 91) Failed to initialise Elasticsearch: > org.elasticsearch.client.transport.NoNodeAvailableException: None of the > configured nodes are available: []* > > > *16:25:16,525 INFO [org.elasticsearch.client.transport] > (elasticsearch[Jaren][generic][T#2]) [Jaren] failed to get node info for > [#transport#-1][cllnxHawkular][inet[localhost/127.0.0.1:9300 > ]], disconnecting...: > org.elasticsearch.transport.NodeDisconnectedException: > [][inet[localhost/127.0.0.1 > :9300]][cluster:monitor/nodes/info] disconnected* > > > > is there a configuration for the elastic search ? > does the external elasticsearch able to make the data persistent ? > > Any comment/help is very appreciated! > > Thanks! > > > -- > > JERCZEY GODOY > > MIDDLEWARE CONSULTANT RHCJA > > Red Hat Chile > > Avenida Apoquindo 2827, Piso 7. Santiago, Chile. > > JGodoy at RedHat.com M: 975791358 IM: @jerczey > > > TRIED. TESTED. TRUSTED. > -- JERCZEY GODOY MIDDLEWARE CONSULTANT RHCJA Red Hat Chile Avenida Apoquindo 2827, Piso 7. Santiago, Chile. JGodoy at RedHat.com M: 975791358 IM: @jerczey TRIED. TESTED. TRUSTED. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171031/c83df7d2/attachment.html From lponce at redhat.com Tue Oct 31 14:35:57 2017 From: lponce at redhat.com (Lucas Ponce) Date: Tue, 31 Oct 2017 19:35:57 +0100 Subject: [Hawkular-dev] possible bug in inventory server In-Reply-To: <2081173691.34285872.1509325434574.JavaMail.zimbra@redhat.com> References: <131097386.34268802.1509322878797.JavaMail.zimbra@redhat.com> <2081173691.34285872.1509325434574.JavaMail.zimbra@redhat.com> Message-ID: > > > Who wants to investigate the inventory service to see if I'm right that > there is a bug here? If there is no bug in inventory, the only other option > is it's a bug in the itest code, but I checked and everything looks good to > me there. I can't see a problem in the itest code. And the fact this is > intermittent (passes sometimes, fails sometimes) tells me there is > something sinister going on in the inventory server (i.e. if it is a > problem in the test code, you would think it would always fail). > After a investigation, I don't think there is a problem in the Inventory. In a preliminar status, that was the assumption, and yes, the inventory has a flag that potentially could add an entry and theorically could make that an entry was not indexed if there was a query fast enough after the insertion. But after that PR in commons, the problem still exists, so I ran several itests of commons + agent and this race happens in a ratio of 10%, it took time to test, as itest are time consuming. Basically what happens according the logs in the failed test is the following: 1) The testXaDs datasource is added in a previous test. 2) Agent thread [Hawkular-Agent-Full-Discovery-Scan-Local DMR-1] starts a discovery in its scheduling period. 3) Agent thread [OkHttp http://127.0.0.1:8080/...] process a remove of the testXaDs and succesfully send to the inventory the delete command. 4) Agent thread [Hawkular-Agent-Full-Discovery-Scan-Local DMR-1] might still see the testXaDs resource and it is added into the inventory. 5) Test expects there is no testXaDs resource in inventory, but there is one, as there is a race condition between both threads, for some reason, when the datasource is deleted, it is not updated in the info used by the discovery task. This doesn't happen always, as it is a random scenario due some moving parts between the autodiscovery threads, and the architecture of the itest. I was analyzing why when the testXaDs is removed is still visibile by the autodiscovery thread. Tomorrow I am off and I can't work on this until thursday, so feel free if you want to continue from here. Lucas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171031/d67d8cae/attachment-0001.html From lponce at redhat.com Tue Oct 31 14:36:42 2017 From: lponce at redhat.com (Lucas Ponce) Date: Tue, 31 Oct 2017 19:36:42 +0100 Subject: [Hawkular-dev] possible bug in inventory server In-Reply-To: References: <131097386.34268802.1509322878797.JavaMail.zimbra@redhat.com> <2081173691.34285872.1509325434574.JavaMail.zimbra@redhat.com> Message-ID: On Tue, Oct 31, 2017 at 7:35 PM, Lucas Ponce wrote: > >> Who wants to investigate the inventory service to see if I'm right that >> there is a bug here? If there is no bug in inventory, the only other option >> is it's a bug in the itest code, but I checked and everything looks good to >> me there. I can't see a problem in the itest code. And the fact this is >> intermittent (passes sometimes, fails sometimes) tells me there is >> something sinister going on in the inventory server (i.e. if it is a >> problem in the test code, you would think it would always fail). >> > > After a investigation, I don't think there is a problem in the Inventory. > > In a preliminar status, that was the assumption, and yes, the inventory > has a flag that potentially could add an entry and theorically could make > that an entry was not indexed if there was a query fast enough after the > insertion. > > But after that PR in commons, the problem still exists, so I ran several > itests of commons + agent and this race happens in a ratio of 10%, it took > time to test, as itest are time consuming. > > Basically what happens according the logs in the failed test is the > following: > > 1) The testXaDs datasource is added in a previous test. > 2) Agent thread [Hawkular-Agent-Full-Discovery-Scan-Local DMR-1] starts a > discovery in its scheduling period. > 3) Agent thread [OkHttp http://127.0.0.1:8080/...] process a remove of > the testXaDs and succesfully send to the inventory the delete command. > 4) Agent thread [Hawkular-Agent-Full-Discovery-Scan-Local DMR-1] might > still see the testXaDs resource and it is added into the inventory. > 5) Test expects there is no testXaDs resource in inventory, but there is > one, as there is a race condition between both threads, for some reason, > when the datasource is deleted, it is not updated in the info used by the > discovery task. > > This doesn't happen always, as it is a random scenario due some moving > parts between the autodiscovery threads, and the architecture of the itest. > > I was analyzing why when the testXaDs is removed is still visibile by the > autodiscovery thread. > > Tomorrow I am off and I can't work on this until thursday, so feel free if > you want to continue from here. > Forgot to say, that JIRA for this is https://issues.jboss.org/browse/HAWKULAR-1313 > > Lucas > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20171031/df93dc33/attachment.html From mazz at redhat.com Tue Oct 31 21:28:03 2017 From: mazz at redhat.com (John Mazzitelli) Date: Tue, 31 Oct 2017 21:28:03 -0400 (EDT) Subject: [Hawkular-dev] possible bug in inventory server In-Reply-To: References: <131097386.34268802.1509322878797.JavaMail.zimbra@redhat.com> <2081173691.34285872.1509325434574.JavaMail.zimbra@redhat.com> Message-ID: <198756795.35004738.1509499683213.JavaMail.zimbra@redhat.com> Crossing fingers - I think this fixes the problem: https://github.com/hawkular/hawkular-agent/pull/400 ----- Original Message ----- > On Tue, Oct 31, 2017 at 7:35 PM, Lucas Ponce wrote: > > > > >> Who wants to investigate the inventory service to see if I'm right that > >> there is a bug here? If there is no bug in inventory, the only other > >> option > >> is it's a bug in the itest code, but I checked and everything looks good > >> to > >> me there. I can't see a problem in the itest code. And the fact this is > >> intermittent (passes sometimes, fails sometimes) tells me there is > >> something sinister going on in the inventory server (i.e. if it is a > >> problem in the test code, you would think it would always fail). > >> > > > > After a investigation, I don't think there is a problem in the Inventory. > > > > In a preliminar status, that was the assumption, and yes, the inventory > > has a flag that potentially could add an entry and theorically could make > > that an entry was not indexed if there was a query fast enough after the > > insertion. > > > > But after that PR in commons, the problem still exists, so I ran several > > itests of commons + agent and this race happens in a ratio of 10%, it took > > time to test, as itest are time consuming. > > > > Basically what happens according the logs in the failed test is the > > following: > > > > 1) The testXaDs datasource is added in a previous test. > > 2) Agent thread [Hawkular-Agent-Full-Discovery-Scan-Local DMR-1] starts a > > discovery in its scheduling period. > > 3) Agent thread [OkHttp http://127.0.0.1:8080/...] process a remove of > > the testXaDs and succesfully send to the inventory the delete command. > > 4) Agent thread [Hawkular-Agent-Full-Discovery-Scan-Local DMR-1] might > > still see the testXaDs resource and it is added into the inventory. > > 5) Test expects there is no testXaDs resource in inventory, but there is > > one, as there is a race condition between both threads, for some reason, > > when the datasource is deleted, it is not updated in the info used by the > > discovery task. > > > > This doesn't happen always, as it is a random scenario due some moving > > parts between the autodiscovery threads, and the architecture of the itest. > > > > I was analyzing why when the testXaDs is removed is still visibile by the > > autodiscovery thread. > > > > Tomorrow I am off and I can't work on this until thursday, so feel free if > > you want to continue from here. > > > > Forgot to say, that JIRA for this is > > https://issues.jboss.org/browse/HAWKULAR-1313 > > > > > > > Lucas > > > > >