Bug 1146953

Summary: Namespace context not set for camel bindings with unmanaged threads
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Rick Wagner <rwagner>
Component: SwitchYardAssignee: Rob Cernich <rcernich>
Status: VERIFIED --- QA Contact: Matej Melko <mmelko>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: ppecka, rcernich, soa-p-jira
Target Milestone: CR1   
Target Release: One-off release   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1146970 (view as bug list) Environment:
Last Closed: Type: Support Patch
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1120384, 1146970    

Description Rick Wagner 2014-09-26 12:26:03 UTC 
Camel components which do not use Camel-managed thread pools can lead to BeanManager resolution issues when the namespace context is not set. The solution to this is to add a routing policy to Camel gateway routes that sets the namespace context for the gateway delivery thread.
Comment 1 Rob Cernich 2014-09-26 13:56:29 UTC 
should be available in p8 or later