9:57 a.m.
Team,
Based on the discussed that followed the last release, here's the
adjusted scheduled based on the next release. Although those are only
*suggestions*, I'll be following that for Accounts.
- Thursday before the release: Parent, Commons and Accounts
- Friday before the release: Inventory, Metrics, BTM
- Monday before the release: Command Gateway, Agent, Alerts
- Tuesday (release day): Hawkular
Once Accounts is released, I'll be submitting a PR for the downstream
components.
- Juca.
4:15 a.m.
On 13.01.2016 16:57, Juraci Paixão Kröhling wrote:
Those three components were released yesterday.
Parent, version 32
Commons, version 0.3.4.Final
Accounts, version 2.0.11.Final
- Friday before the release: Inventory, Metrics, BTM
- Monday before the release: Command Gateway, Agent, Alerts
- Tuesday (release day): Hawkular
- Juca.
4:25 a.m.
On 2016-01-15 11:15, Juraci Paixão Kröhling wrote:
There is a little bit more that perhaps was not announced properly. So
yesterday 2016-01-14 CET, also these ones were released:
Inventory 0.12.1.Final
Command Gateway 0.10.9.Final
There is good hope that Alerts and Agent could follow today 2016-01-15
I am not sure I have enough passion to ask for a release of Metrics.
-- P
3:58 p.m.
Inline...
On 2016-01-15 11:39, Peter Palaga wrote:
Today 2016-01-15 the following components were released:
Alerts 0.8.2.Final
Agent 0.15.4.Final
All versions listed here are now in Hawkular after
https://github.com/hawkular/hawkular/pull/781 was merged.
Metrics is still on 0.10.0.Final in HK main. My attempt to upgrade is
failing on /hawkular/metrics/status returning Not Found. See
https://github.com/hawkular/hawkular/pull/782
Have a nice weekend!
-- P
6:47 p.m.
Today 2016-01-15 the following components were released:
Alerts 0.8.2.Final
Agent 0.15.4.Final
And I just released another agent - 0.15.5.Final - hawkular master now uses that build.
The purpose for this is to ensure the agent can work properly if a user started kettle
with a non-localhost address via -b.
I suggest people periodically run the hawkular server with a non-localhost IP via -b /
-Dkeycloak.server.url to see how the components behave. I still see a stack trace when I
do this - something about alerts timing out:
19:04:04,063 ERROR [org.jboss.as.ejb3.invocation] (ServerService Thread Pool -- 86)
WFLYEJB0034: EJB Invocation failed on component CassDefinitionsServiceImpl for method
public abstract java.util.Collection
org.hawkular.alerts.api.services.DefinitionsService.getAllTriggers() throws
java.lang.Exception: javax.ejb.ConcurrentAccessTimeoutException: WFLYEJB0241: EJB 3.1 PFD2
4.8.5.5.1 concurrent access timeout on CassDefinitionsServiceImpl - could not obtain lock
within 60SECONDS
But the good news is the agent now works.
To run hawkular bound to another IP (e.g. 1.2.3.4):
standalone.sh -b 1.2.3.4 -Dkeycloak.server.url=http://1.2.3.4:8080/auth
3:21 a.m.
Mazz,
I can't reproduce it on master.
Running a
bin/standalone.sh -b 192.168.1.234 -Dkeycloack.server.url=http://192.168.1.234:8080/auth
on my machine
I have this one
2016-01-18 10:16:44,399 ERROR [io.undertow.request] (default task-1) UT005023: Exception
handling request to /hawkular/inventory/tenant: java.lang.RuntimeException: Unable to
resolve realm public key remotely
at
org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:136)
at
org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:85)
at
org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:74)
at
org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:50)
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:284)
at
io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263)
at
io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
at
io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174)
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202)
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793)
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.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at
org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:117)
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:882)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
at
org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:107)
... 16 more
Did I miss some configuration step ?
By the way, can you open a JIRA with details of your error, context and environment ? We
can trace it there.
Lucas
3:24 a.m.
Is it possible that the KC server hasn't finished deploying when this
first request was fired? Could you post the complete boot log somewhere?
- Juca.
On 18.01.2016 10:21, Lucas Ponce wrote:
2016-01-18 10:16:44,399 ERROR [io.undertow.request] (default task-1)
UT005023: Exception handling request to /hawkular/inventory/tenant:
java.lang.RuntimeException: Unable to resolve realm public key remotely
3:40 a.m.
JIRA to track this issue:
https://issues.jboss.org/browse/HAWKULAR-941
----- Original Message -----
3351
days inactive
3356
days old
10 comments
5 participants
participants (5)
-
Jay Shaughnessy -
John Mazzitelli -
Juraci Paixão Kröhling -
Lucas Ponce -
Peter Palaga