Ludo,
I have the same problem n Tomee 7.1
In my case the EAR contains persistence.xml in EAR/META-INF
http://java.sun.com/xml/ns/persistence;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
Thanks Jonathan, brilliant!
We are doing kind of the same using jolokia --> telegraf --> influxdb -->
grafana.
Jonathan: in your opinion what would be the advantages of chronograf over
grafana? Looking forward for your blog post! :)
Thanks,
Luis
[1] https://jolokia.org/
El mar., 9 oct. 2018
Great answer. Wondering if we could create some kind of a page on our
website with this kind of value?
What do you think?
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Tue, Oct 9, 2018 at 5:33 PM exabrial12 wrote:
> To echo Romain's point and add some
I'm using TomEE 7.0.4, EJB version 3.1
I often see this when making a high volume of calls to methods in
@Stateless classes:
javax.ejb.ConcurrentAccessTimeoutException: No instances available in
Stateless Session Bean pool. Waited 30 SECONDS
I've set maxSize to 1000 in my tomee.xml and I still
Grafana is great. I've used it in the past and liked it. If you have multiple
timeseries databases, it's ability to combine them is very handy.
Chronograf offers a similar feature set, but adds a some pre-built
dashboards for quite a few things... But the biggest selling point is the
Kapacitor
