Bug 1067501 - Switchyard component hot deployment via JBoss CLI fails.
Summary: Switchyard component hot deployment via JBoss CLI fails.
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: SwitchYard
Version: 6.0.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: One-off release
Assignee: Rob Cernich
QA Contact: Matej Melko
URL:
Whiteboard:
Depends On:
Blocks: 1063388 1067642 1094865
TreeView+ depends on / blocked
 
Reported: 2014-02-20 14:46 UTC by Yusuf Koer
Modified: 2025-02-10 03:35 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
: 1067642 1094865 (view as bug list)
Environment:
Last Closed: 2025-02-10 03:35:09 UTC
Type: Support Patch
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SWITCHYARD-1979 0 Critical Resolved Threads started from Camel do not have correct namespace context 2017-04-28 10:40:31 UTC

Description Yusuf Koer 2014-02-20 14:46:07 UTC 
Description of problem:
We see following exception when we hot deploy an Switchyard component using jboss-cli. But it doesn't occur when we copy the components in deployments directory.
Unable to find BeanManager. Please ensure that you configured the CDI implementation of your choice properly

Version-Release number of selected component (if applicable):
JBoss Fuse Service Works 6.0.0.GA

How reproducible:

Steps to Reproduce:
1.Enable message tracing in switchyard.xml <property name="org.switchyard.handlers.messageTrace.enabled" value="true"/> 
2.Deploy the component using jboss.cli
3.

Actual results:
Consumer -> {urn:com.redhat:web-in:4.0}WebInBusOut
Provider -> [unassigned]
Operation -> process
MEP -> IN_ONLY
Phase -> IN
State -> OK
Exchange Context ->
    CamelCreatedTimestamp ..............: Wed Feb 19 10:16:57 EST 2014
    CamelExceptionCaught ...............: java.lang.IllegalStateException: Unable to find BeanManager. Please ensure that you configured the CDI implementation of your choice properly.
    CamelFailureEndpoint ...............: direct://%7Burn:com.redhat:web-in:4.0%7DWebInBusOut
    CamelFilterMatched .................: false
    CamelToEndpoint ....................: direct://%7Burn:com.redhat:web-in:4.0%7DWebInBusOut 


Additional info:
Comment 7 Red Hat Bugzilla 2025-02-10 03:35:09 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.