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.
Link: Added: This issue relates to SOA-3363
Oct 4, 2011 bug triage - move Fix Version to ER5
HornetQ is technical preview, so should not hold up the 5.2.0 release.
HornetQ is a TP in SOA 5.2 and cannot be a blocker.
Associated JIRA: https://issues.jboss.org/browse/JBPAPP-8709
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.
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.
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.
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.