November 2015 - hawkular-dev - Jboss List Archives

by Juraci Paixão Kröhling

If you use "@Inject Persona" or "@Inject @CurrentUser HawkularUser", keep reading. If all you consume from Accounts are the Services ("@Inject PermissionChecker" or "@Inject BlaService"), you are not affected. Still, you should update to Accounts 2.0.2.Final. On Accounts code, I was mis-using a behavior of WF8/WF9, where it was possible to inject request-related beans into stateless beans. More concretely, I was able to inject the persona for the current request into a SLSB. With WF10, the bean pooling is now enabled by default, meaning that beans created for a persona are pooled and re-used on future requests. In this case, user "X" would make a request and the bean would see it as being from user "Y". This is being fixed in Accounts 2.0.2.Final, which also comes with the update to WF 10. Unfortunately, I could not find a reasonable workaround for current consumers of Accounts that are using direct injection, so, you'll need to change your code. From: @Inject Persona persona; @Inject @CurrentUser HawkularUser user; To: @Inject Instance<Persona> personaInstance; @Inject @CurrentUser Instance<HawkularUser> userInstance; If your component has no changes required to work on WF 10, let me know and I'll send a PR for this change. Otherwise, please incorporate such change when changing your code to work on WF 10. Code changes are required *only* is you use direct injection. If you get the current persona via PersonaService#getCurrent, you should just update to Accounts 2.0.2.Final. - Juca.

8 years, 4 months

2
1
0 / 0

Cancelled: Discussion, Planning, and status on Testing Openshift & Hawk-Metrics Integration for Openshift 3.1

by Michael Foley

A single instance of the following meeting has been cancelled: Subject: Discussion, Planning, and status on Testing Openshift & Hawk-Metrics Integration for Openshift 3.1 Organizer: "Michael Foley" <mfoley(a)redhat.com> Location: Bluejeans http://www.bluejeans.com/mfoley51 Time: Wednesday, November 25, 2015, 3:00:00 PM - 3:30:00 PM GMT -05:00 US/Canada Eastern Required: pruan(a)redhat.com; mmahoney(a)redhat.com; vnguyen(a)redhat.com; snegrea(a)redhat.com; jsanda(a)redhat.com; mwringe(a)redhat.com Optional: jon-qa-list(a)redhat.com; jboss-on-team(a)redhat.com; hawkular-dev(a)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

8 years, 4 months

1
0
0 / 0

Termin gestrichen: Hawkular-Team Update - Di 24. Nov. 2015 3:30PM - 4PM (hrupp@redhat.com)

by hrupp＠redhat.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 24. Nov. 2015 3:30PM - 4PM Berlin Wo: pc 204 2160 481 Kalender: hrupp(a)redhat.com Wer * Heiko Rupp - Organisator * Viliam Rockai * gbrown(a)redhat.com * Thomas Segismont * amendonc(a)redhat.com * Gabriel Cardoso * John Mazzitelli * snegrea(a)redhat.com * Jiri Kremser * Simeon Pinder * hawkular-dev(a)lists.jboss.org * miburman(a)redhat.com * mwringe(a)redhat.com * John Sanda * Lucas Ponce * theute(a)redhat.com * lkrejci(a)redhat.com * jcosta(a)redhat.com * Peter Palaga * Jay Shaughnessy * Mike Thompson Einladung von Google Kalender: https://www.google.com/calendar/ Sie erhalten diese E-Mail unter hawkular-dev(a)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

8 years, 4 months

1
0
0 / 0

Feature packs - a new way of packaging for WildFly

by Peter Palaga

Hi *, Some of you might have heart of the $subj already. For others: wf feature packs are lightweight recipes for building fat WF distros. wildfly-feature-pack-build-maven-plugin typically produces a zip containing some xml config but no jars/wars/ears. wildfly-server-provisioning-maven-plugin is there to take the recipes and make fat distros out of them. Why I am bringing this topic: It seems that feature packs could help us to consolidate all our modules, itest distros and final distros in such a way that configuration will not be duplicated anymore. I hope to be able to do this together with the upgrade to WF10. There is not much docs about the two plugins except for this terse wiki page: https://developer.jboss.org/wiki/WildflyBuildProcess Nevertheless, examples can be found in wildfly and wildfly-core source trees. We started producing a feature pack in Agent recently: https://github.com/hawkular/hawkular-agent/tree/master/hawkular-wildfly-a... Thanks, Peter

8 years, 4 months

2
4
0 / 0

Alpha7 startup problem

by Van Dillon

Hi, I'm running into a problem trying to start Alpha7 AIO on both Windows 7 and Docker. In Windows I set 'org.hawkular.data.dir' before trying to run. This worked well in Alpha6. When I run I get a lot of WARN entries: 2015-11-19 17:01:16,780 WARN [com.datastax.driver.core.Connection] (cluster4-nio-worker-0) Error closing channel: io.netty.channel.ChannelException: java.net.SocketException: Socket is closed Then I get one or more of these FATAL entries: 2015-11-19 17:01:32,351 FATAL [org.hawkular.accounts.common.internal] (EE-ManagedExecutorService-default-Thread-2) HAWKACC150005: Could not connect to Cassandra after enough attempts. Giving up. Reason: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: /127.0.0.1:9042 (com.datastax.driver.core.TransportException: [/127.0.0.1:9042] Cannot connect)) Finally the server shuts down with: 2015-11-19 17:02:07,987 WARN [org.keycloak.events] (default task-3) type=LOGIN_ERROR, realmId=hawkular-realm, clientId=hawkular-accounts-backend, userId=null, ipAddress=127.0.0.1, error=invalid_user_credentials, auth_method=openid-connect, response_type=token, client_auth_method=client-secret, username=jdoe 2015-11-19 17:02:08,038 WARN [org.keycloak.events] (default task-6) type=LOGIN_ERROR, realmId=hawkular-realm, clientId=hawkular-accounts-backend, userId=null, ipAddress=127.0.0.1, error=invalid_user_credentials, auth_method=openid-connect, response_type=token, client_auth_method=client-secret, username=jdoe 2015-11-19 17:02:08,086 INFO [org.hawkular.nest.extension.log] (MSC service thread 1-6) HAWKBUS130002: Nest service stopping 2015-11-19 17:02:08,100 INFO [org.hawkular.nest.extension.log] (MSC service thread 1-6) HAWKBUS130003: Nest service stopped 2015-11-19 17:02:08,116 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0011: Unbound JCA AdminObject [java:/topic/HawkularAccountsEvents] 2015-11-19 17:02:08,125 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0002: Error booting the container: java.lang.RuntimeException: Cannot get tenant ID at org.hawkular.agent.monitor.service.MonitorService.buildRuntimeConfiguration(MonitorService.java:205) at org.hawkular.agent.monitor.service.MonitorService.startMonitorService(MonitorService.java:413) at org.hawkular.agent.monitor.service.MonitorService$1.propertyChange(MonitorService.java:391) at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:335) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:327) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:263) at org.jboss.as.controller.ControlledProcessStateService.stateChanged(ControlledProcessStateService.java:114) at org.jboss.as.controller.ControlledProcessState.setRunning(ControlledProcessState.java:115) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:277) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.Exception: status-code=[401], reason=[Unauthorized], url=[http://127.0.0.1:8080/hawkular/accounts/personas/current] at org.hawkular.agent.monitor.service.MonitorService.buildRuntimeConfiguration(MonitorService.java:189) ... 9 more In Docker the log has the same FATAL and ERROR entries but does not have the WARN entries. Any help would be much appreciated. Thanks, Van

8 years, 5 months

3
4
0 / 0

securing download WAR

by John Mazzitelli

Today we have a simple WAR [1] that lets you download the agent .zip and the agent installer: 1. Download the agent distro: http://localhost:8080/hawkular/wildfly-agent/download 2. Download the installer: http://localhost:8080/hawkular/wildfly-agent/download?installer=true That second one you can submit a FORM POST with some additional installer config settings. In fact, that /download URL points to a single servlet - its just if you POST with "installer=true" (or pass it in as a GET query string) you'll get the installer instead. We could change this if need by (say "/download" for the agent distro, and "/installer" for the installer). The question I have is - what do I need to do to get that second one "secured" with an Accounts login? We want to keep the "/download" URL such that it doesn't require a user/pass just to serve the agent distro zip (that is just the same one you build via mvn - there is nothing that needs to be secured here - plus, the installer needs to download it later and we don't want to have the installer log in just to download the zip). But that second one, we are going to need the Accounts credentials because the installer will need to do things like create an offline token for the user so it can be put in the installer config - or be able to ask Accounts for the offline token for that user. Before anything like that can be done, I think we need to put accounts in front of that WAR [1] . What needs to be done here for that? [1] https://github.com/hawkular/hawkular/tree/master/modules/hawkular-wildfly...

8 years, 5 months

2
8
0 / 0

Nice article: Drools + Rx

by Thomas Segismont

http://www.javacodegeeks.com/2015/11/using-a-rective-stream-as-a-data-sou...

8 years, 5 months

2
1
0 / 0

Cassandra and DataStax driver versions

by John Sanda

There is a PR[1] open for hawkular-parent that upgrades Cassandra from 2.2.0 to 2.2.2 and the driver from 2.2.0-rc2 to 2.2.0-rc3, so now is a good time to discuss this. Earlier this week, Cassandra 3.0 was released[2]. There are some substantial changes including a rewrite of the storage engine to be better optimized for CQL, materialized views, and range deletes to name a few. The driver repo has been maintaining separate branches for each Cassandra branch which has been causing a lot of maintenance overhead. It was announced earlier today on the driver mailing list that the 2.2 branch, which we are currently using, has been merged into the 3.0 branch[3]. There will be no further development on the 2.2 branch. The driver is designed to be backwards compatible such that newer versions of the driver can be used with older versions of Cassandra. This means we could upgrade the driver without upgrading Cassandra; however, I think it makes sense to upgrade Cassandra as well. Are there any questions, comments, concerns, objections, etc.? [1] https://github.com/hawkular/hawkular-parent-pom/pull/55 <https://github.com/hawkular/hawkular-parent-pom/pull/55> [2] http://www.mail-archive.com/user@cassandra.apache.org/msg44740.html <http://www.mail-archive.com/user@cassandra.apache.org/msg44740.html> [3] https://groups.google.com/a/lists.datastax.com/forum/#!topic/java-driver-... <https://groups.google.com/a/lists.datastax.com/forum/#!topic/java-driver-...>

8 years, 5 months

5
11
0 / 0

Towards WildFly 10: hawkular-parent 26 released

by Peter Palaga

Hi *, Important: hawkular-parent 26 should not be consumed by component versions that go to tomorrow's Hawkular M7 When should HK components start using hawkular-parent 26? - The upgrading should go bottom-up through the dependency tree [4]. I'll try to coordinate the process. ATM, we have working builds in commons and accounts. jsanda is working on bus and I am working in the new nest repo. hawkular-parent 26 brings the upgrade to WildFly 10 CR4. Related dependencies (wf-core, dmr, ...) were upgraded too. * srcdeps-maven-plugin related changes: * srcdeps-maven-plugin upgraded to version 0.0.9 * srcdeps-maven-plugin now allows for per srcdep git repository build profiles and properties - e.g. keycloak is built with distribution profile [1] * keycloak srcdep config was added just in case we should need it in course of upgrading to WildFly 10 * wildfly-server-provisioning-maven-plugin and wildfly-feature-pack-build-maven-plugin were added - see [2] * org.jboss.common:jboss-common-beans was added to bring a replacement for StringPropertyReplacer that is not available in WF10. See e.g. [3] [1] https://github.com/hawkular/hawkular-parent-pom/blob/f5504901de7ae52cdd7e... [2] https://developer.jboss.org/wiki/WildflyBuildProcess [3] https://github.com/ppalaga/hawkular-nest/commit/28095626292a0a978dcdf0140... [4] http://www.hawkular.org/docs/dev/development.html#component-dependencies Thanks, Peter

8 years, 5 months

2
2
0 / 0

Standalone Metrics+Alerts

by John Sanda

Over the past couple weeks I have been working on a standalone deployment of Metrics and Alerts. The work is being tracked under HWKMETRICS-311. One of the changes I made was to introduce a new maven module in the hawkular-metrics project that builds and assembles a WildFly 10 distro which includes Metrics and Alerts. Should this new module and other integration modules live in the main hawkular repo instead of the component repo? - John

8 years, 5 months

4
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

hawkular-dev November 2015