Thanks for reporting this.
I have been trying to think of a way around this issue. One thing that has come to mind is to create my own BarrierController that will map JMX event x to method y. Instead of mapping JMX events to only startService() and stopSevervice().
Any other thoughts?
Is this bug been resolved? Few days ago we experienced the same issue. In our case it was MDB.