Uploaded image for project: 'Qpid Proton'
  1. Qpid Proton
  2. PROTON-2218

Connector.user and Connector.Password are None

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Not A Bug
    • proton-c-0.30.0
    • None
    • python-binding
    • None

    Description

       

              connector.user = kwargs.get('user', self.user)
              print("User", kwargs.get('user', self.user))
              print(connector.user)
              connector.password = kwargs.get('password', self.password)
              print("password", kwargs.get('password', self.password))
              print(connector.password)

      https://github.com/apache/qpid-proton/blob/4265cc7ab8391630b47da2de4c1ead2f28763980/python/proton/_reactor.py#L1264

       

      https://github.com/apache/qpid-proton/blob/4265cc7ab8391630b47da2de4c1ead2f28763980/python/proton/_reactor.py#L1265 

      Dont see to exist in kwargs although the print statement just above the kwargs.get shows that user and password exist...

      The output is below..

       

      KWARGS {'kwargs': {'sasl_enabled': True, 'allow_insecure_mechs': True, 'password': 'DFfoSQM2ZYlLqCLm', 'user': 'DsWPjfKALYgKmtwsVGHBceceygn'}}
      User None
      None
      password None
      None
      

       

      The Code setups a container connection..

       

      No idea why the user and password are not being set although kwagrs contains both the keys....I am trying to get failover to work with AWS Amazon MQ. Does BlockingConnection let you work with multiple URLS? Or do I need to use "container.connect"?

       

      Attachments

        1. image-2020-05-12-17-01-10-260.png
          268 kB
          Angelo Mendonca
        2. jd_answer_1.png
          19 kB
          Jiri Daněk
        3. image-2020-05-12-14-18-33-313.png
          93 kB
          Angelo Mendonca

        Activity

          People

            jdanek Jiri Daněk
            angelomendonca Angelo Mendonca
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: