We have discussed that the JMS/HornetQ address-settings for this fix requires standalone.xml (or CLI) changes.
In detail discussed in http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Heads-up-UPS-JMS-queueing-configuration-in-standalone-xml-td12290.html
In order to optimize how the messages are handled internally we planned to tweak various queue properties (on the level of "address-settings", hornetq-configuration.xml).
if I say optimize, I mean it will work without this configuration, but it is not ideal for production
The bad news is that address-settings can't be changed on the level of deployment (via #hornetq, or see Clebert's answer ). We will have to configure it in standalone.xml.
We've brainstormed with Sebi, seems there are two ways out (both should be implemented at some point IMO):
1) jboss-cli script that will set up WF appropriately (similar as we do with datasource install)
2) WildFly Swarm seems to get a feature to bundle standalone.xml soon SWARM-14
I just wanted to share this and allow feedback and open the discussion for alternative ideas. I will proceed and offer (1) as of now.
As that, we have to shift this to 1.2.0, since this setup was not required for 1.1.0 users.
|