new Fiber(FiberScheduler, SuspendableRunnable) scheduler is not passed
IngvarJackal opened this issue · comments
Here the new Val is allocated on default scheduler instead of one passed to constructor. Is that a bug?
Current behavior leads to javax.management.InstanceAlreadyExistsException: co.paralleluniverse:type=Fibers,name=default-fiber-pool
on every subsequent restart of Wildfly 8.2.1 deployment after default MXBean is created.
If that isn't a bug, is it possible to set executors for all fibers, including internal ones? This is quite important for pools management on application servers.