11:57 a.m.
1. Git clone the hawkular-services master branch
2. From the top directory under hawkular-services, run "mvn clean install -Pdev
-Pembeddedec -Pdozip"
(note: -Pdozip is only needed once - looks like the itests need the zip to build or
something because i got a build error if I didn't build the zip at least once - I
should probably write a JIRA on the new -Pdozip profile - that was added recently).
3. Run "dist/target/hawkular-services-dist-*/bin/standalone.sh"
That's how I see it. I see it pretty regularly. Note, I am NOT running on a machine
with a SSD hard drive :)
----- Original Message -----
I didn't see that error on my tests.
I will take a look.
Are you using the new C* embedded in hawkular-services, right ?
Can you post me the commands/steps to reproduce it ?
Thanks.
----- Mensaje original -----
> De: "John Mazzitelli" <mazz(a)redhat.com>
> Para: "Discussions around Hawkular development"
> <hawkular-dev(a)lists.jboss.org>
> Enviados: Martes, 5 de Julio 2016 18:33:19
> Asunto: [Hawkular-dev] errors when embedding c*
>
> > We have embedded C* today using the maven 'embeddedc' profile.
> > HOWEVER, I can tell you that that still doesn't work quite right
> > ...
> > some components throw errors at startup and you usually have to
> > shutdown the h-server, restart it, and usually (not always) things
> > start working again.
>
> Whether we embed C* in -services or in another distro, either way, we have
> a
> problem.
>
> I'm sure all of us have seen this at one time or another :)
>
> It seems if I restart the server, most times (not all) I no longer see
> these
> errors. I have no idea if this is just going to cause problems in alerts,
> or
> if there are other problems we'll see. But I see lots of these kinds of
> errors:
>
> ===========
>
> 2016-07-05 11:06:21,747 ERROR [org.jboss.as.ejb3.invocation] (Thread-127
> (ActiveMQ-client-global-threads-913106351)) WFLYEJB0034: EJB Invocation
> failed on component CacheManager for method public java.util.Set
> org.hawkular.alerts.bus.init.CacheManager.getActiveDataIds():
> javax.ejb.ConcurrentAccessTimeoutException: WFLYEJB0241: EJB 3.1 PFD2
> 4.8.5.5.1 concurrent access timeout on CacheManager - could not obtain lock
> within 5000MILLISECONDS
> ...
> at
> org.hawkular.alerts.bus.init.CacheManager$$$view16.getActiveDataIds(Unknown
> Source)
> at
>
org.hawkular.alerts.bus.listener.MetricDataListener.onBasicMessage(MetricDataListener.java:82)
> at
>
org.hawkular.alerts.bus.listener.MetricDataListener.onBasicMessage(MetricDataListener.java:50)
> at
>
org.hawkular.bus.common.consumer.BasicMessageListener.onBasicMessage(BasicMessageListener.java:77)
> at
>
org.hawkular.bus.common.consumer.BasicMessageListener.onMessage(BasicMessageListener.java:63)
> ...
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>