Our services are verifying the existence of multiplexer MBean (configured on the postOffice) ... if available, we use multiplexer, if not we use the config on clustered-mysql-persistence-service.xml (I mean.. .regular channels).
I have done this per Brian's suggestion.
If we were running messaging on JBoss 4.0 or 4.2 (not defined yet I guess if we will have or not the multiplexer) we would use regular channels.
If jboss-5 -> multiplexer.
That's what I saw in the code, too.
However, trying to use multiplexer doesn't work, so right now we're resorting to the good old channels.
We don't need to change code for this... just config files.
Is this done yet?
I still see the multiplexer being used:
09:40:55,312 TRACE @RMI TCP Connection(2)-10.11.14.72 [MBeanConfigurationElement] ObjectName is: jgroups.mux:name=Multiplexer 09:40:55,312 INFO @RMI TCP Connection(2)-10.11.14.72 [ServiceContainer] Could find multiplexer config 09:40:55,406 DEBUG @RMI TCP Connection(2)-10.11.14.72 [ServiceContainer] org.jgroups.jmx.JChannelFactory[jgroups.mux:name=Multiplexer] registered and configured
How do I configure this?
Ok that was easy.
I have changed the ServiceContainer "all" config to not start the multiplexer.
What's interesting is that yesterday after my wireformat refactoring pretty much all the clustering tests were failing.
After turning off the multiplexer they now pass :) I can only assume the jgroups stack config the multiplexer was using were incorrect.
We *really* need to get these in one place, so core test, jms tests and multiplxer all use the same stacks, otherwise this is a config nightmare.
BTW I *did* need to change code for this - but it was a trvial change in ServiceContainer so that the "all" config did not include multiplexer.
How could I have done it without changing config. files?
If you removed the attribute multiplexer on the PostOffice, the multiplexer would still be running but we wouldn't be using it.
I understood we didn't want to use the multiplexer any more. (at least not for now)