Bug 801026
Summary: | SOA-P 5.3.0.DR1 Empty HornetQ users/roles make queues unusable for server components | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Martin Vecera <mvecera> |
Component: | Build Process | Assignee: | Julian Coleman <jcoleman> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 5.3.0 GA | CC: | ldimaggi, ncross, soa-p-jira |
Target Milestone: | ER3 | ||
Target Release: | 5.3.0 GA | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2025-02-10 03:19:14 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Martin Vecera
2012-03-07 14:37:05 UTC
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. |