From ppalaga at redhat.com  Fri Oct  2 06:46:14 2015
From: ppalaga at redhat.com (Peter Palaga)
Date: Fri, 2 Oct 2015 12:46:14 +0200
Subject: [Hawkular-dev] Travis cache pruning
Message-ID: <560E6076.9090509@redhat.com>

Hi *,

because we had no cache pruning in place, the cached ~/.m2/repository in 
hk main became too bing. As a consequence of that, when Travis attempted 
to zip the cached folder, the cache archive made the disk full and not 
only that the cache could not be uploaded outside of the transient 
docker container, also all subsequent tasks (deployment of SNAPSHOTs) 
failed.

I could not find a working pruning script quickly enough. To solve the 
problem temporarily at least, I deleted the cache manually under 
https://travis-ci.org/hawkular/hawkular/caches

Best,

Peter

From gbrown at redhat.com  Fri Oct  2 11:38:04 2015
From: gbrown at redhat.com (Gary Brown)
Date: Fri, 2 Oct 2015 11:38:04 -0400 (EDT)
Subject: [Hawkular-dev] Javascript library for displaying a graph of
	nodes/links
In-Reply-To: <1383554301.30509619.1443799634680.JavaMail.zimbra@redhat.com>
Message-ID: <1356559437.30516349.1443800284725.JavaMail.zimbra@redhat.com>

Hi UI devs

I'm looking for guidance on the best JS lib for displaying graphs (i.e. nodes/links) to represent a business process/transaction?

Would need to be able to:

- customise the nodes to represent various types - consumers, producers, components, databases, etc
- annotate nodes/links with information
- capture/act upon actions/events based on node/link selection, offer popup menus, etc.
- colour code nodes/links to highlight different areas of interest
- potentially control link thickness to reflect flows with greater volume of traffic
- collapse/expand certain paths
- ability to scroll around large diagram
- apache licensed

Hoping that we already have a good lib selected for the project to standardise on :)

Regards
Gary

From hrupp at redhat.com  Sat Oct  3 03:41:26 2015
From: hrupp at redhat.com (Heiko W.Rupp)
Date: Sat, 03 Oct 2015 09:41:26 +0200
Subject: [Hawkular-dev] GitHub discount on yubikey
Message-ID: <EEF1E357-A002-414E-BEFE-F0807C1AC774@redhat.com>

Hey,

if you are using 2fa for GitHub (and you should), then this offer may be 
interesting:
https://www.yubico.com/github-special-offer/github-yubikey-special-offer/

  Heiko

From theute at redhat.com  Mon Oct  5 04:50:58 2015
From: theute at redhat.com (Thomas Heute)
Date: Mon, 5 Oct 2015 10:50:58 +0200
Subject: [Hawkular-dev] Javascript library for displaying a graph of
	nodes/links
In-Reply-To: <1356559437.30516349.1443800284725.JavaMail.zimbra@redhat.com>
References: <1383554301.30509619.1443799634680.JavaMail.zimbra@redhat.com>
	<1356559437.30516349.1443800284725.JavaMail.zimbra@redhat.com>
Message-ID: <CA+aN=MpH+jnt42mQMpMC1G5DgwKEkJODTB5yArYU7Bye-wfGVg@mail.gmail.com>

I would like us to check https://github.com/kubernetes-ui/topology-graph
and reuse as much as it makes sense for the inventory work.

In the end it's using the d3 library like the graphs we draw for metrics,
so it would definitely makes sense to see if topology-graph/d3 fit.



On Fri, Oct 2, 2015 at 5:38 PM, Gary Brown <gbrown at redhat.com> wrote:

> Hi UI devs
>
> I'm looking for guidance on the best JS lib for displaying graphs (i.e.
> nodes/links) to represent a business process/transaction?
>
> Would need to be able to:
>
> - customise the nodes to represent various types - consumers, producers,
> components, databases, etc
> - annotate nodes/links with information
> - capture/act upon actions/events based on node/link selection, offer
> popup menus, etc.
> - colour code nodes/links to highlight different areas of interest
> - potentially control link thickness to reflect flows with greater volume
> of traffic
> - collapse/expand certain paths
> - ability to scroll around large diagram
> - apache licensed
>
> Hoping that we already have a good lib selected for the project to
> standardise on :)
>
> Regards
> Gary
> _______________________________________________
> 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/20151005/ed10c4df/attachment-0001.html 

From gbrown at redhat.com  Mon Oct  5 05:05:41 2015
From: gbrown at redhat.com (Gary Brown)
Date: Mon, 5 Oct 2015 05:05:41 -0400 (EDT)
Subject: [Hawkular-dev] Javascript library for displaying a graph
	of	nodes/links
In-Reply-To: <CA+aN=MpH+jnt42mQMpMC1G5DgwKEkJODTB5yArYU7Bye-wfGVg@mail.gmail.com>
References: <1383554301.30509619.1443799634680.JavaMail.zimbra@redhat.com>
	<1356559437.30516349.1443800284725.JavaMail.zimbra@redhat.com>
	<CA+aN=MpH+jnt42mQMpMC1G5DgwKEkJODTB5yArYU7Bye-wfGVg@mail.gmail.com>
Message-ID: <711552941.31191976.1444035941541.JavaMail.zimbra@redhat.com>

Hi Thomas

Not sure the force directed layout would look right for the business transaction, but may be useful if mapping activity to different regions.

Will look more into d3, to see if it has more appropriate layouts, or if there are other libs built upon it.

Regards
Gary

----- Original Message -----
> I would like us to check https://github.com/kubernetes-ui/topology-graph and
> reuse as much as it makes sense for the inventory work.
> 
> In the end it's using the d3 library like the graphs we draw for metrics, so
> it would definitely makes sense to see if topology-graph/d3 fit.
> 
> 
> 
> On Fri, Oct 2, 2015 at 5:38 PM, Gary Brown < gbrown at redhat.com > wrote:
> 
> 
> Hi UI devs
> 
> I'm looking for guidance on the best JS lib for displaying graphs (i.e.
> nodes/links) to represent a business process/transaction?
> 
> Would need to be able to:
> 
> - customise the nodes to represent various types - consumers, producers,
> components, databases, etc
> - annotate nodes/links with information
> - capture/act upon actions/events based on node/link selection, offer popup
> menus, etc.
> - colour code nodes/links to highlight different areas of interest
> - potentially control link thickness to reflect flows with greater volume of
> traffic
> - collapse/expand certain paths
> - ability to scroll around large diagram
> - apache licensed
> 
> Hoping that we already have a good lib selected for the project to
> standardise on :)
> 
> Regards
> Gary
> _______________________________________________
> 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
> 

From hrupp at redhat.com  Mon Oct  5 09:39:26 2015
From: hrupp at redhat.com (Heiko W.Rupp)
Date: Mon, 05 Oct 2015 15:39:26 +0200
Subject: [Hawkular-dev] Resourcetype again
In-Reply-To: <ED1210CA-FC18-4F50-A2C0-B382F42CA3A4@redhat.com>
References: <6859E673-FB75-4957-BE7F-6966ED5203DA@redhat.com>
	<12258003.x1941inYKH@localhost.localdomain>
	<ED1210CA-FC18-4F50-A2C0-B382F42CA3A4@redhat.com>
Message-ID: <3D10C885-C258-4080-B611-3A7C7C5FAB5F@redhat.com>

Hey,

I want to pick up this discussion again. Especially as we had a point in 
time some days ago, where the agent code was supporting the "JDR" 
operation, but only the Hawkular-server-internal one had it in its 
meta-data, while a standalone one was missing it, which was 
inconsistent.

I have attached a diagram, that I labeled "Fallback"-Graph. Basically a 
type on the top, if it does not exist yet in inventory, the code should 
be fall back to the definition below.
E.g. if a WildFly10 server definition does not yet exist, the one for 
WF9 should be taken.

There are tricky places though:
- Product 2.1 may run on top of a Product 1, but also get some 
additional capabilities from Infinispan 8
- Product 2 may be a Hawkular Server, but where some experimental 
features are disabled. It will also run on top of Product 1, while the 
Hawkular Server runs on top of WF9
- Product 1 may have a reduced feature set over WF 10



-------------- next part --------------
A non-text attachment was scrubbed...
Name: type-fallback.png
Type: image/png
Size: 52226 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151005/c6d53686/attachment-0001.png 

From mazz at redhat.com  Mon Oct  5 11:01:09 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Mon, 5 Oct 2015 11:01:09 -0400 (EDT)
Subject: [Hawkular-dev] platform resources/metrics
In-Reply-To: <1508877527.24891559.1444055685558.JavaMail.zimbra@redhat.com>
Message-ID: <966091970.24903792.1444057269226.JavaMail.zimbra@redhat.com>

After a talk with John D. last week, he mentioned we really need some basic platform metrics collected by our wildfly agent. While it is true the agent can collect "some" platform metrics via WildFly like system load average (/core-service=platform-mbean/type=operating-system/:read-attribute(name=system-load-average)) its very limited (in fact, system load average is the only one I found).

So I put together a new pull request to help: https://github.com/hawkular/hawkular-agent/pull/70

This utilizes a third party library Heiko pointed out to me - Oshi (https://github.com/dblock/oshi) - which just does the basics but it has what we want, I believe. It is JNA-based and doesn't require JNI native libraries to be shipped with the product like sigar does. It supports Linux, Windows, and MacOS. It collects basic metrics for four simple resource types - Memory, File Stores (i.e. disks/partitions), Processors, and Power Sources (i.e. batteries).

I have it discovering/inventories those four basic types of resources (along with the parent "OS" resource) and collecting the metrics for them.

The metrics collected are:

A. Memory:
 1. Memory Available
 2. Memory Total

B. File Stores:
 1. Total Disk Space
 2. Available Disk Space

C. Processors
 1. CPU Usage (this is CPU load between 0% and 100%)

D. Power Sources
 1. Remaining Capacity (0% to 100% (fully drained vs. fully charged)
 2. Time Remaining (time left before power source is fully drained)

Here's what the inventory looks like (taken from inventory's REST API results):

The top root of the platform resource tree is the "Operating System" resource (Oshi has no metrics per se for the OS resource):

http://127.0.0.1:8080/hawkular/inventory/test/mazztower/resources/

[ {
  "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/r;GNU%2FLinux%20Fedora%2021%20(Twenty%20One)",
  "type" : {
    "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/rt;Operating%20System",
    "properties" : {
      "name" : "Operating System"
    },
    "id" : "Operating System"
  },
  "properties" : {
    "name" : "GNU/Linux Fedora 21 (Twenty One)"
  },
  "id" : "GNU/Linux Fedora 21 (Twenty One)"
}

Its children are the four types of child resources (Memory, File Stores, Processors, PowerSources (of which I have none)):

http://127.0.0.1:8080/hawkular/inventory/test/mazztower/resources/GNU%2FLinux Fedora 21 (Twenty One)/children

[ {
  "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/r;GNU%2FLinux%20Fedora%2021%20(Twenty%20One)/r;File%20Store%20%5B%2F%5D",
  "type" : {
    "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/rt;File%20Store",
    "properties" : {
      "name" : "File Store"
    },
    "id" : "File Store"
  },
  "properties" : {
    "name" : "File Store [/]"
  },
  "id" : "File Store [/]"
}, {
  "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/r;GNU%2FLinux%20Fedora%2021%20(Twenty%20One)/r;File%20Store%20%5Btmpfs%5D",
  "type" : {
    "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/rt;File%20Store",
    "properties" : {
      "name" : "File Store"
    },
    "id" : "File Store"
  },
  "properties" : {
    "name" : "File Store [tmpfs]"
  },
  "id" : "File Store [tmpfs]"
}, {
  "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/r;GNU%2FLinux%20Fedora%2021%20(Twenty%20One)/r;File%20Store%20%5Bmqueue%5D",
  "type" : {
    "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/rt;File%20Store",
    "properties" : {
      "name" : "File Store"
    },
    "id" : "File Store"
  },
  "properties" : {
    "name" : "File Store [mqueue]"
  },
  "id" : "File Store [mqueue]"
}, {
  "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/r;GNU%2FLinux%20Fedora%2021%20(Twenty%20One)/r;File%20Store%20%5Bhugetlbfs%5D",
  "type" : {
    "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/rt;File%20Store",
    "properties" : {
      "name" : "File Store"
    },
    "id" : "File Store"
  },
  "properties" : {
    "name" : "File Store [hugetlbfs]"
  },
  "id" : "File Store [hugetlbfs]"
}, {
  "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/r;GNU%2FLinux%20Fedora%2021%20(Twenty%20One)/r;File%20Store%20%5Bsunrpc%5D",
  "type" : {
    "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/rt;File%20Store",
    "properties" : {
      "name" : "File Store"
    },
    "id" : "File Store"
  },
  "properties" : {
    "name" : "File Store [sunrpc]"
  },
  "id" : "File Store [sunrpc]"
}, {
  "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/r;GNU%2FLinux%20Fedora%2021%20(Twenty%20One)/r;File%20Store%20%5B%2Fdev%2Fsda1%5D",
  "type" : {
    "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/rt;File%20Store",
    "properties" : {
      "name" : "File Store"
    },
    "id" : "File Store"
  },
  "properties" : {
    "name" : "File Store [/dev/sda1]"
  },
  "id" : "File Store [/dev/sda1]"
}, {
  "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/r;GNU%2FLinux%20Fedora%2021%20(Twenty%20One)/r;File%20Store%20%5B%2Fdev%2Fmapper%2Fvg_mazztower-lv_home2%5D",
  "type" : {
    "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/rt;File%20Store",
    "properties" : {
      "name" : "File Store"
    },
    "id" : "File Store"
  },
  "properties" : {
    "name" : "File Store [/dev/mapper/vg_mazztower-lv_home2]"
  },
  "id" : "File Store [/dev/mapper/vg_mazztower-lv_home2]"
}, {
  "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/r;GNU%2FLinux%20Fedora%2021%20(Twenty%20One)/r;File%20Store%20%5B%2Fdev%2Fmapper%2Fvg_mazztower-lv_home%5D",
  "type" : {
    "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/rt;File%20Store",
    "properties" : {
      "name" : "File Store"
    },
    "id" : "File Store"
  },
  "properties" : {
    "name" : "File Store [/dev/mapper/vg_mazztower-lv_home]"
  },
  "id" : "File Store [/dev/mapper/vg_mazztower-lv_home]"
}, {
  "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/r;GNU%2FLinux%20Fedora%2021%20(Twenty%20One)/r;File%20Store%20%5B%2Fdev%2Fmapper%2Fvg_mazztower-lv_root%5D",
  "type" : {
    "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/rt;File%20Store",
    "properties" : {
      "name" : "File Store"
    },
    "id" : "File Store"
  },
  "properties" : {
    "name" : "File Store [/dev/mapper/vg_mazztower-lv_root]"
  },
  "id" : "File Store [/dev/mapper/vg_mazztower-lv_root]"
}, {
  "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/r;GNU%2FLinux%20Fedora%2021%20(Twenty%20One)/r;Processor%20%5B0%5D",
  "type" : {
    "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/rt;Processor",
    "properties" : {
      "name" : "Processor"
    },
    "id" : "Processor"
  },
  "properties" : {
    "name" : "Processor [0]"
  },
  "id" : "Processor [0]"
}, {
  "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/r;GNU%2FLinux%20Fedora%2021%20(Twenty%20One)/r;Processor%20%5B1%5D",
  "type" : {
    "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/rt;Processor",
    "properties" : {
      "name" : "Processor"
    },
    "id" : "Processor"
  },
  "properties" : {
    "name" : "Processor [1]"
  },
  "id" : "Processor [1]"
}, {
  "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/r;GNU%2FLinux%20Fedora%2021%20(Twenty%20One)/r;Processor%20%5B2%5D",
  "type" : {
    "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/rt;Processor",
    "properties" : {
      "name" : "Processor"
    },
    "id" : "Processor"
  },
  "properties" : {
    "name" : "Processor [2]"
  },
  "id" : "Processor [2]"
}, {
  "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/r;GNU%2FLinux%20Fedora%2021%20(Twenty%20One)/r;Processor%20%5B3%5D",
  "type" : {
    "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/rt;Processor",
    "properties" : {
      "name" : "Processor"
    },
    "id" : "Processor"
  },
  "properties" : {
    "name" : "Processor [3]"
  },
  "id" : "Processor [3]"
}, {
  "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/r;GNU%2FLinux%20Fedora%2021%20(Twenty%20One)/r;Memory",
  "type" : {
    "path" : "/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;mazztower/rt;Memory",
    "properties" : {
      "name" : "Memory"
    },
    "id" : "Memory"
  },
  "properties" : {
    "name" : "Memory"
  },
  "id" : "Memory"
} ]

From hrupp at redhat.com  Mon Oct  5 14:27:34 2015
From: hrupp at redhat.com (hrupp at redhat.com)
Date: Mon, 05 Oct 2015 18:27:34 +0000
Subject: [Hawkular-dev] Termin gestrichen: Hawkular-Team Update - Di 6. Okt.
 2015 3:30PM - 4PM (hrupp@redhat.com)
Message-ID: <047d7bb04e06cb6d7705215faa5d@google.com>

Dieser Termin wurde gestrichen und aus Ihrem Kalender entfernt.

Titel: Hawkular-Team Update
This is a all-Hawkular team meeting to give updates where we are and so on.

This is *open to the public*.

Location:
on bluejeans:  https://redhat.bluejeans.com/hrupp/

or alternatively teleconference Reservationless+ , passcode 204 2160 481

You can find Dial-In telephone numbers here:  
https://www.intercallonline.com/listNumbersByCode.action?confCode=2042160481

RedHat internal short dial numbers are 16666 and 15555 (and probably  
others, depends on your location)
Wann: Di 6. Okt. 2015 3:30PM - 4PM Berlin
Wo: pc 204 2160 481
Kalender: hrupp at redhat.com
Wer
     * Heiko Rupp - Organisator
     * theute at redhat.com
     * miburman at redhat.com
     * hawkular-dev at lists.jboss.org
     * snegrea at redhat.com
     * Jay Shaughnessy
     * jcosta at redhat.com
     * Lucas Ponce
     * Mike Thompson
     * Thomas Segismont
     * gbrown at redhat.com
     * John Sanda
     * Gabriel Cardoso
     * Simeon Pinder
     * Jiri Kremser
     * amendonc at redhat.com
     * lkrejci at redhat.com
     * John Mazzitelli
     * Peter Palaga
     * Viliam Rockai


Einladung von Google Kalender: https://www.google.com/calendar/

Sie erhalten diese E-Mail unter hawkular-dev at lists.jboss.org, da Sie ein  
Gast bei diesem Termin sind.

Lehnen Sie diesen Termin ab, um keine weiteren Informationen zu diesem  
Termin zu erhalten. Sie k?nnen auch unter https://www.google.com/calendar/  
ein Google-Konto erstellen und Ihre Benachrichtigungseinstellungen f?r  
Ihren gesamten Kalender steuern.

Wenn Sie diese Einladung weiterleiten, kann jeder Empf?nger Ihre Antwort  
auf die Einladung ?ndern. Weitere Informationen finden Sie unter  
https://support.google.com/calendar/answer/37135#forwarding
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151005/69419216/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 4132 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151005/69419216/attachment-0002.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: application/ics
Size: 4219 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151005/69419216/attachment-0003.bin 

From mazz at redhat.com  Mon Oct  5 20:30:21 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Mon, 5 Oct 2015 20:30:21 -0400 (EDT)
Subject: [Hawkular-dev] Resourcetype again
In-Reply-To: <3D10C885-C258-4080-B611-3A7C7C5FAB5F@redhat.com>
References: <6859E673-FB75-4957-BE7F-6966ED5203DA@redhat.com>
	<12258003.x1941inYKH@localhost.localdomain>
	<ED1210CA-FC18-4F50-A2C0-B382F42CA3A4@redhat.com>
	<3D10C885-C258-4080-B611-3A7C7C5FAB5F@redhat.com>
Message-ID: <476074189.25063107.1444091421191.JavaMail.zimbra@redhat.com>

And a major question still to be addressed is how and when does the agent get the type metadata? Right now, it "owns" the metadata in standalone.xml. But it would be nice for metadata to be downloaded from the hawkular server - if there is no metadata available, then the agent can fallback and use its standalone.xml definitions.

I have not thought long about the metadata storage in hawkular and the interface the agent should use to get it. We need to figure that out.

----- Original Message -----
> Hey,
> 
> I want to pick up this discussion again. Especially as we had a point in
> time some days ago, where the agent code was supporting the "JDR"
> operation, but only the Hawkular-server-internal one had it in its
> meta-data, while a standalone one was missing it, which was
> inconsistent.
> 
> I have attached a diagram, that I labeled "Fallback"-Graph. Basically a
> type on the top, if it does not exist yet in inventory, the code should
> be fall back to the definition below.
> E.g. if a WildFly10 server definition does not yet exist, the one for
> WF9 should be taken.
> 
> There are tricky places though:
> - Product 2.1 may run on top of a Product 1, but also get some
> additional capabilities from Infinispan 8
> - Product 2 may be a Hawkular Server, but where some experimental
> features are disabled. It will also run on top of Product 1, while the
> Hawkular Server runs on top of WF9
> - Product 1 may have a reduced feature set over WF 10
> 
> 
> 
> 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
> 

From hrupp at redhat.com  Tue Oct  6 02:56:29 2015
From: hrupp at redhat.com (Heiko W.Rupp)
Date: Tue, 06 Oct 2015 08:56:29 +0200
Subject: [Hawkular-dev] Resourcetype again
In-Reply-To: <476074189.25063107.1444091421191.JavaMail.zimbra@redhat.com>
References: <6859E673-FB75-4957-BE7F-6966ED5203DA@redhat.com>
	<12258003.x1941inYKH@localhost.localdomain>
	<ED1210CA-FC18-4F50-A2C0-B382F42CA3A4@redhat.com>
	<3D10C885-C258-4080-B611-3A7C7C5FAB5F@redhat.com>
	<476074189.25063107.1444091421191.JavaMail.zimbra@redhat.com>
Message-ID: <5022218C-ED12-4E25-9FE1-59914755DC61@redhat.com>

On 6 Oct 2015, at 2:30, John Mazzitelli wrote:

> And a major question still to be addressed is how and when does the 
> agent get the type metadata? Right now, it "owns" the metadata in 
> standalone.xml. But it would be nice for metadata to be downloaded 
> from the hawkular
> server - if there is no metadata available, then the

Yes, the agent should download it from the server
for all those types where we have explicit support
in clients like the UI.


> agent can fallback and use its standalone.xml definitions.

What I did not explicitly mention in my previous mail and the graphic is 
that an agent would most probably be able to define their own type 
extensions on top of what is there.

So the base type for e.g. a WildFly 9 would come from us (=defined on 
the Hawkular server, valid for all feeds of that type) and an then a 
user-defined type could be loaded  from the agent (and is then again 
local to that feed).


From tsegismo at redhat.com  Tue Oct  6 09:45:35 2015
From: tsegismo at redhat.com (Thomas Segismont)
Date: Tue, 6 Oct 2015 15:45:35 +0200
Subject: [Hawkular-dev] [Metrics] Better REST API documentation,
	feedback needed
Message-ID: <5613D07F.9080604@redhat.com>

Hi,

Currently our REST API documentation is generated solely from Swagger 
annotations.

This is a good starting point, but I believe it's not enough nor easy 
for new users.

I filed this JIRA:

HWKMETRICS-297 Incorporate static blocks into the REST API documentation
https://issues.jboss.org/browse/HWKMETRICS-297

And started the PR:
https://github.com/hawkular/hawkular-metrics/pull/389

Here's what I have in mind:
- provide general information which does not fit in annotations into a 
base Asciidoc file
- merge the static file with the Swagger generated one

Many services organize their REST API documentation similarly (I liked 
GitHub and PagerDuty examples in particular).

I need your opinion on the static file plan. I started with this:
https://raw.githubusercontent.com/tsegismont/hawkular-metrics/jira/HWKMETRICS-297/api/metrics-api-jaxrs/src/main/rest-doc/base.adoc

Can you think of anything missing? Or do you have any comments?

Of course the result doc is not perfect, but it's a step forward.

Thanks,
Thomas


From mazz at redhat.com  Tue Oct  6 21:40:55 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Tue, 6 Oct 2015 21:40:55 -0400 (EDT)
Subject: [Hawkular-dev] wildfly agent news
In-Reply-To: <801283792.25769129.1444181462789.JavaMail.zimbra@redhat.com>
Message-ID: <1183144415.25770282.1444182055271.JavaMail.zimbra@redhat.com>

Just wanted to give a brief summary of some changes that went into the agent recently.

1) We now produce our own WildFly feature pack and can run in Swarm

Thanks to Bob McWhirter, the agent build now produces a feature pack that can be used by WildFly for installing the agent so it comes with Wildfly out of box. I don't know much more than that - but it sounds cool :)

Bob also got the agent running as a swarm app, so by running an uber-jar (via a command like "java -jar ...") you can run the agent. See https://wildfly-swarm.gitbooks.io/wildfly-swarm-users-guide/content/hawkular.html

2) We now monitor native platform resources.

I think I already announced this but I'll repeat. The agent can now monitor basic native platform resources like CPUs, system memory, and file systems - supported on Linux, Windows, and MacOS. When you run the wildfly agent, by default you will not only get WildFly servers in inventory, but you'll also get platform resources including a root "Operating System" resource along with its children that include Processor resources, File Store resources, and Memory resources. Collected are metrics such as CPU usage, total and free system memory, total and free disk space.

3) We now utilize the inventory batch API

The agent uses the new inventory batch API to store a resource, its type, its resource config, and its relationships to its parent and metrics in one REST API call. This speeds things up somewhat, but hopefully in the future we can optimize this even further to bulk insert multiple resources at a time. As part of this work, you will now see inventory storage diagnostic data logged in the server log. This can help us determine the performance of our rest calls into inventory. For example, in the diagnostic log message, you'll now see something like this: "feedid.diagnostics.inventory.storage-request-timer: type=[timer], count=[115], min=[283.090987], max=[6260.832863], mean=[3732.066908]" meaning we made 115 inventory requests (which means one inventory batch REST call ) that took an average of 3.7s.

All of this is in master and will go out in the next agent release (I actually think the platform resource stuff is already released and in kettle).

From theute at redhat.com  Wed Oct  7 04:48:57 2015
From: theute at redhat.com (Thomas Heute)
Date: Wed, 7 Oct 2015 10:48:57 +0200
Subject: [Hawkular-dev] [Metrics] Better REST API documentation,
	feedback needed
In-Reply-To: <5613D07F.9080604@redhat.com>
References: <5613D07F.9080604@redhat.com>
Message-ID: <CA+aN=Mqs6J-td1QAieyq1ghXkYUgr_Cbxn-eBNiwds+sEGqknw@mail.gmail.com>

Agreed on general information !

I would like us to break some barriers between components.
There are likely notions that should to be shared and shouldn't be just
copied over and over. (Obvious ones are Tenant and Timestamps)

So I would like to see the APIs in a single page (like Pager Duty) with
general information followed by Metrics, Alerts,... sections.



On Tue, Oct 6, 2015 at 3:45 PM, Thomas Segismont <tsegismo at redhat.com>
wrote:

> Hi,
>
> Currently our REST API documentation is generated solely from Swagger
> annotations.
>
> This is a good starting point, but I believe it's not enough nor easy
> for new users.
>
> I filed this JIRA:
>
> HWKMETRICS-297 Incorporate static blocks into the REST API documentation
> https://issues.jboss.org/browse/HWKMETRICS-297
>
> And started the PR:
> https://github.com/hawkular/hawkular-metrics/pull/389
>
> Here's what I have in mind:
> - provide general information which does not fit in annotations into a
> base Asciidoc file
> - merge the static file with the Swagger generated one
>
> Many services organize their REST API documentation similarly (I liked
> GitHub and PagerDuty examples in particular).
>
> I need your opinion on the static file plan. I started with this:
>
> https://raw.githubusercontent.com/tsegismont/hawkular-metrics/jira/HWKMETRICS-297/api/metrics-api-jaxrs/src/main/rest-doc/base.adoc
>
> Can you think of anything missing? Or do you have any comments?
>
> Of course the result doc is not perfect, but it's a step forward.
>
> Thanks,
> Thomas
>
> _______________________________________________
> 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/20151007/8870a132/attachment.html 

From tsegismo at redhat.com  Wed Oct  7 08:45:28 2015
From: tsegismo at redhat.com (Thomas Segismont)
Date: Wed, 7 Oct 2015 14:45:28 +0200
Subject: [Hawkular-dev] [Metrics] Better REST API documentation,
 feedback needed
In-Reply-To: <CA+aN=Mqs6J-td1QAieyq1ghXkYUgr_Cbxn-eBNiwds+sEGqknw@mail.gmail.com>
References: <5613D07F.9080604@redhat.com>
	<CA+aN=Mqs6J-td1QAieyq1ghXkYUgr_Cbxn-eBNiwds+sEGqknw@mail.gmail.com>
Message-ID: <561513E8.9030304@redhat.com>

I've updated the base documentation:

https://raw.githubusercontent.com/tsegismont/hawkular-metrics/jira/HWKMETRICS-297/api/metrics-api-jaxrs/src/main/rest-doc/base.adoc

Attached is a sample of the merge result (base documentation + swagger).

If you've ever felt short of information when using the Metrics REST 
API, this is an opportunity to chime in for improvements.

Le 07/10/2015 10:48, Thomas Heute a ?crit :
> Agreed on general information !
>
> I would like us to break some barriers between components.
> There are likely notions that should to be shared and shouldn't be just
> copied over and over. (Obvious ones are Tenant and Timestamps)
>
> So I would like to see the APIs in a single page (like Pager Duty) with
> general information followed by Metrics, Alerts,... sections.
>
>
>
> On Tue, Oct 6, 2015 at 3:45 PM, Thomas Segismont <tsegismo at redhat.com
> <mailto:tsegismo at redhat.com>> wrote:
>
>     Hi,
>
>     Currently our REST API documentation is generated solely from Swagger
>     annotations.
>
>     This is a good starting point, but I believe it's not enough nor easy
>     for new users.
>
>     I filed this JIRA:
>
>     HWKMETRICS-297 Incorporate static blocks into the REST API documentation
>     https://issues.jboss.org/browse/HWKMETRICS-297
>
>     And started the PR:
>     https://github.com/hawkular/hawkular-metrics/pull/389
>
>     Here's what I have in mind:
>     - provide general information which does not fit in annotations into a
>     base Asciidoc file
>     - merge the static file with the Swagger generated one
>
>     Many services organize their REST API documentation similarly (I liked
>     GitHub and PagerDuty examples in particular).
>
>     I need your opinion on the static file plan. I started with this:
>     https://raw.githubusercontent.com/tsegismont/hawkular-metrics/jira/HWKMETRICS-297/api/metrics-api-jaxrs/src/main/rest-doc/base.adoc
>
>     Can you think of anything missing? Or do you have any comments?
>
>     Of course the result doc is not perfect, but it's a step forward.
>
>     Thanks,
>     Thomas
>
>     _______________________________________________
>     hawkular-dev mailing list
>     hawkular-dev at lists.jboss.org <mailto: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/20151007/5c81043f/attachment-0001.html 

From tsegismo at redhat.com  Wed Oct  7 08:55:54 2015
From: tsegismo at redhat.com (Thomas Segismont)
Date: Wed, 7 Oct 2015 14:55:54 +0200
Subject: [Hawkular-dev] [Metrics] Better REST API documentation,
 feedback needed
In-Reply-To: <CA+aN=Mqs6J-td1QAieyq1ghXkYUgr_Cbxn-eBNiwds+sEGqknw@mail.gmail.com>
References: <5613D07F.9080604@redhat.com>
	<CA+aN=Mqs6J-td1QAieyq1ghXkYUgr_Cbxn-eBNiwds+sEGqknw@mail.gmail.com>
Message-ID: <5615165A.5080608@redhat.com>

Le 07/10/2015 10:48, Thomas Heute a ?crit :
> I would like us to break some barriers between components.
> There are likely notions that should to be shared and shouldn't be just
> copied over and over. (Obvious ones are Tenant and Timestamps)
>
> So I would like to see the APIs in a single page (like Pager Duty) with
> general information followed by Metrics, Alerts,... sections.

As a first step, we may simply add a document at:
http://www.hawkular.org/docs/rest/api.html

Don't try, it doesn't exist yet ;o)

I'm not aware of rules and practices in other components, but I'd gladly 
start this document if this thread allows to gather them.



From gbrown at redhat.com  Wed Oct  7 08:56:07 2015
From: gbrown at redhat.com (Gary Brown)
Date: Wed, 7 Oct 2015 08:56:07 -0400 (EDT)
Subject: [Hawkular-dev] [Metrics] Better REST API documentation,
 feedback needed
In-Reply-To: <561513E8.9030304@redhat.com>
References: <5613D07F.9080604@redhat.com>
	<CA+aN=Mqs6J-td1QAieyq1ghXkYUgr_Cbxn-eBNiwds+sEGqknw@mail.gmail.com>
	<561513E8.9030304@redhat.com>
Message-ID: <77389317.33318615.1444222567796.JavaMail.zimbra@redhat.com>

Content looks good. Is there going to be an index to help navigation of the document?

Regards
Gary

----- Original Message -----
> I've updated the base documentation:
> 
> https://raw.githubusercontent.com/tsegismont/hawkular-metrics/jira/HWKMETRICS-297/api/metrics-api-jaxrs/src/main/rest-doc/base.adoc
> 
> Attached is a sample of the merge result (base documentation + swagger).
> 
> If you've ever felt short of information when using the Metrics REST
> API, this is an opportunity to chime in for improvements.
> 
> Le 07/10/2015 10:48, Thomas Heute a ?crit :
> > Agreed on general information !
> >
> > I would like us to break some barriers between components.
> > There are likely notions that should to be shared and shouldn't be just
> > copied over and over. (Obvious ones are Tenant and Timestamps)
> >
> > So I would like to see the APIs in a single page (like Pager Duty) with
> > general information followed by Metrics, Alerts,... sections.
> >
> >
> >
> > On Tue, Oct 6, 2015 at 3:45 PM, Thomas Segismont <tsegismo at redhat.com
> > <mailto:tsegismo at redhat.com>> wrote:
> >
> >     Hi,
> >
> >     Currently our REST API documentation is generated solely from Swagger
> >     annotations.
> >
> >     This is a good starting point, but I believe it's not enough nor easy
> >     for new users.
> >
> >     I filed this JIRA:
> >
> >     HWKMETRICS-297 Incorporate static blocks into the REST API
> >     documentation
> >     https://issues.jboss.org/browse/HWKMETRICS-297
> >
> >     And started the PR:
> >     https://github.com/hawkular/hawkular-metrics/pull/389
> >
> >     Here's what I have in mind:
> >     - provide general information which does not fit in annotations into a
> >     base Asciidoc file
> >     - merge the static file with the Swagger generated one
> >
> >     Many services organize their REST API documentation similarly (I liked
> >     GitHub and PagerDuty examples in particular).
> >
> >     I need your opinion on the static file plan. I started with this:
> >     https://raw.githubusercontent.com/tsegismont/hawkular-metrics/jira/HWKMETRICS-297/api/metrics-api-jaxrs/src/main/rest-doc/base.adoc
> >
> >     Can you think of anything missing? Or do you have any comments?
> >
> >     Of course the result doc is not perfect, but it's a step forward.
> >
> >     Thanks,
> >     Thomas
> >
> >     _______________________________________________
> >     hawkular-dev mailing list
> >     hawkular-dev at lists.jboss.org <mailto: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
> 


From tsegismo at redhat.com  Wed Oct  7 08:58:02 2015
From: tsegismo at redhat.com (Thomas Segismont)
Date: Wed, 7 Oct 2015 14:58:02 +0200
Subject: [Hawkular-dev] [Metrics] Better REST API documentation,
 feedback needed
In-Reply-To: <77389317.33318615.1444222567796.JavaMail.zimbra@redhat.com>
References: <5613D07F.9080604@redhat.com>
	<CA+aN=Mqs6J-td1QAieyq1ghXkYUgr_Cbxn-eBNiwds+sEGqknw@mail.gmail.com>
	<561513E8.9030304@redhat.com>
	<77389317.33318615.1444222567796.JavaMail.zimbra@redhat.com>
Message-ID: <561516DA.8060005@redhat.com>

Le 07/10/2015 14:56, Gary Brown a ?crit :
> Content looks good. Is there going to be an index to help navigation of the document?

Thanks! Yes, the index will be generated by jBake the Asciidoc source is 
merged in to the website repo.

From tsegismo at redhat.com  Wed Oct  7 08:58:41 2015
From: tsegismo at redhat.com (Thomas Segismont)
Date: Wed, 7 Oct 2015 14:58:41 +0200
Subject: [Hawkular-dev] [Metrics] Better REST API documentation,
 feedback needed
In-Reply-To: <561516DA.8060005@redhat.com>
References: <5613D07F.9080604@redhat.com>
	<CA+aN=Mqs6J-td1QAieyq1ghXkYUgr_Cbxn-eBNiwds+sEGqknw@mail.gmail.com>
	<561513E8.9030304@redhat.com>
	<77389317.33318615.1444222567796.JavaMail.zimbra@redhat.com>
	<561516DA.8060005@redhat.com>
Message-ID: <56151701.1030002@redhat.com>

Le 07/10/2015 14:58, Thomas Segismont a ?crit :
> Le 07/10/2015 14:56, Gary Brown a ?crit :
>> Content looks good. Is there going to be an index to help navigation of the document?
>
> Thanks! Yes, the index will be generated by jBake the Asciidoc source is
> merged in to the website repo.

by jBake **WHEN** the


From jshaughn at redhat.com  Wed Oct  7 14:59:56 2015
From: jshaughn at redhat.com (Jay Shaughnessy)
Date: Wed, 7 Oct 2015 14:59:56 -0400
Subject: [Hawkular-dev] wildfly agent news
In-Reply-To: <1183144415.25770282.1444182055271.JavaMail.zimbra@redhat.com>
References: <1183144415.25770282.1444182055271.JavaMail.zimbra@redhat.com>
Message-ID: <56156BAC.8060707@redhat.com>



On 10/6/2015 9:40 PM, John Mazzitelli wrote:
> I think I already announced this but I'll repeat. The agent can now monitor basic native platform resources like CPUs, system memory, and file systems - supported on Linux, Windows, and MacOS. When you run the wildfly agent, by default you will not only get WildFly servers in inventory, but you'll also get platform resources including a root "Operating System" resource along with its children that include Processor resources, File Store resources, and Memory resources. Collected are metrics such as CPU usage, total and free system memory, total and free disk space.

So, if you are running multiple WFly instances, each with an agent, are 
we creating the same logical resources repeatedly?



From mazz at redhat.com  Wed Oct  7 18:08:04 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Wed, 7 Oct 2015 18:08:04 -0400 (EDT)
Subject: [Hawkular-dev] wildfly agent news
In-Reply-To: <56156BAC.8060707@redhat.com>
References: <1183144415.25770282.1444182055271.JavaMail.zimbra@redhat.com>
	<56156BAC.8060707@redhat.com>
Message-ID: <1762778963.26432539.1444255684689.JavaMail.zimbra@redhat.com>

If you are running N WildFly instances on the same machine, each installed with the agent, you will get N sets of the same platform resources. They technically wouldn't be the same resources because they would all be under different feeds, but they would essentially be the same resources in a logical sense.

----- Original Message -----
> 
> 
> On 10/6/2015 9:40 PM, John Mazzitelli wrote:
> > I think I already announced this but I'll repeat. The agent can now monitor
> > basic native platform resources like CPUs, system memory, and file systems
> > - supported on Linux, Windows, and MacOS. When you run the wildfly agent,
> > by default you will not only get WildFly servers in inventory, but you'll
> > also get platform resources including a root "Operating System" resource
> > along with its children that include Processor resources, File Store
> > resources, and Memory resources. Collected are metrics such as CPU usage,
> > total and free system memory, total and free disk space.
> 
> So, if you are running multiple WFly instances, each with an agent, are
> we creating the same logical resources repeatedly?
> 
> 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
> 

From snegrea at redhat.com  Thu Oct  8 16:14:51 2015
From: snegrea at redhat.com (Stefan Negrea)
Date: Thu, 8 Oct 2015 16:14:51 -0400 (EDT)
Subject: [Hawkular-dev] Hawkular Metrics - 2K Commits
In-Reply-To: <1545335898.41688918.1444335118221.JavaMail.zimbra@redhat.com>
Message-ID: <1118102308.41691185.1444335291001.JavaMail.zimbra@redhat.com>

Hello Everybody,

Earlier this week we published a blog post about a nice Hawkular Metrics milestone. The project reached last week 2K commits on the master branch. Please take a moment and read the blog entry and join me in congratulating all past and present project contributors.


http://www.hawkular.org/blog/2015/10/05/hawkular-metrics-2k-commits.html


To 4K commits in half the time!


Thank you,
Stefan Negrea

Software Engineer


From theute at redhat.com  Fri Oct  9 04:05:35 2015
From: theute at redhat.com (Thomas Heute)
Date: Fri, 9 Oct 2015 10:05:35 +0200
Subject: [Hawkular-dev] Hawkular Metrics - 2K Commits
In-Reply-To: <1118102308.41691185.1444335291001.JavaMail.zimbra@redhat.com>
References: <1545335898.41688918.1444335118221.JavaMail.zimbra@redhat.com>
	<1118102308.41691185.1444335291001.JavaMail.zimbra@redhat.com>
Message-ID: <CA+aN=MqATsgxuU3EzvqzrB8Cxwy1U9C1jRQENumWdf54EitZsQ@mail.gmail.com>

Nice activity, congrats !

Don't squash them all :-P


On Thu, Oct 8, 2015 at 10:14 PM, Stefan Negrea <snegrea at redhat.com> wrote:

> Hello Everybody,
>
> Earlier this week we published a blog post about a nice Hawkular Metrics
> milestone. The project reached last week 2K commits on the master branch.
> Please take a moment and read the blog entry and join me in congratulating
> all past and present project contributors.
>
>
> http://www.hawkular.org/blog/2015/10/05/hawkular-metrics-2k-commits.html
>
>
> To 4K commits in half the time!
>
>
> Thank you,
> Stefan Negrea
>
> Software Engineer
>
> _______________________________________________
> 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/20151009/49098c8f/attachment.html 

From lkrejci at redhat.com  Fri Oct  9 07:58:18 2015
From: lkrejci at redhat.com (Lukas Krejci)
Date: Fri, 09 Oct 2015 13:58:18 +0200
Subject: [Hawkular-dev] Resourcetype again
In-Reply-To: <5022218C-ED12-4E25-9FE1-59914755DC61@redhat.com>
References: <6859E673-FB75-4957-BE7F-6966ED5203DA@redhat.com>
	<476074189.25063107.1444091421191.JavaMail.zimbra@redhat.com>
	<5022218C-ED12-4E25-9FE1-59914755DC61@redhat.com>
Message-ID: <32099564.56ockzxRnr@localhost.localdomain>

I disagree about the server being the authoritative source of metadata.

After all it is the feed that actually "sees" and can "touch" the resource, 
not the server.

What the server can (and will) do is to provide for quickly checking if 
certain metadata are present in inventory. I preliminarily call it "metadata 
packs" which will be a collection of resource, metric and operation types 
together with a method to compute their collective hash. The feed then will 
check if a pack with a given hash is present in the server and if there is, 
then it's good to go.

If the hash does not match it means that some metadata, that the agent expects 
(and requires) to correctly describe what it sees, needs to be changed on the 
server (i.e. the agent uploads the changes it needs and forms a new pack if it 
wants to).

Now for this to make sense, a metadata pack uploaded by one feed (or uploaded 
by an operator prior to any feed connecting to the server or even pre-
installed with Hawkular) needs to be "globally visible" so that other feeds 
don't have to upload their own version of it with the same hash - i.e. pack 
with the same hash should be defined only once in the server.

Why do it this way?

Wildfly agent speaks DMR and can therefore support new functionality/resource 
types in the wildfly server without any new code needing to be written. I.e. 
the wildfly agent can DEDUCE the metadata directly from what it sees in DMR, 
it doesn't need to be told what to see. If it was told, it would also have to 
reconcile the differences (i.e. an op is defined on hawk server, but the 
underlying wfly doesn't declare it) - i.e. what Heiko is talking about - 
fallbacks, compositions of product features, etc.

IMHO, if the agent stays the source of metadata and has the ability to quickly 
check that all it needs is already "up with the hawk" then that's a simpler 
solution that will be in the end easier on the feeds.

Note that these packs essentially don't need to be user-visible or amendable 
"things" - primarily because it would be generally difficult to call them 
user-friendly names.

For example, if the agent required (Wfly 10 + product A) it can check for the 
presence of the types in 2 ways: 
1) 2 calls to inventory checking if "Wfly 10" pack is present and if  "product 
A" pack is present) or 

2) 1 call to check if "wfly10 + product A" pack is present

If we throw into the mix the "minus 2 components from product A" possibility 
as outlined by Heiko, then it becomes quite complex to call it a name or even 
"explain" to the user, what this is. But it can still be a metadata pack with 
a single hash (the common types would now be members of all 3 packs) and the 
agent can still check for its presence with 1 call.

On Tuesday, October 06, 2015 08:56:29 Heiko W.Rupp wrote:
> On 6 Oct 2015, at 2:30, John Mazzitelli wrote:
> > And a major question still to be addressed is how and when does the
> > agent get the type metadata? Right now, it "owns" the metadata in
> > standalone.xml. But it would be nice for metadata to be downloaded
> > from the hawkular
> > server - if there is no metadata available, then the
> 
> Yes, the agent should download it from the server
> for all those types where we have explicit support
> in clients like the UI.
> 
> > agent can fallback and use its standalone.xml definitions.
> 
> What I did not explicitly mention in my previous mail and the graphic is
> that an agent would most probably be able to define their own type
> extensions on top of what is there.
> 
> So the base type for e.g. a WildFly 9 would come from us (=defined on
> the Hawkular server, valid for all feeds of that type) and an then a
> user-defined type could be loaded  from the agent (and is then again
> local to that feed).
> 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev


From mfoley at redhat.com  Fri Oct  9 08:16:27 2015
From: mfoley at redhat.com (Michael Foley)
Date: Fri, 9 Oct 2015 08:16:27 -0400 (EDT)
Subject: [Hawkular-dev] Preliminary results on Hawkular MS5 from QE
In-Reply-To: <2034028275.68321180.1444392879278.JavaMail.zimbra@redhat.com>
References: <2034028275.68321180.1444392879278.JavaMail.zimbra@redhat.com>
Message-ID: <561345164.68322529.1444392987404.JavaMail.zimbra@redhat.com>

Hi, 


QE is almost done qualifying MS5 ... so I thought I would share information at this intermediary point. The link is to a mojo page which summarizes QE activities and findings. 


https://mojo.redhat.com/docs/DOC-1047356 

The highlights are: 


    * UI Automation. New tests added for every JMAN4 Jira delivered. Regression testing on previously delivered Jiras. All results stored in Polarion. All links to pull requests for the creation and refactoring of UI automation. 
    * REST API automation. New tests added for every JMAN4 Jira delivered. Regression testing on previously delivered Jiras. All results stored in Polarion. All links to pull requests for the creation and refactoring of REST API automation. 
    * Performance CI on Hawk-Metrics. Throughput, response time, and disk usage for every pull request, with a goal to catch performance regressions as they happen. All results stored in Perf Repo. 
    * Manual testcases. New documented testcases for every JMAN4 delivered in MS5. Documented testcase execution with results stored in Polarion. 
    * Continuous Delivery Pipeline. Hawkular is containerized, a smaller suite of REST API tests are run, and if successful then pushed to a public facing endpoint. http://livingontheedge.hawkular.org/ 
    * Jiras logged for every issue found as a result of these activities. 


We are planning on reviewing the testing activities next Thursday October 15th. Please, you are invited to review, listen, ask questions on this testing ... or even influence or contribute to testing on the next sprint. Please feel free to contact me if you have questions, comments, or suggestions regarding this testing. 

Regards, 

Michael Foley 
QE Supervisor, Middleware BU 




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151009/8b443d2c/attachment.html 

From tsegismo at redhat.com  Fri Oct  9 10:58:47 2015
From: tsegismo at redhat.com (Thomas Segismont)
Date: Fri, 9 Oct 2015 16:58:47 +0200
Subject: [Hawkular-dev] HWKMETRICS-83 Create glue code component to
 integrate with hawkular-bus
Message-ID: <5617D627.90200@redhat.com>

Hi everyone,

I sent a pull request to the Metrics repo to implement $subject.
https://github.com/hawkular/hawkular-metrics/pull/393

I won't paste here the whole PR description, but the following might be 
of interest.

There is a new "hawkular-metrics-component" WAR module. It is meant to 
replace "hawkular-metrics-api-jaxrs" module in Hawkular deployments.

This new WAR is a "super"-module: it uses Maven WAR plugin overlay 
mechanism to add extra classes to the standalone metrics web application.

The extra classes allow to subscribe to the 
MetricsService#insertedDataEvents observable and publish messages on the 
bus.

In order to make the migration easy, I have shamelessly copied Alerts' 
AvailDataMessage and MetricDataMessage classes. Theses messages are 
posted on to the "HawkularAvailData" and "HawkularMetricData" topics, 
respectively.

After this PR is merged we only need to change the agent code to remove 
the "double-push" part. And change Hawkular POM to switch to the new 
Metrics component. That's it.

I would like to discuss the JSON payload format later. It might need to 
be changed, but let's flip this coin first.

Thanks,
Thomas

From mazz at redhat.com  Fri Oct  9 11:20:21 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Fri, 9 Oct 2015 11:20:21 -0400 (EDT)
Subject: [Hawkular-dev] HWKMETRICS-83 Create glue code component to
 integrate with hawkular-bus
In-Reply-To: <5617D627.90200@redhat.com>
References: <5617D627.90200@redhat.com>
Message-ID: <1732984829.27884822.1444404021949.JavaMail.zimbra@redhat.com>

I can work on a agent PR to strip that out. I have a bunch of TODO comments around the code that should remind me all I need to take out :)

----- Original Message -----
> Hi everyone,
> 
> I sent a pull request to the Metrics repo to implement $subject.
> https://github.com/hawkular/hawkular-metrics/pull/393
> 
> I won't paste here the whole PR description, but the following might be
> of interest.
> 
> There is a new "hawkular-metrics-component" WAR module. It is meant to
> replace "hawkular-metrics-api-jaxrs" module in Hawkular deployments.
> 
> This new WAR is a "super"-module: it uses Maven WAR plugin overlay
> mechanism to add extra classes to the standalone metrics web application.
> 
> The extra classes allow to subscribe to the
> MetricsService#insertedDataEvents observable and publish messages on the
> bus.
> 
> In order to make the migration easy, I have shamelessly copied Alerts'
> AvailDataMessage and MetricDataMessage classes. Theses messages are
> posted on to the "HawkularAvailData" and "HawkularMetricData" topics,
> respectively.
> 
> After this PR is merged we only need to change the agent code to remove
> the "double-push" part. And change Hawkular POM to switch to the new
> Metrics component. That's it.
> 
> I would like to discuss the JSON payload format later. It might need to
> be changed, but let's flip this coin first.
> 
> Thanks,
> Thomas
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
> 

From vnguyen at redhat.com  Fri Oct  9 13:35:14 2015
From: vnguyen at redhat.com (Viet Nguyen)
Date: Fri, 9 Oct 2015 13:35:14 -0400 (EDT)
Subject: [Hawkular-dev] [Metrics] Better REST API documentation,
 feedback needed
In-Reply-To: <561513E8.9030304@redhat.com>
References: <5613D07F.9080604@redhat.com>
	<CA+aN=Mqs6J-td1QAieyq1ghXkYUgr_Cbxn-eBNiwds+sEGqknw@mail.gmail.com>
	<561513E8.9030304@redhat.com>
Message-ID: <2077093250.24760680.1444412114704.JavaMail.zimbra@redhat.com>

In general more concrete examples such as curl commands would be tremendously helpful.

1. Explain 'start' and 'end' time range concept a bit more, Not everyone knows it is epoch in millisecond.  A visual explanation of raw vs aggregation data would be nice:

x X x x x x X x x  raw data
  ^start    ^end   -> now

        
2. How to use tags. Ex: tags=tagName:regexp,tagNameB:regexp


3. An online sandbox to try out different api calls (similar to https://jsfiddle.net/)


 

----- Original Message -----
From: "Thomas Segismont" <tsegismo at redhat.com>
To: hawkular-dev at lists.jboss.org
Sent: Wednesday, October 7, 2015 5:45:28 AM
Subject: Re: [Hawkular-dev] [Metrics] Better REST API documentation, feedback needed

I've updated the base documentation:

https://raw.githubusercontent.com/tsegismont/hawkular-metrics/jira/HWKMETRICS-297/api/metrics-api-jaxrs/src/main/rest-doc/base.adoc

Attached is a sample of the merge result (base documentation + swagger).

If you've ever felt short of information when using the Metrics REST 
API, this is an opportunity to chime in for improvements.

Le 07/10/2015 10:48, Thomas Heute a ?crit :
> Agreed on general information !
>
> I would like us to break some barriers between components.
> There are likely notions that should to be shared and shouldn't be just
> copied over and over. (Obvious ones are Tenant and Timestamps)
>
> So I would like to see the APIs in a single page (like Pager Duty) with
> general information followed by Metrics, Alerts,... sections.
>
>
>
> On Tue, Oct 6, 2015 at 3:45 PM, Thomas Segismont <tsegismo at redhat.com
> <mailto:tsegismo at redhat.com>> wrote:
>
>     Hi,
>
>     Currently our REST API documentation is generated solely from Swagger
>     annotations.
>
>     This is a good starting point, but I believe it's not enough nor easy
>     for new users.
>
>     I filed this JIRA:
>
>     HWKMETRICS-297 Incorporate static blocks into the REST API documentation
>     https://issues.jboss.org/browse/HWKMETRICS-297
>
>     And started the PR:
>     https://github.com/hawkular/hawkular-metrics/pull/389
>
>     Here's what I have in mind:
>     - provide general information which does not fit in annotations into a
>     base Asciidoc file
>     - merge the static file with the Swagger generated one
>
>     Many services organize their REST API documentation similarly (I liked
>     GitHub and PagerDuty examples in particular).
>
>     I need your opinion on the static file plan. I started with this:
>     https://raw.githubusercontent.com/tsegismont/hawkular-metrics/jira/HWKMETRICS-297/api/metrics-api-jaxrs/src/main/rest-doc/base.adoc
>
>     Can you think of anything missing? Or do you have any comments?
>
>     Of course the result doc is not perfect, but it's a step forward.
>
>     Thanks,
>     Thomas
>
>     _______________________________________________
>     hawkular-dev mailing list
>     hawkular-dev at lists.jboss.org <mailto: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


From mazz at redhat.com  Fri Oct  9 18:08:53 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Fri, 9 Oct 2015 18:08:53 -0400 (EDT)
Subject: [Hawkular-dev] https and accounts/keycloak
In-Reply-To: <846845671.27998973.1444428214111.JavaMail.zimbra@redhat.com>
Message-ID: <116841775.27999177.1444428533268.JavaMail.zimbra@redhat.com>

I'm trying to figure out what does or does not work over HTTPS. So I configured kettle with my own self-signed keystore using these instructions:

http://blog.eisele.net/2015/01/ssl-with-wildfly-8-and-undertow.html

I can see the UI at https://localhost:8443 - I first had to tell Firefox to accept the certificate (so I know its really going over SSL). And the fact I can see the login screen tells me the SSL setup is OK and I'm able to access the UI over https. However, when I try to log in, I get an exception - and its a similar exception I get when the agent tries to call into kettle.

Has anyone tried accessing kettle over https and have you seen any keycloak issues when doing so? (nudge, nudge, juca :-)

Here's the exception I get when I try to log into the UI - I'm curious if there are other configuration settings we need to get HTTPS to work:

384109 [default task-21] ERROR io.undertow.request  - UT005023: Exception handling request to /hawkular/accounts/personas/current
java.lang.RuntimeException: Unable to resolve realm public key remotely
	at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:134)
	at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83)
	at org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:71)
	at org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:47)
	at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68)
	at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
	at io.undertow.server.handlers.MetricsHandler.handleRequest(MetricsHandler.java:62)
	at io.undertow.servlet.core.MetricsChainHandler.handleRequest(MetricsChainHandler.java:59)
	at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:282)
	at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:261)
	at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:80)
	at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:172)
	at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199)
	at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774)
	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)
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
	at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
	at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1937)
	at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
	at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
	at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1478)
	at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:212)
	at sun.security.ssl.Handshaker.processLoop(Handshaker.java:957)
	at sun.security.ssl.Handshaker.process_record(Handshaker.java:892)
	at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1050)
	at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1363)
	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1391)
	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1375)
	at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:535)
	at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
	at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
	at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
	at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
	at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
	at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
	at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
	at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:105)
	... 16 more
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
	at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:387)
	at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292)
	at sun.security.validator.Validator.validate(Validator.java:260)
	at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
	at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229)
	at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
	at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1460)
	... 35 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
	at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:145)
	at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:131)
	at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280)
	at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:382)

From tsegismo at redhat.com  Mon Oct 12 03:44:15 2015
From: tsegismo at redhat.com (Thomas Segismont)
Date: Mon, 12 Oct 2015 09:44:15 +0200
Subject: [Hawkular-dev] [Metrics] Better REST API documentation,
 feedback needed
In-Reply-To: <2077093250.24760680.1444412114704.JavaMail.zimbra@redhat.com>
References: <5613D07F.9080604@redhat.com>
	<CA+aN=Mqs6J-td1QAieyq1ghXkYUgr_Cbxn-eBNiwds+sEGqknw@mail.gmail.com>
	<561513E8.9030304@redhat.com>
	<2077093250.24760680.1444412114704.JavaMail.zimbra@redhat.com>
Message-ID: <561B64CF.9080403@redhat.com>

Le 09/10/2015 19:35, Viet Nguyen a ?crit :
> In general more concrete examples such as curl commands would be tremendously helpful.

+1

The most important examples I can think of:
- POST requests for new data
- GET requests for data
- GET requests for stats
- Tagging samples
- Find by tags samples

>
> 1. Explain 'start' and 'end' time range concept a bit more, Not everyone knows it is epoch in millisecond.  A visual explanation of raw vs aggregation data would be nice:
>
> x X x x x x X x x  raw data
>    ^start    ^end   -> now
>

Did you look at the latest version? In the "Time Ranges" section, 
there's a cross-reference to the "Timestamps" section, which clearly 
explains how Metrics understands timestamps.

+1 for visual explanations. But I'm not sure I get what you meant with 
the schema.

>
> 2. How to use tags. Ex: tags=tagName:regexp,tagNameB:regexp
>

I suppose the examples mentioned above would do this.

>
> 3. An online sandbox to try out different api calls (similar to https://jsfiddle.net/)
>

You mean prepare javascript files for testing?
Or having a public server for testing?

>
>
>
> ----- Original Message -----
> From: "Thomas Segismont" <tsegismo at redhat.com>
> To: hawkular-dev at lists.jboss.org
> Sent: Wednesday, October 7, 2015 5:45:28 AM
> Subject: Re: [Hawkular-dev] [Metrics] Better REST API documentation, feedback needed
>
> I've updated the base documentation:
>
> https://raw.githubusercontent.com/tsegismont/hawkular-metrics/jira/HWKMETRICS-297/api/metrics-api-jaxrs/src/main/rest-doc/base.adoc
>
> Attached is a sample of the merge result (base documentation + swagger).
>
> If you've ever felt short of information when using the Metrics REST
> API, this is an opportunity to chime in for improvements.
>
> Le 07/10/2015 10:48, Thomas Heute a ?crit :
>> Agreed on general information !
>>
>> I would like us to break some barriers between components.
>> There are likely notions that should to be shared and shouldn't be just
>> copied over and over. (Obvious ones are Tenant and Timestamps)
>>
>> So I would like to see the APIs in a single page (like Pager Duty) with
>> general information followed by Metrics, Alerts,... sections.
>>
>>
>>
>> On Tue, Oct 6, 2015 at 3:45 PM, Thomas Segismont <tsegismo at redhat.com
>> <mailto:tsegismo at redhat.com>> wrote:
>>
>>      Hi,
>>
>>      Currently our REST API documentation is generated solely from Swagger
>>      annotations.
>>
>>      This is a good starting point, but I believe it's not enough nor easy
>>      for new users.
>>
>>      I filed this JIRA:
>>
>>      HWKMETRICS-297 Incorporate static blocks into the REST API documentation
>>      https://issues.jboss.org/browse/HWKMETRICS-297
>>
>>      And started the PR:
>>      https://github.com/hawkular/hawkular-metrics/pull/389
>>
>>      Here's what I have in mind:
>>      - provide general information which does not fit in annotations into a
>>      base Asciidoc file
>>      - merge the static file with the Swagger generated one
>>
>>      Many services organize their REST API documentation similarly (I liked
>>      GitHub and PagerDuty examples in particular).
>>
>>      I need your opinion on the static file plan. I started with this:
>>      https://raw.githubusercontent.com/tsegismont/hawkular-metrics/jira/HWKMETRICS-297/api/metrics-api-jaxrs/src/main/rest-doc/base.adoc
>>
>>      Can you think of anything missing? Or do you have any comments?
>>
>>      Of course the result doc is not perfect, but it's a step forward.
>>
>>      Thanks,
>>      Thomas
>>
>>      _______________________________________________
>>      hawkular-dev mailing list
>>      hawkular-dev at lists.jboss.org <mailto: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
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>


From tsegismo at redhat.com  Mon Oct 12 03:44:58 2015
From: tsegismo at redhat.com (Thomas Segismont)
Date: Mon, 12 Oct 2015 09:44:58 +0200
Subject: [Hawkular-dev] [Metrics] Better REST API documentation,
 feedback needed
In-Reply-To: <561B64CF.9080403@redhat.com>
References: <5613D07F.9080604@redhat.com>
	<CA+aN=Mqs6J-td1QAieyq1ghXkYUgr_Cbxn-eBNiwds+sEGqknw@mail.gmail.com>
	<561513E8.9030304@redhat.com>
	<2077093250.24760680.1444412114704.JavaMail.zimbra@redhat.com>
	<561B64CF.9080403@redhat.com>
Message-ID: <561B64FA.2040608@redhat.com>

And thanks for the feedback Viet!

Le 12/10/2015 09:44, Thomas Segismont a ?crit :
> Le 09/10/2015 19:35, Viet Nguyen a ?crit :
>> In general more concrete examples such as curl commands would be tremendously helpful.
>
> +1
>
> The most important examples I can think of:
> - POST requests for new data
> - GET requests for data
> - GET requests for stats
> - Tagging samples
> - Find by tags samples
>
>>
>> 1. Explain 'start' and 'end' time range concept a bit more, Not everyone knows it is epoch in millisecond.  A visual explanation of raw vs aggregation data would be nice:
>>
>> x X x x x x X x x  raw data
>>     ^start    ^end   -> now
>>
>
> Did you look at the latest version? In the "Time Ranges" section,
> there's a cross-reference to the "Timestamps" section, which clearly
> explains how Metrics understands timestamps.
>
> +1 for visual explanations. But I'm not sure I get what you meant with
> the schema.
>
>>
>> 2. How to use tags. Ex: tags=tagName:regexp,tagNameB:regexp
>>
>
> I suppose the examples mentioned above would do this.
>
>>
>> 3. An online sandbox to try out different api calls (similar to https://jsfiddle.net/)
>>
>
> You mean prepare javascript files for testing?
> Or having a public server for testing?
>
>>
>>
>>
>> ----- Original Message -----
>> From: "Thomas Segismont" <tsegismo at redhat.com>
>> To: hawkular-dev at lists.jboss.org
>> Sent: Wednesday, October 7, 2015 5:45:28 AM
>> Subject: Re: [Hawkular-dev] [Metrics] Better REST API documentation, feedback needed
>>
>> I've updated the base documentation:
>>
>> https://raw.githubusercontent.com/tsegismont/hawkular-metrics/jira/HWKMETRICS-297/api/metrics-api-jaxrs/src/main/rest-doc/base.adoc
>>
>> Attached is a sample of the merge result (base documentation + swagger).
>>
>> If you've ever felt short of information when using the Metrics REST
>> API, this is an opportunity to chime in for improvements.
>>
>> Le 07/10/2015 10:48, Thomas Heute a ?crit :
>>> Agreed on general information !
>>>
>>> I would like us to break some barriers between components.
>>> There are likely notions that should to be shared and shouldn't be just
>>> copied over and over. (Obvious ones are Tenant and Timestamps)
>>>
>>> So I would like to see the APIs in a single page (like Pager Duty) with
>>> general information followed by Metrics, Alerts,... sections.
>>>
>>>
>>>
>>> On Tue, Oct 6, 2015 at 3:45 PM, Thomas Segismont <tsegismo at redhat.com
>>> <mailto:tsegismo at redhat.com>> wrote:
>>>
>>>       Hi,
>>>
>>>       Currently our REST API documentation is generated solely from Swagger
>>>       annotations.
>>>
>>>       This is a good starting point, but I believe it's not enough nor easy
>>>       for new users.
>>>
>>>       I filed this JIRA:
>>>
>>>       HWKMETRICS-297 Incorporate static blocks into the REST API documentation
>>>       https://issues.jboss.org/browse/HWKMETRICS-297
>>>
>>>       And started the PR:
>>>       https://github.com/hawkular/hawkular-metrics/pull/389
>>>
>>>       Here's what I have in mind:
>>>       - provide general information which does not fit in annotations into a
>>>       base Asciidoc file
>>>       - merge the static file with the Swagger generated one
>>>
>>>       Many services organize their REST API documentation similarly (I liked
>>>       GitHub and PagerDuty examples in particular).
>>>
>>>       I need your opinion on the static file plan. I started with this:
>>>       https://raw.githubusercontent.com/tsegismont/hawkular-metrics/jira/HWKMETRICS-297/api/metrics-api-jaxrs/src/main/rest-doc/base.adoc
>>>
>>>       Can you think of anything missing? Or do you have any comments?
>>>
>>>       Of course the result doc is not perfect, but it's a step forward.
>>>
>>>       Thanks,
>>>       Thomas
>>>
>>>       _______________________________________________
>>>       hawkular-dev mailing list
>>>       hawkular-dev at lists.jboss.org <mailto: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
>>
>> _______________________________________________
>> 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
>


From tsegismo at redhat.com  Mon Oct 12 03:56:19 2015
From: tsegismo at redhat.com (Thomas Segismont)
Date: Mon, 12 Oct 2015 09:56:19 +0200
Subject: [Hawkular-dev] [Metrics] Better REST API documentation,
 feedback needed
In-Reply-To: <561B64FA.2040608@redhat.com>
References: <5613D07F.9080604@redhat.com>
	<CA+aN=Mqs6J-td1QAieyq1ghXkYUgr_Cbxn-eBNiwds+sEGqknw@mail.gmail.com>
	<561513E8.9030304@redhat.com>
	<2077093250.24760680.1444412114704.JavaMail.zimbra@redhat.com>
	<561B64CF.9080403@redhat.com> <561B64FA.2040608@redhat.com>
Message-ID: <561B67A3.10703@redhat.com>

I've created a JIRA to gather and track feedback:
https://issues.jboss.org/browse/HWKMETRICS-302

Feel free to contribute. On JIRA. Or GitHub :)


Le 12/10/2015 09:44, Thomas Segismont a ?crit :
> And thanks for the feedback Viet!
>
> Le 12/10/2015 09:44, Thomas Segismont a ?crit :
>> Le 09/10/2015 19:35, Viet Nguyen a ?crit :
>>> In general more concrete examples such as curl commands would be tremendously helpful.
>>
>> +1
>>
>> The most important examples I can think of:
>> - POST requests for new data
>> - GET requests for data
>> - GET requests for stats
>> - Tagging samples
>> - Find by tags samples
>>
>>>
>>> 1. Explain 'start' and 'end' time range concept a bit more, Not everyone knows it is epoch in millisecond.  A visual explanation of raw vs aggregation data would be nice:
>>>
>>> x X x x x x X x x  raw data
>>>      ^start    ^end   -> now
>>>
>>
>> Did you look at the latest version? In the "Time Ranges" section,
>> there's a cross-reference to the "Timestamps" section, which clearly
>> explains how Metrics understands timestamps.
>>
>> +1 for visual explanations. But I'm not sure I get what you meant with
>> the schema.
>>
>>>
>>> 2. How to use tags. Ex: tags=tagName:regexp,tagNameB:regexp
>>>
>>
>> I suppose the examples mentioned above would do this.
>>
>>>
>>> 3. An online sandbox to try out different api calls (similar to https://jsfiddle.net/)
>>>
>>
>> You mean prepare javascript files for testing?
>> Or having a public server for testing?
>>
>>>
>>>
>>>
>>> ----- Original Message -----
>>> From: "Thomas Segismont" <tsegismo at redhat.com>
>>> To: hawkular-dev at lists.jboss.org
>>> Sent: Wednesday, October 7, 2015 5:45:28 AM
>>> Subject: Re: [Hawkular-dev] [Metrics] Better REST API documentation, feedback needed
>>>
>>> I've updated the base documentation:
>>>
>>> https://raw.githubusercontent.com/tsegismont/hawkular-metrics/jira/HWKMETRICS-297/api/metrics-api-jaxrs/src/main/rest-doc/base.adoc
>>>
>>> Attached is a sample of the merge result (base documentation + swagger).
>>>
>>> If you've ever felt short of information when using the Metrics REST
>>> API, this is an opportunity to chime in for improvements.
>>>
>>> Le 07/10/2015 10:48, Thomas Heute a ?crit :
>>>> Agreed on general information !
>>>>
>>>> I would like us to break some barriers between components.
>>>> There are likely notions that should to be shared and shouldn't be just
>>>> copied over and over. (Obvious ones are Tenant and Timestamps)
>>>>
>>>> So I would like to see the APIs in a single page (like Pager Duty) with
>>>> general information followed by Metrics, Alerts,... sections.
>>>>
>>>>
>>>>
>>>> On Tue, Oct 6, 2015 at 3:45 PM, Thomas Segismont <tsegismo at redhat.com
>>>> <mailto:tsegismo at redhat.com>> wrote:
>>>>
>>>>        Hi,
>>>>
>>>>        Currently our REST API documentation is generated solely from Swagger
>>>>        annotations.
>>>>
>>>>        This is a good starting point, but I believe it's not enough nor easy
>>>>        for new users.
>>>>
>>>>        I filed this JIRA:
>>>>
>>>>        HWKMETRICS-297 Incorporate static blocks into the REST API documentation
>>>>        https://issues.jboss.org/browse/HWKMETRICS-297
>>>>
>>>>        And started the PR:
>>>>        https://github.com/hawkular/hawkular-metrics/pull/389
>>>>
>>>>        Here's what I have in mind:
>>>>        - provide general information which does not fit in annotations into a
>>>>        base Asciidoc file
>>>>        - merge the static file with the Swagger generated one
>>>>
>>>>        Many services organize their REST API documentation similarly (I liked
>>>>        GitHub and PagerDuty examples in particular).
>>>>
>>>>        I need your opinion on the static file plan. I started with this:
>>>>        https://raw.githubusercontent.com/tsegismont/hawkular-metrics/jira/HWKMETRICS-297/api/metrics-api-jaxrs/src/main/rest-doc/base.adoc
>>>>
>>>>        Can you think of anything missing? Or do you have any comments?
>>>>
>>>>        Of course the result doc is not perfect, but it's a step forward.
>>>>
>>>>        Thanks,
>>>>        Thomas
>>>>
>>>>        _______________________________________________
>>>>        hawkular-dev mailing list
>>>>        hawkular-dev at lists.jboss.org <mailto: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
>>>
>>> _______________________________________________
>>> 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
>


From jpkroehling at redhat.com  Mon Oct 12 04:48:55 2015
From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=)
Date: Mon, 12 Oct 2015 10:48:55 +0200
Subject: [Hawkular-dev] https and accounts/keycloak
In-Reply-To: <116841775.27999177.1444428533268.JavaMail.zimbra@redhat.com>
References: <116841775.27999177.1444428533268.JavaMail.zimbra@redhat.com>
Message-ID: <561B73F7.7090300@redhat.com>

I have an instance with TLS at https://hawkular.kroehling.de working, 
but I can't promise to keep it running 24x7 :) It's a bit old already 
(MS4, IIRC) , but the setup should not be too different between MS4 and MS5.

When setting it up, there were a few issues (like, using http by default 
in some components without the possibility of overriding it), but the UI 
worked fine once those were fixed and merged. Granted, I haven't tested 
*everything*, so, I can't say that it all worked :)

Anyway, about the error you are seeing: it seems like the certificate is 
missing from "some" keystore. Have you added the cert to the 
keycloak.jks keystore? There are a few Keycloak-specific steps that are 
required, documented here:

http://keycloak.github.io/docs/userguide/html_single/index.html#d4e336


- Juca.

On 10/10/2015 12:08 AM, John Mazzitelli wrote:
> I'm trying to figure out what does or does not work over HTTPS. So I configured kettle with my own self-signed keystore using these instructions:
>
> http://blog.eisele.net/2015/01/ssl-with-wildfly-8-and-undertow.html
>
> I can see the UI at https://localhost:8443 - I first had to tell Firefox to accept the certificate (so I know its really going over SSL). And the fact I can see the login screen tells me the SSL setup is OK and I'm able to access the UI over https. However, when I try to log in, I get an exception - and its a similar exception I get when the agent tries to call into kettle.
>
> Has anyone tried accessing kettle over https and have you seen any keycloak issues when doing so? (nudge, nudge, juca :-)
>
> Here's the exception I get when I try to log into the UI - I'm curious if there are other configuration settings we need to get HTTPS to work:
>
> 384109 [default task-21] ERROR io.undertow.request  - UT005023: Exception handling request to /hawkular/accounts/personas/current
> java.lang.RuntimeException: Unable to resolve realm public key remotely
> 	at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:134)
> 	at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83)
> 	at org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:71)
> 	at org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:47)
> 	at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68)
> 	at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> 	at io.undertow.server.handlers.MetricsHandler.handleRequest(MetricsHandler.java:62)
> 	at io.undertow.servlet.core.MetricsChainHandler.handleRequest(MetricsChainHandler.java:59)
> 	at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:282)
> 	at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:261)
> 	at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:80)
> 	at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:172)
> 	at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199)
> 	at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774)
> 	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)
> Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
> 	at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> 	at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1937)
> 	at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
> 	at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
> 	at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1478)
> 	at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:212)
> 	at sun.security.ssl.Handshaker.processLoop(Handshaker.java:957)
> 	at sun.security.ssl.Handshaker.process_record(Handshaker.java:892)
> 	at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1050)
> 	at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1363)
> 	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1391)
> 	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1375)
> 	at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:535)
> 	at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
> 	at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
> 	at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
> 	at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
> 	at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
> 	at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
> 	at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
> 	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> 	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> 	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
> 	at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:105)
> 	... 16 more
> Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
> 	at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:387)
> 	at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292)
> 	at sun.security.validator.Validator.validate(Validator.java:260)
> 	at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
> 	at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229)
> 	at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
> 	at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1460)
> 	... 35 more
> Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
> 	at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:145)
> 	at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:131)
> 	at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280)
> 	at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:382)
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>

From tsegismo at redhat.com  Mon Oct 12 05:08:10 2015
From: tsegismo at redhat.com (Thomas Segismont)
Date: Mon, 12 Oct 2015 11:08:10 +0200
Subject: [Hawkular-dev] https and accounts/keycloak
In-Reply-To: <561B73F7.7090300@redhat.com>
References: <116841775.27999177.1444428533268.JavaMail.zimbra@redhat.com>
	<561B73F7.7090300@redhat.com>
Message-ID: <561B787A.5090207@redhat.com>

I guess not only KC needs to be updated. The exception below is very 
common and is due to the self-signed certificate.

All the JVM involved must be configured so that the certificate CA is 
trusted (that is, add your certificate to the trust store).

Le 12/10/2015 10:48, Juraci Paix?o Kr?hling a ?crit :
> I have an instance with TLS at https://hawkular.kroehling.de working,
> but I can't promise to keep it running 24x7 :) It's a bit old already
> (MS4, IIRC) , but the setup should not be too different between MS4 and MS5.
>
> When setting it up, there were a few issues (like, using http by default
> in some components without the possibility of overriding it), but the UI
> worked fine once those were fixed and merged. Granted, I haven't tested
> *everything*, so, I can't say that it all worked :)
>
> Anyway, about the error you are seeing: it seems like the certificate is
> missing from "some" keystore. Have you added the cert to the
> keycloak.jks keystore? There are a few Keycloak-specific steps that are
> required, documented here:
>
> http://keycloak.github.io/docs/userguide/html_single/index.html#d4e336
>
>
> - Juca.
>
> On 10/10/2015 12:08 AM, John Mazzitelli wrote:
>> I'm trying to figure out what does or does not work over HTTPS. So I configured kettle with my own self-signed keystore using these instructions:
>>
>> http://blog.eisele.net/2015/01/ssl-with-wildfly-8-and-undertow.html
>>
>> I can see the UI at https://localhost:8443 - I first had to tell Firefox to accept the certificate (so I know its really going over SSL). And the fact I can see the login screen tells me the SSL setup is OK and I'm able to access the UI over https. However, when I try to log in, I get an exception - and its a similar exception I get when the agent tries to call into kettle.
>>
>> Has anyone tried accessing kettle over https and have you seen any keycloak issues when doing so? (nudge, nudge, juca :-)
>>
>> Here's the exception I get when I try to log into the UI - I'm curious if there are other configuration settings we need to get HTTPS to work:
>>
>> 384109 [default task-21] ERROR io.undertow.request  - UT005023: Exception handling request to /hawkular/accounts/personas/current
>> java.lang.RuntimeException: Unable to resolve realm public key remotely
>> 	at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:134)
>> 	at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83)
>> 	at org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:71)
>> 	at org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:47)
>> 	at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68)
>> 	at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
>> 	at io.undertow.server.handlers.MetricsHandler.handleRequest(MetricsHandler.java:62)
>> 	at io.undertow.servlet.core.MetricsChainHandler.handleRequest(MetricsChainHandler.java:59)
>> 	at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:282)
>> 	at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:261)
>> 	at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:80)
>> 	at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:172)
>> 	at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199)
>> 	at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774)
>> 	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)
>> Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
>> 	at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
>> 	at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1937)
>> 	at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
>> 	at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
>> 	at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1478)
>> 	at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:212)
>> 	at sun.security.ssl.Handshaker.processLoop(Handshaker.java:957)
>> 	at sun.security.ssl.Handshaker.process_record(Handshaker.java:892)
>> 	at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1050)
>> 	at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1363)
>> 	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1391)
>> 	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1375)
>> 	at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:535)
>> 	at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
>> 	at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
>> 	at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
>> 	at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
>> 	at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
>> 	at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
>> 	at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
>> 	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
>> 	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
>> 	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
>> 	at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:105)
>> 	... 16 more
>> Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
>> 	at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:387)
>> 	at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292)
>> 	at sun.security.validator.Validator.validate(Validator.java:260)
>> 	at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
>> 	at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229)
>> 	at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
>> 	at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1460)
>> 	... 35 more
>> Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
>> 	at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:145)
>> 	at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:131)
>> 	at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280)
>> 	at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:382)
>> _______________________________________________
>> 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
>


From jpkroehling at redhat.com  Mon Oct 12 05:09:57 2015
From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=)
Date: Mon, 12 Oct 2015 11:09:57 +0200
Subject: [Hawkular-dev] https and accounts/keycloak
In-Reply-To: <561B73F7.7090300@redhat.com>
References: <116841775.27999177.1444428533268.JavaMail.zimbra@redhat.com>
	<561B73F7.7090300@redhat.com>
Message-ID: <561B78E5.7020402@redhat.com>

By the way: on that instance, I have these URLs on the Keycloak subsystem:

<auth-server-url>https://hawkular.kroehling.de/auth</auth-server-url>
<auth-server-url-for-backend-requests>http://192.168.122.230:8080/auth</auth-server-url-for-backend-requests>

This means: users of the application would be redirected to the first 
URL when logging in, while the internal backend calls are made using the 
second URL.

- Juca.

On 10/12/2015 10:48 AM, Juraci Paix?o Kr?hling wrote:
> I have an instance with TLS at https://hawkular.kroehling.de working,
> but I can't promise to keep it running 24x7 :) It's a bit old already
> (MS4, IIRC) , but the setup should not be too different between MS4 and
> MS5.
>
> When setting it up, there were a few issues (like, using http by default
> in some components without the possibility of overriding it), but the UI
> worked fine once those were fixed and merged. Granted, I haven't tested
> *everything*, so, I can't say that it all worked :)
>
> Anyway, about the error you are seeing: it seems like the certificate is
> missing from "some" keystore. Have you added the cert to the
> keycloak.jks keystore? There are a few Keycloak-specific steps that are
> required, documented here:
>
> http://keycloak.github.io/docs/userguide/html_single/index.html#d4e336
>
>
> - Juca.
>
> On 10/10/2015 12:08 AM, John Mazzitelli wrote:
>> I'm trying to figure out what does or does not work over HTTPS. So I
>> configured kettle with my own self-signed keystore using these
>> instructions:
>>
>> http://blog.eisele.net/2015/01/ssl-with-wildfly-8-and-undertow.html
>>
>> I can see the UI at https://localhost:8443 - I first had to tell
>> Firefox to accept the certificate (so I know its really going over
>> SSL). And the fact I can see the login screen tells me the SSL setup
>> is OK and I'm able to access the UI over https. However, when I try to
>> log in, I get an exception - and its a similar exception I get when
>> the agent tries to call into kettle.
>>
>> Has anyone tried accessing kettle over https and have you seen any
>> keycloak issues when doing so? (nudge, nudge, juca :-)
>>
>> Here's the exception I get when I try to log into the UI - I'm curious
>> if there are other configuration settings we need to get HTTPS to work:
>>
>> 384109 [default task-21] ERROR io.undertow.request  - UT005023:
>> Exception handling request to /hawkular/accounts/personas/current
>> java.lang.RuntimeException: Unable to resolve realm public key remotely
>>     at
>> org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:134)
>>
>>     at
>> org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83)
>>
>>     at
>> org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:71)
>>
>>     at
>> org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:47)
>>
>>     at
>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68)
>>
>>     at
>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
>>
>>     at
>> io.undertow.server.handlers.MetricsHandler.handleRequest(MetricsHandler.java:62)
>>
>>     at
>> io.undertow.servlet.core.MetricsChainHandler.handleRequest(MetricsChainHandler.java:59)
>>
>>     at
>> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:282)
>>
>>     at
>> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:261)
>>
>>     at
>> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:80)
>>
>>     at
>> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:172)
>>
>>     at
>> io.undertow.server.Connectors.executeRootHandler(Connectors.java:199)
>>     at
>> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774)
>>     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)
>> Caused by: javax.net.ssl.SSLHandshakeException:
>> sun.security.validator.ValidatorException: PKIX path building failed:
>> sun.security.provider.certpath.SunCertPathBuilderException: unable to
>> find valid certification path to requested target
>>     at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
>>     at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1937)
>>     at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
>>     at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
>>     at
>> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1478)
>>
>>     at
>> sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:212)
>>
>>     at sun.security.ssl.Handshaker.processLoop(Handshaker.java:957)
>>     at sun.security.ssl.Handshaker.process_record(Handshaker.java:892)
>>     at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1050)
>>     at
>> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1363)
>>
>>     at
>> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1391)
>>     at
>> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1375)
>>     at
>> org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:535)
>>
>>     at
>> org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
>>
>>     at
>> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
>>
>>     at
>> org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
>>
>>     at
>> org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
>>
>>     at
>> org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
>>
>>     at
>> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
>>
>>     at
>> org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
>>
>>     at
>> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
>>
>>     at
>> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
>>
>>     at
>> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
>>
>>     at
>> org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:105)
>>
>>     ... 16 more
>> Caused by: sun.security.validator.ValidatorException: PKIX path
>> building failed:
>> sun.security.provider.certpath.SunCertPathBuilderException: unable to
>> find valid certification path to requested target
>>     at
>> sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:387)
>>     at
>> sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292)
>>
>>     at sun.security.validator.Validator.validate(Validator.java:260)
>>     at
>> sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
>>
>>     at
>> sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229)
>>
>>     at
>> sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
>>
>>     at
>> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1460)
>>
>>     ... 35 more
>> Caused by: sun.security.provider.certpath.SunCertPathBuilderException:
>> unable to find valid certification path to requested target
>>     at
>> sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:145)
>>
>>     at
>> sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:131)
>>
>>     at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280)
>>     at
>> sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:382)
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>

From mazz at redhat.com  Mon Oct 12 09:07:58 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Mon, 12 Oct 2015 09:07:58 -0400 (EDT)
Subject: [Hawkular-dev] https and accounts/keycloak
In-Reply-To: <561B78E5.7020402@redhat.com>
References: <116841775.27999177.1444428533268.JavaMail.zimbra@redhat.com>
	<561B73F7.7090300@redhat.com> <561B78E5.7020402@redhat.com>
Message-ID: <24467371.28832727.1444655278958.JavaMail.zimbra@redhat.com>

So, does this mean we can't ship SSL support out of box? Seems like some of these settings are very particular to the machine kettle is running on. Assuming we don't have an installer, how can we zip up the distro and have it run with SSL enabled out of box? I don't think we are going to be able to do that. If we cannot, we are going to need some VERY clear and easy-to-follow documentation to enable security.

Right now, it looks like there are steps required to:

1) create or obtain your own keystore/truststores
2) set up a security realm in WF
3) set up keycloak security specifically

Juca - did you happen to right down any notes on what you did to get your system running? That could be the start to some docs.

----- Original Message -----
> By the way: on that instance, I have these URLs on the Keycloak subsystem:
> 
> <auth-server-url>https://hawkular.kroehling.de/auth</auth-server-url>
> <auth-server-url-for-backend-requests>http://192.168.122.230:8080/auth</auth-server-url-for-backend-requests>
> 
> This means: users of the application would be redirected to the first
> URL when logging in, while the internal backend calls are made using the
> second URL.
> 
> - Juca.
> 
> On 10/12/2015 10:48 AM, Juraci Paix?o Kr?hling wrote:
> > I have an instance with TLS at https://hawkular.kroehling.de working,
> > but I can't promise to keep it running 24x7 :) It's a bit old already
> > (MS4, IIRC) , but the setup should not be too different between MS4 and
> > MS5.
> >
> > When setting it up, there were a few issues (like, using http by default
> > in some components without the possibility of overriding it), but the UI
> > worked fine once those were fixed and merged. Granted, I haven't tested
> > *everything*, so, I can't say that it all worked :)
> >
> > Anyway, about the error you are seeing: it seems like the certificate is
> > missing from "some" keystore. Have you added the cert to the
> > keycloak.jks keystore? There are a few Keycloak-specific steps that are
> > required, documented here:
> >
> > http://keycloak.github.io/docs/userguide/html_single/index.html#d4e336
> >
> >
> > - Juca.
> >
> > On 10/10/2015 12:08 AM, John Mazzitelli wrote:
> >> I'm trying to figure out what does or does not work over HTTPS. So I
> >> configured kettle with my own self-signed keystore using these
> >> instructions:
> >>
> >> http://blog.eisele.net/2015/01/ssl-with-wildfly-8-and-undertow.html
> >>
> >> I can see the UI at https://localhost:8443 - I first had to tell
> >> Firefox to accept the certificate (so I know its really going over
> >> SSL). And the fact I can see the login screen tells me the SSL setup
> >> is OK and I'm able to access the UI over https. However, when I try to
> >> log in, I get an exception - and its a similar exception I get when
> >> the agent tries to call into kettle.
> >>
> >> Has anyone tried accessing kettle over https and have you seen any
> >> keycloak issues when doing so? (nudge, nudge, juca :-)
> >>
> >> Here's the exception I get when I try to log into the UI - I'm curious
> >> if there are other configuration settings we need to get HTTPS to work:
> >>
> >> 384109 [default task-21] ERROR io.undertow.request  - UT005023:
> >> Exception handling request to /hawkular/accounts/personas/current
> >> java.lang.RuntimeException: Unable to resolve realm public key remotely
> >>     at
> >> org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:134)
> >>
> >>     at
> >> org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83)
> >>
> >>     at
> >> org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:71)
> >>
> >>     at
> >> org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:47)
> >>
> >>     at
> >> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68)
> >>
> >>     at
> >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> >>
> >>     at
> >> io.undertow.server.handlers.MetricsHandler.handleRequest(MetricsHandler.java:62)
> >>
> >>     at
> >> io.undertow.servlet.core.MetricsChainHandler.handleRequest(MetricsChainHandler.java:59)
> >>
> >>     at
> >> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:282)
> >>
> >>     at
> >> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:261)
> >>
> >>     at
> >> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:80)
> >>
> >>     at
> >> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:172)
> >>
> >>     at
> >> io.undertow.server.Connectors.executeRootHandler(Connectors.java:199)
> >>     at
> >> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774)
> >>     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)
> >> Caused by: javax.net.ssl.SSLHandshakeException:
> >> sun.security.validator.ValidatorException: PKIX path building failed:
> >> sun.security.provider.certpath.SunCertPathBuilderException: unable to
> >> find valid certification path to requested target
> >>     at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> >>     at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1937)
> >>     at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
> >>     at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
> >>     at
> >> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1478)
> >>
> >>     at
> >> sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:212)
> >>
> >>     at sun.security.ssl.Handshaker.processLoop(Handshaker.java:957)
> >>     at sun.security.ssl.Handshaker.process_record(Handshaker.java:892)
> >>     at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1050)
> >>     at
> >> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1363)
> >>
> >>     at
> >> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1391)
> >>     at
> >> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1375)
> >>     at
> >> org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:535)
> >>
> >>     at
> >> org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
> >>
> >>     at
> >> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
> >>
> >>     at
> >> org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
> >>
> >>     at
> >> org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
> >>
> >>     at
> >> org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
> >>
> >>     at
> >> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
> >>
> >>     at
> >> org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
> >>
> >>     at
> >> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> >>
> >>     at
> >> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> >>
> >>     at
> >> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
> >>
> >>     at
> >> org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:105)
> >>
> >>     ... 16 more
> >> Caused by: sun.security.validator.ValidatorException: PKIX path
> >> building failed:
> >> sun.security.provider.certpath.SunCertPathBuilderException: unable to
> >> find valid certification path to requested target
> >>     at
> >> sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:387)
> >>     at
> >> sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292)
> >>
> >>     at sun.security.validator.Validator.validate(Validator.java:260)
> >>     at
> >> sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
> >>
> >>     at
> >> sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229)
> >>
> >>     at
> >> sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
> >>
> >>     at
> >> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1460)
> >>
> >>     ... 35 more
> >> Caused by: sun.security.provider.certpath.SunCertPathBuilderException:
> >> unable to find valid certification path to requested target
> >>     at
> >> sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:145)
> >>
> >>     at
> >> sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:131)
> >>
> >>     at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280)
> >>     at
> >> sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:382)
> >> _______________________________________________
> >> 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
> 


From jpkroehling at redhat.com  Mon Oct 12 09:42:23 2015
From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=)
Date: Mon, 12 Oct 2015 15:42:23 +0200
Subject: [Hawkular-dev] https and accounts/keycloak
In-Reply-To: <24467371.28832727.1444655278958.JavaMail.zimbra@redhat.com>
References: <116841775.27999177.1444428533268.JavaMail.zimbra@redhat.com>
	<561B73F7.7090300@redhat.com> <561B78E5.7020402@redhat.com>
	<24467371.28832727.1444655278958.JavaMail.zimbra@redhat.com>
Message-ID: <561BB8BF.7090904@redhat.com>

On 10/12/2015 03:07 PM, John Mazzitelli wrote:
> So, does this mean we can't ship SSL support out of box? Seems like some of these settings are very particular to the machine kettle is running on. Assuming we don't have an installer, how can we zip up the distro and have it run with SSL enabled out of box? I don't think we are going to be able to do that. If we cannot, we are going to need some VERY clear and easy-to-follow documentation to enable security.

I'm not quite sure I understand what you mean by "SSL support out of the 
box". We cannot ship a distribution set for SSL if the keystore doesn't 
have the appropriate certificates, and we cannot ship "default" 
certificates. We *could* add those to the -dev profile, like we do with 
the default username/password.

> Right now, it looks like there are steps required to:
>
> 1) create or obtain your own keystore/truststores
> 2) set up a security realm in WF
> 3) set up keycloak security specifically

The step 3 is already a set of 1 and 2. IIRC, the only difference is 
that the keystore has to be named "keycloak.jks".

> Juca - did you happen to right down any notes on what you did to get your system running? That could be the start to some docs.

Sure, I still have the puppet scripts for it. My setup is a bit 
different than the usual, though, as I have a nginx proxy in front of 
all the VMs, including Hawkular's. Once I get the MS6 items done, I'll 
either document my setup with nginx (if I'm short in time) or setup a 
new VM with a "pure" Wildfly setup (if time allows).

- Juca.


From mazz at redhat.com  Mon Oct 12 09:47:58 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Mon, 12 Oct 2015 09:47:58 -0400 (EDT)
Subject: [Hawkular-dev] https and accounts/keycloak
In-Reply-To: <561BB8BF.7090904@redhat.com>
References: <116841775.27999177.1444428533268.JavaMail.zimbra@redhat.com>
	<561B73F7.7090300@redhat.com> <561B78E5.7020402@redhat.com>
	<24467371.28832727.1444655278958.JavaMail.zimbra@redhat.com>
	<561BB8BF.7090904@redhat.com>
Message-ID: <97668897.28855654.1444657678923.JavaMail.zimbra@redhat.com>

> I'm not quite sure I understand what you mean by "SSL support out of the
> box". We cannot ship a distribution set for SSL if the keystore doesn't
> have the appropriate certificates, and we cannot ship "default"
> certificates. We *could* add those to the -dev profile, like we do with
> the default username/password.

Right. I just want to make that clear to everyone. We will not have full secure/SSL communications out of box if we just ship the distro as we are doing now. It will require manual steps for people to perform, thus we need some really good docs here.

> 
> > Right now, it looks like there are steps required to:
> >
> > 1) create or obtain your own keystore/truststores
> > 2) set up a security realm in WF
> > 3) set up keycloak security specifically
> 
> The step 3 is already a set of 1 and 2. IIRC, the only difference is
> that the keystore has to be named "keycloak.jks".
> 

That seems odd they would require it to be named something specific. If they just pick up the security-realm defined in standalone.xml (which is what the https listener uses), the name shouldn't matter. Unless there is some OTHER setting specific to keycloak, in addition to the standard security realm definition.

I can write up some docs since I'm testing the SSL functionality now - if you have any links or notes or anything pass them my way. Right now, I'm flying blind wrt keycloak :)

From mazz at redhat.com  Mon Oct 12 10:03:14 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Mon, 12 Oct 2015 10:03:14 -0400 (EDT)
Subject: [Hawkular-dev] https and accounts/keycloak
In-Reply-To: <561B78E5.7020402@redhat.com>
References: <116841775.27999177.1444428533268.JavaMail.zimbra@redhat.com>
	<561B73F7.7090300@redhat.com> <561B78E5.7020402@redhat.com>
Message-ID: <326276473.28873705.1444658594971.JavaMail.zimbra@redhat.com>

> > Anyway, about the error you are seeing: it seems like the certificate is
> > missing from "some" keystore. Have you added the cert to the
> > keycloak.jks keystore? There are a few Keycloak-specific steps that are
> > required, documented here:
> >
> > http://keycloak.github.io/docs/userguide/html_single/index.html#d4e336

Ah, OK. I didn't do that "reverse proxy" stuff. Everything else I did. And I see they are using the security-realm stuff. So it doesn't have to be called "keycloak.jks", just as long as you point the <ssl> setting to the proper keystore.

From jpkroehling at redhat.com  Mon Oct 12 10:11:19 2015
From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=)
Date: Mon, 12 Oct 2015 16:11:19 +0200
Subject: [Hawkular-dev] https and accounts/keycloak
In-Reply-To: <326276473.28873705.1444658594971.JavaMail.zimbra@redhat.com>
References: <116841775.27999177.1444428533268.JavaMail.zimbra@redhat.com>
	<561B73F7.7090300@redhat.com> <561B78E5.7020402@redhat.com>
	<326276473.28873705.1444658594971.JavaMail.zimbra@redhat.com>
Message-ID: <561BBF87.70904@redhat.com>

On 10/12/2015 04:03 PM, John Mazzitelli wrote:
>>> Anyway, about the error you are seeing: it seems like the certificate is
>>> missing from "some" keystore. Have you added the cert to the
>>> keycloak.jks keystore? There are a few Keycloak-specific steps that are
>>> required, documented here:
>>>
>>> http://keycloak.github.io/docs/userguide/html_single/index.html#d4e336
>
> Ah, OK. I didn't do that "reverse proxy" stuff. Everything else I did. And I see they are using the security-realm stuff. So it doesn't have to be called "keycloak.jks", just as long as you point the <ssl> setting to the proper keystore.

I had the impression it has to be named keycloak.jks , as Keycloak would 
store other keys there than the cert, but if there's no such 
requirement, then it's better :)

- Juca.

From mazz at redhat.com  Mon Oct 12 17:28:19 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Mon, 12 Oct 2015 17:28:19 -0400 (EDT)
Subject: [Hawkular-dev] how to configure Hawkular Kettle for SSL/HTTPS
In-Reply-To: <1584887919.28892118.1444659291520.JavaMail.zimbra@redhat.com>
Message-ID: <1010165163.29133240.1444685299363.JavaMail.zimbra@redhat.com>

Here are some basic instructions on how to get SSL configured and working in Hawkular Kettle. I still have to verify that everything works wrt inventory, but this should be what needs to get done to get SSL/https working. Note that the securityRealm agent attribute is a new attribute that will be added to the agent shortly - it is not available in the latest agent release.

You should run these commands from within kettle's standalone/configuration directory.

1) If you do not have a keystore with your own private key/certificate, you can generate a self-signed cert. We will assume this is for testing purposes only so this will be a valid certificate for your localhost only (see "CN=localhost" and the Subject Alternative Name of 127.0.0.1):

keytool -genkey -keystore hawkular.keystore -alias hawkular -dname "CN=localhost" -keyalg RSA -storepass hawkular -keypass hawkular -validity 36500 -ext san=ip:127.0.0.1

Again, make sure your new "hawkular.keystore" is in kettle's standalone/configuration directory.

2) If you did create your own self-signed certificate, you will need to tell your Java VM that it can trust it. You do this by adding your self-signed cert to the cacerts file.

2.a) First, export your certificate from your keystore file (hawkular.keystore if you followed instructions in step 1) into a file called hawkular.cert:

keytool -export -alias hawkular -file hawkular.cert -storepass hawkular -keystore hawkular.keystore

2.b) Now import your self-signed certificate into your Java's CA certificates file - this makes your certificate trusted by your Java apps:

keytool -import -keystore $JAVA_HOME/jre/lib/security/cacerts -alias hawkular -storepass changeit -file hawkular.cert 

You can examine your certificate and answer the prompt to indicate you do trust that certificate. If you want to automate this, you can pass in the -noprompt command line argument and it will automatically add the certificate without asking you for confirmation.

3) Now that your keystore is generated and trusted, you have to tell Hawkular Kettle to use your keystore when using SSL. Add a security-realm first:

    <management>
        <security-realms>
            <security-realm name="UndertowRealm">
                <server-identities>
                    <ssl>
                        <keystore path="hawkular.keystore" relative-to="jboss.server.config.dir" keystore-password="hawkular" key-password="hawkular" alias="hawkular" />
                    </ssl>
                </server-identities>
            </security-realm>

4) Now add an HTTPS listener, using your new security-realm that is configured with your new keystore:

   <server name="default-server">
       <https-listener name="https" security-realm="UndertowRealm" socket-binding="https"/>

5) Turn on SSL in the agent by adding these two attributes to the <storage-adapter> element:

  * useSSL="true"
  * securityRealm="UndertowRealm"

From mazz at redhat.com  Mon Oct 12 22:36:30 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Mon, 12 Oct 2015 22:36:30 -0400 (EDT)
Subject: [Hawkular-dev] how to configure Hawkular Kettle for SSL/HTTPS
In-Reply-To: <1010165163.29133240.1444685299363.JavaMail.zimbra@redhat.com>
References: <1010165163.29133240.1444685299363.JavaMail.zimbra@redhat.com>
Message-ID: <429532993.29227310.1444703790409.JavaMail.zimbra@redhat.com>

I've put some basic instructions on how to enable SSL / HTTPS in Hawkular here:

https://github.com/hawkular/hawkular.github.io/blob/pages/src/main/jbake/content/docs/user/secure-comm.adoc

I do not know if this is complete - there may be some other things I am missing, specifically around keycloak (I do not talk about reverse proxies in this doc, and I don't know if I should (the keycloak docs mention it) and I didn't mention anything about changing any keycloak configuration file (there should probably be something about <auth-server-url> and <auth-server-url-for-backend-requests> but I am not sure what they are for so I didn't mention them). FWIW, the instructions I linked to above worked on my local machine - I was able to see the browser and agent access the server over SSL.

From hrupp at redhat.com  Tue Oct 13 03:36:50 2015
From: hrupp at redhat.com (Heiko W.Rupp)
Date: Tue, 13 Oct 2015 09:36:50 +0200
Subject: [Hawkular-dev] Resourcetype again
In-Reply-To: <32099564.56ockzxRnr@localhost.localdomain>
References: <6859E673-FB75-4957-BE7F-6966ED5203DA@redhat.com>
	<476074189.25063107.1444091421191.JavaMail.zimbra@redhat.com>
	<5022218C-ED12-4E25-9FE1-59914755DC61@redhat.com>
	<32099564.56ockzxRnr@localhost.localdomain>
Message-ID: <79CBDA60-DF15-4982-988D-0A8ECABC1BE2@redhat.com>

On 9 Oct 2015, at 13:58, Lukas Krejci wrote:

> I disagree about the server being the authoritative source of 
> metadata.
>
> After all it is the feed that actually "sees" and can "touch" the 
> resource,
> not the server.

This is  complicated topic with no easy answer.
On one side we need to avoid storing the same
stuff over and over again. Take an Infinispan
cluster with 1000 nodes - here we do not want
to have 1000 times the same metadata stored
in inventory, but only one copy that all those
1000 nodes share.
On the other hand, we as Hawkular team do not
want to maintain the metadata of Infinispan.
Infinispan should indeed deliver their metadata
in some way. That could be like they provide that
on the 1st connecting node and then all others
share that metadata.

Also as Infinispan runs on top of WildFly, (but
exchanges some subsystems with their version),
and we need that information so that e.g. the
UI can show the stuff for WildFly unless it is
explicitly enabled/disabled for Infinispan.

The same applies for Hawkular server, which
also runs on top of WildFly.

> What the server can (and will) do is to provide for quickly checking 
> if
> certain metadata are present in inventory. I preliminarily call it 
> "metadata
> packs" which will be a collection of resource, metric and operation 
> types
> together with a method to compute their collective hash. The feed then 
> will
> check if a pack with a given hash is present in the server and if 
> there is,
> then it's good to go.
>
> If the hash does not match it means that some metadata, that the agent 
> expects
> (and requires) to correctly describe what it sees, needs to be changed 
> on the
> server (i.e. the agent uploads the changes it needs and forms a new 
> pack if it
> wants to).
>
> Now for this to make sense, a metadata pack uploaded by one feed (or 
> uploaded
> by an operator prior to any feed connecting to the server or even pre-
> installed with Hawkular) needs to be "globally visible" so that other 
> feeds
> don't have to upload their own version of it with the same hash - i.e. 
> pack
> with the same hash should be defined only once in the server.

That certainly makes sense and reflects what I wrote above.

> IMHO, if the agent stays the source of metadata and has the ability to 
> quickly
> check that all it needs is already "up with the hawk" then that's a 
> simpler
> solution that will be in the end easier on the feeds.

This is certainly a good approach. Where I am concerned,
and you sort of mention that in the next paragraph
is users messing with the resource types so that they
get into an indeterministic state.

> Note that these packs essentially don't need to be user-visible or 
> amendable
> "things" - primarily because it would be generally difficult to call 
> them
> user-friendly names.

   Heiko

From snegrea at redhat.com  Tue Oct 13 13:25:19 2015
From: snegrea at redhat.com (Stefan Negrea)
Date: Tue, 13 Oct 2015 13:25:19 -0400 (EDT)
Subject: [Hawkular-dev] Hawkular Metrics 0.8.0 - Release & Beyond
In-Reply-To: <1815555006.36803806.1443656015921.JavaMail.zimbra@redhat.com>
Message-ID: <725703957.44011096.1444757119588.JavaMail.zimbra@redhat.com>

Hello Everybody,

I am happy to announce release 0.8.0 of Hawkular Metrics. This short schedule release is anchored by major enhancements for metrics query aggregation, updated container support, and performance and stability enhancements.


Here is a list of major changes in this release:

1) Counters
  * Counter rates computations now avoid counter value resets (HWKMETRICS-218)
  * Counter rates are now aligned with the actual counter data used to calculate the rate (HWKMETRICS-284)

2) Aggregate Metric Statistics
  * Added support for aggregate statistics based on multiple metrics
  * Gauges, counters, and counter rates are supported
  * Two methods of aggregation are currently available
    * uniform: data from multiple metrics is bucketed as originating from a single source and then statistics are computed on the entire set
    * stacked: statistics are first computed for every matching metric and then those statistics are stacked (added)
    * by default uniform statistics are enabled, stacking is enabled by stacked=true query parameter
  * The end-points are /gauges/data , /counters/data, /counters/data/rate 
  * There is support to query by either tags or metrics ids; but not both
  * Relevant JIRAs: HWKMETRICS-292, HWKMETRICS-263, HWKMETRICS-264

3) Data storage updates
  * Schema changes will require rebuilding the database
  * Reduced data storage footprint by limiting the size of metric type (HWKMETRICS-301)

4) Container support
  * Secure connections are enabled between Hawkular Metrics and the Heapster sink (HWKMETRICS-217)
  * cqlsh can be access directly from within the Cassandra docker (HWKMETRICS-260)
  * Various updates to the Heapster sink to support latest Hawkular Metrics features: HWKMETRICS-285, HWKMETRICS-273, HWKMETRICS-276, HWKMETRICS-292


Github Release:
https://github.com/hawkular/hawkular-metrics/releases/tag/0.8.0

JBoss Nexus Maven artifacts:
http://origin-repository.jboss.org/nexus/content/repositories/public/org/hawkular/metrics/

Jira release tracker:
https://issues.jboss.org/browse/HWKMETRICS/fixforversion/12328157

Hawkular Metrics Clients
  * Ruby: https://github.com/hawkular/hawkular-client-ruby
  * Python: https://github.com/hawkular/hawkular-client-python
  * Go: https://github.com/hawkular/hawkular-client-go


Hawkular Metrics 0.9.0 & Beyond:
1) Continuous agggregation - this has been a long term project goal and we are getting closer with refining the requirements and infrastructure
2) Improved docker and kubernetes support - this is a long term goal for the project
3) Improved tag support - to add bulk tag operations and tag queries
4) Improved aggregate downsampling for multiple metrics - the project has now a base with recently added stacking and uniform support; the goal is to expand the aggregation methods


A big "Thank you" goes to John Sanda, Thomas Segismont, Mike Thompson, Matt Wringe, Michael Burman, Libor Zoubek, Jirka Kremser, and Heiko Rupp for their project contributions.


Thank you,
Stefan Negrea

Software Engineer


From theute at redhat.com  Wed Oct 14 06:38:57 2015
From: theute at redhat.com (Thomas Heute)
Date: Wed, 14 Oct 2015 12:38:57 +0200
Subject: [Hawkular-dev] Hawkular Metrics 0.8.0 - Release & Beyond
In-Reply-To: <725703957.44011096.1444757119588.JavaMail.zimbra@redhat.com>
References: <1815555006.36803806.1443656015921.JavaMail.zimbra@redhat.com>
	<725703957.44011096.1444757119588.JavaMail.zimbra@redhat.com>
Message-ID: <CA+aN=Mqn3mFEPW48Wakj8zm8nD=oNwNYU5xJzpe_2tQqDAf44w@mail.gmail.com>

Congrats !

On Tue, Oct 13, 2015 at 7:25 PM, Stefan Negrea <snegrea at redhat.com> wrote:

> Hello Everybody,
>
> I am happy to announce release 0.8.0 of Hawkular Metrics. This short
> schedule release is anchored by major enhancements for metrics query
> aggregation, updated container support, and performance and stability
> enhancements.
>
>
> Here is a list of major changes in this release:
>
> 1) Counters
>   * Counter rates computations now avoid counter value resets
> (HWKMETRICS-218)
>   * Counter rates are now aligned with the actual counter data used to
> calculate the rate (HWKMETRICS-284)
>
> 2) Aggregate Metric Statistics
>   * Added support for aggregate statistics based on multiple metrics
>   * Gauges, counters, and counter rates are supported
>   * Two methods of aggregation are currently available
>     * uniform: data from multiple metrics is bucketed as originating from
> a single source and then statistics are computed on the entire set
>     * stacked: statistics are first computed for every matching metric and
> then those statistics are stacked (added)
>     * by default uniform statistics are enabled, stacking is enabled by
> stacked=true query parameter
>   * The end-points are /gauges/data , /counters/data, /counters/data/rate
>   * There is support to query by either tags or metrics ids; but not both
>   * Relevant JIRAs: HWKMETRICS-292, HWKMETRICS-263, HWKMETRICS-264
>
> 3) Data storage updates
>   * Schema changes will require rebuilding the database
>   * Reduced data storage footprint by limiting the size of metric type
> (HWKMETRICS-301)
>
> 4) Container support
>   * Secure connections are enabled between Hawkular Metrics and the
> Heapster sink (HWKMETRICS-217)
>   * cqlsh can be access directly from within the Cassandra docker
> (HWKMETRICS-260)
>   * Various updates to the Heapster sink to support latest Hawkular
> Metrics features: HWKMETRICS-285, HWKMETRICS-273, HWKMETRICS-276,
> HWKMETRICS-292
>
>
> Github Release:
> https://github.com/hawkular/hawkular-metrics/releases/tag/0.8.0
>
> JBoss Nexus Maven artifacts:
>
> http://origin-repository.jboss.org/nexus/content/repositories/public/org/hawkular/metrics/
>
> Jira release tracker:
> https://issues.jboss.org/browse/HWKMETRICS/fixforversion/12328157
>
> Hawkular Metrics Clients
>   * Ruby: https://github.com/hawkular/hawkular-client-ruby
>   * Python: https://github.com/hawkular/hawkular-client-python
>   * Go: https://github.com/hawkular/hawkular-client-go
>
>
> Hawkular Metrics 0.9.0 & Beyond:
> 1) Continuous agggregation - this has been a long term project goal and we
> are getting closer with refining the requirements and infrastructure
> 2) Improved docker and kubernetes support - this is a long term goal for
> the project
> 3) Improved tag support - to add bulk tag operations and tag queries
> 4) Improved aggregate downsampling for multiple metrics - the project has
> now a base with recently added stacking and uniform support; the goal is to
> expand the aggregation methods
>
>
> A big "Thank you" goes to John Sanda, Thomas Segismont, Mike Thompson,
> Matt Wringe, Michael Burman, Libor Zoubek, Jirka Kremser, and Heiko Rupp
> for their project contributions.
>
>
> Thank you,
> Stefan Negrea
>
> Software Engineer
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151014/9b37f681/attachment-0001.html 

From theute at redhat.com  Wed Oct 14 06:47:38 2015
From: theute at redhat.com (Thomas Heute)
Date: Wed, 14 Oct 2015 12:47:38 +0200
Subject: [Hawkular-dev] hawkular.org
Message-ID: <CA+aN=MpRj20c3GcnXmai+ioweEph_XPcV09sSOCXYAxtn8PvLw@mail.gmail.com>

I have proposed a rework of hawkular.org.
The idea is to make it more clear what features are offered. The actual
management console is pushed back a bit as this is less advanced than the
services such as metrics + alerts.

The PR is here, and can be previewed here for the next 3 days:
http://209.132.178.114:10108/

With Thomas's work on the REST API documentation, it should help people who
just need metrics+alerting(+inventory?+BTM?) to understand how they can use
Hawkular.

Now I think we also need a trimmed down package to download for those
users. Metrics+Alerts for now probably ? It could be named "Hawkular Core"
or "Hawkular Services", ideally "Hawkular Middleware Management Console ?
(JBMC upstream)" would build on this.

WDYT ?

Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151014/f7e562cb/attachment.html 

From gbrown at redhat.com  Wed Oct 14 07:17:23 2015
From: gbrown at redhat.com (Gary Brown)
Date: Wed, 14 Oct 2015 07:17:23 -0400 (EDT)
Subject: [Hawkular-dev] hawkular.org
In-Reply-To: <CA+aN=MpRj20c3GcnXmai+ioweEph_XPcV09sSOCXYAxtn8PvLw@mail.gmail.com>
References: <CA+aN=MpRj20c3GcnXmai+ioweEph_XPcV09sSOCXYAxtn8PvLw@mail.gmail.com>
Message-ID: <1533720335.36583783.1444821443022.JavaMail.zimbra@redhat.com>

+1, although I think we would need to restructure the Quick Start page around the features, and provide links from the features described on the Overview page to those quick start sections, to make it as easy as possible for someone interested in a particular feature to install and try it out.

Regards
Gary

----- Original Message -----
> I have proposed a rework of hawkular.org .
> The idea is to make it more clear what features are offered. The actual
> management console is pushed back a bit as this is less advanced than the
> services such as metrics + alerts.
> 
> The PR is here, and can be previewed here for the next 3 days:
> http://209.132.178.114:10108/
> 
> With Thomas's work on the REST API documentation, it should help people who
> just need metrics+alerting(+inventory?+BTM?) to understand how they can use
> Hawkular.
> 
> Now I think we also need a trimmed down package to download for those users.
> Metrics+Alerts for now probably ? It could be named "Hawkular Core" or
> "Hawkular Services", ideally "Hawkular Middleware Management Console ? (JBMC
> upstream)" would build on this.
> 
> WDYT ?
> 
> Thomas
> 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
> 

From theute at redhat.com  Wed Oct 14 07:47:49 2015
From: theute at redhat.com (Thomas Heute)
Date: Wed, 14 Oct 2015 13:47:49 +0200
Subject: [Hawkular-dev] hawkular.org
In-Reply-To: <1533720335.36583783.1444821443022.JavaMail.zimbra@redhat.com>
References: <CA+aN=MpRj20c3GcnXmai+ioweEph_XPcV09sSOCXYAxtn8PvLw@mail.gmail.com>
	<1533720335.36583783.1444821443022.JavaMail.zimbra@redhat.com>
Message-ID: <CA+aN=MrOLdvf1_xEun_3pegA3nvT+J_rTOdKTLoQYnoTPGMVOA@mail.gmail.com>

Agreed

On Wed, Oct 14, 2015 at 1:17 PM, Gary Brown <gbrown at redhat.com> wrote:

> +1, although I think we would need to restructure the Quick Start page
> around the features, and provide links from the features described on the
> Overview page to those quick start sections, to make it as easy as possible
> for someone interested in a particular feature to install and try it out.
>
> Regards
> Gary
>
> ----- Original Message -----
> > I have proposed a rework of hawkular.org .
> > The idea is to make it more clear what features are offered. The actual
> > management console is pushed back a bit as this is less advanced than the
> > services such as metrics + alerts.
> >
> > The PR is here, and can be previewed here for the next 3 days:
> > http://209.132.178.114:10108/
> >
> > With Thomas's work on the REST API documentation, it should help people
> who
> > just need metrics+alerting(+inventory?+BTM?) to understand how they can
> use
> > Hawkular.
> >
> > Now I think we also need a trimmed down package to download for those
> users.
> > Metrics+Alerts for now probably ? It could be named "Hawkular Core" or
> > "Hawkular Services", ideally "Hawkular Middleware Management Console ?
> (JBMC
> > upstream)" would build on this.
> >
> > WDYT ?
> >
> > Thomas
> >
> > _______________________________________________
> > 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/20151014/00fd8fe0/attachment.html 

From lkrejci at redhat.com  Wed Oct 14 16:29:29 2015
From: lkrejci at redhat.com (Lukas Krejci)
Date: Wed, 14 Oct 2015 22:29:29 +0200
Subject: [Hawkular-dev] Hawkular Inventory 0.6.0.Final released
Message-ID: <11378857.1JTEo0Jn29@localhost.localdomain>

Hi all,

I'd like to announce that we've just released Hawkular Inventory 0.6.0.Final.

This release doesn't have many new features, in fact it doesn't have any. This 
is purely a bugfix release but we decided to bump the minor version anyway 
because of the one big improvement we've made. The read queries should now be 
way more performant than they used to (up to an order of magnitude).

The release includes:
* improved logging of initialization failures
* adaptation to the new bus API introduced in Hawkular Bus 0.7.x
* more consistency checks on relationships of inventory entities
* streaming serialization should now work (still off by default) giving a 
slight speed boost to REST calls
* Many querying optimizations (collapsing of hops into a single index lookup, 
more indices on frequently queries properties, reducing the number of 
scenarios requiring backtracking in graph queries, filtering on mirrored 
immutable properties of vertices on edges) giving up to an order of magnitude 
speed up on read REST calls.
* Moved integration tests to the component so that we can properly test all 
scenarios conveniently.
* Fixes to support windows paths in configuration.

This release was made possible thanks to the contributions of the following 
fine gentlemen:

Jay Shaughnessy
Jirka Kremser
John Mazzitelli
Lukas Krejci
Pavol Loffay
Peter Palaga

Future releases already have some pull requests ready for inclusion - namely: 
* introduction of "name" as a first-class property on entities (instead of 
being just a free-form unindexed user-defined property), 
* move of feeds from environments directly under tenants, making it possible 
to easily move feeds between envs and requiring 1 less thing to remember by 
feeds (this will break clients but is hopefully worth it given the early stage 
of development of everything Hawkular).

Well under way is the development of "metadata packs", aka "global resource 
types". A feature that will enable feeds to very quickly check for presence of 
a set of resource, metric and operation types with precise properties 
(configurations, parameters, units, etc.) by computing their "content hash" 
locally and checking with inventory if a pack with such hash exists.

Thanks,

Lukas


From ppalaga at redhat.com  Thu Oct 15 05:12:29 2015
From: ppalaga at redhat.com (Peter Palaga)
Date: Thu, 15 Oct 2015 11:12:29 +0200
Subject: [Hawkular-dev] Hawkular Inventory 0.6.0.Final released
In-Reply-To: <11378857.1JTEo0Jn29@localhost.localdomain>
References: <11378857.1JTEo0Jn29@localhost.localdomain>
Message-ID: <561F6DFD.8080808@redhat.com>

Hi Luk??, what is streaming serialization? -- P

 > * streaming serialization should now work (still off by default)
 > giving a slight speed boost to REST calls


On 2015-10-14 22:29, Lukas Krejci wrote:
> Hi all,
>
> I'd like to announce that we've just released Hawkular Inventory 0.6.0.Final.
>
> This release doesn't have many new features, in fact it doesn't have any. This
> is purely a bugfix release but we decided to bump the minor version anyway
> because of the one big improvement we've made. The read queries should now be
> way more performant than they used to (up to an order of magnitude).
>
> The release includes:
> * improved logging of initialization failures
> * adaptation to the new bus API introduced in Hawkular Bus 0.7.x
> * more consistency checks on relationships of inventory entities
> * streaming serialization should now work (still off by default) giving a
> slight speed boost to REST calls
> * Many querying optimizations (collapsing of hops into a single index lookup,
> more indices on frequently queries properties, reducing the number of
> scenarios requiring backtracking in graph queries, filtering on mirrored
> immutable properties of vertices on edges) giving up to an order of magnitude
> speed up on read REST calls.
> * Moved integration tests to the component so that we can properly test all
> scenarios conveniently.
> * Fixes to support windows paths in configuration.
>
> This release was made possible thanks to the contributions of the following
> fine gentlemen:
>
> Jay Shaughnessy
> Jirka Kremser
> John Mazzitelli
> Lukas Krejci
> Pavol Loffay
> Peter Palaga
>
> Future releases already have some pull requests ready for inclusion - namely:
> * introduction of "name" as a first-class property on entities (instead of
> being just a free-form unindexed user-defined property),
> * move of feeds from environments directly under tenants, making it possible
> to easily move feeds between envs and requiring 1 less thing to remember by
> feeds (this will break clients but is hopefully worth it given the early stage
> of development of everything Hawkular).
>
> Well under way is the development of "metadata packs", aka "global resource
> types". A feature that will enable feeds to very quickly check for presence of
> a set of resource, metric and operation types with precise properties
> (configurations, parameters, units, etc.) by computing their "content hash"
> locally and checking with inventory if a pack with such hash exists.
>
> Thanks,
>
> Lukas
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>


From theute at redhat.com  Thu Oct 15 06:41:06 2015
From: theute at redhat.com (Thomas Heute)
Date: Thu, 15 Oct 2015 12:41:06 +0200
Subject: [Hawkular-dev] Hawkular Inventory 0.6.0.Final released
In-Reply-To: <11378857.1JTEo0Jn29@localhost.localdomain>
References: <11378857.1JTEo0Jn29@localhost.localdomain>
Message-ID: <CA+aN=MrjVrmzhLV0g6K67mR8phrfNARntC3XMczthW+BVKmg7w@mail.gmail.com>

Excellent news !

On Wed, Oct 14, 2015 at 10:29 PM, Lukas Krejci <lkrejci at redhat.com> wrote:

> Hi all,
>
> I'd like to announce that we've just released Hawkular Inventory
> 0.6.0.Final.
>
> This release doesn't have many new features, in fact it doesn't have any.
> This
> is purely a bugfix release but we decided to bump the minor version anyway
> because of the one big improvement we've made. The read queries should now
> be
> way more performant than they used to (up to an order of magnitude).
>
> The release includes:
> * improved logging of initialization failures
> * adaptation to the new bus API introduced in Hawkular Bus 0.7.x
> * more consistency checks on relationships of inventory entities
> * streaming serialization should now work (still off by default) giving a
> slight speed boost to REST calls
> * Many querying optimizations (collapsing of hops into a single index
> lookup,
> more indices on frequently queries properties, reducing the number of
> scenarios requiring backtracking in graph queries, filtering on mirrored
> immutable properties of vertices on edges) giving up to an order of
> magnitude
> speed up on read REST calls.
> * Moved integration tests to the component so that we can properly test all
> scenarios conveniently.
> * Fixes to support windows paths in configuration.
>
> This release was made possible thanks to the contributions of the following
> fine gentlemen:
>
> Jay Shaughnessy
> Jirka Kremser
> John Mazzitelli
> Lukas Krejci
> Pavol Loffay
> Peter Palaga
>
> Future releases already have some pull requests ready for inclusion -
> namely:
> * introduction of "name" as a first-class property on entities (instead of
> being just a free-form unindexed user-defined property),
> * move of feeds from environments directly under tenants, making it
> possible
> to easily move feeds between envs and requiring 1 less thing to remember by
> feeds (this will break clients but is hopefully worth it given the early
> stage
> of development of everything Hawkular).
>
> Well under way is the development of "metadata packs", aka "global resource
> types". A feature that will enable feeds to very quickly check for
> presence of
> a set of resource, metric and operation types with precise properties
> (configurations, parameters, units, etc.) by computing their "content hash"
> locally and checking with inventory if a pack with such hash exists.
>
> Thanks,
>
> Lukas
>
> _______________________________________________
> 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/20151015/0a408c77/attachment-0001.html 

From jsanda at redhat.com  Thu Oct 15 09:33:17 2015
From: jsanda at redhat.com (John Sanda)
Date: Thu, 15 Oct 2015 09:33:17 -0400
Subject: [Hawkular-dev] ActiveMQ and JMS
Message-ID: <6A8556E5-4A63-49E2-AA10-78B92CA980EF@redhat.com>

Hawkular uses ActiveMQ for JMS. I learned earlier this week that ActiveMQ implements JMS 1.1 but not 2.0 which has been out for some time and is in WildFly 9. JMS 2.0 has some nice changes including async sending of messages. In JMS 1.1 the client blocks until the server acknowledges successful delivery of the message. In 2.0 the sender can receive that acknowledgement asynchronously via a callback.

HornetQ is the default JMS provider in WildFly 8/9. If I am not mistaken part of the reason to go with ActiveMQ was due to the uncertainty around the future of HornetQ. HornetQ is now ActiveMQ Artemis[1] and will be the JMS provider in WlidFly 10haw. It does not look like ActiveMQ will implement JMS 2.0 any time soon which again, has been out for some time. Can/should we consider switching to HornetQ/Artemis?

[1] https://activemq.apache.org/artemis/ <https://activemq.apache.org/artemis/>


- John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151015/7347ce61/attachment.html 

From jkremser at redhat.com  Thu Oct 15 09:58:55 2015
From: jkremser at redhat.com (Jiri Kremser)
Date: Thu, 15 Oct 2015 09:58:55 -0400 (EDT)
Subject: [Hawkular-dev] ActiveMQ and JMS
In-Reply-To: <6A8556E5-4A63-49E2-AA10-78B92CA980EF@redhat.com>
References: <6A8556E5-4A63-49E2-AA10-78B92CA980EF@redhat.com>
Message-ID: <96930560.26394989.1444917535109.JavaMail.zimbra@redhat.com>

+1 on async messages
+1 on switching to Artemis, because afaik ActiveMQ is currently used as a common third part library + the resource adapter thing, while Artemis integration can be done in the standalone.xml (a subsystem - [1][2])

[1] http://javalibs.com/artifact/org.wildfly/wildfly-messaging-activemq
[2] http://git.io/vCXKy

jk

----- Original Message -----
| From: "John Sanda" <jsanda at redhat.com>
| To: "Discussions around Hawkular development" <hawkular-dev at lists.jboss.org>
| Sent: Thursday, 15 October, 2015 3:33:17 PM
| Subject: [Hawkular-dev] ActiveMQ and JMS
| 
| Hawkular uses ActiveMQ for JMS. I learned earlier this week that ActiveMQ
| implements JMS 1.1 but not 2.0 which has been out for some time and is in
| WildFly 9. JMS 2.0 has some nice changes including async sending of
| messages. In JMS 1.1 the client blocks until the server acknowledges
| successful delivery of the message. In 2.0 the sender can receive that
| acknowledgement asynchronously via a callback.
| 
| HornetQ is the default JMS provider in WildFly 8/9. If I am not mistaken part
| of the reason to go with ActiveMQ was due to the uncertainty around the
| future of HornetQ. HornetQ is now ActiveMQ Artemis[1] and will be the JMS
| provider in WlidFly 10haw. It does not look like ActiveMQ will implement JMS
| 2.0 any time soon which again, has been out for some time. Can/should we
| consider switching to HornetQ/Artemis?
| 
| [1] https://activemq.apache.org/artemis/
| 
| 
| - John
| 
| _______________________________________________
| hawkular-dev mailing list
| hawkular-dev at lists.jboss.org
| https://lists.jboss.org/mailman/listinfo/hawkular-dev
| 

From jkremser at redhat.com  Thu Oct 15 10:07:32 2015
From: jkremser at redhat.com (Jiri Kremser)
Date: Thu, 15 Oct 2015 10:07:32 -0400 (EDT)
Subject: [Hawkular-dev] Hawkular Inventory 0.6.0.Final released
In-Reply-To: <561F6DFD.8080808@redhat.com>
References: <11378857.1JTEo0Jn29@localhost.localdomain>
	<561F6DFD.8080808@redhat.com>
Message-ID: <1250114958.26398167.1444918052185.JavaMail.zimbra@redhat.com>

> what is streaming serialization

It's not probably officially called like that, but it means that instead of firstly serializing the objects into JSON and then returning the string as a response to the REST request, we return the InputStream so that clients start receiving the response sooner and it streams the content. Internally there is a thread pool executor that feeds the input stream in parallel using the Piped{Input|Output}Streams. It makes sense for longer responses, try 

curl -u jdoe:password http://localhost:8080/hawkular/inventory/graph

..for instance

From gcardoso at redhat.com  Thu Oct 15 13:15:53 2015
From: gcardoso at redhat.com (Gabriel Cardoso)
Date: Thu, 15 Oct 2015 14:15:53 -0300
Subject: [Hawkular-dev] Incremental UX - for Agile
Message-ID: <9CFAD95B-7451-48A6-9D3A-B22D9E1F96CC@redhat.com>

This post shows and inspiring perspective on working the design in agile context: Incremental UX. 

Basically they bring the concept of MVP down to the feature level. For sure we can benefit from some ideas.

https://medium.com/user-experience-design-1/incremental-ux-62aa1283b105


Gabriel Cardoso
UX designer @ Red Hat





From ppalaga at redhat.com  Thu Oct 15 16:45:44 2015
From: ppalaga at redhat.com (Peter Palaga)
Date: Thu, 15 Oct 2015 22:45:44 +0200
Subject: [Hawkular-dev] Travis cache pruning
In-Reply-To: <560E6076.9090509@redhat.com>
References: <560E6076.9090509@redhat.com>
Message-ID: <56201078.4080705@redhat.com>

Hi *,

I first thought, it would be possible to come up with a pruning strategy 
that would be able to remove artifacts from the local repo that were not 
used during the last build, but I have not find a way how to filter them 
out. I am not sure if any way of relying on file system dates would 
bring something useful because the cache is downloaded from persistent 
storage as an archive and unpacked just before the build which sets 
current dates (on directories at least).

The only solution I can think about is to delete the whole ~/.m2 once 
its size gets more than roughly the free space on the disk after the build.
Say that the space available to the build even before downloading any 
cache or sources is 5 GB.
Further, say that the build tree after the build spends say 200 MB.
5 GB minus 200 MB is 4.8 GB
4.8 GB / 2 = 2.4 GB would be the size we could allow as the max cache 
size. 2.4 GB free space must be enough to pack the 2.4 GB of data to an 
archive that will be uploaded to the persistent storage.

Does anybody have a better idea?

Thanks,

Peter

On 2015-10-02 12:46, Peter Palaga wrote:
> Hi *,
>
> because we had no cache pruning in place, the cached ~/.m2/repository in
> hk main became too bing. As a consequence of that, when Travis attempted
> to zip the cached folder, the cache archive made the disk full and not
> only that the cache could not be uploaded outside of the transient
> docker container, also all subsequent tasks (deployment of SNAPSHOTs)
> failed.
>
> I could not find a working pruning script quickly enough. To solve the
> problem temporarily at least, I deleted the cache manually under
> https://travis-ci.org/hawkular/hawkular/caches
>
> Best,
>
> Peter
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>


From mazz at redhat.com  Thu Oct 15 18:18:49 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Thu, 15 Oct 2015 18:18:49 -0400 (EDT)
Subject: [Hawkular-dev] some new agent features
In-Reply-To: <2017231076.32195510.1444946530424.JavaMail.zimbra@redhat.com>
Message-ID: <2008517076.32197921.1444947529940.JavaMail.zimbra@redhat.com>

Just wanted to blast out a message about some new wildfly agent features.

1) Agent now supports secure communications between itself and any of its managed WildFly servers. I documented how to enable security in the management interface of WildFly here:

https://github.com/hawkular/hawkular.github.io/blob/pages/src/main/jbake/content/docs/user/secure-comm.adoc#securing-communications-between-agent-and-a-managed-wildfly-server

2) Agent now supports monitoring JMX resources via Jolokia interface.

The agent now can collect JMX metrics and availability data and can inventory JMX resources in the same manner as it can with DMR resources using the Jolokia interface (Jolokia is a very nice REST interface to JMX). Just as we have <metric-dmr>, <avail-dmr>, <resource-type-dmr>, <remote-dmr>, and related DMR settings in the agent subsystem, we now have <metric-jmx>, <avail-jmx>, <resource-type-jmx>, <remote-jmx> settings as well. So the agent can be given metadata that tells it what to do. As with remote WF servers, the agent also supports secure comm to the remote jolokia JMX server.

There are a few things currently on the TODO for the agent:

1) utilize the new inventory "name" attribute - they now have "name" as a first-class setting - I need to see what the agent has to do to use it
2) utilize the inventory's "operation" metadata - I believe operations are now first class concepts in inventory - I need to figure out how to populate it
3) provide a mechanism for the agent to detect runtime changes to inventory. Right now, after the agent does its initial inventory scan, that's it. The inventory is fixed, all resource configuration is fixed, and all we do is collect metrics. The caveat is that if someone deploys a new app or adds a new JDBC driver, we force a new scan. We need a way to detect new resources in inventory (and old resources removed from inventory) and we need a way to detect changes to resource config. This should work for both DMR and JMX inventory items.
4) Need a way to consume wildfly notifications that other subsystems emit and figure out how to send that to a hawkualr events subsystem.
5) Peter is implementing/has implemented the JDBC driver CRUD and datasource CRUD, gonna see how easy it is to implement reload.

I'm sure I'm forgetting something, but .. that's what I remember.

From tsegismo at redhat.com  Fri Oct 16 06:19:32 2015
From: tsegismo at redhat.com (Thomas Segismont)
Date: Fri, 16 Oct 2015 12:19:32 +0200
Subject: [Hawkular-dev] HAWKULAR-698 Upgrade to Hawkular Metrics Component
Message-ID: <5620CF34.8000300@redhat.com>

Hi everyone,

The pull request for $subject is ready:
https://github.com/hawkular/hawkular/pull/569/files

With these changes, Metrics component will publish inserted data points 
on the bus.

Once the PR is merged, the agent can be updated as well.

Regards,
Thomas

From jpkroehling at redhat.com  Fri Oct 16 10:45:34 2015
From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=)
Date: Fri, 16 Oct 2015 16:45:34 +0200
Subject: [Hawkular-dev] Funny compilation issue on Hawkular? Downgrade to
 JDK 1.8.0_51 for a minute
Message-ID: <56210D8E.5000000@redhat.com>

Team,

We just had a case today about Hawkular failing to build on my machine 
after updating to a specific version of the Agent. While *this* specific 
issue is going away with a change from Peter, you might still see this 
for a while.

So, if you see a build error on Hawkular related to a compilation issue 
for 
agent/hawkular-dmr-client/src/main/java/org/hawkular/dmr/api/OperationBuilder.java 
, you can just:

- switch to Oracle's or OpenJDK's 1.8.0_51
- cd ~/.m2/dependency-sources/agent
- mvn clean install
- build Hawkular (with whatever JDK you want)

The third step will build the required version of Agent inside srcdep's 
cache directory, effectively bypassing the issue.

- Juca.

From mazz at redhat.com  Sun Oct 18 06:42:57 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Sun, 18 Oct 2015 06:42:57 -0400 (EDT)
Subject: [Hawkular-dev] agent i-test "failures" - false negatives
In-Reply-To: <hawkular/hawkular-agent/pull/87/c148995009@github.com>
References: <hawkular/hawkular-agent/pull/87@github.com>
	<hawkular/hawkular-agent/pull/87/c148995009@github.com>
Message-ID: <1964241910.33090878.1445164977554.JavaMail.zimbra@redhat.com>

We need to fix those transient errors, I'm seeing this a lot with the agent builds. Seems to fail 50% of the time, pass 50% of the time.

Peter - is there anything we can do to fix the i-tests? Otherwise, I recommend we disable them in travis - false negatives are bad because I am afraid to merge PRs when I see them. But most times, the failures aren't really failures and the code is good. I normally just kick off another build - wait the N minutes it takes for travis to run, see it go green, then merge. (just like what heiko is saying happened to him).

----- Forwarded Message -----
From: "Heiko W. Rupp" <notifications at github.com>
To: "hawkular/hawkular-agent" <hawkular-agent at noreply.github.com>
Sent: Sunday, October 18, 2015 5:30:00 AM
Subject: Re: [hawkular-agent] HAWKULAR-604 The message field of ExecuteOperationResponse should not? (#87)

@josejulio Thank you for your contribution - the Travis failure seems transient - I've kicked of a 2nd build that passes. I am sure @ppalaga will have a look at your patch on Monday.


From lkrejci at redhat.com  Mon Oct 19 02:58:30 2015
From: lkrejci at redhat.com (Lukas Krejci)
Date: Mon, 19 Oct 2015 08:58:30 +0200
Subject: [Hawkular-dev] Funny compilation issue on Hawkular? Downgrade
	to JDK 1.8.0_51 for a minute
In-Reply-To: <56210D8E.5000000@redhat.com>
References: <56210D8E.5000000@redhat.com>
Message-ID: <3570538.l7mGIxsVo4@localhost.localdomain>

Note that Travis still uses 1.8.0_31-b13 so make sure the code compiles with 
that version, too.

On Friday, October 16, 2015 16:45:34 Juraci Paix?o Kr?hling wrote:
> Team,
> 
> We just had a case today about Hawkular failing to build on my machine
> after updating to a specific version of the Agent. While *this* specific
> issue is going away with a change from Peter, you might still see this
> for a while.
> 
> So, if you see a build error on Hawkular related to a compilation issue
> for
> agent/hawkular-dmr-client/src/main/java/org/hawkular/dmr/api/OperationBuilde
> r.java , you can just:
> 
> - switch to Oracle's or OpenJDK's 1.8.0_51
> - cd ~/.m2/dependency-sources/agent
> - mvn clean install
> - build Hawkular (with whatever JDK you want)
> 
> The third step will build the required version of Agent inside srcdep's
> cache directory, effectively bypassing the issue.
> 
> - Juca.
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev



From ppalaga at redhat.com  Mon Oct 19 05:10:26 2015
From: ppalaga at redhat.com (Peter Palaga)
Date: Mon, 19 Oct 2015 11:10:26 +0200
Subject: [Hawkular-dev] agent i-test "failures" - false negatives
In-Reply-To: <1964241910.33090878.1445164977554.JavaMail.zimbra@redhat.com>
References: <hawkular/hawkular-agent/pull/87@github.com>
	<hawkular/hawkular-agent/pull/87/c148995009@github.com>
	<1964241910.33090878.1445164977554.JavaMail.zimbra@redhat.com>
Message-ID: <5624B382.4020903@redhat.com>

Yes, that needs to be fixed. Do you happen to have a link to a travis 
log that show the failure? -- P

On 2015-10-18 12:42, John Mazzitelli wrote:
> We need to fix those transient errors, I'm seeing this a lot with the agent builds. Seems to fail 50% of the time, pass 50% of the time.
>
> Peter - is there anything we can do to fix the i-tests? Otherwise, I recommend we disable them in travis - false negatives are bad because I am afraid to merge PRs when I see them. But most times, the failures aren't really failures and the code is good. I normally just kick off another build - wait the N minutes it takes for travis to run, see it go green, then merge. (just like what heiko is saying happened to him).
>
> ----- Forwarded Message -----
> From: "Heiko W. Rupp" <notifications at github.com>
> To: "hawkular/hawkular-agent" <hawkular-agent at noreply.github.com>
> Sent: Sunday, October 18, 2015 5:30:00 AM
> Subject: Re: [hawkular-agent] HAWKULAR-604 The message field of ExecuteOperationResponse should not? (#87)
>
> @josejulio Thank you for your contribution - the Travis failure seems transient - I've kicked of a 2nd build that passes. I am sure @ppalaga will have a look at your patch on Monday.
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>


From mfoley at redhat.com  Mon Oct 19 09:05:27 2015
From: mfoley at redhat.com (Michael Foley)
Date: Mon, 19 Oct 2015 09:05:27 -0400 (EDT)
Subject: [Hawkular-dev] Review High-level Hawkular MS6 Test Plan
Message-ID: <617392684.76015138.1445259927227.JavaMail.zimbra@redhat.com>

The following is a new meeting request:

Subject: Review High-level Hawkular MS6 Test Plan 
Organizer: "Michael Foley" <mfoley at redhat.com> 

Location: bluejeans   http://www.bluejeans.com/mfoley51 
Time: Friday, October 23, 2015, 9:00:00 AM - 9:30:00 AM GMT -05:00 US/Canada Eastern
 
Required: jon-qa-list at redhat.com 
Optional: jboss-on-team at redhat.com; hawkular-dev at lists.jboss.org 

*~*~*~*~*~*~*~*~*~*

Hi, 

The developer demo for MS6 is scheduled for October 22, so let's today review how we will test and qualify MS6. 

I have an etherpad here that we can use a strawman -->> http://pad.engineering.redhat.com/HawkularMS6TestPlanning 

Regards, 

Michael Foley 
QE Supervisor, Middleware QE 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151019/94b4f7ed/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 3756 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151019/94b4f7ed/attachment.bin 

From l_roitman at yahoo.com  Mon Oct 19 12:44:44 2015
From: l_roitman at yahoo.com (Luba Roitman)
Date: Mon, 19 Oct 2015 16:44:44 +0000 (UTC)
Subject: [Hawkular-dev] Problems installing Alpha 5 on Windows
In-Reply-To: <156179456.2756309.1445269950723.JavaMail.yahoo@mail.yahoo.com>
References: <156179456.2756309.1445269950723.JavaMail.yahoo@mail.yahoo.com>
	<156179456.2756309.1445269950723.JavaMail.yahoo@mail.yahoo.com>
Message-ID: <1251329922.2778990.1445273084070.JavaMail.yahoo@mail.yahoo.com>

Hi,?
I am having problems installing Hawkular Alpha 5 on Windows, but before I delve into describing them, I am wondering as to whether Docker install option is going to be available soon? That would indeed be helpful.
As for the Windows install problem, after I downloaded Alpha 5 and run standalone.bat I have the following exceptions in the server.log (excerpts here, more stacktrace in the end of the email)
jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service
Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind
And then2015-10-18 13:01:53,226 WARN ?[org.hawkular.inventory.cdi] (ServerService Thread Pool -- 68) HAWKINV003501: Inventory backend failed to initialize in an attempt 5 of 5.2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 68) MSC000001: Failed to start service jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instanceCaused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory.Caused by: java.lang.IllegalStateException: Could not initialize inventory.

Do you think these two could be connected? I can't think of any source for binding address conflict, I start Hawkular the first thing after the laptop restart, so don't run any local http servers. It is also not clear what is the reason for inventory initialization problem, the log doesn't indicate any wrong before throwing error.
I am running Windows 8.1 64bit
Would appreciate any input!
Respectfully,?Luba Roitman.
-------------2015-10-18 13:01:33,144 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:269) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) 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)Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind at org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:160) at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:235) ... 5 moreCaused by: java.net.BindException: Address already in use: bind at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Net.java:433)------------------
2015-10-18 13:01:53,226 WARN ?[org.hawkular.inventory.cdi] (ServerService Thread Pool -- 68) HAWKINV003501: Inventory backend failed to initialize in an attempt 5 of 5.2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 68) MSC000001: Failed to start service jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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) at org.jboss.threads.JBossThread.run(JBossThread.java:320)Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134) at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:122) at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:136) at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) ... 6 moreCaused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory. at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:187) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:277) at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:349) at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) ... 11 moreCaused by: java.lang.IllegalStateException: Could not initialize inventory. at org.hawkular.inventory.cdi.OfficialInventoryProducer.initInventory(OfficialInventoryProducer.java:115) at org.hawkular.inventory.cdi.OfficialInventoryProducer.getInventory(OfficialInventoryProducer.java:64) 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:497) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:88) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:78) at org.jboss.weld.injection.producer.ProducerMethodProducer.produce(ProducerMethodProducer.java:95) at org.jboss.weld.injection.producer.AbstractMemberProducer.produce(AbstractMemberProducer.java:167) at org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:183) at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101) at org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141) at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:761) at org.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:861) at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:92) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:375) at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:386) at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:71) at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:73) at org.jboss.weld.injection.producer.ejb.SessionBeanInjectionTarget.inject(SessionBeanInjectionTarget.java:140) at org.jboss.as.weld.injection.WeldInjectionContext.inject(WeldInjectionContext.java:39) at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:51) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:100) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275) ... 27 more
2015-10-18 13:01:54,251 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([? ? ("core-service" => "management"),? ? ("management-interface" => "http-interface")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.serverManagement.controller.management.http" => "org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service? ? Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind? ? Caused by: java.net.BindException: Address already in use: bind"}}2015-10-18 13:01:54,251 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "hawkular-inventory-dist.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance? ? Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance? ? Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory.? ? Caused by: java.lang.IllegalStateException: Could not initialize inventory."}}2015-10-18 13:01:54,251 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "hawkular-metrics-api-jaxrs.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance? ? Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance? ? Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory.? ? Caused by: java.lang.IllegalStateException: Could not initialize inventory."}}2015-10-18 13:01:54,251 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "hawkular-pinger.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance? ? Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance? ? Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory.? ? Caused by: java.lang.IllegalStateException: Could not initialize inventory."}}2015-10-18 13:01:54,267 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "hawkular-redhat-access-integration-backend.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance? ? Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance? ? Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory.? ? Caused by: java.lang.IllegalStateException: Could not initialize inventory."}}



  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151019/c6bca34c/attachment-0001.html 

From lkrejci at redhat.com  Mon Oct 19 13:01:58 2015
From: lkrejci at redhat.com (Lukas Krejci)
Date: Mon, 19 Oct 2015 19:01:58 +0200
Subject: [Hawkular-dev] Problems installing Alpha 5 on Windows
In-Reply-To: <1251329922.2778990.1445273084070.JavaMail.yahoo@mail.yahoo.com>
References: <156179456.2756309.1445269950723.JavaMail.yahoo@mail.yahoo.com>
	<1251329922.2778990.1445273084070.JavaMail.yahoo@mail.yahoo.com>
Message-ID: <5276773.tlBKnxjgBE@localhost.localdomain>

Hi,

They could indeed be connected but it's hard to say. Inventory in Alpha6 will 
emit more info in such situations but unfortunately in Alpha5 there's no way 
of getting more info about inventory init failures from the logs.

As for the ports that need to be open, I believe we need 8080, 9042 and 9160. 
The former is for the http interface and the latter two for Cassandra and 
Cassandra RPC servers.

On Monday, October 19, 2015 16:44:44 Luba Roitman wrote:
> Hi, 
> I am having problems installing Hawkular Alpha 5 on Windows, but before I
> delve into describing them, I am wondering as to whether Docker install
> option is going to be available soon? That would indeed be helpful. As for
> the Windows install problem, after I downloaded Alpha 5 and run
> standalone.bat I have the following exceptions in the server.log (excerpts
> here, more stacktrace in the end of the email)
> jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to
> start the http-interface service Caused by: java.lang.RuntimeException:
> java.net.BindException: Address already in use: bind And then2015-10-18
> 13:01:53,226 WARN  [org.hawkular.inventory.cdi] (ServerService Thread Pool
> -- 68) HAWKINV003501: Inventory backend failed to initialize in an attempt
> 5 of 5.2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail]
> (ServerService Thread Pool -- 68) MSC000001: Failed to start service
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDI
> Publisher.START: org.jboss.msc.service.StartException in service
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDI
> Publisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instanceCaused by: javax.ejb.EJBException:
> java.lang.IllegalStateException: Could not initialize inventory.Caused by:
> java.lang.IllegalStateException: Could not initialize inventory.
> 
> Do you think these two could be connected? I can't think of any source for
> binding address conflict, I start Hawkular the first thing after the laptop
> restart, so don't run any local http servers. It is also not clear what is
> the reason for inventory initialization problem, the log doesn't indicate
> any wrong before throwing error. I am running Windows 8.1 64bit
> Would appreciate any input!
> Respectfully, Luba Roitman.
> -------------2015-10-18 13:01:33,144 ERROR [org.jboss.msc.service.fail] (MSC
> service thread 1-4) MSC000001: Failed to start service
> jboss.serverManagement.controller.management.http:
> org.jboss.msc.service.StartException in service
> jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to
> start the http-interface service at
> org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpMa
> nagementService.java:269) at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceC
> ontrollerImpl.java:1948) at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceController
> Impl.java:1881) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1
> 142) at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
> 617) at java.lang.Thread.run(Thread.java:745)Caused by:
> java.lang.RuntimeException: java.net.BindException: Address already in use:
> bind at
> org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpSe
> rver.java:160) at
> org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpMa
> nagementService.java:235) ... 5 moreCaused by: java.net.BindException:
> Address already in use: bind at sun.nio.ch.Net.bind0(Native Method) at
> sun.nio.ch.Net.bind(Net.java:433)------------------ 2015-10-18 13:01:53,226
> WARN  [org.hawkular.inventory.cdi] (ServerService Thread Pool -- 68)
> HAWKINV003501: Inventory backend failed to initialize in an attempt 5 of
> 5.2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail] (ServerService
> Thread Pool -- 68) MSC000001: Failed to start service
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDI
> Publisher.START: org.jboss.msc.service.StartException in service
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDI
> Publisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instance at
> org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService
> .java:57) at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at
> java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1
> 142) at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
> 617) at java.lang.Thread.run(Thread.java:745) at
> org.jboss.threads.JBossThread.run(JBossThread.java:320)Caused by:
> java.lang.IllegalStateException: WFLYEE0042: Failed to construct component
> instance at
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicCo
> mponent.java:163) at
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicCo
> mponent.java:134) at
> org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java
> :88) at
> org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstan
> ce(SingletonComponent.java:122) at
> org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonCom
> ponent.java:136) at
> org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService
> .java:54) ... 6 moreCaused by: javax.ejb.EJBException:
> java.lang.IllegalStateException: Could not initialize inventory. at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxIntercept
> or.java:187) at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:2
> 77) at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:349
> ) at
> org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleC
> MTTxInterceptor.java:66) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocati
> on(WeldInjectionContextInterceptor.java:43) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextIntercepto
> r.processInvocation(CurrentInvocationContextInterceptor.java:41) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(C
> oncurrentContextInterceptor.java:45) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(Contex
> tClassLoaderInterceptor.java:64) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at
> org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(Pr
> ivilegedWithCombinerInterceptor.java:80) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedIntercepto
> r.java:61) at
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicCo
> mponent.java:161) ... 11 moreCaused by: java.lang.IllegalStateException:
> Could not initialize inventory. at
> org.hawkular.inventory.cdi.OfficialInventoryProducer.initInventory(Official
> InventoryProducer.java:115) at
> org.hawkular.inventory.cdi.OfficialInventoryProducer.getInventory(OfficialI
> nventoryProducer.java:64) at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:6
> 2) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
> l.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at
> org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInje
> ctionPoint.java:88) at
> org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInje
> ctionPoint.java:78) at
> org.jboss.weld.injection.producer.ProducerMethodProducer.produce(ProducerMe
> thodProducer.java:95) at
> org.jboss.weld.injection.producer.AbstractMemberProducer.produce(AbstractMe
> mberProducer.java:167) at
> org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:1
> 83) at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
> at
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStr
> ategy.get(ContextualInstanceStrategy.java:101) at
> org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualI
> nstanceStrategy.get(ContextualInstanceStrategy.java:141) at
> org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) at
> org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:76
> 1) at
> org.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerIm
> pl.java:861) at
> org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.jav
> a:92) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:375) at
> org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:386) at
> org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector
> .java:71) at
> org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java
> :48) at
> org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.ja
> va:73) at
> org.jboss.weld.injection.producer.ejb.SessionBeanInjectionTarget.inject(Ses
> sionBeanInjectionTarget.java:140) at
> org.jboss.as.weld.injection.WeldInjectionContext.inject(WeldInjectionContex
> t.java:39) at
> org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(Weld
> InjectionInterceptor.java:51) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvoca
> tion(AroundConstructInterceptorFactory.java:28) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvo
> cation(WeldInterceptorInjectionInterceptor.java:56) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr
> 299BindingsCreateInterceptor.java:100) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(Nam
> espaceContextInterceptor.java:50) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:2
> 75) ... 27 more 2015-10-18 13:01:54,251 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("add") failed - address: ([    ("core-service" =>
> "management"),    ("management-interface" => "http-interface")]) - failure
> description: {"WFLYCTL0080: Failed services" =>
> {"jboss.serverManagement.controller.management.http" =>
> "org.jboss.msc.service.StartException in service
> jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to
> start the http-interface service    Caused by: java.lang.RuntimeException:
> java.net.BindException: Address already in use: bind    Caused by:
> java.net.BindException: Address already in use: bind"}}2015-10-18
> 13:01:54,251 ERROR [org.jboss.as.controller.management-operation]
> (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address:
> ([("deployment" => "hawkular-inventory-dist.war")]) - failure description:
> {"WFLYCTL0080: Failed services" =>
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.Inventory
> JNDIPublisher.START" => "org.jboss.msc.service.StartException in service
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJN
> DIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instance    Caused by: java.lang.IllegalStateException:
> WFLYEE0042: Failed to construct component instance    Caused by:
> javax.ejb.EJBException: java.lang.IllegalStateException: Could not
> initialize inventory.    Caused by: java.lang.IllegalStateException: Could
> not initialize inventory."}}2015-10-18 13:01:54,251 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("add") failed - address: ([("deployment" =>
> "hawkular-metrics-api-jaxrs.war")]) - failure description: {"WFLYCTL0080:
> Failed services" =>
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.Inventory
> JNDIPublisher.START" => "org.jboss.msc.service.StartException in service
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJN
> DIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instance    Caused by: java.lang.IllegalStateException:
> WFLYEE0042: Failed to construct component instance    Caused by:
> javax.ejb.EJBException: java.lang.IllegalStateException: Could not
> initialize inventory.    Caused by: java.lang.IllegalStateException: Could
> not initialize inventory."}}2015-10-18 13:01:54,251 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("add") failed - address: ([("deployment" =>
> "hawkular-pinger.war")]) - failure description: {"WFLYCTL0080: Failed
> services" =>
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.Inventory
> JNDIPublisher.START" => "org.jboss.msc.service.StartException in service
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJN
> DIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instance    Caused by: java.lang.IllegalStateException:
> WFLYEE0042: Failed to construct component instance    Caused by:
> javax.ejb.EJBException: java.lang.IllegalStateException: Could not
> initialize inventory.    Caused by: java.lang.IllegalStateException: Could
> not initialize inventory."}}2015-10-18 13:01:54,267 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("add") failed - address: ([("deployment" =>
> "hawkular-redhat-access-integration-backend.war")]) - failure description:
> {"WFLYCTL0080: Failed services" =>
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.Inventory
> JNDIPublisher.START" => "org.jboss.msc.service.StartException in service
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJN
> DIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instance    Caused by: java.lang.IllegalStateException:
> WFLYEE0042: Failed to construct component instance    Caused by:
> javax.ejb.EJBException: java.lang.IllegalStateException: Could not
> initialize inventory.    Caused by: java.lang.IllegalStateException: Could
> not initialize inventory."}}


From jshaughn at redhat.com  Mon Oct 19 13:29:19 2015
From: jshaughn at redhat.com (Jay Shaughnessy)
Date: Mon, 19 Oct 2015 13:29:19 -0400
Subject: [Hawkular-dev] Problems installing Alpha 5 on Windows
In-Reply-To: <1251329922.2778990.1445273084070.JavaMail.yahoo@mail.yahoo.com>
References: <156179456.2756309.1445269950723.JavaMail.yahoo@mail.yahoo.com>
	<156179456.2756309.1445269950723.JavaMail.yahoo@mail.yahoo.com>
	<1251329922.2778990.1445273084070.JavaMail.yahoo@mail.yahoo.com>
Message-ID: <5625286F.4080201@redhat.com>


There are two known issues in M5 on Windows. Both are path related and 
one of them kills the inventory deployment.  Both are fixed in M6, due 
out this week.
  For M5 you need to do some work if you want to run on windows:

You must replace occurrences of ${jboss.server.data.dir} 1) with the 
explicit Windows path, using *FORWARD SLASHES*.   For example, on my box 
it's:

c:/work/hawkular/dist/target/hawkular1.0.0.Alpha6-SNAPSHOT/hawkular-1.0.0.Alpha6-SNAPSHOT/standalone/data

First Occurence:

<HawkularRoot>/standalone/configuration/standalone.xml

Second Occurence:

   This one is more difficult.  You need to unzip:

<HawkularRoot>\modules\org\hawkular\nest\main\deployments\hawkular-inventory-dist.war

Then, edit hawkular-inventory.properties, make the change, and rezip.

I *think* it will then work for you.

In M6 you should be able to just do the following.  On the command line 
start up like this:

   ...\bin>standalone.bat 
-Dorg.hawkular.data.dir=<YourDataDirWithForwardSlashes>



On 10/19/2015 12:44 PM, Luba Roitman wrote:
> Hi,
> I am having problems installing Hawkular Alpha 5 on Windows, but 
> before I delve into describing them, I am wondering as to whether 
> Docker install option is going to be available soon? That would indeed 
> be helpful.
>
> As for the Windows install problem, after I downloaded Alpha 5 and run 
> standalone.bat I have the following exceptions in the server.log 
> (excerpts here, more stacktrace in the end of the email)
>
> jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed 
> to start the http-interface service
> Caused by: java.lang.RuntimeException: java.net.BindException: Address 
> already in use: bind
>
> And then
> 2015-10-18 13:01:53,226 WARN  [org.hawkular.inventory.cdi] 
> (ServerService Thread Pool -- 68) HAWKINV003501: Inventory backend 
> failed to initialize in an attempt 5 of 5.
> 2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail] 
> (ServerService Thread Pool -- 68) MSC000001: Failed to start service 
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START: 
> org.jboss.msc.service.StartException in service 
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START: 
> java.lang.IllegalStateException: WFLYEE0042: Failed to construct 
> component instance
> Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: 
> Could not initialize inventory.
> Caused by: java.lang.IllegalStateException: Could not initialize 
> inventory.
>
>
> Do you think these two could be connected? I can't think of any source 
> for binding address conflict, I start Hawkular the first thing after 
> the laptop restart, so don't run any local http servers. It is also 
> not clear what is the reason for inventory initialization problem, the 
> log doesn't indicate any wrong before throwing error.
>
> I am running Windows 8.1 64bit
>
> Would appreciate any input!
>
> Respectfully,
> Luba Roitman.
>
> -------------
> 2015-10-18 13:01:33,144 ERROR [org.jboss.msc.service.fail] (MSC 
> service thread 1-4) MSC000001: Failed to start service 
> jboss.serverManagement.controller.management.http: 
> org.jboss.msc.service.StartException in service 
> jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed 
> to start the http-interface service
> at 
> org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:269)
> at 
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at 
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> 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)
> Caused by: java.lang.RuntimeException: java.net.BindException: Address 
> already in use: bind
> at 
> org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:160)
> at 
> org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:235)
> ... 5 more
> Caused by: java.net.BindException: Address already in use: bind
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> ------------------
>
> 2015-10-18 13:01:53,226 WARN  [org.hawkular.inventory.cdi] 
> (ServerService Thread Pool -- 68) HAWKINV003501: Inventory backend 
> failed to initialize in an attempt 5 of 5.
> 2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail] 
> (ServerService Thread Pool -- 68) MSC000001: Failed to start service 
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START: 
> org.jboss.msc.service.StartException in service 
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START: 
> java.lang.IllegalStateException: WFLYEE0042: Failed to construct 
> component instance
> at 
> org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to 
> construct component instance
> at 
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163)
> at 
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134)
> at 
> org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88)
> at 
> org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:122)
> at 
> org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:136)
> at 
> org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
> ... 6 more
> Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: 
> Could not initialize inventory.
> at 
> org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:187)
> at 
> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:277)
> at 
> org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:349)
> at 
> org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66)
> at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at 
> org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43)
> at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at 
> org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at 
> org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
> at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at 
> org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
> at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at 
> org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> at 
> org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
> at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at 
> org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)at 
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161)
> ... 11 more
> Caused by: java.lang.IllegalStateException: Could not initialize 
> inventory.
> at 
> org.hawkular.inventory.cdi.OfficialInventoryProducer.initInventory(OfficialInventoryProducer.java:115)
> at 
> org.hawkular.inventory.cdi.OfficialInventoryProducer.getInventory(OfficialInventoryProducer.java:64)
> 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:497)
> at 
> org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:88)
> at 
> org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:78)
> at 
> org.jboss.weld.injection.producer.ProducerMethodProducer.produce(ProducerMethodProducer.java:95)
> at 
> org.jboss.weld.injection.producer.AbstractMemberProducer.produce(AbstractMemberProducer.java:167)
> at 
> org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:183)
> at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
> at 
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)
> at 
> org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141)
> at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
> at 
> org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:761)
> at 
> org.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:861)
> at 
> org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:92)
> at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:375)
> at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:386)
> at 
> org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:71)
> at 
> org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48)
> at 
> org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:73)
> at 
> org.jboss.weld.injection.producer.ejb.SessionBeanInjectionTarget.inject(SessionBeanInjectionTarget.java:140)
> at 
> org.jboss.as.weld.injection.WeldInjectionContext.inject(WeldInjectionContext.java:39)
> at 
> org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:51)
> at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at 
> org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28)
> at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at 
> org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56)
> at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at 
> org.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:100)
> at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at 
> org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at 
> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)
> ... 27 more
>
> 2015-10-18 13:01:54,251 ERROR 
> [org.jboss.as.controller.management-operation] (Controller Boot 
> Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]) - failure description: {"WFLYCTL0080: Failed services" => 
> {"jboss.serverManagement.controller.management.http" => 
> "org.jboss.msc.service.StartException in service 
> jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed 
> to start the http-interface service
>     Caused by: java.lang.RuntimeException: java.net.BindException: 
> Address already in use: bind
>     Caused by: java.net.BindException: Address already in use: bind"}}
> 2015-10-18 13:01:54,251 ERROR 
> [org.jboss.as.controller.management-operation] (Controller Boot 
> Thread) WFLYCTL0013: Operation ("add") failed - address: 
> ([("deployment" => "hawkular-inventory-dist.war")]) - failure 
> description: {"WFLYCTL0080: Failed services" => 
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START" 
> => "org.jboss.msc.service.StartException in service 
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START: 
> java.lang.IllegalStateException: WFLYEE0042: Failed to construct 
> component instance
>     Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to 
> construct component instance
>     Caused by: javax.ejb.EJBException: 
> java.lang.IllegalStateException: Could not initialize inventory.
>     Caused by: java.lang.IllegalStateException: Could not initialize 
> inventory."}}
> 2015-10-18 13:01:54,251 ERROR 
> [org.jboss.as.controller.management-operation] (Controller Boot 
> Thread) WFLYCTL0013: Operation ("add") failed - address: 
> ([("deployment" => "hawkular-metrics-api-jaxrs.war")]) - failure 
> description: {"WFLYCTL0080: Failed services" => 
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START" 
> => "org.jboss.msc.service.StartException in service 
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START: 
> java.lang.IllegalStateException: WFLYEE0042: Failed to construct 
> component instance
>     Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to 
> construct component instance
>     Caused by: javax.ejb.EJBException: 
> java.lang.IllegalStateException: Could not initialize inventory.
>     Caused by: java.lang.IllegalStateException: Could not initialize 
> inventory."}}
> 2015-10-18 13:01:54,251 ERROR 
> [org.jboss.as.controller.management-operation] (Controller Boot 
> Thread) WFLYCTL0013: Operation ("add") failed - address: 
> ([("deployment" => "hawkular-pinger.war")]) - failure description: 
> {"WFLYCTL0080: Failed services" => 
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START" 
> => "org.jboss.msc.service.StartException in service 
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START: 
> java.lang.IllegalStateException: WFLYEE0042: Failed to construct 
> component instance
>     Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to 
> construct component instance
>     Caused by: javax.ejb.EJBException: 
> java.lang.IllegalStateException: Could not initialize inventory.
>     Caused by: java.lang.IllegalStateException: Could not initialize 
> inventory."}}
> 2015-10-18 13:01:54,267 ERROR 
> [org.jboss.as.controller.management-operation] (Controller Boot 
> Thread) WFLYCTL0013: Operation ("add") failed - address: 
> ([("deployment" => "hawkular-redhat-access-integration-backend.war")]) 
> - failure description: {"WFLYCTL0080: Failed services" => 
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START" 
> => "org.jboss.msc.service.StartException in service 
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START: 
> java.lang.IllegalStateException: WFLYEE0042: Failed to construct 
> component instance
>     Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to 
> construct component instance
>     Caused by: javax.ejb.EJBException: 
> java.lang.IllegalStateException: Could not initialize inventory.
>     Caused by: java.lang.IllegalStateException: Could not initialize 
> inventory."}}
>
>
>
>
>
>
> _______________________________________________
> 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/20151019/a0eceadd/attachment-0001.html 

From l_roitman at yahoo.com  Mon Oct 19 13:33:57 2015
From: l_roitman at yahoo.com (Luba Roitman)
Date: Mon, 19 Oct 2015 17:33:57 +0000 (UTC)
Subject: [Hawkular-dev] Problems installing Alpha 5 on Windows
In-Reply-To: <5276773.tlBKnxjgBE@localhost.localdomain>
References: <5276773.tlBKnxjgBE@localhost.localdomain>
Message-ID: <1128773543.2846406.1445276037574.JavaMail.yahoo@mail.yahoo.com>

Thanks a lot Lukas,?
All these ports are free at the time I run Hawkular. I was able to register after starting, as well as log in afterwords.After I log in I am getting spinner, possibly due to failed inventory.
What about the Docker image for Alpha 5? Is it going to be available?
Thanks,?Luba.


      From: Lukas Krejci <lkrejci at redhat.com>
 To: Luba Roitman <l_roitman at yahoo.com>; Discussions around Hawkular development <hawkular-dev at lists.jboss.org> 
 Sent: Monday, October 19, 2015 12:01 PM
 Subject: Re: [Hawkular-dev] Problems installing Alpha 5 on Windows
   
Hi,

They could indeed be connected but it's hard to say. Inventory in Alpha6 will 
emit more info in such situations but unfortunately in Alpha5 there's no way 
of getting more info about inventory init failures from the logs.

As for the ports that need to be open, I believe we need 8080, 9042 and 9160. 
The former is for the http interface and the latter two for Cassandra and 
Cassandra RPC servers.



On Monday, October 19, 2015 16:44:44 Luba Roitman wrote:
> Hi, 
> I am having problems installing Hawkular Alpha 5 on Windows, but before I
> delve into describing them, I am wondering as to whether Docker install
> option is going to be available soon? That would indeed be helpful. As for
> the Windows install problem, after I downloaded Alpha 5 and run
> standalone.bat I have the following exceptions in the server.log (excerpts
> here, more stacktrace in the end of the email)
> jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to
> start the http-interface service Caused by: java.lang.RuntimeException:
> java.net.BindException: Address already in use: bind And then2015-10-18
> 13:01:53,226 WARN? [org.hawkular.inventory.cdi] (ServerService Thread Pool
> -- 68) HAWKINV003501: Inventory backend failed to initialize in an attempt
> 5 of 5.2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail]
> (ServerService Thread Pool -- 68) MSC000001: Failed to start service
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDI
> Publisher.START: org.jboss.msc.service.StartException in service
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDI
> Publisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instanceCaused by: javax.ejb.EJBException:
> java.lang.IllegalStateException: Could not initialize inventory.Caused by:
> java.lang.IllegalStateException: Could not initialize inventory.
> 
> Do you think these two could be connected? I can't think of any source for
> binding address conflict, I start Hawkular the first thing after the laptop
> restart, so don't run any local http servers. It is also not clear what is
> the reason for inventory initialization problem, the log doesn't indicate
> any wrong before throwing error. I am running Windows 8.1 64bit
> Would appreciate any input!
> Respectfully, Luba Roitman.
> -------------2015-10-18 13:01:33,144 ERROR [org.jboss.msc.service.fail] (MSC
> service thread 1-4) MSC000001: Failed to start service
> jboss.serverManagement.controller.management.http:
> org.jboss.msc.service.StartException in service
> jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to
> start the http-interface service at
> org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpMa
> nagementService.java:269) at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceC
> ontrollerImpl.java:1948) at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceController
> Impl.java:1881) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1
> 142) at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
> 617) at java.lang.Thread.run(Thread.java:745)Caused by:
> java.lang.RuntimeException: java.net.BindException: Address already in use:
> bind at
> org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpSe
> rver.java:160) at
> org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpMa
> nagementService.java:235) ... 5 moreCaused by: java.net.BindException:
> Address already in use: bind at sun.nio.ch.Net.bind0(Native Method) at
> sun.nio.ch.Net.bind(Net.java:433)------------------ 2015-10-18 13:01:53,226
> WARN? [org.hawkular.inventory.cdi] (ServerService Thread Pool -- 68)
> HAWKINV003501: Inventory backend failed to initialize in an attempt 5 of
> 5.2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail] (ServerService
> Thread Pool -- 68) MSC000001: Failed to start service
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDI
> Publisher.START: org.jboss.msc.service.StartException in service
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDI
> Publisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instance at
> org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService
> .java:57) at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at
> java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1
> 142) at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
> 617) at java.lang.Thread.run(Thread.java:745) at
> org.jboss.threads.JBossThread.run(JBossThread.java:320)Caused by:
> java.lang.IllegalStateException: WFLYEE0042: Failed to construct component
> instance at
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicCo
> mponent.java:163) at
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicCo
> mponent.java:134) at
> org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java
> :88) at
> org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstan
> ce(SingletonComponent.java:122) at
> org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonCom
> ponent.java:136) at
> org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService
> .java:54) ... 6 moreCaused by: javax.ejb.EJBException:
> java.lang.IllegalStateException: Could not initialize inventory. at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxIntercept
> or.java:187) at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:2
> 77) at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:349
> ) at
> org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleC
> MTTxInterceptor.java:66) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocati
> on(WeldInjectionContextInterceptor.java:43) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextIntercepto
> r.processInvocation(CurrentInvocationContextInterceptor.java:41) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(C
> oncurrentContextInterceptor.java:45) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(Contex
> tClassLoaderInterceptor.java:64) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at
> org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(Pr
> ivilegedWithCombinerInterceptor.java:80) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedIntercepto
> r.java:61) at
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicCo
> mponent.java:161) ... 11 moreCaused by: java.lang.IllegalStateException:
> Could not initialize inventory. at
> org.hawkular.inventory.cdi.OfficialInventoryProducer.initInventory(Official
> InventoryProducer.java:115) at
> org.hawkular.inventory.cdi.OfficialInventoryProducer.getInventory(OfficialI
> nventoryProducer.java:64) at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:6
> 2) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
> l.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at
> org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInje
> ctionPoint.java:88) at
> org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInje
> ctionPoint.java:78) at
> org.jboss.weld.injection.producer.ProducerMethodProducer.produce(ProducerMe
> thodProducer.java:95) at
> org.jboss.weld.injection.producer.AbstractMemberProducer.produce(AbstractMe
> mberProducer.java:167) at
> org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:1
> 83) at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
> at
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStr
> ategy.get(ContextualInstanceStrategy.java:101) at
> org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualI
> nstanceStrategy.get(ContextualInstanceStrategy.java:141) at
> org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) at
> org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:76
> 1) at
> org.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerIm
> pl.java:861) at
> org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.jav
> a:92) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:375) at
> org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:386) at
> org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector
> .java:71) at
> org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java
> :48) at
> org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.ja
> va:73) at
> org.jboss.weld.injection.producer.ejb.SessionBeanInjectionTarget.inject(Ses
> sionBeanInjectionTarget.java:140) at
> org.jboss.as.weld.injection.WeldInjectionContext.inject(WeldInjectionContex
> t.java:39) at
> org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(Weld
> InjectionInterceptor.java:51) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvoca
> tion(AroundConstructInterceptorFactory.java:28) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvo
> cation(WeldInterceptorInjectionInterceptor.java:56) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr
> 299BindingsCreateInterceptor.java:100) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(Nam
> espaceContextInterceptor.java:50) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:2
> 75) ... 27 more 2015-10-18 13:01:54,251 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("add") failed - address: ([? ? ("core-service" =>
> "management"),? ? ("management-interface" => "http-interface")]) - failure
> description: {"WFLYCTL0080: Failed services" =>
> {"jboss.serverManagement.controller.management.http" =>
> "org.jboss.msc.service.StartException in service
> jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to
> start the http-interface service? ? Caused by: java.lang.RuntimeException:
> java.net.BindException: Address already in use: bind? ? Caused by:
> java.net.BindException: Address already in use: bind"}}2015-10-18
> 13:01:54,251 ERROR [org.jboss.as.controller.management-operation]
> (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address:
> ([("deployment" => "hawkular-inventory-dist.war")]) - failure description:
> {"WFLYCTL0080: Failed services" =>
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.Inventory
> JNDIPublisher.START" => "org.jboss.msc.service.StartException in service
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJN
> DIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instance? ? Caused by: java.lang.IllegalStateException:
> WFLYEE0042: Failed to construct component instance? ? Caused by:
> javax.ejb.EJBException: java.lang.IllegalStateException: Could not
> initialize inventory.? ? Caused by: java.lang.IllegalStateException: Could
> not initialize inventory."}}2015-10-18 13:01:54,251 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("add") failed - address: ([("deployment" =>
> "hawkular-metrics-api-jaxrs.war")]) - failure description: {"WFLYCTL0080:
> Failed services" =>
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.Inventory
> JNDIPublisher.START" => "org.jboss.msc.service.StartException in service
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJN
> DIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instance? ? Caused by: java.lang.IllegalStateException:
> WFLYEE0042: Failed to construct component instance? ? Caused by:
> javax.ejb.EJBException: java.lang.IllegalStateException: Could not
> initialize inventory.? ? Caused by: java.lang.IllegalStateException: Could
> not initialize inventory."}}2015-10-18 13:01:54,251 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("add") failed - address: ([("deployment" =>
> "hawkular-pinger.war")]) - failure description: {"WFLYCTL0080: Failed
> services" =>
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.Inventory
> JNDIPublisher.START" => "org.jboss.msc.service.StartException in service
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJN
> DIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instance? ? Caused by: java.lang.IllegalStateException:
> WFLYEE0042: Failed to construct component instance? ? Caused by:
> javax.ejb.EJBException: java.lang.IllegalStateException: Could not
> initialize inventory.? ? Caused by: java.lang.IllegalStateException: Could
> not initialize inventory."}}2015-10-18 13:01:54,267 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("add") failed - address: ([("deployment" =>
> "hawkular-redhat-access-integration-backend.war")]) - failure description:
> {"WFLYCTL0080: Failed services" =>
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.Inventory
> JNDIPublisher.START" => "org.jboss.msc.service.StartException in service
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJN
> DIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instance? ? Caused by: java.lang.IllegalStateException:
> WFLYEE0042: Failed to construct component instance? ? Caused by:
> javax.ejb.EJBException: java.lang.IllegalStateException: Could not
> initialize inventory.? ? Caused by: java.lang.IllegalStateException: Could
> not initialize inventory."}}



  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151019/8ecc2040/attachment-0001.html 

From l_roitman at yahoo.com  Mon Oct 19 13:36:28 2015
From: l_roitman at yahoo.com (Luba Roitman)
Date: Mon, 19 Oct 2015 17:36:28 +0000 (UTC)
Subject: [Hawkular-dev] Problems installing Alpha 5 on Windows
In-Reply-To: <5625286F.4080201@redhat.com>
References: <5625286F.4080201@redhat.com>
Message-ID: <1943521334.2859130.1445276188863.JavaMail.yahoo@mail.yahoo.com>

Thanks a lot Jay,?
I'll try that and let you know if helped.And very good news about M6, looking forward to it!
Thanks?Luba.
      From: Jay Shaughnessy <jshaughn at redhat.com>
 To: hawkular-dev at lists.jboss.org 
 Sent: Monday, October 19, 2015 12:29 PM
 Subject: Re: [Hawkular-dev] Problems installing Alpha 5 on Windows
   
 
 There are two known issues in M5 on Windows.? Both are path related and one of them kills the inventory deployment.? Both are fixed in M6, due out this week.
 ?For M5 you need to do some work if you want to run on windows:
 
 You must replace occurrences of?${jboss.server.data.dir} 1) with the explicit Windows path, using *FORWARD SLASHES*.?? For example, on my box it's:
 
 ? c:/work/hawkular/dist/target/hawkular1.0.0.Alpha6-SNAPSHOT/hawkular-1.0.0.Alpha6-SNAPSHOT/standalone/data
 
 First Occurence:
 
 ? <HawkularRoot>/standalone/configuration/standalone.xml
 
 Second Occurence: 
 
 ? This one is more difficult.? You need to unzip:
 
 ?<HawkularRoot>\modules\org\hawkular\nest\main\deployments\hawkular-inventory-dist.war
 
 Then, edit hawkular-inventory.properties, make the change, and rezip.
 
 I *think* it will then work for you.
 
 In M6 you should be able to just do the following.? On the command line start up like this:
 
 ? ...\bin>standalone.bat -Dorg.hawkular.data.dir=<YourDataDirWithForwardSlashes>
 
 
 
  

On 10/19/2015 12:44 PM, Luba Roitman wrote:
  
  Hi,?
          I am having problems installing Hawkular Alpha 5 on Windows, but before I delve into describing them, I am wondering as  to whether Docker install option is going to be available soon? That would indeed be helpful. 
  As for the Windows install problem, after I downloaded Alpha 5 and run standalone.bat I have the following exceptions  in the server.log (excerpts here, more stacktrace in the end of the email) 
  jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service
  Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind 
  And then 2015-10-18 13:01:53,226 WARN ?[org.hawkular.inventory.cdi] (ServerService Thread Pool -- 68) HAWKINV003501: Inventory backend failed to initialize in an attempt 5 of 5. 2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 68) MSC000001: Failed to start service jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START:  org.jboss.msc.service.StartException in service jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory. Caused by: java.lang.IllegalStateException: Could not initialize inventory. 
  
  Do you think these two could be connected? I can't think of any source for binding address conflict, I  start Hawkular the first thing after the laptop restart, so don't run any local http servers. It is also not clear what is the reason for inventory initialization problem, the log doesn't indicate any wrong before throwing error. 
  I am running Windows 8.1 64bit 
  Would appreciate any input! 
  Respectfully,? Luba Roitman. 
  ------------- 2015-10-18 13:01:33,144 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in  service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service  atorg.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:269)  atorg.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)  atorg.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)  atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)  atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)  at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind  atorg.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:160)  atorg.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:235)  ... 5 more Caused by: java.net.BindException: Address already in use: bind  at sun.nio.ch.Net.bind0(Native Method)  at sun.nio.ch.Net.bind(Net.java:433) ------------------ 
  2015-10-18 13:01:53,226 WARN ?[org.hawkular.inventory.cdi] (ServerService Thread Pool -- 68) HAWKINV003501: Inventory backend failed to initialize in an attempt 5 of 5. 2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 68) MSC000001: Failed to start service jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START:  org.jboss.msc.service.StartException in service jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance  atorg.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57)  atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)  atjava.util.concurrent.FutureTask.run(FutureTask.java:266)  atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)  atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)  at java.lang.Thread.run(Thread.java:745)  atorg.jboss.threads.JBossThread.run(JBossThread.java:320) Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance  atorg.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163)  atorg.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134)  atorg.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88)  atorg.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:122)  atorg.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:136)  atorg.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)  ... 6 more Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory.  atorg.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:187)  atorg.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:277)  atorg.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:349)  atorg.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)  atorg.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) atorg.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161)  ... 11 more Caused by: java.lang.IllegalStateException: Could not initialize inventory.  atorg.hawkular.inventory.cdi.OfficialInventoryProducer.initInventory(OfficialInventoryProducer.java:115)  atorg.hawkular.inventory.cdi.OfficialInventoryProducer.getInventory(OfficialInventoryProducer.java:64)  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)  atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)  atjava.lang.reflect.Method.invoke(Method.java:497)  atorg.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:88)  atorg.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:78)  atorg.jboss.weld.injection.producer.ProducerMethodProducer.produce(ProducerMethodProducer.java:95)  atorg.jboss.weld.injection.producer.AbstractMemberProducer.produce(AbstractMemberProducer.java:167)  atorg.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:183)  atorg.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)  atorg.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)  atorg.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141)  atorg.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)  atorg.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:761)  atorg.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:861)  atorg.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:92)  atorg.jboss.weld.util.Beans.injectBoundFields(Beans.java:375)  atorg.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:386)  atorg.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:71)  atorg.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48)  atorg.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:73)  atorg.jboss.weld.injection.producer.ejb.SessionBeanInjectionTarget.inject(SessionBeanInjectionTarget.java:140)  atorg.jboss.as.weld.injection.WeldInjectionContext.inject(WeldInjectionContext.java:39)  atorg.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:51)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:100)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)  ... 27 more 
  2015-10-18 13:01:54,251 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ? ? ("core-service" => "management"), ? ? ("management-interface" => "http-interface") ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.serverManagement.controller.management.http" => "org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service ? ? Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind ? ? Caused by: java.net.BindException: Address already in use: bind"}} 2015-10-18 13:01:54,251 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "hawkular-inventory-dist.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance ? ? Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance ? ? Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory. ? ? Caused by: java.lang.IllegalStateException: Could not initialize inventory."}} 2015-10-18 13:01:54,251 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "hawkular-metrics-api-jaxrs.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance ? ? Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance ? ? Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory. ? ? Caused by: java.lang.IllegalStateException: Could not initialize inventory."}} 2015-10-18 13:01:54,251 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "hawkular-pinger.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance ? ? Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance ? ? Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory. ? ? Caused by: java.lang.IllegalStateException: Could not initialize inventory."}} 2015-10-18 13:01:54,267 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "hawkular-redhat-access-integration-backend.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance ? ? Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance ? ? Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory. ? ? Caused by: java.lang.IllegalStateException: Could not initialize inventory."}} 
  
       
 
     
  
 _______________________________________________
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/20151019/f0a7686e/attachment-0001.html 

From mazz at redhat.com  Mon Oct 19 18:12:34 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Mon, 19 Oct 2015 18:12:34 -0400 (EDT)
Subject: [Hawkular-dev] agent release
In-Reply-To: <1541153681.33936462.1445292596424.JavaMail.zimbra@redhat.com>
Message-ID: <2050062171.33936741.1445292754116.JavaMail.zimbra@redhat.com>

New releases have been done to get the latest agent ready for kettle.

This PR is to move kettle to the latest agent:

https://github.com/hawkular/hawkular/pull/581

Problem is - UI looks to be broken. The application server page just spins with no data. However, I do see inventory populated with my agent data (resources, types, etc). So I don't know what's wrong. The only thing I see in the browser debug console is the following error that gets logged repeatedly every few seconds (the log messages aren't time stamped, so I don't know how often it is, but it looks like something is polling something). 

Error: res.properties is undefined
AppServerListController.prototype.getResourceListForOneFeed/</</<@http://127.0.0.1:8080/dist/hawkular-console.js?v=2015-10-19T21:49:55Z:2475:25
resourceFactory/</Resource[name]/promise<@http://127.0.0.1:8080/libs/angular-resource/angular-resource.js?v=1445291596061:634:18
processQueue at http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:14745:28
scheduleProcessQueue/<@http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:14761:27
$RootScopeProvider/this.$get</Scope.prototype.$eval at http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:15989:16
$RootScopeProvider/this.$get</Scope.prototype.$digest at http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:15800:15
$RootScopeProvider/this.$get</Scope.prototype.$apply at http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:16097:13
done at http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:10546:36
completeRequest at http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:10744:7
requestLoaded at http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:10685:1

From mazz at redhat.com  Mon Oct 19 18:29:27 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Mon, 19 Oct 2015 18:29:27 -0400 (EDT)
Subject: [Hawkular-dev] agent release
In-Reply-To: <2050062171.33936741.1445292754116.JavaMail.zimbra@redhat.com>
References: <2050062171.33936741.1445292754116.JavaMail.zimbra@redhat.com>
Message-ID: <144741411.33939851.1445293767728.JavaMail.zimbra@redhat.com>

Both Alex and Mike T. are saying one problem is:

(06:18:01 PM) mtho11: http://livingontheedge.hawkular.org/hawkular/metrics/availability/AI~R~%5Bsnapshot-rc-b896d~Local~~%5D~AT~Server%20Availability~App%20Server/data?distinct=true
(06:18:08 PM) mtho11: giving 500s

I don't see that locally, but my application server page in the UI still spins. I suspect its something else. Hopefully on Tuesday we can figure out what's up. I won't merge the kettle PR until we know what's going on with the UI.

----- Original Message -----
> New releases have been done to get the latest agent ready for kettle.
> 
> This PR is to move kettle to the latest agent:
> 
> https://github.com/hawkular/hawkular/pull/581
> 
> Problem is - UI looks to be broken. The application server page just spins
> with no data. However, I do see inventory populated with my agent data
> (resources, types, etc). So I don't know what's wrong. The only thing I see
> in the browser debug console is the following error that gets logged
> repeatedly every few seconds (the log messages aren't time stamped, so I
> don't know how often it is, but it looks like something is polling
> something).
> 
> Error: res.properties is undefined
> AppServerListController.prototype.getResourceListForOneFeed/</</<@http://127.0.0.1:8080/dist/hawkular-console.js?v=2015-10-19T21:49:55Z:2475:25
> resourceFactory/</Resource[name]/promise<@http://127.0.0.1:8080/libs/angular-resource/angular-resource.js?v=1445291596061:634:18
> processQueue at http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:14745:28
> scheduleProcessQueue/<@http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:14761:27
> $RootScopeProvider/this.$get</Scope.prototype.$eval at http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:15989:16
> $RootScopeProvider/this.$get</Scope.prototype.$digest at http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:15800:15
> $RootScopeProvider/this.$get</Scope.prototype.$apply at http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:16097:13
> done at http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:10546:36
> completeRequest at http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:10744:7
> requestLoaded at http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:10685:1
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
> 

From l_roitman at yahoo.com  Mon Oct 19 18:34:20 2015
From: l_roitman at yahoo.com (Luba Roitman)
Date: Mon, 19 Oct 2015 22:34:20 +0000 (UTC)
Subject: [Hawkular-dev] Problems installing Alpha 5 on Windows
In-Reply-To: <5625286F.4080201@redhat.com>
References: <5625286F.4080201@redhat.com>
Message-ID: <538100693.149550.1445294060082.JavaMail.yahoo@mail.yahoo.com>

Thanks Jay, this worked!
-L.
      From: Jay Shaughnessy <jshaughn at redhat.com>
 To: hawkular-dev at lists.jboss.org 
 Sent: Monday, October 19, 2015 12:29 PM
 Subject: Re: [Hawkular-dev] Problems installing Alpha 5 on Windows
   
 
 There are two known issues in M5 on Windows.? Both are path related and one of them kills the inventory deployment.? Both are fixed in M6, due out this week.
 ?For M5 you need to do some work if you want to run on windows:
 
 You must replace occurrences of?${jboss.server.data.dir} 1) with the explicit Windows path, using *FORWARD SLASHES*.?? For example, on my box it's:
 
 ? c:/work/hawkular/dist/target/hawkular1.0.0.Alpha6-SNAPSHOT/hawkular-1.0.0.Alpha6-SNAPSHOT/standalone/data
 
 First Occurence:
 
 ? <HawkularRoot>/standalone/configuration/standalone.xml
 
 Second Occurence: 
 
 ? This one is more difficult.? You need to unzip:
 
 ?<HawkularRoot>\modules\org\hawkular\nest\main\deployments\hawkular-inventory-dist.war
 
 Then, edit hawkular-inventory.properties, make the change, and rezip.
 
 I *think* it will then work for you.
 
 In M6 you should be able to just do the following.? On the command line start up like this:
 
 ? ...\bin>standalone.bat -Dorg.hawkular.data.dir=<YourDataDirWithForwardSlashes>
 
 
 
  

On 10/19/2015 12:44 PM, Luba Roitman wrote:
  
  Hi,?
          I am having problems installing Hawkular Alpha 5 on Windows, but before I delve into describing them, I am wondering as  to whether Docker install option is going to be available soon? That would indeed be helpful. 
  As for the Windows install problem, after I downloaded Alpha 5 and run standalone.bat I have the following exceptions  in the server.log (excerpts here, more stacktrace in the end of the email) 
  jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service
  Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind 
  And then 2015-10-18 13:01:53,226 WARN ?[org.hawkular.inventory.cdi] (ServerService Thread Pool -- 68) HAWKINV003501: Inventory backend failed to initialize in an attempt 5 of 5. 2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 68) MSC000001: Failed to start service jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START:  org.jboss.msc.service.StartException in service jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory. Caused by: java.lang.IllegalStateException: Could not initialize inventory. 
  
  Do you think these two could be connected? I can't think of any source for binding address conflict, I  start Hawkular the first thing after the laptop restart, so don't run any local http servers. It is also not clear what is the reason for inventory initialization problem, the log doesn't indicate any wrong before throwing error. 
  I am running Windows 8.1 64bit 
  Would appreciate any input! 
  Respectfully,? Luba Roitman. 
  ------------- 2015-10-18 13:01:33,144 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in  service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service  atorg.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:269)  atorg.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)  atorg.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)  atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)  atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)  at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind  atorg.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:160)  atorg.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:235)  ... 5 more Caused by: java.net.BindException: Address already in use: bind  at sun.nio.ch.Net.bind0(Native Method)  at sun.nio.ch.Net.bind(Net.java:433) ------------------ 
  2015-10-18 13:01:53,226 WARN ?[org.hawkular.inventory.cdi] (ServerService Thread Pool -- 68) HAWKINV003501: Inventory backend failed to initialize in an attempt 5 of 5. 2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 68) MSC000001: Failed to start service jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START:  org.jboss.msc.service.StartException in service jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance  atorg.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57)  atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)  atjava.util.concurrent.FutureTask.run(FutureTask.java:266)  atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)  atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)  at java.lang.Thread.run(Thread.java:745)  atorg.jboss.threads.JBossThread.run(JBossThread.java:320) Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance  atorg.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163)  atorg.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134)  atorg.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88)  atorg.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:122)  atorg.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:136)  atorg.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)  ... 6 more Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory.  atorg.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:187)  atorg.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:277)  atorg.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:349)  atorg.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)  atorg.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) atorg.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161)  ... 11 more Caused by: java.lang.IllegalStateException: Could not initialize inventory.  atorg.hawkular.inventory.cdi.OfficialInventoryProducer.initInventory(OfficialInventoryProducer.java:115)  atorg.hawkular.inventory.cdi.OfficialInventoryProducer.getInventory(OfficialInventoryProducer.java:64)  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)  atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)  atjava.lang.reflect.Method.invoke(Method.java:497)  atorg.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:88)  atorg.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:78)  atorg.jboss.weld.injection.producer.ProducerMethodProducer.produce(ProducerMethodProducer.java:95)  atorg.jboss.weld.injection.producer.AbstractMemberProducer.produce(AbstractMemberProducer.java:167)  atorg.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:183)  atorg.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)  atorg.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)  atorg.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141)  atorg.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)  atorg.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:761)  atorg.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:861)  atorg.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:92)  atorg.jboss.weld.util.Beans.injectBoundFields(Beans.java:375)  atorg.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:386)  atorg.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:71)  atorg.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48)  atorg.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:73)  atorg.jboss.weld.injection.producer.ejb.SessionBeanInjectionTarget.inject(SessionBeanInjectionTarget.java:140)  atorg.jboss.as.weld.injection.WeldInjectionContext.inject(WeldInjectionContext.java:39)  atorg.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:51)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:100)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)  atorg.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)  atorg.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)  ... 27 more 
  2015-10-18 13:01:54,251 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ? ? ("core-service" => "management"), ? ? ("management-interface" => "http-interface") ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.serverManagement.controller.management.http" => "org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service ? ? Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind ? ? Caused by: java.net.BindException: Address already in use: bind"}} 2015-10-18 13:01:54,251 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "hawkular-inventory-dist.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance ? ? Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance ? ? Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory. ? ? Caused by: java.lang.IllegalStateException: Could not initialize inventory."}} 2015-10-18 13:01:54,251 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "hawkular-metrics-api-jaxrs.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance ? ? Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance ? ? Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory. ? ? Caused by: java.lang.IllegalStateException: Could not initialize inventory."}} 2015-10-18 13:01:54,251 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "hawkular-pinger.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance ? ? Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance ? ? Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory. ? ? Caused by: java.lang.IllegalStateException: Could not initialize inventory."}} 2015-10-18 13:01:54,267 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "hawkular-redhat-access-integration-backend.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance ? ? Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance ? ? Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: Could not initialize inventory. ? ? Caused by: java.lang.IllegalStateException: Could not initialize inventory."}} 
  
       
 
     
  
 _______________________________________________
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/20151019/e1bf6ac4/attachment-0001.html 

From ppalaga at redhat.com  Tue Oct 20 03:07:06 2015
From: ppalaga at redhat.com (Peter Palaga)
Date: Tue, 20 Oct 2015 09:07:06 +0200
Subject: [Hawkular-dev] Problems installing Alpha 5 on Windows
In-Reply-To: <5625286F.4080201@redhat.com>
References: <156179456.2756309.1445269950723.JavaMail.yahoo@mail.yahoo.com>
	<156179456.2756309.1445269950723.JavaMail.yahoo@mail.yahoo.com>
	<1251329922.2778990.1445273084070.JavaMail.yahoo@mail.yahoo.com>
	<5625286F.4080201@redhat.com>
Message-ID: <5625E81A.2090206@redhat.com>

Given that we had such problems on Windows, I think it is time to setup 
a Windows CI. I could set up http://www.appveyor.com/ for Hawkular 
unless somebody wants to propose something else. I recently set up 
appveyor for srcdeps plugin. Tt was fairly easy, the VMs are faster than 
Travis. -- P

On 2015-10-19 19:29, Jay Shaughnessy wrote:
>
> There are two known issues in M5 on Windows. Both are path related and
> one of them kills the inventory deployment.  Both are fixed in M6, due
> out this week.
>   For M5 you need to do some work if you want to run on windows:
>
> You must replace occurrences of ${jboss.server.data.dir} 1) with the
> explicit Windows path, using *FORWARD SLASHES*.   For example, on my box
> it's:
>
> c:/work/hawkular/dist/target/hawkular1.0.0.Alpha6-SNAPSHOT/hawkular-1.0.0.Alpha6-SNAPSHOT/standalone/data
>
> First Occurence:
>
> <HawkularRoot>/standalone/configuration/standalone.xml
>
> Second Occurence:
>
>    This one is more difficult.  You need to unzip:
>
> <HawkularRoot>\modules\org\hawkular\nest\main\deployments\hawkular-inventory-dist.war
>
> Then, edit hawkular-inventory.properties, make the change, and rezip.
>
> I *think* it will then work for you.
>
> In M6 you should be able to just do the following.  On the command line
> start up like this:
>
>    ...\bin>standalone.bat
> -Dorg.hawkular.data.dir=<YourDataDirWithForwardSlashes>
>
>
>
> On 10/19/2015 12:44 PM, Luba Roitman wrote:
>> Hi,
>> I am having problems installing Hawkular Alpha 5 on Windows, but
>> before I delve into describing them, I am wondering as to whether
>> Docker install option is going to be available soon? That would indeed
>> be helpful.
>>
>> As for the Windows install problem, after I downloaded Alpha 5 and run
>> standalone.bat I have the following exceptions in the server.log
>> (excerpts here, more stacktrace in the end of the email)
>>
>> jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed
>> to start the http-interface service
>> Caused by: java.lang.RuntimeException: java.net.BindException: Address
>> already in use: bind
>>
>> And then
>> 2015-10-18 13:01:53,226 WARN  [org.hawkular.inventory.cdi]
>> (ServerService Thread Pool -- 68) HAWKINV003501: Inventory backend
>> failed to initialize in an attempt 5 of 5.
>> 2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail]
>> (ServerService Thread Pool -- 68) MSC000001: Failed to start service
>> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START:
>> org.jboss.msc.service.StartException in service
>> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START:
>> java.lang.IllegalStateException: WFLYEE0042: Failed to construct
>> component instance
>> Caused by: javax.ejb.EJBException: java.lang.IllegalStateException:
>> Could not initialize inventory.
>> Caused by: java.lang.IllegalStateException: Could not initialize
>> inventory.
>>
>>
>> Do you think these two could be connected? I can't think of any source
>> for binding address conflict, I start Hawkular the first thing after
>> the laptop restart, so don't run any local http servers. It is also
>> not clear what is the reason for inventory initialization problem, the
>> log doesn't indicate any wrong before throwing error.
>>
>> I am running Windows 8.1 64bit
>>
>> Would appreciate any input!
>>
>> Respectfully,
>> Luba Roitman.
>>
>> -------------
>> 2015-10-18 13:01:33,144 ERROR [org.jboss.msc.service.fail] (MSC
>> service thread 1-4) MSC000001: Failed to start service
>> jboss.serverManagement.controller.management.http:
>> org.jboss.msc.service.StartException in service
>> jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed
>> to start the http-interface service
>> at
>> org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:269)
>> at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
>> at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
>> 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)
>> Caused by: java.lang.RuntimeException: java.net.BindException: Address
>> already in use: bind
>> at
>> org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:160)
>> at
>> org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:235)
>> ... 5 more
>> Caused by: java.net.BindException: Address already in use: bind
>> at sun.nio.ch.Net.bind0(Native Method)
>> at sun.nio.ch.Net.bind(Net.java:433)
>> ------------------
>>
>> 2015-10-18 13:01:53,226 WARN  [org.hawkular.inventory.cdi]
>> (ServerService Thread Pool -- 68) HAWKINV003501: Inventory backend
>> failed to initialize in an attempt 5 of 5.
>> 2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail]
>> (ServerService Thread Pool -- 68) MSC000001: Failed to start service
>> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START:
>> org.jboss.msc.service.StartException in service
>> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDIPublisher.START:
>> java.lang.IllegalStateException: WFLYEE0042: Failed to construct
>> component instance
>> at
>> org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57)
>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>> 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)
>> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
>> Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to
>> construct component instance
>> at
>> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163)
>> at
>> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134)
>> at
>> org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88)
>> at
>> org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:122)
>> at
>> org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:136)
>> at
>> org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
>> ... 6 more
>> Caused by: javax.ejb.EJBException: java.lang.IllegalStateException:
>> Could not initialize inventory.
>> at
>> org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:187)
>> at
>> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:277)
>> at
>> org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:349)
>> at
>> org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
>> at
>> org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
>> at
>> org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
>> at
>> org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
>> at
>> org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
>> at
>> org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
>> at
>> org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
>> at
>> org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)at
>> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161)
>> ... 11 more
>> Caused by: java.lang.IllegalStateException: Could not initialize
>> inventory.
>> at
>> org.hawkular.inventory.cdi.OfficialInventoryProducer.initInventory(OfficialInventoryProducer.java:115)
>> at
>> org.hawkular.inventory.cdi.OfficialInventoryProducer.getInventory(OfficialInventoryProducer.java:64)
>> 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:497)
>> at
>> org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:88)
>> at
>> org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:78)
>> at
>> org.jboss.weld.injection.producer.ProducerMethodProducer.produce(ProducerMethodProducer.java:95)
>> at
>> org.jboss.weld.injection.producer.AbstractMemberProducer.produce(AbstractMemberProducer.java:167)
>> at
>> org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:183)
>> at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
>> at
>> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)
>> at
>> org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141)
>> at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
>> at
>> org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:761)
>> at
>> org.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:861)
>> at
>> org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:92)
>> at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:375)
>> at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:386)
>> at
>> org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:71)
>> at
>> org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48)
>> at
>> org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:73)
>> at
>> org.jboss.weld.injection.producer.ejb.SessionBeanInjectionTarget.inject(SessionBeanInjectionTarget.java:140)
>> at
>> org.jboss.as.weld.injection.WeldInjectionContext.inject(WeldInjectionContext.java:39)
>> at
>> org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:51)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
>> at
>> org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
>> at
>> org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
>> at
>> org.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:100)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
>> at
>> org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
>> at
>> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)
>> ... 27 more
>>
>> 2015-10-18 13:01:54,251 ERROR
>> [org.jboss.as.controller.management-operation] (Controller Boot
>> Thread) WFLYCTL0013: Operation ("add") failed - address: ([
>> ("core-service" => "management"),
>> ("management-interface" => "http-interface")
>> ]) - failure description: {"WFLYCTL0080: Failed services" =>
>> {"jboss.serverManagement.controller.management.http" =>
>> "org.jboss.msc.service.StartException in service
>> jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed
>> to start the http-interface service
>>     Caused by: java.lang.RuntimeException: java.net.BindException:
>> Address already in use: bind
>>     Caused by: java.net.BindException: Address already in use: bind"}}
>> 2015-10-18 13:01:54,251 ERROR
>> [org.jboss.as.controller.management-operation] (Controller Boot
>> Thread) WFLYCTL0013: Operation ("add") failed - address:
>> ([("deployment" => "hawkular-inventory-dist.war")]) - failure
>> description: {"WFLYCTL0080: Failed services" =>
>> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START"
>> => "org.jboss.msc.service.StartException in service
>> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START:
>> java.lang.IllegalStateException: WFLYEE0042: Failed to construct
>> component instance
>>     Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to
>> construct component instance
>>     Caused by: javax.ejb.EJBException:
>> java.lang.IllegalStateException: Could not initialize inventory.
>>     Caused by: java.lang.IllegalStateException: Could not initialize
>> inventory."}}
>> 2015-10-18 13:01:54,251 ERROR
>> [org.jboss.as.controller.management-operation] (Controller Boot
>> Thread) WFLYCTL0013: Operation ("add") failed - address:
>> ([("deployment" => "hawkular-metrics-api-jaxrs.war")]) - failure
>> description: {"WFLYCTL0080: Failed services" =>
>> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START"
>> => "org.jboss.msc.service.StartException in service
>> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START:
>> java.lang.IllegalStateException: WFLYEE0042: Failed to construct
>> component instance
>>     Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to
>> construct component instance
>>     Caused by: javax.ejb.EJBException:
>> java.lang.IllegalStateException: Could not initialize inventory.
>>     Caused by: java.lang.IllegalStateException: Could not initialize
>> inventory."}}
>> 2015-10-18 13:01:54,251 ERROR
>> [org.jboss.as.controller.management-operation] (Controller Boot
>> Thread) WFLYCTL0013: Operation ("add") failed - address:
>> ([("deployment" => "hawkular-pinger.war")]) - failure description:
>> {"WFLYCTL0080: Failed services" =>
>> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START"
>> => "org.jboss.msc.service.StartException in service
>> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START:
>> java.lang.IllegalStateException: WFLYEE0042: Failed to construct
>> component instance
>>     Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to
>> construct component instance
>>     Caused by: javax.ejb.EJBException:
>> java.lang.IllegalStateException: Could not initialize inventory.
>>     Caused by: java.lang.IllegalStateException: Could not initialize
>> inventory."}}
>> 2015-10-18 13:01:54,267 ERROR
>> [org.jboss.as.controller.management-operation] (Controller Boot
>> Thread) WFLYCTL0013: Operation ("add") failed - address:
>> ([("deployment" => "hawkular-redhat-access-integration-backend.war")])
>> - failure description: {"WFLYCTL0080: Failed services" =>
>> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START"
>> => "org.jboss.msc.service.StartException in service
>> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJNDIPublisher.START:
>> java.lang.IllegalStateException: WFLYEE0042: Failed to construct
>> component instance
>>     Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to
>> construct component instance
>>     Caused by: javax.ejb.EJBException:
>> java.lang.IllegalStateException: Could not initialize inventory.
>>     Caused by: java.lang.IllegalStateException: Could not initialize
>> inventory."}}
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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
>


From theute at redhat.com  Tue Oct 20 03:11:00 2015
From: theute at redhat.com (Thomas Heute)
Date: Tue, 20 Oct 2015 09:11:00 +0200
Subject: [Hawkular-dev] Problems installing Alpha 5 on Windows
In-Reply-To: <5276773.tlBKnxjgBE@localhost.localdomain>
References: <156179456.2756309.1445269950723.JavaMail.yahoo@mail.yahoo.com>
	<1251329922.2778990.1445273084070.JavaMail.yahoo@mail.yahoo.com>
	<5276773.tlBKnxjgBE@localhost.localdomain>
Message-ID: <CA+aN=MorGMrpq324pg014EcRt7+8hp-a9Yqpq5zZVAC6C+kH3g@mail.gmail.com>

Docker installation is available, it's a docker image with everything in
it, including Cassandra, which is good to get started.

http://www.hawkular.org/docs/user/quick-start.html#_option_b_install_from_a_docker_image

Thomas



On Mon, Oct 19, 2015 at 7:01 PM, Lukas Krejci <lkrejci at redhat.com> wrote:

> Hi,
>
> They could indeed be connected but it's hard to say. Inventory in Alpha6
> will
> emit more info in such situations but unfortunately in Alpha5 there's no
> way
> of getting more info about inventory init failures from the logs.
>
> As for the ports that need to be open, I believe we need 8080, 9042 and
> 9160.
> The former is for the http interface and the latter two for Cassandra and
> Cassandra RPC servers.
>
> On Monday, October 19, 2015 16:44:44 Luba Roitman wrote:
> > Hi,
> > I am having problems installing Hawkular Alpha 5 on Windows, but before I
> > delve into describing them, I am wondering as to whether Docker install
> > option is going to be available soon? That would indeed be helpful. As
> for
> > the Windows install problem, after I downloaded Alpha 5 and run
> > standalone.bat I have the following exceptions in the server.log
> (excerpts
> > here, more stacktrace in the end of the email)
> > jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to
> > start the http-interface service Caused by: java.lang.RuntimeException:
> > java.net.BindException: Address already in use: bind And then2015-10-18
> > 13:01:53,226 WARN  [org.hawkular.inventory.cdi] (ServerService Thread
> Pool
> > -- 68) HAWKINV003501: Inventory backend failed to initialize in an
> attempt
> > 5 of 5.2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail]
> > (ServerService Thread Pool -- 68) MSC000001: Failed to start service
> >
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDI
> > Publisher.START: org.jboss.msc.service.StartException in service
> >
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDI
> > Publisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> > construct component instanceCaused by: javax.ejb.EJBException:
> > java.lang.IllegalStateException: Could not initialize inventory.Caused
> by:
> > java.lang.IllegalStateException: Could not initialize inventory.
> >
> > Do you think these two could be connected? I can't think of any source
> for
> > binding address conflict, I start Hawkular the first thing after the
> laptop
> > restart, so don't run any local http servers. It is also not clear what
> is
> > the reason for inventory initialization problem, the log doesn't indicate
> > any wrong before throwing error. I am running Windows 8.1 64bit
> > Would appreciate any input!
> > Respectfully, Luba Roitman.
> > -------------2015-10-18 13:01:33,144 ERROR [org.jboss.msc.service.fail]
> (MSC
> > service thread 1-4) MSC000001: Failed to start service
> > jboss.serverManagement.controller.management.http:
> > org.jboss.msc.service.StartException in service
> > jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to
> > start the http-interface service at
> >
> org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpMa
> > nagementService.java:269) at
> >
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceC
> > ontrollerImpl.java:1948) at
> >
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceController
> > Impl.java:1881) at
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1
> > 142) at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
> > 617) at java.lang.Thread.run(Thread.java:745)Caused by:
> > java.lang.RuntimeException: java.net.BindException: Address already in
> use:
> > bind at
> >
> org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpSe
> > rver.java:160) at
> >
> org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpMa
> > nagementService.java:235) ... 5 moreCaused by: java.net.BindException:
> > Address already in use: bind at sun.nio.ch.Net.bind0(Native Method) at
> > sun.nio.ch.Net.bind(Net.java:433)------------------ 2015-10-18
> 13:01:53,226
> > WARN  [org.hawkular.inventory.cdi] (ServerService Thread Pool -- 68)
> > HAWKINV003501: Inventory backend failed to initialize in an attempt 5 of
> > 5.2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail]
> (ServerService
> > Thread Pool -- 68) MSC000001: Failed to start service
> >
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDI
> > Publisher.START: org.jboss.msc.service.StartException in service
> >
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDI
> > Publisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> > construct component instance at
> >
> org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService
> > .java:57) at
> > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at
> > java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1
> > 142) at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
> > 617) at java.lang.Thread.run(Thread.java:745) at
> > org.jboss.threads.JBossThread.run(JBossThread.java:320)Caused by:
> > java.lang.IllegalStateException: WFLYEE0042: Failed to construct
> component
> > instance at
> >
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicCo
> > mponent.java:163) at
> >
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicCo
> > mponent.java:134) at
> >
> org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java
> > :88) at
> >
> org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstan
> > ce(SingletonComponent.java:122) at
> >
> org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonCom
> > ponent.java:136) at
> >
> org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService
> > .java:54) ... 6 moreCaused by: javax.ejb.EJBException:
> > java.lang.IllegalStateException: Could not initialize inventory. at
> >
> org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxIntercept
> > or.java:187) at
> >
> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:2
> > 77) at
> >
> org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:349
> > ) at
> >
> org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleC
> > MTTxInterceptor.java:66) at
> >
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> > ) at
> >
> org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocati
> > on(WeldInjectionContextInterceptor.java:43) at
> >
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> > ) at
> >
> org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextIntercepto
> > r.processInvocation(CurrentInvocationContextInterceptor.java:41) at
> >
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> > ) at
> >
> org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(C
> > oncurrentContextInterceptor.java:45) at
> >
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> > ) at
> >
> org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(Contex
> > tClassLoaderInterceptor.java:64) at
> >
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> > ) at
> > org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> at
> >
> org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(Pr
> > ivilegedWithCombinerInterceptor.java:80) at
> >
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> > ) at
> >
> org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedIntercepto
> > r.java:61) at
> >
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicCo
> > mponent.java:161) ... 11 moreCaused by: java.lang.IllegalStateException:
> > Could not initialize inventory. at
> >
> org.hawkular.inventory.cdi.OfficialInventoryProducer.initInventory(Official
> > InventoryProducer.java:115) at
> >
> org.hawkular.inventory.cdi.OfficialInventoryProducer.getInventory(OfficialI
> > nventoryProducer.java:64) at
> > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:6
> > 2) at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
> > l.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at
> >
> org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInje
> > ctionPoint.java:88) at
> >
> org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInje
> > ctionPoint.java:78) at
> >
> org.jboss.weld.injection.producer.ProducerMethodProducer.produce(ProducerMe
> > thodProducer.java:95) at
> >
> org.jboss.weld.injection.producer.AbstractMemberProducer.produce(AbstractMe
> > mberProducer.java:167) at
> >
> org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:1
> > 83) at
> org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
> > at
> >
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStr
> > ategy.get(ContextualInstanceStrategy.java:101) at
> >
> org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualI
> > nstanceStrategy.get(ContextualInstanceStrategy.java:141) at
> > org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) at
> >
> org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:76
> > 1) at
> >
> org.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerIm
> > pl.java:861) at
> >
> org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.jav
> > a:92) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:375) at
> > org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:386) at
> >
> org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector
> > .java:71) at
> >
> org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java
> > :48) at
> >
> org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.ja
> > va:73) at
> >
> org.jboss.weld.injection.producer.ejb.SessionBeanInjectionTarget.inject(Ses
> > sionBeanInjectionTarget.java:140) at
> >
> org.jboss.as.weld.injection.WeldInjectionContext.inject(WeldInjectionContex
> > t.java:39) at
> >
> org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(Weld
> > InjectionInterceptor.java:51) at
> >
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> > ) at
> >
> org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvoca
> > tion(AroundConstructInterceptorFactory.java:28) at
> >
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> > ) at
> >
> org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvo
> > cation(WeldInterceptorInjectionInterceptor.java:56) at
> >
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> > ) at
> >
> org.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr
> > 299BindingsCreateInterceptor.java:100) at
> >
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> > ) at
> >
> org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(Nam
> > espaceContextInterceptor.java:50) at
> >
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> > ) at
> >
> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:2
> > 75) ... 27 more 2015-10-18 13:01:54,251 ERROR
> > [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> > WFLYCTL0013: Operation ("add") failed - address: ([    ("core-service" =>
> > "management"),    ("management-interface" => "http-interface")]) -
> failure
> > description: {"WFLYCTL0080: Failed services" =>
> > {"jboss.serverManagement.controller.management.http" =>
> > "org.jboss.msc.service.StartException in service
> > jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to
> > start the http-interface service    Caused by:
> java.lang.RuntimeException:
> > java.net.BindException: Address already in use: bind    Caused by:
> > java.net.BindException: Address already in use: bind"}}2015-10-18
> > 13:01:54,251 ERROR [org.jboss.as.controller.management-operation]
> > (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address:
> > ([("deployment" => "hawkular-inventory-dist.war")]) - failure
> description:
> > {"WFLYCTL0080: Failed services" =>
> >
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.Inventory
> > JNDIPublisher.START" => "org.jboss.msc.service.StartException in service
> >
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJN
> > DIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> > construct component instance    Caused by:
> java.lang.IllegalStateException:
> > WFLYEE0042: Failed to construct component instance    Caused by:
> > javax.ejb.EJBException: java.lang.IllegalStateException: Could not
> > initialize inventory.    Caused by: java.lang.IllegalStateException:
> Could
> > not initialize inventory."}}2015-10-18 13:01:54,251 ERROR
> > [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> > WFLYCTL0013: Operation ("add") failed - address: ([("deployment" =>
> > "hawkular-metrics-api-jaxrs.war")]) - failure description: {"WFLYCTL0080:
> > Failed services" =>
> >
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.Inventory
> > JNDIPublisher.START" => "org.jboss.msc.service.StartException in service
> >
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJN
> > DIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> > construct component instance    Caused by:
> java.lang.IllegalStateException:
> > WFLYEE0042: Failed to construct component instance    Caused by:
> > javax.ejb.EJBException: java.lang.IllegalStateException: Could not
> > initialize inventory.    Caused by: java.lang.IllegalStateException:
> Could
> > not initialize inventory."}}2015-10-18 13:01:54,251 ERROR
> > [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> > WFLYCTL0013: Operation ("add") failed - address: ([("deployment" =>
> > "hawkular-pinger.war")]) - failure description: {"WFLYCTL0080: Failed
> > services" =>
> >
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.Inventory
> > JNDIPublisher.START" => "org.jboss.msc.service.StartException in service
> >
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJN
> > DIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> > construct component instance    Caused by:
> java.lang.IllegalStateException:
> > WFLYEE0042: Failed to construct component instance    Caused by:
> > javax.ejb.EJBException: java.lang.IllegalStateException: Could not
> > initialize inventory.    Caused by: java.lang.IllegalStateException:
> Could
> > not initialize inventory."}}2015-10-18 13:01:54,267 ERROR
> > [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> > WFLYCTL0013: Operation ("add") failed - address: ([("deployment" =>
> > "hawkular-redhat-access-integration-backend.war")]) - failure
> description:
> > {"WFLYCTL0080: Failed services" =>
> >
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.Inventory
> > JNDIPublisher.START" => "org.jboss.msc.service.StartException in service
> >
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJN
> > DIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> > construct component instance    Caused by:
> java.lang.IllegalStateException:
> > WFLYEE0042: Failed to construct component instance    Caused by:
> > javax.ejb.EJBException: java.lang.IllegalStateException: Could not
> > initialize inventory.    Caused by: java.lang.IllegalStateException:
> Could
> > not initialize inventory."}}
>
> _______________________________________________
> 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/20151020/67191ae5/attachment-0001.html 

From jkremser at redhat.com  Tue Oct 20 07:22:06 2015
From: jkremser at redhat.com (Jiri Kremser)
Date: Tue, 20 Oct 2015 07:22:06 -0400 (EDT)
Subject: [Hawkular-dev] cmdgw forwarding messages from bus to UI
In-Reply-To: <170514487.27701750.1445338945704.JavaMail.zimbra@redhat.com>
Message-ID: <280824539.27704959.1445340126336.JavaMail.zimbra@redhat.com>

Hello,
  when creating the topology graph, the nice feature would be to see the newly added resources in inventory in a real-time. Currently, the approach on many places in UI is polling with long intervals. Each 20 seconds the url list, app server list or topology is updated with the fresh data. 

We have the server-side bus in place into which inventory events when anyone is 'CRUDing' the entities, I believe alerts are being sent there, etc. Also we have the cmdgw module for dealing with the bus-agent-ui communication, it uses the WebSockets for full-duplex comm. From what I've seen it works like this:

1) ui initializes the WS connection
2) server stores the session, correlation id is the session id
3) later on ui invokes a command with some id
4) once the command is done the ui is notified by the server side (no polling, real server push)
+ some magic with bus (bus works here as a glue with the other components)

What would be imho really useful would be not only using the web socket layer for sending the responses on previously requested operations but also having the ability to send the notification to whoever cares on the ui (without any former explicit action in the ui). I mean events like "something bad happened". After talking with Peter, the better correlation id here is the tenant id, because we don't want to leak the information among the tenants. So if the server keeps the info which session id was created for which tenant we are almost there.

pros:
* alerts can be displayed immediately (no need to wait 20 seconds for the refresh)
* no polling = no wasting with resources
* cool demos

cons:
* switching the persona needs to be handled, but it's doable

What do you think?

jk

From lponce at redhat.com  Tue Oct 20 07:43:20 2015
From: lponce at redhat.com (Lucas Ponce)
Date: Tue, 20 Oct 2015 07:43:20 -0400 (EDT)
Subject: [Hawkular-dev] cmdgw forwarding messages from bus to UI
In-Reply-To: <280824539.27704959.1445340126336.JavaMail.zimbra@redhat.com>
References: <280824539.27704959.1445340126336.JavaMail.zimbra@redhat.com>
Message-ID: <676626853.34134727.1445341400080.JavaMail.zimbra@redhat.com>



----- Original Message -----
> From: "Jiri Kremser" <jkremser at redhat.com>
> To: "Discussions around Hawkular development" <hawkular-dev at lists.jboss.org>
> Sent: Tuesday, October 20, 2015 1:22:06 PM
> Subject: [Hawkular-dev] cmdgw forwarding messages from bus to UI
> 
> Hello,
>   when creating the topology graph, the nice feature would be to see the
>   newly added resources in inventory in a real-time. Currently, the approach
>   on many places in UI is polling with long intervals. Each 20 seconds the
>   url list, app server list or topology is updated with the fresh data.
> 
> We have the server-side bus in place into which inventory events when anyone
> is 'CRUDing' the entities, I believe alerts are being sent there, etc. Also
> we have the cmdgw module for dealing with the bus-agent-ui communication, it
> uses the WebSockets for full-duplex comm. From what I've seen it works like
> this:
> 
> 1) ui initializes the WS connection
> 2) server stores the session, correlation id is the session id
> 3) later on ui invokes a command with some id
> 4) once the command is done the ui is notified by the server side (no
> polling, real server push)
> + some magic with bus (bus works here as a glue with the other components)
> 
> What would be imho really useful would be not only using the web socket layer
> for sending the responses on previously requested operations but also having
> the ability to send the notification to whoever cares on the ui (without any
> former explicit action in the ui). I mean events like "something bad
> happened". After talking with Peter, the better correlation id here is the
> tenant id, because we don't want to leak the information among the tenants.
> So if the server keeps the info which session id was created for which
> tenant we are almost there.
> 
> pros:
> * alerts can be displayed immediately (no need to wait 20 seconds for the
> refresh)

(Small disclaimer, about alerts, being displayed inmediately on the UI are not a strong requeriment on that side, on the contrary alerts are sent inmediately via the actions architecture via configured transport)

> * no polling = no wasting with resources
> * cool demos
> 
> cons:
> * switching the persona needs to be handled, but it's doable
> 
> What do you think?

In a first thought, having a real full duplex communication is attractive.

But, dealing with session on server also mean an extra complexity where the tradeoff is not trivial IMO.

I know that the "clustering-scalability" chapter is not formally open yet, but my first thought is that we deal with a custom session mechanism on the server the complexity might be increased (we need to use ISPN to share this state, to deal with distributed scenarios, etc).

Also, there was a related topic some weeks ago about a server side component to do high level integrations between components, Jay started to think about it, perhaps these two topics can be related and on that scenario, having a full duplex communication could be interesting.

Just my 2 cents.

> 
> jk
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
> 

From jpkroehling at redhat.com  Tue Oct 20 08:10:26 2015
From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=)
Date: Tue, 20 Oct 2015 14:10:26 +0200
Subject: [Hawkular-dev] Accounts 1.0.16.Final released
Message-ID: <56262F32.9080907@redhat.com>

All,

As we have a Hawkular release tomorrow, I just released Accounts 
1.0.16.Final. This is pretty much the same as the Accounts we had last 
week, plus a couple of minor bug fixes. Unfortunately, Keycloak hasn't 
been released yet, so, the offline tokens feature is coming only for the 
next release.

It should be safe for consumers of a recent Accounts to use this newer 
version. As such, I'm sending PRs for all projects that are consuming 
Accounts (to my knowledge):

- Hawkular
- Agent
- Alerts
- BTM
- Command Gateway
- Inventory

- Juca.

From hrupp at redhat.com  Tue Oct 20 08:18:30 2015
From: hrupp at redhat.com (Heiko W.Rupp)
Date: Tue, 20 Oct 2015 14:18:30 +0200
Subject: [Hawkular-dev] Resourcetype again
In-Reply-To: <79CBDA60-DF15-4982-988D-0A8ECABC1BE2@redhat.com>
References: <6859E673-FB75-4957-BE7F-6966ED5203DA@redhat.com>
	<476074189.25063107.1444091421191.JavaMail.zimbra@redhat.com>
	<5022218C-ED12-4E25-9FE1-59914755DC61@redhat.com>
	<32099564.56ockzxRnr@localhost.localdomain>
	<79CBDA60-DF15-4982-988D-0A8ECABC1BE2@redhat.com>
Message-ID: <EC1DDBA2-483C-4094-BCFD-F8727CD6BB57@redhat.com>

Hey,

I just had a good discussion with Lukas in the STR office around
resource types, metadata, syncing and so on. No conclusion yet,
but a much better common understanding. Lukas' idea of 
metadata packs looks like a promising way forward.

We did some drawing on those "whiteboard" glass walls in the
office. You can find those two at

https://www.dropbox.com/s/oktwsuk1mt4g3fa/IMG_20151020_134356.jpg?dl=0
and
https://www.dropbox.com/s/lhlrekprs5xyf2f/IMG_20151020_134406.jpg?dl=0

  Heiko

From hrupp at redhat.com  Tue Oct 20 08:49:04 2015
From: hrupp at redhat.com (Heiko W.Rupp)
Date: Tue, 20 Oct 2015 14:49:04 +0200
Subject: [Hawkular-dev] Resourcetype again
In-Reply-To: <EC1DDBA2-483C-4094-BCFD-F8727CD6BB57@redhat.com>
References: <6859E673-FB75-4957-BE7F-6966ED5203DA@redhat.com>
	<476074189.25063107.1444091421191.JavaMail.zimbra@redhat.com>
	<5022218C-ED12-4E25-9FE1-59914755DC61@redhat.com>
	<32099564.56ockzxRnr@localhost.localdomain>
	<79CBDA60-DF15-4982-988D-0A8ECABC1BE2@redhat.com>
	<EC1DDBA2-483C-4094-BCFD-F8727CD6BB57@redhat.com>
Message-ID: <3FE055D1-F16F-4E5D-B7E9-93FD86CC465C@redhat.com>

Hey,

I wrote:
> and
> https://www.dropbox.com/s/lhlrekprs5xyf2f/IMG_20151020_134406.jpg?dl=0
>

The quality of the other photo has room for improvement, so here it is 
with some
better quality: 
https://www.dropbox.com/s/i7clakhbik4zdky/IMG_20151020_144524.jpg?dl=0

From l_roitman at yahoo.com  Tue Oct 20 11:17:01 2015
From: l_roitman at yahoo.com (Luba Roitman)
Date: Tue, 20 Oct 2015 15:17:01 +0000 (UTC)
Subject: [Hawkular-dev] Problems installing Alpha 5 on Windows
In-Reply-To: <CA+aN=MorGMrpq324pg014EcRt7+8hp-a9Yqpq5zZVAC6C+kH3g@mail.gmail.com>
References: <CA+aN=MorGMrpq324pg014EcRt7+8hp-a9Yqpq5zZVAC6C+kH3g@mail.gmail.com>
Message-ID: <1636422316.379463.1445354221526.JavaMail.yahoo@mail.yahoo.com>

Thanks Thomas, I checked the Docker hub https://hub.docker.com/r/jboss/hawkular-aio/, it looks like it has Alpha 4? (it hasn't been updated for 2 months, and Alpha 5 came out Sept 23)
Are there plans to put Alpha 5 on Docker??
Thanks,?Luba

      From: Thomas Heute <theute at redhat.com>
 To: Discussions around Hawkular development <hawkular-dev at lists.jboss.org> 
Cc: Luba Roitman <l_roitman at yahoo.com> 
 Sent: Tuesday, October 20, 2015 2:11 AM
 Subject: Re: [Hawkular-dev] Problems installing Alpha 5 on Windows
   
Docker installation is available, it's a docker image with everything in it, including Cassandra, which is good to get started.
http://www.hawkular.org/docs/user/quick-start.html#_option_b_install_from_a_docker_image
Thomas





On Mon, Oct 19, 2015 at 7:01 PM, Lukas Krejci <lkrejci at redhat.com> wrote:

Hi,

They could indeed be connected but it's hard to say. Inventory in Alpha6 will
emit more info in such situations but unfortunately in Alpha5 there's no way
of getting more info about inventory init failures from the logs.

As for the ports that need to be open, I believe we need 8080, 9042 and 9160.
The former is for the http interface and the latter two for Cassandra and
Cassandra RPC servers.

On Monday, October 19, 2015 16:44:44 Luba Roitman wrote:
> Hi,
> I am having problems installing Hawkular Alpha 5 on Windows, but before I
> delve into describing them, I am wondering as to whether Docker install
> option is going to be available soon? That would indeed be helpful. As for
> the Windows install problem, after I downloaded Alpha 5 and run
> standalone.bat I have the following exceptions in the server.log (excerpts
> here, more stacktrace in the end of the email)
> jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to
> start the http-interface service Caused by: java.lang.RuntimeException:
> java.net.BindException: Address already in use: bind And then2015-10-18
> 13:01:53,226 WARN? [org.hawkular.inventory.cdi] (ServerService Thread Pool
> -- 68) HAWKINV003501: Inventory backend failed to initialize in an attempt
> 5 of 5.2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail]
> (ServerService Thread Pool -- 68) MSC000001: Failed to start service
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDI
> Publisher.START: org.jboss.msc.service.StartException in service
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDI
> Publisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instanceCaused by: javax.ejb.EJBException:
> java.lang.IllegalStateException: Could not initialize inventory.Caused by:
> java.lang.IllegalStateException: Could not initialize inventory.
>
> Do you think these two could be connected? I can't think of any source for
> binding address conflict, I start Hawkular the first thing after the laptop
> restart, so don't run any local http servers. It is also not clear what is
> the reason for inventory initialization problem, the log doesn't indicate
> any wrong before throwing error. I am running Windows 8.1 64bit
> Would appreciate any input!
> Respectfully, Luba Roitman.
> -------------2015-10-18 13:01:33,144 ERROR [org.jboss.msc.service.fail] (MSC
> service thread 1-4) MSC000001: Failed to start service
> jboss.serverManagement.controller.management.http:
> org.jboss.msc.service.StartException in service
> jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to
> start the http-interface service at
> org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpMa
> nagementService.java:269) at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceC
> ontrollerImpl.java:1948) at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceController
> Impl.java:1881) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1
> 142) at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
> 617) at java.lang.Thread.run(Thread.java:745)Caused by:
> java.lang.RuntimeException: java.net.BindException: Address already in use:
> bind at
> org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpSe
> rver.java:160) at
> org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpMa
> nagementService.java:235) ... 5 moreCaused by: java.net.BindException:
> Address already in use: bind at sun.nio.ch.Net.bind0(Native Method) at
> sun.nio.ch.Net.bind(Net.java:433)------------------ 2015-10-18 13:01:53,226
> WARN? [org.hawkular.inventory.cdi] (ServerService Thread Pool -- 68)
> HAWKINV003501: Inventory backend failed to initialize in an attempt 5 of
> 5.2015-10-18 13:01:54,236 ERROR [org.jboss.msc.service.fail] (ServerService
> Thread Pool -- 68) MSC000001: Failed to start service
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDI
> Publisher.START: org.jboss.msc.service.StartException in service
> jboss.deployment.unit."hawkular-inventory-dist.war".component.InventoryJNDI
> Publisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instance at
> org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService
> .java:57) at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at
> java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1
> 142) at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
> 617) at java.lang.Thread.run(Thread.java:745) at
> org.jboss.threads.JBossThread.run(JBossThread.java:320)Caused by:
> java.lang.IllegalStateException: WFLYEE0042: Failed to construct component
> instance at
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicCo
> mponent.java:163) at
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicCo
> mponent.java:134) at
> org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java
> :88) at
> org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstan
> ce(SingletonComponent.java:122) at
> org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonCom
> ponent.java:136) at
> org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService
> .java:54) ... 6 moreCaused by: javax.ejb.EJBException:
> java.lang.IllegalStateException: Could not initialize inventory. at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxIntercept
> or.java:187) at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:2
> 77) at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:349
> ) at
> org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleC
> MTTxInterceptor.java:66) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocati
> on(WeldInjectionContextInterceptor.java:43) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextIntercepto
> r.processInvocation(CurrentInvocationContextInterceptor.java:41) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(C
> oncurrentContextInterceptor.java:45) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(Contex
> tClassLoaderInterceptor.java:64) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at
> org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(Pr
> ivilegedWithCombinerInterceptor.java:80) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedIntercepto
> r.java:61) at
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicCo
> mponent.java:161) ... 11 moreCaused by: java.lang.IllegalStateException:
> Could not initialize inventory. at
> org.hawkular.inventory.cdi.OfficialInventoryProducer.initInventory(Official
> InventoryProducer.java:115) at
> org.hawkular.inventory.cdi.OfficialInventoryProducer.getInventory(OfficialI
> nventoryProducer.java:64) at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:6
> 2) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
> l.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at
> org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInje
> ctionPoint.java:88) at
> org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInje
> ctionPoint.java:78) at
> org.jboss.weld.injection.producer.ProducerMethodProducer.produce(ProducerMe
> thodProducer.java:95) at
> org.jboss.weld.injection.producer.AbstractMemberProducer.produce(AbstractMe
> mberProducer.java:167) at
> org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:1
> 83) at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
> at
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStr
> ategy.get(ContextualInstanceStrategy.java:101) at
> org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualI
> nstanceStrategy.get(ContextualInstanceStrategy.java:141) at
> org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) at
> org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:76
> 1) at
> org.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerIm
> pl.java:861) at
> org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.jav
> a:92) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:375) at
> org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:386) at
> org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector
> .java:71) at
> org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java
> :48) at
> org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.ja
> va:73) at
> org.jboss.weld.injection.producer.ejb.SessionBeanInjectionTarget.inject(Ses
> sionBeanInjectionTarget.java:140) at
> org.jboss.as.weld.injection.WeldInjectionContext.inject(WeldInjectionContex
> t.java:39) at
> org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(Weld
> InjectionInterceptor.java:51) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvoca
> tion(AroundConstructInterceptorFactory.java:28) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvo
> cation(WeldInterceptorInjectionInterceptor.java:56) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr
> 299BindingsCreateInterceptor.java:100) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(Nam
> espaceContextInterceptor.java:50) at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340
> ) at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:2
> 75) ... 27 more 2015-10-18 13:01:54,251 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("add") failed - address: ([? ? ("core-service" =>
> "management"),? ? ("management-interface" => "http-interface")]) - failure
> description: {"WFLYCTL0080: Failed services" =>
> {"jboss.serverManagement.controller.management.http" =>
> "org.jboss.msc.service.StartException in service
> jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to
> start the http-interface service? ? Caused by: java.lang.RuntimeException:
> java.net.BindException: Address already in use: bind? ? Caused by:
> java.net.BindException: Address already in use: bind"}}2015-10-18
> 13:01:54,251 ERROR [org.jboss.as.controller.management-operation]
> (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address:
> ([("deployment" => "hawkular-inventory-dist.war")]) - failure description:
> {"WFLYCTL0080: Failed services" =>
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.Inventory
> JNDIPublisher.START" => "org.jboss.msc.service.StartException in service
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJN
> DIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instance? ? Caused by: java.lang.IllegalStateException:
> WFLYEE0042: Failed to construct component instance? ? Caused by:
> javax.ejb.EJBException: java.lang.IllegalStateException: Could not
> initialize inventory.? ? Caused by: java.lang.IllegalStateException: Could
> not initialize inventory."}}2015-10-18 13:01:54,251 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("add") failed - address: ([("deployment" =>
> "hawkular-metrics-api-jaxrs.war")]) - failure description: {"WFLYCTL0080:
> Failed services" =>
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.Inventory
> JNDIPublisher.START" => "org.jboss.msc.service.StartException in service
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJN
> DIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instance? ? Caused by: java.lang.IllegalStateException:
> WFLYEE0042: Failed to construct component instance? ? Caused by:
> javax.ejb.EJBException: java.lang.IllegalStateException: Could not
> initialize inventory.? ? Caused by: java.lang.IllegalStateException: Could
> not initialize inventory."}}2015-10-18 13:01:54,251 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("add") failed - address: ([("deployment" =>
> "hawkular-pinger.war")]) - failure description: {"WFLYCTL0080: Failed
> services" =>
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.Inventory
> JNDIPublisher.START" => "org.jboss.msc.service.StartException in service
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJN
> DIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instance? ? Caused by: java.lang.IllegalStateException:
> WFLYEE0042: Failed to construct component instance? ? Caused by:
> javax.ejb.EJBException: java.lang.IllegalStateException: Could not
> initialize inventory.? ? Caused by: java.lang.IllegalStateException: Could
> not initialize inventory."}}2015-10-18 13:01:54,267 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("add") failed - address: ([("deployment" =>
> "hawkular-redhat-access-integration-backend.war")]) - failure description:
> {"WFLYCTL0080: Failed services" =>
> {"jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.Inventory
> JNDIPublisher.START" => "org.jboss.msc.service.StartException in service
> jboss.deployment.unit.\"hawkular-inventory-dist.war\".component.InventoryJN
> DIPublisher.START: java.lang.IllegalStateException: WFLYEE0042: Failed to
> construct component instance? ? Caused by: java.lang.IllegalStateException:
> WFLYEE0042: Failed to construct component instance? ? Caused by:
> javax.ejb.EJBException: java.lang.IllegalStateException: Could not
> initialize inventory.? ? Caused by: java.lang.IllegalStateException: Could
> not initialize inventory."}}

_______________________________________________
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/20151020/8a9cf5f3/attachment-0001.html 

From jshaughn at redhat.com  Tue Oct 20 17:06:01 2015
From: jshaughn at redhat.com (Jay Shaughnessy)
Date: Tue, 20 Oct 2015 17:06:01 -0400
Subject: [Hawkular-dev] Hawkular Alerts 0.5.0.Final Released!
Message-ID: <5626ACB9.2070900@redhat.com>


Hawkular Alerts 0.5.0.Final has been Released!

Notable Features:

  * Action History
      o The history of executed actions is now persisted and queryable
        in a flexible way.
  * Alerts now support Notes
      o Any number of Notes can now be added to an Alert, to track it's
        progress and/or resolution.
      o This more flexible mechanism replaces the ackNotes and
        resolvedNotes.
  * Actions are now executed asynchronously in Standalone deployments
      o Previously a hung action could hang a standalone engine.
  * Triggers now support criteria fetch and paging.


There have been some changes to the REST endpoints as we refine the model.

Jira Summary for features above, as well as minor enhancements and fixes:

  *   https://issues.jboss.org/projects/HWKALERTS/versions/12328199


The next scheduled version is 0.6.0, targeted for November 10, 2015.  It 
is scheduled to include a major new feature, Event support!

Hawkular Alerts Team
    Jay Shaughnessy (jshaughn at redhat.com)
    Lucas Ponce (lponce at redhat.com)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151020/373a8d7b/attachment.html 

From jkremser at redhat.com  Wed Oct 21 09:42:41 2015
From: jkremser at redhat.com (Jiri Kremser)
Date: Wed, 21 Oct 2015 09:42:41 -0400 (EDT)
Subject: [Hawkular-dev] cmdgw forwarding messages from bus to UI
In-Reply-To: <676626853.34134727.1445341400080.JavaMail.zimbra@redhat.com>
References: <280824539.27704959.1445340126336.JavaMail.zimbra@redhat.com>
	<676626853.34134727.1445341400080.JavaMail.zimbra@redhat.com>
Message-ID: <1105926321.28035190.1445434961567.JavaMail.zimbra@redhat.com>

| on the contrary alerts are sent
| inmediately via the actions architecture via configured transport

notifications are quite ok, but notifications on the dashboard in web UI are quite common today (take social networks for instance)
Lucas, do you also send the notification on the bus if the alert is triggered?


| In a first thought, having a real full duplex communication is attractive.

well, we have the full duplex communication right now. Web Sockets are by design full-duplex comm layer. What I was suggesting was to extend the set of use-cases we are using it for, currently (afaik) it's only invoking commands.


| But, dealing with session on server also mean an extra complexity where the
| tradeoff is not trivial IMO.

agreed, the current approach is quite naive. It's the in-memory hashmap. This works for 1 instance of Hawkular, but won't probably work for multi-node deployments, on the other hand I see bigger challenges that are blocking the multi-node Hawkular right now than this.

jk

From lponce at redhat.com  Wed Oct 21 10:01:45 2015
From: lponce at redhat.com (Lucas Ponce)
Date: Wed, 21 Oct 2015 10:01:45 -0400 (EDT)
Subject: [Hawkular-dev] cmdgw forwarding messages from bus to UI
In-Reply-To: <1105926321.28035190.1445434961567.JavaMail.zimbra@redhat.com>
References: <280824539.27704959.1445340126336.JavaMail.zimbra@redhat.com>
	<676626853.34134727.1445341400080.JavaMail.zimbra@redhat.com>
	<1105926321.28035190.1445434961567.JavaMail.zimbra@redhat.com>
Message-ID: <775104839.35229044.1445436105677.JavaMail.zimbra@redhat.com>



----- Original Message -----
> From: "Jiri Kremser" <jkremser at redhat.com>
> To: "Discussions around Hawkular development" <hawkular-dev at lists.jboss.org>
> Sent: Wednesday, October 21, 2015 3:42:41 PM
> Subject: Re: [Hawkular-dev] cmdgw forwarding messages from bus to UI
> 
> | on the contrary alerts are sent
> | inmediately via the actions architecture via configured transport
> 
> notifications are quite ok, but notifications on the dashboard in web UI are
> quite common today (take social networks for instance)
> Lucas, do you also send the notification on the bus if the alert is
> triggered?
> 

There are notifications showed in the UI today, but using the general polling mechanism used for communication UI vs REST API.

Bus is used internally as a mechanism of communication between the alerts engine and its plugins architecture.

> 
> | In a first thought, having a real full duplex communication is attractive.
> 
> well, we have the full duplex communication right now. Web Sockets are by
> design full-duplex comm layer. What I was suggesting was to extend the set
> of use-cases we are using it for, currently (afaik) it's only invoking
> commands.
>

I guess this could be an interesting topic for a watercooler meeting.

It would be interesting how is it designed.

So, if at some point we need to apply a similar design, we can just reuse/adapt it.
 
Thanks,
Lucas

From mazz at redhat.com  Wed Oct 21 10:31:06 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Wed, 21 Oct 2015 10:31:06 -0400 (EDT)
Subject: [Hawkular-dev] cmdgw forwarding messages from bus to UI
In-Reply-To: <1105926321.28035190.1445434961567.JavaMail.zimbra@redhat.com>
References: <280824539.27704959.1445340126336.JavaMail.zimbra@redhat.com>
	<676626853.34134727.1445341400080.JavaMail.zimbra@redhat.com>
	<1105926321.28035190.1445434961567.JavaMail.zimbra@redhat.com>
Message-ID: <1199871535.35250246.1445437866726.JavaMail.zimbra@redhat.com>

> | But, dealing with session on server also mean an extra complexity where the
> | tradeoff is not trivial IMO.
> 
> agreed, the current approach is quite naive. It's the in-memory hashmap. This
> works for 1 instance of Hawkular, but won't probably work for multi-node
> deployments, on the other hand I see bigger challenges that are blocking the
> multi-node Hawkular right now than this.

The WebSocket stuff that cmdgw has fully supports multi-node Hawkular servers. In fact, the demo I showed a month or two ago illustrated this (though it was in the one direction of UI->agent, not the other way around).

The way it works is each WS client (be it a UI client or a feed) connects to one hawkular server in the cluster - call it H. As soon as a WS client connects to H, H will add all the appropriate bus subscriptions for that client so when a message destined for that UI client is received on the bus, the message is immediately forwarded over the WS to the client. Now, if Hawkular Server X wants to send a message to that UI client, it does so via the bus. It sends a message to a queue or topic which H can consume and forward to the UI client over the WS.

The whole reason behind using the bus in the WebSocket stuff was to support multi-node Hawkular Server deployments.

From mfoley at redhat.com  Thu Oct 22 14:41:38 2015
From: mfoley at redhat.com (Michael Foley)
Date: Thu, 22 Oct 2015 14:41:38 -0400 (EDT)
Subject: [Hawkular-dev] Discussion, Planning,
 and status on Testing Openshift & Hawk-Metrics Integration for
 Openshift 3.1
Message-ID: <1920060852.80011129.1445539298489.JavaMail.zimbra@zmail15.collab.prod.int.phx2.redhat.com>

The following meeting has been modified:

Subject: Discussion, Planning, and status  on Testing Openshift &amp; Hawk-Metrics Integration for Openshift 3.1  [MODIFIED]
Organizer: "Michael Foley" <mfoley at redhat.com> 

Location: Bluejeans   http://www.bluejeans.com/mfoley51 
Time: 3:00:00 PM - 3:30:00 PM GMT -05:00 US/Canada Eastern [MODIFIED]
 Recurrence : Every 1 week(s) on  No end date Effective Sep 9, 2015

Required: pruan at redhat.com; mmahoney at redhat.com; vnguyen at redhat.com; snegrea at redhat.com; jsanda at redhat.com; mwringe at redhat.com 
Optional: jon-qa-list at redhat.com; jboss-on-team at redhat.com; hawkular-dev at lists.jboss.org 

*~*~*~*~*~*~*~*~*~*

Hi, 

Let's have a discussion and planning session on testing Openshift & Hawkular Integration! 

Let's use this etherpad to coordinate the discussion -->> http://pad.engineering.redhat.com/Management-nextAndOpenshiftTestPlanning 

5 Point Plan for Openshift 3.1 GA 


    * Unit tests .... owned by Hawk-Metrics developers 
    * Integration tests ... owned by Hawk-Metrics developers and Hawk-Metrics QE 


        * Performance CI on Hawk-Metrics (this one is actually new and was not discussed on Wednesday , but I now see it makes sense) 
        * Functional Integration tests on Hawk-Metrics latest + Openshift Origin latest 
    * 
Funtional/UI .... Cucumber/Ruby tests ...owned by Openshift QE     * Functional/Rest ... Cucumber/Ruby tests ... owned by Openshift QE 
    * Performance & Scalability .... owned by Openshift QE 

Regards, 

Michael Foley 
QE Supervisor, Middleware BU 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151022/faa5081d/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 195832 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151022/faa5081d/attachment-0001.bin 

From lkrejci at redhat.com  Thu Oct 22 18:26:55 2015
From: lkrejci at redhat.com (Lukas Krejci)
Date: Fri, 23 Oct 2015 00:26:55 +0200
Subject: [Hawkular-dev] Inspecting inventory storage internals
Message-ID: <15059891.ZooVxGJpLV@localhost.localdomain>

Hi,

a couple of folks asked how we inspect what is stored inside inventory's live 
DB.

The truth is that mostly it is the REST API ;) but sometimes, it is true that 
one needs to really look at individual vertices and edges in the graph 
storage.

To see that, Jirka spent some time on a low level inventory visualization but 
I am not sure that has come to conclusion. In the meantime, this is how I do 
it.

I suppose you're running hawkular dist in dev mode, C* backing the metrics and 
inventory running on localhost, default ports.

0) Build Hawkular with dev profile and start it up.

1) Install Titan 0.5.4 separately [1].
2) Unzip and cd into it.
3) run "bin/gremlin.sh"
4) Run the following in the gremlin CLI: 
  g = TitanFactory.build().set("storage.backend", 
"cassandrathrift").set("storage.cassandra.keyspace", 
"hawkular_inventory").open()

That will open the inventory graph in the variable "g".
You now have the full power of Groovy and Gremlin [2] at your fingertips.

To get you started, here are a few queries you can run:

1) list all properties of all tenants

  g.V().has("__type", "tenant").map

`V()` will give you all vertices in the graph,
`.has()` will filter them on a value of some property
`.map` will output the properties of each vertex as a map

2) List all outgoing edges from all environments
  
  g.V().has("__type", "tenant").out("contains").has("__type", 
"environment").outE()

`.out(...)` will hop from a vertex over all edges with given label to all 
target vertices (if no label is given (call without arguments), target 
vertices of all outgoing edges are listed)
`.outE(...)` will list the outgoing edges (constrained to given labels, if 
any)

(if you want to see the properties of those edges, add ".map" to the end).

3) List all Wildfly servers under a feed:

  g.V().has("__cp", 
"/t;<tenantId>/e;test/f;<feedId>").outE("contains").has("__targetType", 
"resource").inV().as("resource").inE("defines").has("__sourceType", 
"resourceType").outV().has("__eid", "WildFly Server").back("resource")

4) To see the root map of the resource config of the those resources, add the 
following to the above query:

  .out("contains").has("__type", "dataEntity").has("__eid", 
"configuration").out("hasData")

5) To see the values inside that map, additionally add the following:

  .out.map


Hope this helps,

Lukas

[1] http://s3.thinkaurelius.com/downloads/titan/titan-0.5.4-hadoop2.zip
[2] http://s3.thinkaurelius.com/docs/titan/0.5.4/gremlin.html

From mazz at redhat.com  Thu Oct 22 19:32:16 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Thu, 22 Oct 2015 19:32:16 -0400 (EDT)
Subject: [Hawkular-dev] strange chars in test output
In-Reply-To: <731200964.36024522.1445556570625.JavaMail.zimbra@redhat.com>
Message-ID: <706714537.36024861.1445556736695.JavaMail.zimbra@redhat.com>

Just ran a build and it looks like we are logging the contents of a zip file - which causes all kinds of bad things in the console:

FINE: Received over WebSocket: ExportJdrResponse={"fileName":"jdr_15-10-22_10-04-43_testing-worker-linux-docker-4d45e4b4-3236-linux-3.zip","resourcePath":"/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;testing-worker-linux-docker-4d45e4b4-3236-linux-3/r;testing-worker-linux-docker-4d45e4b4-3236-linux-3~Local~~","destinationSessionId":"0I6Sw6bmxVggotD_2ti9F8WuY1R8-no6YDbDRJfn","status":"OK","message":"{\"start-time\" => \"Thu Oct 22 22:04:43 UTC 2015\",\"end-time\" => \"Thu Oct 22 22:05:46 UTC 2015\",\"report-location\" => \"/home/travis/build/hawkular/hawkular-agent/hawkular-agent-itest-parent/hawkular-agent-itest/target/hawkular-agent-itest-dist/hawkular-agent-itest-dist-0.12.0.Final-SNAPSHOT/standalone/tmp/jdr_15-10-22_10-04-43_testing-worker-linux-docker-4d45e4b4-3236-linux-3.zip\"}"}PK??????VGSjdr_15-10-22_10-04-43_testing-worker-linux-docker-4d45e4b4-3236-linux-3/version.txt???r	???R(-?????J???/.???J??????M???rR????????????
?????????

It looks like we are trying to log the full JSON message that the WS receives, which is very bad because this could include a) sensitive data in the message (like passwords) and b) raw binary data

I'll look to see where this is coming from and fix it.


From mazz at redhat.com  Thu Oct 22 19:33:58 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Thu, 22 Oct 2015 19:33:58 -0400 (EDT)
Subject: [Hawkular-dev] strange chars in test output
In-Reply-To: <706714537.36024861.1445556736695.JavaMail.zimbra@redhat.com>
References: <706714537.36024861.1445556736695.JavaMail.zimbra@redhat.com>
Message-ID: <1418973462.36024904.1445556838637.JavaMail.zimbra@redhat.com>

> receives, which is very bad because this could include a) sensitive data in
> the message (like passwords)

Like this:

FINE: Sending over WebSocket: ExportJdrRequest={"authentication":{"username":"jdoe","password":"password"}, "resourcePath":"/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;testing-worker-linux-docker-4d45e4b4-3236-linux-3/r;testing-worker-linux-docker-4d45e4b4-3236-linux-3~Local~~"}

From mazz at redhat.com  Thu Oct 22 19:36:44 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Thu, 22 Oct 2015 19:36:44 -0400 (EDT)
Subject: [Hawkular-dev] strange chars in test output
In-Reply-To: <1418973462.36024904.1445556838637.JavaMail.zimbra@redhat.com>
References: <706714537.36024861.1445556736695.JavaMail.zimbra@redhat.com>
	<1418973462.36024904.1445556838637.JavaMail.zimbra@redhat.com>
Message-ID: <1650573830.36025082.1445557004278.JavaMail.zimbra@redhat.com>

Oh, this logging is being done in test code (should have realized that when I noticed it was using Java logging).

I'll still have to fix this to avoid dumping binary content.

----- Original Message -----
> > receives, which is very bad because this could include a) sensitive data in
> > the message (like passwords)
> 
> Like this:
> 
> FINE: Sending over WebSocket:
> ExportJdrRequest={"authentication":{"username":"jdoe","password":"password"},
> "resourcePath":"/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;testing-worker-linux-docker-4d45e4b4-3236-linux-3/r;testing-worker-linux-docker-4d45e4b4-3236-linux-3~Local~~"}
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
> 

From ah at tradeworks.io  Fri Oct 23 19:21:28 2015
From: ah at tradeworks.io (Anton Hughes)
Date: Sat, 24 Oct 2015 01:21:28 +0200
Subject: [Hawkular-dev] Is this an applicable use-case for Hawkular
Message-ID: <CAMOUzMAJG38aDKFgvfuvjhLOeGMzzU98rDugyH7xQfGjdQ6Tvg@mail.gmail.com>

Hello

I have been watching the developments of Hawkular, and am really impressed!

I have a few questions about Hawkular.

Hawkular seems to be primarily focused on server metrics and monitoring.

I am, however, interested in exploring the possibility of using it for
monitoring and alerting of specific business events. For example, lets say
I had an online shop and I sold my widgets via affiliates. Would it be
possible to capture the sales event, persist and display metrics - so the
affiliate partner could login and see their activities? And to send such
events to Hawkular, is there a java client?

When using the server agent, are captured events sent async?

Thanks



-- 
Anton Hughes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151024/b6c25a6c/attachment.html 

From vandillon at gmail.com  Sun Oct 25 10:20:19 2015
From: vandillon at gmail.com (Van Dillon)
Date: Sun, 25 Oct 2015 10:20:19 -0400
Subject: [Hawkular-dev] Hawkular Alhpa6 questions
Message-ID: <CAB4ARSCsNYM3jv1OKJHK+FTFate7pB5JQmswR3pr8NpFwX7f3g@mail.gmail.com>

Hi,

I have a few questions about Hawkular-aio Alpha6.

1) I can't get metric data to stay in the system for more than about 8
hours.  The documentation says data retention units are in days.  I've
tried using the REST APIs to set the retentions to 365 when I create a
Metrics tenant.  I've also tried setting it to 365 for individual Metric
definitions.  Neither approach seems to make a difference.  Am I missing
something?  I'm running on Windows 7 x64.

2) Will the jboss/hawkular-aio docker image be updated to this release?  It
hasn't been updated since Alpha4.

Any help would be greatly appreciated.


Thanks,

Van Dillon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151025/e0dda340/attachment.html 

From jsanda at redhat.com  Sun Oct 25 10:51:03 2015
From: jsanda at redhat.com (John Sanda)
Date: Sun, 25 Oct 2015 10:51:03 -0400
Subject: [Hawkular-dev] Hawkular Alhpa6 questions
In-Reply-To: <CAB4ARSCsNYM3jv1OKJHK+FTFate7pB5JQmswR3pr8NpFwX7f3g@mail.gmail.com>
References: <CAB4ARSCsNYM3jv1OKJHK+FTFate7pB5JQmswR3pr8NpFwX7f3g@mail.gmail.com>
Message-ID: <9E91F372-B7CD-414D-9CDB-DF8A08ACF458@redhat.com>

It looks like there is a bug in the tenant creation operation. Cassandra stores data retention in seconds. Hawkular Metrics is supposed to convert from days to seconds; however, it appears that the tenant creation operation is not doing that conversion. If you want 10 days retention, then try a value of 864000. If no retention is specified, then the system wide default of 7 days is used. If you create a ticket for this, it would be greatly appreciated.

- John

> On Oct 25, 2015, at 10:20 AM, Van Dillon <vandillon at gmail.com> wrote:
> 
> Hi,
> 
> I have a few questions about Hawkular-aio Alpha6.
> 
> 1) I can't get metric data to stay in the system for more than about 8 hours.  The documentation says data retention units are in days.  I've tried using the REST APIs to set the retentions to 365 when I create a Metrics tenant.  I've also tried setting it to 365 for individual Metric definitions.  Neither approach seems to make a difference.  Am I missing something?  I'm running on Windows 7 x64.
> 
> 2) Will the jboss/hawkular-aio docker image be updated to this release?  It hasn't been updated since Alpha4.
> 
> Any help would be greatly appreciated.
> 
> 
> Thanks,
> 
> Van Dillon
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev



From gbrown at redhat.com  Mon Oct 26 04:26:50 2015
From: gbrown at redhat.com (Gary Brown)
Date: Mon, 26 Oct 2015 04:26:50 -0400 (EDT)
Subject: [Hawkular-dev] Is this an applicable use-case for Hawkular
In-Reply-To: <CAMOUzMAJG38aDKFgvfuvjhLOeGMzzU98rDugyH7xQfGjdQ6Tvg@mail.gmail.com>
References: <CAMOUzMAJG38aDKFgvfuvjhLOeGMzzU98rDugyH7xQfGjdQ6Tvg@mail.gmail.com>
Message-ID: <536565134.40626954.1445848010233.JavaMail.zimbra@redhat.com>

Hi Anton

It sounds like from your scenario, you are just interested in reporting a specific business event, in which case I believe it is possible to just create your own metric with data points, using the metrics REST API - however I'll let the members of the metrics team comment more on that.

If you are interested in recording more information about your business transaction, then you may want to consider Hawkular BTM. Its currently possible to capture the 'call trace' of a business transaction instance and analyse the information using Kibana - you can also extract relevant properties from the txn (e.g. affiliate) and use that information to focus any queries.

The intention is to integrate at the backend with Hawkular Metrics and Alerts, but this isn't in place at the moment.

Regards
Gary

----- Original Message -----
> Hello
> 
> I have been watching the developments of Hawkular, and am really impressed!
> 
> I have a few questions about Hawkular.
> 
> Hawkular seems to be primarily focused on server metrics and monitoring.
> 
> I am, however, interested in exploring the possibility of using it for
> monitoring and alerting of specific business events. For example, lets say I
> had an online shop and I sold my widgets via affiliates. Would it be
> possible to capture the sales event, persist and display metrics - so the
> affiliate partner could login and see their activities? And to send such
> events to Hawkular, is there a java client?
> 
> When using the server agent, are captured events sent async?
> 
> Thanks
> 
> 
> 
> --
> Anton Hughes
> 
> 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
> 

From ah at tradeworks.io  Mon Oct 26 04:56:52 2015
From: ah at tradeworks.io (Anton Hughes)
Date: Mon, 26 Oct 2015 09:56:52 +0100
Subject: [Hawkular-dev] Is this an applicable use-case for Hawkular
In-Reply-To: <536565134.40626954.1445848010233.JavaMail.zimbra@redhat.com>
References: <CAMOUzMAJG38aDKFgvfuvjhLOeGMzzU98rDugyH7xQfGjdQ6Tvg@mail.gmail.com>
	<536565134.40626954.1445848010233.JavaMail.zimbra@redhat.com>
Message-ID: <CAMOUzMA=XmjNEdrY5gTj7zvvqY0MLqwO+32t3hBQDuF_qc2Dog@mail.gmail.com>

Thanks Gary
On 26 October 2015 at 09:26, Gary Brown <gbrown at redhat.com> wrote:

> If you are interested in recording more information about your business
> transaction, then you may want to consider Hawkular BTM. Its currently
> possible to capture the 'call trace' of a business transaction instance and
> analyse the information using Kibana - you can also extract relevant
> properties from the txn (e.g. affiliate) and use that information to focus
> any queries.
>
Does this capturing happen via the wildfly agent, or is it possible to do
it via a java client or rest call?


>
> The intention is to integrate at the backend with Hawkular Metrics and
> Alerts, but this isn't in place at the moment.
>
Is there a scheduled plan for this?

Thanks




-- 
Anton Hughes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151026/8c79dc5a/attachment-0001.html 

From gbrown at redhat.com  Mon Oct 26 05:34:31 2015
From: gbrown at redhat.com (Gary Brown)
Date: Mon, 26 Oct 2015 05:34:31 -0400 (EDT)
Subject: [Hawkular-dev] Is this an applicable use-case for Hawkular
In-Reply-To: <CAMOUzMA=XmjNEdrY5gTj7zvvqY0MLqwO+32t3hBQDuF_qc2Dog@mail.gmail.com>
References: <CAMOUzMAJG38aDKFgvfuvjhLOeGMzzU98rDugyH7xQfGjdQ6Tvg@mail.gmail.com>
	<536565134.40626954.1445848010233.JavaMail.zimbra@redhat.com>
	<CAMOUzMA=XmjNEdrY5gTj7zvvqY0MLqwO+32t3hBQDuF_qc2Dog@mail.gmail.com>
Message-ID: <1831924103.40650265.1445852071842.JavaMail.zimbra@redhat.com>



----- Original Message -----
> Thanks Gary
> On 26 October 2015 at 09:26, Gary Brown < gbrown at redhat.com > wrote:
> 
> 
> 
> If you are interested in recording more information about your business
> transaction, then you may want to consider Hawkular BTM. Its currently
> possible to capture the 'call trace' of a business transaction instance and
> analyse the information using Kibana - you can also extract relevant
> properties from the txn (e.g. affiliate) and use that information to focus
> any queries.
> Does this capturing happen via the wildfly agent, or is it possible to do it
> via a java client or rest call?

BTM uses ByteMan to instrument a java app and the information is then reported to the server via a REST API - so it would also be possible for apps to directly report the business transaction info to the server via the same REST API if they wished.

A demo of the latest release can be found here: https://www.youtube.com/watch?v=vCIgC3QuJTI

Currently business transaction config details are stored in json files, but I'm currently working on a UI for the next release which should make it a bit easier to work with.

> 
> 
> 
> 
> The intention is to integrate at the backend with Hawkular Metrics and
> Alerts, but this isn't in place at the moment.
> Is there a scheduled plan for this?

Not currently. Before BTM could store information in metrics, this issue https://issues.jboss.org/browse/HWKMETRICS-253 would need to be resolved.

Regards
Gary

> 
> Thanks
> 
> 
> 
> 
> --
> Anton Hughes
> 
> 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
> 

From theute at redhat.com  Mon Oct 26 06:01:11 2015
From: theute at redhat.com (Thomas Heute)
Date: Mon, 26 Oct 2015 11:01:11 +0100
Subject: [Hawkular-dev] Hawkular Alhpa6 questions
In-Reply-To: <9E91F372-B7CD-414D-9CDB-DF8A08ACF458@redhat.com>
References: <CAB4ARSCsNYM3jv1OKJHK+FTFate7pB5JQmswR3pr8NpFwX7f3g@mail.gmail.com>
	<9E91F372-B7CD-414D-9CDB-DF8A08ACF458@redhat.com>
Message-ID: <CA+aN=Mo=mE5OKriO4p3S7-ihvnCxgEG1n_NeCet-tJYR=v0MhA@mail.gmail.com>

I just made a PR for the new AIO Docker image version:
https://github.com/jboss-dockerfiles/hawkular/pull/5
It usually takes a day.

Sorry, this was a release glitch for the past 2 releases.

On Sun, Oct 25, 2015 at 3:51 PM, John Sanda <jsanda at redhat.com> wrote:

> It looks like there is a bug in the tenant creation operation. Cassandra
> stores data retention in seconds. Hawkular Metrics is supposed to convert
> from days to seconds; however, it appears that the tenant creation
> operation is not doing that conversion. If you want 10 days retention, then
> try a value of 864000. If no retention is specified, then the system wide
> default of 7 days is used. If you create a ticket for this, it would be
> greatly appreciated.
>
> - John
>
> > On Oct 25, 2015, at 10:20 AM, Van Dillon <vandillon at gmail.com> wrote:
> >
> > Hi,
> >
> > I have a few questions about Hawkular-aio Alpha6.
> >
> > 1) I can't get metric data to stay in the system for more than about 8
> hours.  The documentation says data retention units are in days.  I've
> tried using the REST APIs to set the retentions to 365 when I create a
> Metrics tenant.  I've also tried setting it to 365 for individual Metric
> definitions.  Neither approach seems to make a difference.  Am I missing
> something?  I'm running on Windows 7 x64.
> >
> > 2) Will the jboss/hawkular-aio docker image be updated to this release?
> It hasn't been updated since Alpha4.
> >
> > Any help would be greatly appreciated.
> >
> >
> > Thanks,
> >
> > Van Dillon
> > _______________________________________________
> > 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/20151026/fd1c9d26/attachment.html 

From fryan53 at gmail.com  Mon Oct 26 06:43:24 2015
From: fryan53 at gmail.com (Frank Ryan)
Date: Mon, 26 Oct 2015 06:43:24 -0400
Subject: [Hawkular-dev] Hawkular integration questions
Message-ID: <CAFx3BUqf8rW0TxURbA6xGCL2A1u046at9STKT9uD05Pe4msF=g@mail.gmail.com>

At this time both PTrans and Heapster only integrate with the Hawkular
Metrics subsytem.  Are there plans to integrate these modules with Hawkular
AIO to populate inventory as well?

Thanks

Frank Ryan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151026/a90d3f11/attachment.html 

From tsegismo at redhat.com  Mon Oct 26 08:37:18 2015
From: tsegismo at redhat.com (Thomas Segismont)
Date: Mon, 26 Oct 2015 13:37:18 +0100
Subject: [Hawkular-dev] Hawkular integration questions
In-Reply-To: <CAFx3BUqf8rW0TxURbA6xGCL2A1u046at9STKT9uD05Pe4msF=g@mail.gmail.com>
References: <CAFx3BUqf8rW0TxURbA6xGCL2A1u046at9STKT9uD05Pe4msF=g@mail.gmail.com>
Message-ID: <562E1E7E.6030601@redhat.com>

PTrans was started to allow metrics reporting from external sources 
(well known collectors with well known protocols).

Could you elaborate on the need?

Le 26/10/2015 11:43, Frank Ryan a ?crit :
> At this time both PTrans and Heapster only integrate with the Hawkular
> Metrics subsytem.  Are there plans to integrate these modules with
> Hawkular AIO to populate inventory as well?
>
> Thanks
>
> Frank Ryan
>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>


From tsegismo at redhat.com  Mon Oct 26 13:47:10 2015
From: tsegismo at redhat.com (Thomas Segismont)
Date: Mon, 26 Oct 2015 18:47:10 +0100
Subject: [Hawkular-dev] ActiveMQ + XA
Message-ID: <562E671E.8030106@redhat.com>

Hi everyone,

Just a note in case you didn't know: you should pay attention to 
transaction declarations when you combine MDB bus listeners with other 
beans:

*ActiveMQ does not currently support XA Transaction suspend / resume 
semantics.*
http://activemq.apache.org/should-i-use-xa.html

Regards,
Thomas

From jsanda at redhat.com  Mon Oct 26 14:11:54 2015
From: jsanda at redhat.com (John Sanda)
Date: Mon, 26 Oct 2015 14:11:54 -0400
Subject: [Hawkular-dev] ActiveMQ + XA
In-Reply-To: <562E671E.8030106@redhat.com>
References: <562E671E.8030106@redhat.com>
Message-ID: <878843B2-D17D-4028-A602-BA27A552CF2F@redhat.com>

FYI, I am currently working on https://issues.jboss.org/browse/HAWKULAR-732 <https://issues.jboss.org/browse/HAWKULAR-732>.

> On Oct 26, 2015, at 1:47 PM, Thomas Segismont <tsegismo at redhat.com> wrote:
> 
> Hi everyone,
> 
> Just a note in case you didn't know: you should pay attention to 
> transaction declarations when you combine MDB bus listeners with other 
> beans:
> 
> *ActiveMQ does not currently support XA Transaction suspend / resume 
> semantics.*
> http://activemq.apache.org/should-i-use-xa.html
> 
> Regards,
> Thomas
> _______________________________________________
> 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/20151026/1aa759b4/attachment.html 

From jpkroehling at redhat.com  Tue Oct 27 07:08:32 2015
From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=)
Date: Tue, 27 Oct 2015 12:08:32 +0100
Subject: [Hawkular-dev] Accounts on Cassandra
Message-ID: <562F5B30.5030302@redhat.com>

Team,

I'm moving Accounts to Cassandra, so that Hawkular won't need a RDMBS 
just because of it.

I tried to keep backwards compatibility, but there's one part that could 
break your code: the models are now using UUIDs for the IDs. Previously, 
the IDs were strings, which were UUIDs as string by default, but your 
component had the freedom to specify an own ID.

As far as I know, only Inventory specifies its own ID for the Resource 
class. It seems that Jirka is OK with changing it to UUID, but if you 
have any problems with that, let me know and I'll remove this requirement.

Note that if all you do is consume the IDs generated by Accounts, you 
should *not* be affected, as all old methods are converting the UUIDs 
that you send as String back to UUID.

Apart from that, it should be fully backwards compatible, but in any 
case, I'll be releasing accounts 1.0.17.Final and branching 1.0.x.

Cassandra changes will be applied to 1.1.0.Final. All changes from 
1.1.0.Final and on will be backported to 1.0.x *up to the next MS*. If 
everything goes right for the next MS, I'll stop maintaining 1.0.x.

- Juca.

From jpkroehling at redhat.com  Tue Oct 27 07:57:59 2015
From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=)
Date: Tue, 27 Oct 2015 12:57:59 +0100
Subject: [Hawkular-dev] Accounts on Cassandra
In-Reply-To: <562F5B30.5030302@redhat.com>
References: <562F5B30.5030302@redhat.com>
Message-ID: <562F66C7.3050306@redhat.com>

On 10/27/2015 12:08 PM, Juraci Paix?o Kr?hling wrote:
> I'm moving Accounts to Cassandra, so that Hawkular won't need a RDMBS
> just because of it.

I guess this point is a bit misleading: while our Hawkular components 
wouldn't need a RDMBS, Keycloak still needs might require one.

- Juca.

From mazz at redhat.com  Tue Oct 27 08:14:16 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Tue, 27 Oct 2015 08:14:16 -0400 (EDT)
Subject: [Hawkular-dev] Accounts on Cassandra
In-Reply-To: <562F5B30.5030302@redhat.com>
References: <562F5B30.5030302@redhat.com>
Message-ID: <2132208163.37662735.1445948056110.JavaMail.zimbra@redhat.com>

Can you clarify what ID you are talking about? This isn't the resource IDs is it? The IDs that feeds create and send to inventory and metrics? AFAIK, the hawkular design for these IDs was that feeds were free to create their own IDs with their own formats/syntax (so long as they are Strings).

But I have a feeling the "ID" you are talking about is different - but I just wanted to clarify to make sure.

----- Original Message -----
> Team,
> 
> I'm moving Accounts to Cassandra, so that Hawkular won't need a RDMBS
> just because of it.
> 
> I tried to keep backwards compatibility, but there's one part that could
> break your code: the models are now using UUIDs for the IDs. Previously,
> the IDs were strings, which were UUIDs as string by default, but your
> component had the freedom to specify an own ID.
> 
> As far as I know, only Inventory specifies its own ID for the Resource
> class. It seems that Jirka is OK with changing it to UUID, but if you
> have any problems with that, let me know and I'll remove this requirement.
> 
> Note that if all you do is consume the IDs generated by Accounts, you
> should *not* be affected, as all old methods are converting the UUIDs
> that you send as String back to UUID.
> 
> Apart from that, it should be fully backwards compatible, but in any
> case, I'll be releasing accounts 1.0.17.Final and branching 1.0.x.
> 
> Cassandra changes will be applied to 1.1.0.Final. All changes from
> 1.1.0.Final and on will be backported to 1.0.x *up to the next MS*. If
> everything goes right for the next MS, I'll stop maintaining 1.0.x.
> 
> - Juca.
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
> 

From jshaughn at redhat.com  Tue Oct 27 08:29:03 2015
From: jshaughn at redhat.com (Jay Shaughnessy)
Date: Tue, 27 Oct 2015 08:29:03 -0400
Subject: [Hawkular-dev] Is this an applicable use-case for Hawkular
In-Reply-To: <536565134.40626954.1445848010233.JavaMail.zimbra@redhat.com>
References: <CAMOUzMAJG38aDKFgvfuvjhLOeGMzzU98rDugyH7xQfGjdQ6Tvg@mail.gmail.com>
	<536565134.40626954.1445848010233.JavaMail.zimbra@redhat.com>
Message-ID: <562F6E0F.2000908@redhat.com>


Hi Anton,

You're right that at the moment server monitoring is the focus and the 
only significant feed is the Wildfly feed.  But the APIs should be there 
to develop a custom feed if you like, to generate your own resources, 
metrics and alert definitions.   Also, depending on your needs, you 
could find that your main needs are metrics and alerting, maybe BTM as 
well, and those components can both be used in a "standalone" mode, 
independent of the Hawkular framework.  REST APIs are the typical way to 
interact with Hawkular.  Hawkular Alerts has no built-in UI, I'm not 
sure if Metrics comes with any visualization outside of Hawkular.


On 10/26/2015 4:26 AM, Gary Brown wrote:
> Hi Anton
>
> It sounds like from your scenario, you are just interested in reporting a specific business event, in which case I believe it is possible to just create your own metric with data points, using the metrics REST API - however I'll let the members of the metrics team comment more on that.
>
> If you are interested in recording more information about your business transaction, then you may want to consider Hawkular BTM. Its currently possible to capture the 'call trace' of a business transaction instance and analyse the information using Kibana - you can also extract relevant properties from the txn (e.g. affiliate) and use that information to focus any queries.
>
> The intention is to integrate at the backend with Hawkular Metrics and Alerts, but this isn't in place at the moment.
>
> Regards
> Gary
>
> ----- Original Message -----
>> Hello
>>
>> I have been watching the developments of Hawkular, and am really impressed!
>>
>> I have a few questions about Hawkular.
>>
>> Hawkular seems to be primarily focused on server metrics and monitoring.
>>
>> I am, however, interested in exploring the possibility of using it for
>> monitoring and alerting of specific business events. For example, lets say I
>> had an online shop and I sold my widgets via affiliates. Would it be
>> possible to capture the sales event, persist and display metrics - so the
>> affiliate partner could login and see their activities? And to send such
>> events to Hawkular, is there a java client?
>>
>> When using the server agent, are captured events sent async?
>>
>> Thanks
>>
>>
>>
>> --
>> Anton Hughes
>>
>>
>> _______________________________________________
>> 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/20151027/d8ccf89a/attachment.html 

From jpkroehling at redhat.com  Tue Oct 27 08:29:14 2015
From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=)
Date: Tue, 27 Oct 2015 13:29:14 +0100
Subject: [Hawkular-dev] Accounts on Cassandra
In-Reply-To: <2132208163.37662735.1445948056110.JavaMail.zimbra@redhat.com>
References: <562F5B30.5030302@redhat.com>
	<2132208163.37662735.1445948056110.JavaMail.zimbra@redhat.com>
Message-ID: <562F6E1A.2060007@redhat.com>

On 10/27/2015 01:14 PM, John Mazzitelli wrote:
> Can you clarify what ID you are talking about? This isn't the resource IDs is it? The IDs that feeds create and send to inventory and metrics? AFAIK, the hawkular design for these IDs was that feeds were free to create their own IDs with their own formats/syntax (so long as they are Strings).

Inventory folks can correct me if I'm wrong, but as far as I understand, 
Inventory uses the path as the ID on their side. That's their "Resource".

When dealing with Accounts, they reuse this ID if the path's length is 
smaller than X. If it's bigger than X, then they resort to UUID when 
talking to accounts.

So, I assume that consumers of Inventory won't be affected by this 
change, as inventory is already translating between path-based IDs and 
UUIDs.

- Juca.

From tsegismo at redhat.com  Wed Oct 28 04:31:12 2015
From: tsegismo at redhat.com (Thomas Segismont)
Date: Wed, 28 Oct 2015 09:31:12 +0100
Subject: [Hawkular-dev] Is this an applicable use-case for Hawkular
In-Reply-To: <562F6E0F.2000908@redhat.com>
References: <CAMOUzMAJG38aDKFgvfuvjhLOeGMzzU98rDugyH7xQfGjdQ6Tvg@mail.gmail.com>
	<536565134.40626954.1445848010233.JavaMail.zimbra@redhat.com>
	<562F6E0F.2000908@redhat.com>
Message-ID: <563087D0.3000201@redhat.com>

It does, two solutions:
[1] use hawkular-charts library (preferred)
[2] use Grafana (Metrics has an API adaptor for InfluxDB v0.8 protocol)

[1] https://github.com/hawkular/hawkular-charts
[2] http://www.hawkular.org/docs/components/metrics/grafana_integration.html

Le 27/10/2015 13:29, Jay Shaughnessy a ?crit :
> I'm not sure if Metrics comes with any visualization outside of Hawkular.


From ah at tradeworks.io  Wed Oct 28 12:49:00 2015
From: ah at tradeworks.io (Anton Hughes)
Date: Wed, 28 Oct 2015 17:49:00 +0100
Subject: [Hawkular-dev] Is this an applicable use-case for Hawkular
In-Reply-To: <562F6E0F.2000908@redhat.com>
References: <CAMOUzMAJG38aDKFgvfuvjhLOeGMzzU98rDugyH7xQfGjdQ6Tvg@mail.gmail.com>
	<536565134.40626954.1445848010233.JavaMail.zimbra@redhat.com>
	<562F6E0F.2000908@redhat.com>
Message-ID: <CAMOUzMBH70ifa4kxTRD-MKXH5V-YTcA+RxX4cWM+EK8yHsrz7g@mail.gmail.com>

On 27 October 2015 at 13:29, Jay Shaughnessy <jshaughn at redhat.com> wrote:

> lso, depending on your needs, you could find that your main needs are
> metrics and alerting, maybe BTM as well, and those components can both be
> used in a "standalone" mode, independent of the Hawkular framework.  REST
> APIs are the typical way to interact with Hawkular.  Hawkular Alerts has no
> built-in UI, I'm not sure if Metrics comes with any visualization outside
> of Hawkular.


Thanks.

I wasnt aware that the hawkular components could be run separately.

The BTM module looks interesting, however I am concerned about maintenance.
For example, in the configuration example on
http://www.hawkular.org/docs/components/btm/index.html, if I were to change
the switchyard service names it would break - and I assume there would be
no compile time errors? Therefore, using a strongly typed hawkular client
to communicate with hawkular would be preferred.

With Metrics, is it possible to add custom data? To illustrate, I have the
following use-case:
*log events of interest - *as a product owner I would like to use all  user
events of interest so that the user and system auditors can see what and
when a user did something. So, we would log "user John, with user id 1234
logged in at wed 25 oct 17:46. So we would be logging a custom event, and
storing custom data.

Thanks





-- 
Anton Hughes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151028/09f674ed/attachment.html 

From gbrown at redhat.com  Wed Oct 28 13:16:43 2015
From: gbrown at redhat.com (Gary Brown)
Date: Wed, 28 Oct 2015 13:16:43 -0400 (EDT)
Subject: [Hawkular-dev] Is this an applicable use-case for Hawkular
In-Reply-To: <CAMOUzMBH70ifa4kxTRD-MKXH5V-YTcA+RxX4cWM+EK8yHsrz7g@mail.gmail.com>
References: <CAMOUzMAJG38aDKFgvfuvjhLOeGMzzU98rDugyH7xQfGjdQ6Tvg@mail.gmail.com>
	<536565134.40626954.1445848010233.JavaMail.zimbra@redhat.com>
	<562F6E0F.2000908@redhat.com>
	<CAMOUzMBH70ifa4kxTRD-MKXH5V-YTcA+RxX4cWM+EK8yHsrz7g@mail.gmail.com>
Message-ID: <882409564.41884267.1446052603120.JavaMail.zimbra@redhat.com>

Hi Anton

> The BTM module looks interesting, however I am concerned about maintenance.
> For example, in the configuration example on
> http://www.hawkular.org/docs/components/btm/index.html , if I were to change
> the switchyard service names it would break - and I assume there would be no
> compile time errors? Therefore, using a strongly typed hawkular client to
> communicate with hawkular would be preferred.

Good point. The reason it is done this way is to give administrators control over what is monitored at any particular time, rather than having something that needs to be defined at development time.

At present, if a business transaction is recognised (i.e. by the URI), then it will be named and processed as defined by its configuration. But as you point out, if something changes in the service (i.e. its URI is changed), then there is potential for the administrators to miss this, and subsequently receive no further information about the business transaction.

At the moment there is a high level property that indicates that any instrumented activity, that is not associated with a named business txn, should be ignored - by default this is not enabled, so the server will receive business txn fragments that may or may not be associated with a business transaction name - this config option enables the unnamed fragments to be filtered out, but this could potentially miss the case where a service has had its URI changed, and so will go from being named, to being ignored.

One alternative would be to use the 'exclusion' filter approach to filter out any fragments that are definitely not of interest, so if a URI change occurred, the fragments would be reported - but just not have a business transaction name. We could use this fact to pick up the fact that unnamed fragments are being reported, which could direct an administrator to fix the problem or add it to the exclusions if no longer of interest.

Although a typed API may still work best in your situation, would the approach outlined above address your concern?

Regards
Gary

From mfoley at redhat.com  Wed Oct 28 16:02:21 2015
From: mfoley at redhat.com (Michael Foley)
Date: Wed, 28 Oct 2015 16:02:21 -0400 (EDT)
Subject: [Hawkular-dev] zaproxy/zaproxy
In-Reply-To: <CAMQ91EeKzwwOkm6o8AKem+S3JqnqugVZmO6CB3byrkZpYuCefA@mail.gmail.com>
References: <CAMQ91EeKzwwOkm6o8AKem+S3JqnqugVZmO6CB3byrkZpYuCefA@mail.gmail.com>
Message-ID: <230943676.85756644.1446062541776.JavaMail.zimbra@redhat.com>

Might be useful to tool to try on Hawkular to identify security vulnerabilities ... 

The OWASP Zed Attack Proxy (ZAP) is an easy to use integrated penetration testing tool for finding vulnerabilities in web applications. 

https://github.com/zaproxy/zaproxy 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151028/127f610a/attachment.html 

From ah at tradeworks.io  Thu Oct 29 08:45:36 2015
From: ah at tradeworks.io (Anton Hughes)
Date: Thu, 29 Oct 2015 13:45:36 +0100
Subject: [Hawkular-dev] Is this an applicable use-case for Hawkular
In-Reply-To: <882409564.41884267.1446052603120.JavaMail.zimbra@redhat.com>
References: <CAMOUzMAJG38aDKFgvfuvjhLOeGMzzU98rDugyH7xQfGjdQ6Tvg@mail.gmail.com>
	<536565134.40626954.1445848010233.JavaMail.zimbra@redhat.com>
	<562F6E0F.2000908@redhat.com>
	<CAMOUzMBH70ifa4kxTRD-MKXH5V-YTcA+RxX4cWM+EK8yHsrz7g@mail.gmail.com>
	<882409564.41884267.1446052603120.JavaMail.zimbra@redhat.com>
Message-ID: <CAMOUzMC4Q+F0mzBRkq=yB7-Zdw-8BST1Cp+YnzGzwczt9p=2cQ@mail.gmail.com>

On 28 October 2015 at 18:16, Gary Brown <gbrown at redhat.com> wrote:

> Good point. The reason it is done this way is to give administrators
> control over what is monitored at any particular time, rather than having
> something that needs to be defined at development time.
>
Yes, I can see that is a good reason. And I think, so long as there is a
traditional in-code way, then you can have options for both parties. I do
see a trend - as part of the devops movement - where developers take on
more operations roles, and ops does more work in code - that the in-code
approach is likely to be favored by many.

>
> Although a typed API may still work best in your situation, would the
> approach outlined above address your concern?
>
We currently use the New Relic agent, and it is my understanding that Jboss
( possibly Wildfly too) can only run one agent at a time? It would be
difficult to convince my team to drop New Relic for Hawkular. And, as
mentioned in the initial thread, our use for Hawkular is more about
monitoring and capturing in code.

I know that, at this stage at least, Hawkular is very focus on server and
system monitoring. Should you wish to explore further the possiblity of
monitoring/capturing and alerting from more user-defined metrics and
events, you may wish to consider using something like the jbpm/drools
modeller. The idea being, a hawkular admin could define the model, then -
again possibly re-use from drools - alert rules could be described using
the user-defined model.




-- 
Anton Hughes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151029/124db92f/attachment-0001.html 

From jshaughn at redhat.com  Thu Oct 29 09:12:02 2015
From: jshaughn at redhat.com (Jay Shaughnessy)
Date: Thu, 29 Oct 2015 09:12:02 -0400
Subject: [Hawkular-dev] Is this an applicable use-case for Hawkular
In-Reply-To: <CAMOUzMBH70ifa4kxTRD-MKXH5V-YTcA+RxX4cWM+EK8yHsrz7g@mail.gmail.com>
References: <CAMOUzMAJG38aDKFgvfuvjhLOeGMzzU98rDugyH7xQfGjdQ6Tvg@mail.gmail.com>
	<536565134.40626954.1445848010233.JavaMail.zimbra@redhat.com>
	<562F6E0F.2000908@redhat.com>
	<CAMOUzMBH70ifa4kxTRD-MKXH5V-YTcA+RxX4cWM+EK8yHsrz7g@mail.gmail.com>
Message-ID: <56321B22.8010509@redhat.com>



On 10/28/2015 12:49 PM, Anton Hughes wrote:
>
> On 27 October 2015 at 13:29, Jay Shaughnessy <jshaughn at redhat.com 
> <mailto:jshaughn at redhat.com>> wrote:
>
>     lso, depending on your needs, you could find that your main needs
>     are metrics and alerting, maybe BTM as well, and those components
>     can both be used in a "standalone" mode, independent of the
>     Hawkular framework.  REST APIs are the typical way to interact
>     with Hawkular.  Hawkular Alerts has no built-in UI, I'm not sure
>     if Metrics comes with any visualization outside of Hawkular.
>
>
> Thanks.
>
> I wasnt aware that the hawkular components could be run separately.
>
> The BTM module looks interesting, however I am concerned about 
> maintenance. For example, in the configuration example on 
> http://www.hawkular.org/docs/components/btm/index.html, if I were to 
> change the switchyard service names it would break - and I assume 
> there would be no compile time errors? Therefore, using a strongly 
> typed hawkular client to communicate with hawkular would be preferred.
>
> With Metrics, is it possible to add custom data? To illustrate, I have 
> the following use-case:
> *log events of interest - *as a product owner I would like to use all 
>  user events of interest so that the user and system auditors can see 
> what and when a user did something. So, we would log "user John, with 
> user id 1234 logged in at wed 25 oct 17:46. So we would be logging a 
> custom event, and storing custom data.

Metrics and Alerts can both be used outside of the Hawkular framework so 
really you can store any metric you like, or alert on basically any data 
you like.  As for Events, the next release of Hawkular Alerts (0.6.0) 
will include a new Events feature that you may find interesting.  
Whereas Alerts are relatively rare, typically involve human interaction, 
and run through a simple life-cycle; Events are likely much more 
numerous, representing any sort of happening that a client wants to 
persist.  The interesting thing about Events in HK-Alerts is that they 
can be inserted directly via API or can be generated via Trigger, like 
an Alert.  And Events can also be used as Trigger conditions, to 
contribute to further Alert or Event generation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151029/94116ca7/attachment.html 

From ah at tradeworks.io  Thu Oct 29 09:16:48 2015
From: ah at tradeworks.io (Anton Hughes)
Date: Thu, 29 Oct 2015 14:16:48 +0100
Subject: [Hawkular-dev] Is this an applicable use-case for Hawkular
In-Reply-To: <56321B22.8010509@redhat.com>
References: <CAMOUzMAJG38aDKFgvfuvjhLOeGMzzU98rDugyH7xQfGjdQ6Tvg@mail.gmail.com>
	<536565134.40626954.1445848010233.JavaMail.zimbra@redhat.com>
	<562F6E0F.2000908@redhat.com>
	<CAMOUzMBH70ifa4kxTRD-MKXH5V-YTcA+RxX4cWM+EK8yHsrz7g@mail.gmail.com>
	<56321B22.8010509@redhat.com>
Message-ID: <CAMOUzMBMsSi7soi3eEG-8FmwnevODJfOBRG0=HdCRwOjg=Mc_g@mail.gmail.com>

On 29 October 2015 at 14:12, Jay Shaughnessy <jshaughn at redhat.com> wrote:

> Metrics and Alerts can both be used outside of the Hawkular framework so
> really you can store any metric you like, or alert on basically any data
> you like.  As for Events, the next release of Hawkular Alerts (0.6.0) will
> include a new Events feature that you may find interesting.  Whereas Alerts
> are relatively rare, typically involve human interaction, and run through a
> simple life-cycle; Events are likely much more numerous, representing any
> sort of happening that a client wants to persist.  The interesting thing
> about Events in HK-Alerts is that they can be inserted directly via API or
> can be generated via Trigger, like an Alert.  And Events can also be used
> as Trigger conditions, to contribute to further Alert or Event generation.


Thanks Jay - this sounds really cool!

I have heard a few times now that hawkular components can be used outside
of the hawkular framework. What exactly is the hawkular framework? As an
outsider I am learning about Hawkular and its features. There is good
documentation on the features, but the underlying framework, not so much.

Also, regarding documentation, I could not find how to store any 'metric'
or data. Specifically, I am looking to store not just a metric but a pojo.




-- 
Anton Hughes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151029/e4ba5c11/attachment.html 

From jshaughn at redhat.com  Thu Oct 29 09:34:02 2015
From: jshaughn at redhat.com (Jay Shaughnessy)
Date: Thu, 29 Oct 2015 09:34:02 -0400
Subject: [Hawkular-dev] Is this an applicable use-case for Hawkular
In-Reply-To: <CAMOUzMBMsSi7soi3eEG-8FmwnevODJfOBRG0=HdCRwOjg=Mc_g@mail.gmail.com>
References: <CAMOUzMAJG38aDKFgvfuvjhLOeGMzzU98rDugyH7xQfGjdQ6Tvg@mail.gmail.com>
	<536565134.40626954.1445848010233.JavaMail.zimbra@redhat.com>
	<562F6E0F.2000908@redhat.com>
	<CAMOUzMBH70ifa4kxTRD-MKXH5V-YTcA+RxX4cWM+EK8yHsrz7g@mail.gmail.com>
	<56321B22.8010509@redhat.com>
	<CAMOUzMBMsSi7soi3eEG-8FmwnevODJfOBRG0=HdCRwOjg=Mc_g@mail.gmail.com>
Message-ID: <5632204A.8050305@redhat.com>


Anton, yes, it can be a little confusing.  The Hawkular project is an 
end-to-end monitoring and management tool focused on Red Hat software.  
Today it basically offers a Wildfly agent for discovering and managing 
app servers, their hosted apps, and all of the things that make up those 
apps.  What is can handle grows with every release.  Hawkular leverages 
a bunch of components to perform that job.  There is HK-Inventory to 
represent a network of inventories resources (like an app server, a 
datasource, a jvm, etc), HK-Metrics as a Cassandra-backed time-series 
store, HK-Alerts as a Drools-backed alerting tool, HK-Accounts as a 
KeyCloak backed multi-tenant/auth/authz tool, HK-Console for UI, HK-Bus 
for a comm backbone, etc..

Some of the HK components, namely HK-Metrics and HK-Alerts support 
standalone deployment outside of Hawkular.  They are named 
Hawkular-Metrics and Hawkular-Alerts because they have been developed as 
part of the Hawkular project, but they can be used independently.  Hope 
that helps...


On 10/29/2015 9:16 AM, Anton Hughes wrote:
>
> On 29 October 2015 at 14:12, Jay Shaughnessy <jshaughn at redhat.com 
> <mailto:jshaughn at redhat.com>> wrote:
>
>     Metrics and Alerts can both be used outside of the Hawkular
>     framework so really you can store any metric you like, or alert on
>     basically any data you like.  As for Events, the next release of
>     Hawkular Alerts (0.6.0) will include a new Events feature that you
>     may find interesting.  Whereas Alerts are relatively rare,
>     typically involve human interaction, and run through a simple
>     life-cycle; Events are likely much more numerous, representing any
>     sort of happening that a client wants to persist.  The interesting
>     thing about Events in HK-Alerts is that they can be inserted
>     directly via API or can be generated via Trigger, like an Alert. 
>     And Events can also be used as Trigger conditions, to contribute
>     to further Alert or Event generation.
>
>
> Thanks Jay - this sounds really cool!
>
> I have heard a few times now that hawkular components can be used 
> outside of the hawkular framework. What exactly is the hawkular 
> framework? As an outsider I am learning about Hawkular and its 
> features. There is good documentation on the features, but the 
> underlying framework, not so much.
>
> Also, regarding documentation, I could not find how to store any 
> 'metric' or data. Specifically, I am looking to store not just a 
> metric but a pojo.
>
>
>
>
> -- 
> Anton Hughes
>
>
>
> _______________________________________________
> 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/20151029/6ad23e86/attachment.html 

From mazz at redhat.com  Thu Oct 29 11:16:09 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Thu, 29 Oct 2015 11:16:09 -0400 (EDT)
Subject: [Hawkular-dev] agent distro changed
In-Reply-To: <55645727.38699985.1446131714826.JavaMail.zimbra@redhat.com>
Message-ID: <162845029.38700303.1446131769164.JavaMail.zimbra@redhat.com>

Just wanted to give a heads up on a change that went into Hawkular Agent repo.

The agent distribution is no longer built in the hawkular-wildfly-monitor module (that used to build the jar and then a distro "module.zip" file).

Instead, there is a new hawkular-wildfly-monitor-module-dist that produces a .zip and a tar.gz for the module distribution. This is build from our feature pack using the new feature provided by the wildfly built tool maven provisioning plugin. This means we no longer have to maintain two separate and independent copies of module.xml and we can build the .zip directly from a feature pack which is nice.

This means kettle needs to change its dist/pom.xml so it pulls in the new dist zip and not the only one (which no longer exists). I will submit a PR for this shortly.

From mazz at redhat.com  Thu Oct 29 19:12:27 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Thu, 29 Oct 2015 19:12:27 -0400 (EDT)
Subject: [Hawkular-dev] agent installer used in kettle
In-Reply-To: <1143268914.38843285.1446153605194.JavaMail.zimbra@redhat.com>
Message-ID: <1132299922.38872559.1446160347063.JavaMail.zimbra@redhat.com>

The hawkular kettle build is now ready to use the agent installer when putting the agent into the server.

I need someone can look at this PR to peer review:

https://github.com/hawkular/hawkular/pull/620

Notice that this bumps up kettle to inventory 0.8.0 - i have not seen any problems with doing this in my latest testing, so hopefully that is OK. I just bumped to the latest srcdep git hash and even the end-to-end tests are now passing on my box (who knows if it will pass on travis... still waiting)

I added a little extra to the agent installer docs here: https://github.com/hawkular/hawkular-agent/blob/master/hawkular-wildfly-monitor-installer/README.adoc


From ah at tradeworks.io  Fri Oct 30 09:16:29 2015
From: ah at tradeworks.io (Anton Hughes)
Date: Fri, 30 Oct 2015 14:16:29 +0100
Subject: [Hawkular-dev] Is this an applicable use-case for Hawkular
In-Reply-To: <5632204A.8050305@redhat.com>
References: <CAMOUzMAJG38aDKFgvfuvjhLOeGMzzU98rDugyH7xQfGjdQ6Tvg@mail.gmail.com>
	<536565134.40626954.1445848010233.JavaMail.zimbra@redhat.com>
	<562F6E0F.2000908@redhat.com>
	<CAMOUzMBH70ifa4kxTRD-MKXH5V-YTcA+RxX4cWM+EK8yHsrz7g@mail.gmail.com>
	<56321B22.8010509@redhat.com>
	<CAMOUzMBMsSi7soi3eEG-8FmwnevODJfOBRG0=HdCRwOjg=Mc_g@mail.gmail.com>
	<5632204A.8050305@redhat.com>
Message-ID: <CAMOUzMAVmzfK0wJ6U2HUBPYH1JDqRft1DBXChQzoDLLTPxZqPQ@mail.gmail.com>

Coming back to my original question - and based on some further thinking
and reading of the Hawkular website, I have the following thoughts.

On the Hawkular website, it is written:

For who ?
> There are primarly (BTW - this is spelled incorrect) two types of users.
> Users who wants a toolkit to do server/*system monitoring in general, for
> them we provide a rich REST API to store metrics, trigger alerts* and
> manage an inventory of resources
> Users who want a full-fledge admin console to monitor and manage
> middleware servers (Currently, only WildFly <http://www.wildfly.org/> is
> supported)

I've highlighted the general area that I am most interested - and I think
many others would be too.
Please take a quick look at
http://martinfowler.com/eaaDev/EventSourcing.html. Event Sourcing places
emphasis on events of interest - in the Shipping example in this link the
interesting events are:

   - Ship Arrives
   - Ship Departs

To be able store (store metrics?) and react (trigger alert) in this example
would be very beneficial in many situations.

I hope this helps to illustrates my use-case.

On 29 October 2015 at 14:34, Jay Shaughnessy <jshaughn at redhat.com> wrote:

>
> Anton, yes, it can be a little confusing.  The Hawkular project is an
> end-to-end monitoring and management tool focused on Red Hat software.
> Today it basically offers a Wildfly agent for discovering and managing app
> servers, their hosted apps, and all of the things that make up those apps.
> What is can handle grows with every release.  Hawkular leverages a bunch of
> components to perform that job.  There is HK-Inventory to represent a
> network of inventories resources (like an app server, a datasource, a jvm,
> etc), HK-Metrics as a Cassandra-backed time-series store, HK-Alerts as a
> Drools-backed alerting tool, HK-Accounts as a KeyCloak backed
> multi-tenant/auth/authz tool, HK-Console for UI, HK-Bus for a comm
> backbone, etc..
>
> Some of the HK components, namely HK-Metrics and HK-Alerts support
> standalone deployment outside of Hawkular.  They are named Hawkular-Metrics
> and Hawkular-Alerts because they have been developed as part of the
> Hawkular project, but they can be used independently.  Hope that helps...
>
>
> On 10/29/2015 9:16 AM, Anton Hughes wrote:
>
>
> On 29 October 2015 at 14:12, Jay Shaughnessy <jshaughn at redhat.com> wrote:
>
>> Metrics and Alerts can both be used outside of the Hawkular framework so
>> really you can store any metric you like, or alert on basically any data
>> you like.  As for Events, the next release of Hawkular Alerts (0.6.0) will
>> include a new Events feature that you may find interesting.  Whereas Alerts
>> are relatively rare, typically involve human interaction, and run through a
>> simple life-cycle; Events are likely much more numerous, representing any
>> sort of happening that a client wants to persist.  The interesting thing
>> about Events in HK-Alerts is that they can be inserted directly via API or
>> can be generated via Trigger, like an Alert.  And Events can also be used
>> as Trigger conditions, to contribute to further Alert or Event generation.
>
>
> Thanks Jay - this sounds really cool!
>
> I have heard a few times now that hawkular components can be used outside
> of the hawkular framework. What exactly is the hawkular framework? As an
> outsider I am learning about Hawkular and its features. There is good
> documentation on the features, but the underlying framework, not so much.
>
> Also, regarding documentation, I could not find how to store any 'metric'
> or data. Specifically, I am looking to store not just a metric but a pojo.
>
>
>
>
> --
> Anton Hughes
>
>
>
> _______________________________________________
> hawkular-dev mailing listhawkular-dev at lists.jboss.orghttps://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
>
>


-- 
Anton Hughes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151030/eccef628/attachment-0001.html 

From mfoley at redhat.com  Fri Oct 30 12:19:32 2015
From: mfoley at redhat.com (Michael Foley)
Date: Fri, 30 Oct 2015 12:19:32 -0400 (EDT)
Subject: [Hawkular-dev] Openshift Origin release candidate 1 is now
	available ....
In-Reply-To: <1068488704.31642424.1446220647971.JavaMail.zimbra@redhat.com>
References: <CAH16ShLJskRSCW1jdqS92rVotC5dy729omy5psqQi_bgzJVB4w@mail.gmail.com>
	<CAH16ShJdxGX=jap0n7uP_A-DbnkTDgJ_OZwmGkSEF-t_d_9kdA@mail.gmail.com>
	<1068488704.31642424.1446220647971.JavaMail.zimbra@redhat.com>
Message-ID: <1980897020.87133257.1446221972775.JavaMail.zimbra@redhat.com>

Hi, 

Openshift Origin Release Candidate 1 is now available. 

Unfortunately, Metrics is not in this release candidate ...and will be in the next version 1.0.8, which I presume will be Release Candidate 2. 

So ...when Release Candidate 2 becomes available ... we will have to test extremely quickly ..as GA is scheduled for November 19th. 

Here's a strawman of the QE Plan: 



    * When Openshift 3.1 Release Candidate 2 is available (I think it is November 9th ...from looking at the document from the OSE PM call) ...we need to jump right on this. 
    * We have a 5-point QE Plan ... but with just 10 days to test ...I don't think we will make enough progress with automation in that limited amount of time. 
    * Let's focus on a manual qualification ... 


        * a visual inspection of the Openshift Admin Console to see if metrics from Hawk-metrics are appearing 
        * re-execute the few testcases we have (ie, the curl command ... and visually inspect the data) 
    * 
If there is an issue detected, we will need fast turnaround time from Hawk-Metrics developers. Please.     * QE Deliverable is a documented testcase execution run in Polarion, and a QE Sign-off document ...so I can communicate what was done and the test results. 


Regards, 

Michael Foley 
QE Supervisor, Middleware QE 

----- Forwarded Message ----- 
From: "Clayton Coleman" <ccoleman at redhat.com> 
To: "aos-devel" <aos-devel at redhat.com> 
Sent: Thursday, October 29, 2015 12:27:14 PM 
Subject: Re: [aos-devel] v1.0.7 is out for download (release candidate 1 for Origin 1.1) 

FYI 

On Thu, Oct 29, 2015 at 2:26 PM, Clayton Coleman <ccoleman at redhat.com> wrote: 
> v1.0.7 has been tagged, pushed to the Docker Hub, and uploaded to 
> GitHub. The release notes are here 
> https://github.com/openshift/origin/releases/tag/v1.0.7 
> 
> This is the first release candidate for Origin 1.1. There are a ton 
> of new features, a massive amount of new UI, and lots of exciting new 
> features. 
> 
> Some features are still in the process of being merged (Jobs, 
> Horizontal Pod Autoscaler, Metrics, Logging) - expect to see them in 
> v1.0.8 
> 
> Please note that v1beta3 is now no longer supported in the UI, and you 
> will need to change your master config to use a different storage 
> version if you are still using v1beta3 (old data will continue to 
> work). If you hit any issues upgrading your clusters, please let us 
> know! 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20151030/92df2459/attachment.html 

From mazz at redhat.com  Fri Oct 30 19:02:16 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Fri, 30 Oct 2015 19:02:16 -0400 (EDT)
Subject: [Hawkular-dev] the name of our hawkular agent/wildfly monitor/feed
 is confusing - I'm fixing it
In-Reply-To: <280652770.39402500.1446245912220.JavaMail.zimbra@redhat.com>
Message-ID: <1298262702.39404099.1446246136758.JavaMail.zimbra@redhat.com>

As I'm writing code and docs and javadocs all around, I realize that the name of our "agent" is utterly confused. We need to fix this or we will eventually confuse users/customers.

Right now in code, or comments, or docs, or just in talking, the names of the "agent" have been at one time or another:

agent
wildfly monitor
wildfly hawkular feed
wildfly monitor agent
wildfly extension
wildfly agent module
wildfly agent
etc. etc. etc.

Over the weekend, I'm going to start renaming this so it is consistent across the board.

It will be called "Hawkular WildFly Agent"

This will affect maven artifact names moving forward. But we need to fix this now, because its confusing ME. I can only imagine the confusion when people start to ask "what do you call the hawkular thing that monitors Wildfly?"

From mazz at redhat.com  Sat Oct 31 13:22:01 2015
From: mazz at redhat.com (John Mazzitelli)
Date: Sat, 31 Oct 2015 13:22:01 -0400 (EDT)
Subject: [Hawkular-dev] giving up on travis
In-Reply-To: <949959796.73601.1446311770225.JavaMail.zimbra@redhat.com>
Message-ID: <1328663941.74047.1446312121930.JavaMail.zimbra@redhat.com>

I've wasted an enormous amount of time waiting for Travis to go green, only to go red, and then trying to figure out why.

We need to fix the CI environment we are using - or someone needs to tell me what I'm doing wrong (it is NOT the cache problem this time). I'm about ready to just ignore Travis.

I just ran "mvn clean install -Pitest" on the hawkular/hawkular repo; everything passed - twice. I try travis, and it fails - twice.

My box:

[INFO] Hawkular: End-To-End integration tests ............. SUCCESS [02:51 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:22 min
[INFO] Finished at: 2015-10-31T12:46:12-04:00

Travis - https://travis-ci.org/hawkular/hawkular/builds/88478339

[INFO] Hawkular: End-To-End integration tests ............. FAILURE [03:33 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 16:21 min
[INFO] Finished at: 2015-10-31T04:08:16+00:00

I have three words... "What the H-E-double-hockey-sticks" ?!?!?!