"NoSuchBeanException: No bean could be found in the registry for: ..." when deploying multiple SwitchYard applications with Camel services

Solution Verified - Updated -

Issue

  • When we deploy a single service, everything works fine. However, when we deploy the second service the camel bean registry of the first service is getting mixed up. It is overridden to point to the bean registry of the second service and subsequently we get "bean not found" exceptions.
  • Steps to recreate the issue using a service1 and a service2:
    1. Deploy service1
    2. Enable service1
    3. Send a request to service1; Get a successful response
    4. Deploy service2
    5. Enable service2
    6. Send a request to service2; Get a successful response
    7. Send a request to service1; Get an error
  • The log shows:

    org.apache.camel.NoSuchBeanException: No bean could be found in the registry for: exampleBean1: org.apache.camel.NoSuchBeanException: No bean could be found in the registry for: exampleBean1
    
  • Patches installed: fsw-6.0_3_2014-switchyard.zip

Environment

  • Red Hat JBoss Fuse Service Works (FSW)
    • 6.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content