Bug 780922 (SOA-3384) - org.jboss.jms.server.container.SecurityAspect.check is missing privileged blocks
Summary: org.jboss.jms.server.container.SecurityAspect.check is missing privileged blocks
Keywords:
Status: NEW
Alias: SOA-3384
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBoss Messaging
Version: 5.2.0.ER3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.3.0 GA
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-18 15:02 UTC by Julian Coleman
Modified: 2018-03-29 21:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When sending a message in JBoss, the org.jboss.jms.server.container.SecurityAspect.check property is missing privileged blocks.
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-3352 0 Major Resolved org.jboss.jms.server.container.SecurityAspect.check is missing privileged blocks 2020-07-01 09:55:55 UTC
Red Hat Issue Tracker SOA-3384 0 Major Closed org.jboss.jms.server.container.SecurityAspect.check is missing privileged blocks 2020-07-01 09:55:55 UTC

Description Julian Coleman 2011-09-18 15:02:22 UTC 
project_key: SOA

See SOA-3352 for details.  The unfixed mesaging code is present under:

  integration/EAP5/src/main/org/jboss/jms/server/container/

in 1.4.8.SP1 (EAP 5.1.1) and 1.4.8.SP3 (EAP 5.1.2) sources.
Comment 1 Julian Coleman 2011-09-18 15:06:23 UTC 
Note that SOA-P 5.2.0 also has a patch for SOA-3160 (JBPAPP-6835, JBMESSAGING-1884),
so an SOA-P patch must contain that fix as well.
Comment 2 Suz 2012-06-15 04:51:31 UTC 
    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:
When sending a message in JBoss, the org.jboss.jms.server.container.SecurityAspect.check property is missing privileged blocks.
Note You need to log in before you can comment on or make changes to this bug.