Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-4850

No bean could be found in the registry for: ConnectionFactory of type: javax.jms.ConnectionFactory

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: jboss-fuse-6.3
    • Fix Version/s: fuse-7.0
    • Component/s: SwitchYard, WildFly Camel
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      Actually, I did some more testing, and it appears that the number of applications which are needed to is less than 20. Here are some details:

      1. Use a clean instance of Fuse 6.2.1 on EAP, add the content of attached queues.txt to standalone-full.xml. Notice that queue GreetingService1Queue is missing on purpose

      2. Copy attached GreetingService[1-7].jar to standalone/deployments

      3. Start the server. Deployment will work, followed by the following periodic warning (which is expected due to the missing queue definition):

      WARN [org.apache.camel.component.jms.DefaultJmsMessageListenerContainer] (pool-18-thread-1) Setup of JMS message listener invoker failed for destination 'GreetingService1Queue' - trying to recover. Cause: There is no queue with name GreetingService1Queue

      4. Shut down the server

      5. Add GreetingService[8-9].jar to standalone/deployments

      6. Delete all GreetingService?.deployed marker files

      7. Start the server again. This time it will fail with the No bean could be found error. Strangely though, this causes all but one GreetingService?.jar applications to fail

      Show
      Actually, I did some more testing, and it appears that the number of applications which are needed to is less than 20. Here are some details: 1. Use a clean instance of Fuse 6.2.1 on EAP, add the content of attached queues.txt to standalone-full.xml. Notice that queue GreetingService1Queue is missing on purpose 2. Copy attached GreetingService [1-7] .jar to standalone/deployments 3. Start the server. Deployment will work, followed by the following periodic warning (which is expected due to the missing queue definition): WARN [org.apache.camel.component.jms.DefaultJmsMessageListenerContainer] (pool-18-thread-1) Setup of JMS message listener invoker failed for destination 'GreetingService1Queue' - trying to recover. Cause: There is no queue with name GreetingService1Queue 4. Shut down the server 5. Add GreetingService [8-9] .jar to standalone/deployments 6. Delete all GreetingService?.deployed marker files 7. Start the server again. This time it will fail with the No bean could be found error. Strangely though, this causes all but one GreetingService?.jar applications to fail
    • Git Pull Request:

      Description

      From Martin Weiler:

      when I generate variations of the camel-jms-binding quickstart, there is no issue starting the server. But when I add another one, most deployments fail with an ERROR that a bean could not be found (see full stacktrace below).

      Questions:
      1. Has anyone come across this? I noticed we had similar issues on FSW 6.0.0 - https://bugzilla.redhat.com/show_bug.cgi?id=1241859

      2. Could it be a configuration issue, like a pool limit of 20?

      [1]

      12:16:37,956 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."GreetingService8.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."GreetingService8.jar".SwitchYardService: org.switchyard.SwitchYardException: org.apache.camel.FailedToCreateRouteException: Failed to create route V1CamelJmsBindingModel/GreetingService8@_GreetingService8_jms_1#-1809602182: Route(V1CamelJmsBindingModel/GreetingService8@_GreetingServi... because of Failed to resolve endpoint: jms://queue:GreetingService8Queue?connectionFactory=%23ConnectionFactory due to: No bean could be found in the registry for: ConnectionFactory of type: javax.jms.ConnectionFactory
      		 
              at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:84)
      		 
              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
      		 
              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
      		 
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60]
      		 
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60]
      		 
              at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
      		 
      Caused by: org.switchyard.SwitchYardException: org.apache.camel.FailedToCreateRouteException: Failed to create route V1CamelJmsBindingModel/GreetingService8@_GreetingService8_jms_1#-1809602182: Route(V1CamelJmsBindingModel/GreetingService8@_GreetingServi... because of Failed to resolve endpoint: jms://queue:GreetingService8Queue?connectionFactory=%23ConnectionFactory due to: No bean could be found in the registry for: ConnectionFactory of type: javax.jms.ConnectionFactory
      		 
              at org.switchyard.component.camel.common.handler.InboundHandler.<init>(InboundHandler.java:74)
      		 
              at org.switchyard.component.camel.common.deploy.BaseBindingActivator.createInboundHandler(BaseBindingActivator.java:50)
      		 
              at org.switchyard.component.camel.common.deploy.BaseBindingActivator.activateBinding(BaseBindingActivator.java:43)
      		 
              at org.switchyard.deploy.internal.Deployment.deployServiceBindings(Deployment.java:629)
      		 
              at org.switchyard.deploy.internal.Deployment.start(Deployment.java:145)
      		 
              at org.switchyard.as7.extension.deployment.SwitchYardDeployment.start(SwitchYardDeployment.java:127)
      		 
              at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:77)
      		 
              ... 5 more
      		 
      Caused by: org.apache.camel.FailedToCreateRouteException: Failed to create route V1CamelJmsBindingModel/GreetingService8@_GreetingService8_jms_1#-1809602182: Route(V1CamelJmsBindingModel/GreetingService8@_GreetingServi... because of Failed to resolve endpoint: jms://queue:GreetingService8Queue?connectionFactory=%23ConnectionFactory due to: No bean could be found in the registry for: ConnectionFactory of type: javax.jms.ConnectionFactory
      		 
              at org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:190)
      		 
              at org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:841)
      		 
              at org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:2895)
      		 
              at org.apache.camel.impl.DefaultCamelContext.addRouteDefinitions(DefaultCamelContext.java:775)
      		 
              at org.apache.camel.impl.DefaultCamelContext.addRouteDefinition(DefaultCamelContext.java:780)
      		 
              at org.switchyard.component.camel.common.handler.InboundHandler.<init>(InboundHandler.java:72)
      		 
              ... 11 more
      		 
      Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: jms://queue:GreetingService8Queue?connectionFactory=%23ConnectionFactory due to: No bean could be found in the registry for: ConnectionFactory of type: javax.jms.ConnectionFactory
      		 
              at org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:578)
      		 
              at org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:79)
      		 
              at org.apache.camel.model.RouteDefinition.resolveEndpoint(RouteDefinition.java:200)
      		 
              at org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:107)
      		 
              at org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:113)
      		 
              at org.apache.camel.model.FromDefinition.resolveEndpoint(FromDefinition.java:70)
      		 
              at org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:89)
      		 
              at org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:1008)
      		 
              at org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:185)
      		 
              ... 16 more
      		 
      Caused by: org.apache.camel.NoSuchBeanException: No bean could be found in the registry for: ConnectionFactory of type: javax.jms.ConnectionFactory
      		 
              at org.apache.camel.util.CamelContextHelper.mandatoryLookup(CamelContextHelper.java:159)
      		 
              at org.apache.camel.util.EndpointHelper.resolveReferenceParameter(EndpointHelper.java:323)
      		 
              at org.apache.camel.util.EndpointHelper.resolveReferenceParameter(EndpointHelper.java:305)
      		 
              at org.apache.camel.impl.DefaultComponent.resolveAndRemoveReferenceParameter(DefaultComponent.java:379)
      		 
              at org.apache.camel.impl.DefaultComponent.resolveAndRemoveReferenceParameter(DefaultComponent.java:358)
      		 
              at org.apache.camel.component.jms.JmsComponent.createEndpoint(JmsComponent.java:515)
      		 
              at org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:114)
      		 
              at org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:558)
      		 
              ... 24 more

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                tadayosi Tadayoshi Sato
                Reporter:
                tcunning Tom Cunningham
                Tester:
                Stefan Veres
              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: