As far as I know if you don't use JNDI with 'auto-group' on JMS Connection Factories, enabling/disabling message grouping is simply controlled from client side, no need to change the server configuration at all.
You are right. Sorry for not mentioning that I don't want to make any changes to the client side either. And yes, currently the message grouping is being configured on the client side. My goal is to change that behavior without deploying new artifacts into this production system. A JBoss restart is viable, but not new artifacts.
nope, gouping is started automatically so you will have to stop adding the header on the client side.
Bummers. And now that I'm looking at the code more closely I can see how this can't be done. But let me correctly restate my setup, which I seem to keep messing up on, in case there is a glimmer of hope left:
- The Producer and Consumer of the queue are on separate Linux servers, each with their own JBoss 6.1 instance.
- Currently the Producer is configuring the message grouping by using a Spring MessagePostProcessor. Thus, before each message delivery it is setting the JMS message grouping property on the message and then delivering it to the queue.
- My goal is to disable message grouping without making changes to the code. Restarting JBoss is a viable option if some properties files can be leverged. Runtime settings might be another.
Given that the message grouping header is being added dynamically like I've stated above, hope seems to be lost, but please confirm. Thanks everyone for your speedy help.
@andy: could we add a property that would use the group one more time and then close it?
you would add a property to the message it would be used a last time and then delete it.
I think that's how I hve seen another system doing it.
From the point of view of grouping single node this would be easy. I'm not sure about clustering groups.