Bug 780956 (SOA-3423)

Summary:	Deletion of whole security-setting element from honetq-configuration.xml have no effect
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Filip Nguyen <fnguyen>
Component:	JBoss Messaging, Security	Assignee:	Julian Coleman <jcoleman>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.2.0.ER4	CC:	ldimaggi, tcunning
Target Milestone:	---
Target Release:	FUTURE
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-3423
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	When a HornetQ security setting element configuration was delegated, it did not propagate its settings as expected.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:14:51 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 Filip Nguyen 2011-09-29 14:27:13 UTC

Steps to Reproduce:  # install SOAP with hornetq, set HDScanner to low time value to get faster redeployments
 # Take jms_secured and set it up according to readme
 # run soa platform with and deploy+run quickstart. output from helloworld should be seen in console
 # delete whole element <security-setting match="jms.queue.quickstart_jms_secured_Request_esb">
 # Wait for redeployment
 # Now it is possible to still "runtest" without problem
project_key: SOA

When deleting whole element security-setting from hornetq configuration this change doesn't propagate. See steps to reproduce.

In my opinion the reason that this is happening is cache (different one than in SOA-3363). This cache is located in HierarchicalObjectRepository.java. On line SecurityStoreImpl.java:164 these cached data are indirectly used.

Comment 1 Filip Nguyen 2011-09-29 14:27:38 UTC

Link: Added: This issue relates to SOA-3363

Comment 2 Len DiMaggio 2011-10-04 16:47:14 UTC

Oct 4, 2011 bug triage - move Fix Version to ER5

Comment 3 Julian Coleman 2011-10-13 12:45:13 UTC

HornetQ is technical preview, so should not hold up the 5.2.0 release.

Comment 4 Anne-Louise Tangring 2011-10-25 13:34:23 UTC

HornetQ is a TP in SOA 5.2 and cannot be a blocker.

Comment 5 Rick Wagner 2012-04-13 15:45:53 UTC

Associated JIRA:  

https://issues.jboss.org/browse/JBPAPP-8709

Comment 6 Rick Wagner 2012-04-16 20:29:31 UTC

Note that this BZ was opened against an older version of HornetQ than what we currently have in SOA-P 5.3 DR builds.  It's possible this issue was fixed, but this isn't known.

Comment 7 Suz 2012-06-14 23:56:09 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:
Deleting the security-setting element in HornetQ fails to produce expected results. Upon deleting this setting from hornet2-configuration.xml, the removal is not propagated.

Comment 8 Filip Nguyen 2012-06-15 12:16:02 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-Deleting the security-setting element in HornetQ fails to produce expected results. Upon deleting this setting from hornet2-configuration.xml, the removal is not propagated.+Deletion of a security-setting element in HornetQ configuration didn't propagated expected security settings.

Comment 10 David Le Sage 2012-07-02 03:27:36 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-Deletion of a security-setting element in HornetQ configuration didn't propagated expected security settings.+When a HornetQ security setting element configuration was delegated, it did not propagate its settings as expected.

Comment 12 Red Hat Bugzilla 2025-02-10 03:14:51 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.