Definitely worth looking into it. If you can't use it or it doesn't do
what you need, maybe you can get some inspiration from the code.
On Wednesday, April 1, 2015, Kevin Burton wrote:
> I might re-investigate it… we were having problems with class path hell due
> to it conflicting with my code
I might re-investigate it… we were having problems with class path hell due
to it conflicting with my code and activemq. I think I might have resolved
that though. I would still need to run activemq in embedded mode and still
make sure the performance is decent :)
On Wed, Apr 1, 2015 at 8:07 PM,
This is very true for more reasons than those you describe. I am
presenting on activemq at apachecon in a couple of weeks and I will
probably talk about this a bit.
JMX can only give you a very limited number of useful metrics. JMX is
also almost useless in a more complex topology.
I would s
Jolokia maybe?
On Wednesday, April 1, 2015, Kevin Burton wrote:
> A couple things I wanted to talk about which are somewhat related.
>
> JMX is somewhat slow. Further, at least from my perspective, it’s somewhat
> dated. All the cool kinds have fancy REST API endpoints except for
> ActiveMQ.
>
A couple things I wanted to talk about which are somewhat related.
JMX is somewhat slow. Further, at least from my perspective, it’s somewhat
dated. All the cool kinds have fancy REST API endpoints except for
ActiveMQ.
I think we’re going to migrate to our own embedded activemq using our own
in
