6 Replies Latest reply on Nov 5, 2015 2:32 PM by delivren

    A service reference to service '<<X>>' is not bound into this client proxy instance.

    calca
    calca Jun 16, 2014 9:18 AM

      Hi Guys,

       

      we are using SwitchYard 1.1.0.Final in our app and we are reproducing a behaviour that is happening from some to time.

       

      Sometimes, when we start our application, some services seems not be be initialized, and we get errors like this:

       

      014/06/08 08:20:53,267 ERROR stderr (pool-21-thread-69) Caused by: org.switchyard.component.bean.BeanComponentException: SWITCHYARD030402: A service reference to service 'MailReference' is not bound into this client proxy instance. A reference configuration to the service may be required in the application configuration.

      2014/06/08 08:20:53,266 ERROR stderr (http-/127.1.246.1:8080-1) Caused by: org.switchyard.component.bean.BeanComponentException: SWITCHYARD030402: A service reference to service 'IndicatorService' is not bound into this client proxy instance. A reference configuration to the service may be required in the application configuration.

       

      And the service that fails seems to be different from time to time. Then, when we restart, seems to be working fine.

       

      Do you guys have some clue on were to check or how can I get more information about what may be happening?

       

      Thanks in advance,


      Demian

        • 1. Re: A service reference to service '<<X>>' is not bound into this client proxy instance.
          kcbabo
          kcbabo Jun 30, 2014 9:16 AM (in response to calca)

          What type of deployment are you using (jar ,war, ear)?  Does it happen at deployment-time before a message has been received, or do you get this message when a message is first received?  If it's when a message is received, what service binding is used for that service?

            • Actions
          • 2. Re: A service reference to service '<<X>>' is not bound into this client proxy instance.
            calca
            calca Jul 1, 2014 6:01 PM (in response to kcbabo)

            Hey Keith, thanks for the response.

            I am using a WAR deployment. This happens after the deployment, when a message is received by this services. And I have seen this error to happen in a service which is a bean service, and also in MailService, which is a mail bilnding.

            Also, I also have another SY app which uses JAR deployment, and never seen this exception.

             

            Hope this information helps.. If any other information needed, just let me know,

             

            Thanks!

             

            Demian

              • Actions
            • 3. Re: A service reference to service '<<X>>' is not bound into this client proxy instance.
              jorgemoralespou_2
              jorgemoralespou_2 Jul 2, 2014 4:32 AM (in response to calca)

              Hi,

              We are having similar issues, not same, with .ear packaging of applications, that we do not see if we deploy as jar applications, although it is not what expected. We are using FSW 6.0 and have tried different patches, but still some random issues, like Demian says. Some of teh problems dissapear when redpeloyment occurs, and some remain.

               

              An example of the behaviour:

              I have an EAR containing several SY applications each one containing a service (A1, A2, ...) exposed with a SOAP binding. All these services consume services (B1, B2, ..., C1, C2, ...) from other EAR packages via SCA bindings. Sometimes when An is invoked I get an InvokationTargetException which seems to be caused by

              Caused by: org.switchyard.HandlerException: org.switchyard.SwitchYardException: SWITCHYARD014012: No registered service found for {namespace of Ak}AkBean/B1

               

              Demian, do you have SCA calls between the modules in your SwitchYard war?

                • Actions
              • 4. Re: A service reference to service '<<X>>' is not bound into this client proxy instance.
                kcbabo
                kcbabo Jul 2, 2014 8:10 AM (in response to calca)

                Demian Calcaprina wrote:

                 

                Also, I also have another SY app which uses JAR deployment, and never seen this exception.

                 

                Hope this information helps.. If any other information needed, just let me know,

                 

                Any chance you could try this out on SY 2.0.0.Alpha1 and let us know if you see the same issue?  If you do try it, keep in mind that the version of EAP required for SY 2.0 has been bumped to EAP 6.3.0 (EAP 6.3.0.Beta to be precise).  The reason I'm asking is there have been several patches in this area for the product which are also included in the upstream version (2.0) of the project as well.

                  • Actions
                • 5. Re: A service reference to service '<<X>>' is not bound into this client proxy instance.
                  dk_decay
                  dk_decay Jul 9, 2014 12:58 PM (in response to calca)

                  Hi ,

                   

                  I use to face this issue of service reference is not bound to client proxy if i am not wrong when the service name of my reference interface use to be different than the service name for the reference which was promoted.

                    • Actions
                  • 6. Re: A service reference to service '<<X>>' is not bound into this client proxy instance.
                    delivren
                    delivren Nov 5, 2015 2:32 PM (in response to dk_decay)

                    Thanks for the solution.

                      • Actions