Thanks Mr Droski-
Can you add a JIRA and we'll be investigate?
If you can replicate this without using the GoorvyMBean class that would be very helpful, so we can eliminate it from the enquiry.
def hornetServer = new GroovyMBean(server, 'org.hornetq:type=Server,module=JMS')
def q = new GroovyMBean(server, 'org.hornetq:type=Queue,module=JMS,name="out"')
In HornetQ 2.0.0.Beta5, the MBeans use underneath a HornetQ connection to handle replication to the backup node.
If you kill all the connections, it will also kill the connection used for management operations replication. Since the management operation can not be properly replicated, the error is reported to the user.
This behavior will change for the final 2.0.0 release. Management operations replication will no longer use a HornetQ connection. Closing all connections will not prevent the management operation to be performed.
But, in the mean time, you're right about the workaround, remove all messages from the queue before closing all the connections.
hope that helps
Thanks Jeff, you confirmed what I suspected about the implementation. Should I still file a JIRA or is this change already in a pipeline?
Yes, it is a good idea to file a JIRA issue to ensure the bug will be correctly fixed and verified for our next release.