[Hawkular-dev] Release schedule

[Lucas Ponce]

> 
> > 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
> 


This is something it happens in master ? and you can reproduce it always or it is a random behaviour ?

I'm looking into it.



> 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
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>