Components dependent on messaging (e.g. jBPM, ESB...) do not work out-of-box when the server is switched to use HornetQ as a messaging provider. This is caused by missing guest user in hornetq-users.properties and guest role in hornetq-roles.properties in each server configuration. The defaul user should be uncommented, or all the components must use secured access to the queues/topics. In this case, another default user will need to be configured.
Trying ER3 and a jBPM quickstart I did not manage to reproduce this.
Verified in ER3.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Components which use messaging, including jBPM and the JBoss ESB, have startup issues when the user is employing HornetQ. These components do not work out-of-box when the server uses HornetQ as a messaging provider. This is caused by a missing guest user property in hornetq-users.properties and guest role in hornetq-roles.properties in each server configuration. To work around this, uncomment the default user or ensure all the components use secured access to the queues/topics.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.