Github user cshannon commented on the issue:
https://github.com/apache/activemq-artemis/pull/2012
@franz1981 and @michaelandrepearce - thanks for taking a look
---
Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/2012
@michaelandrepearce @cshannon my sider-sense doesn't feel dangers anymore :
---
+1 to investigate this for sure.
I’ve seen and attended a few of the same Akka presentations.
The main bit is for it to be able to split the work and execute in parallel
when possible (divide and conquer) so if the work/code isn’t splittable into
smaller units of concurrent work then not going
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2012
@franz1981, any comment?
---
Github user clebertsuconic commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/2010#discussion_r181386656
--- Diff:
artemis-server/src/main/java/org/apache/activemq/artemis/core/server/impl/QueueImpl.java
---
@@ -2712,6 +2713,11 @@ private Mess
HI guys!!!
after a couple of talks I've seen about Akka and the (seems good)
ForkJoinPool experience and a tons of metrics i have collected on Artemis
related to the current implementation used, I'm starting to believe that the
broker could benefit a lot by using a ForkJoinPool.
The current imple
GitHub user stanlyDoge opened a pull request:
https://github.com/apache/activemq-artemis/pull/2013
ARTEMIS-1805 fix for broker operations in hawtio
There are two operations, which causes an error while selected in hawtio
console under broker/operations. Adding @Operation annotation