[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Angelo Mendonca updated PROTON-2218:
------------------------------------
Description:
{noformat}
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){noformat}
[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..
{code:java}
KWARGS {'kwargs': {'sasl_enabled': True, 'allow_insecure_mechs': True,
'password': 'DFfoSQM2ZYlLqCLm', 'user': 'DsWPjfKALYgKmtwsVGHBceceygn'}}
User None
None
password None
None
{code}
The Code setups a container connection..
!image-2020-05-12-14-18-33-313.png!
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"?
was:
{noformat}
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){noformat}
[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..
{code:java}
KWARGS {'kwargs': {'sasl_enabled': True, 'allow_insecure_mechs': True,
'password': 'DFfoSQM2ZYlLqCLm', 'user': 'DsWPjfKALYgKmtwsVGHBceceygn'}}
User None
None
password None
None
{code}
The Code setups a container connection..
!image-2020-05-12-14-18-33-313.png!
No idea why the user and password are not being set although kwagrs contains
both the keys....
> Connector.user and Connector.Password are None
> ----------------------------------------------
>
> Key: PROTON-2218
> URL: https://issues.apache.org/jira/browse/PROTON-2218
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
> Affects Versions: proton-c-0.30.0
> Reporter: Angelo Mendonca
> Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png
>
>
>
> {noformat}
> 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){noformat}
> [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..
>
> {code:java}
> KWARGS {'kwargs': {'sasl_enabled': True, 'allow_insecure_mechs': True,
> 'password': 'DFfoSQM2ZYlLqCLm', 'user': 'DsWPjfKALYgKmtwsVGHBceceygn'}}
> User None
> None
> password None
> None
> {code}
>
> The Code setups a container connection..
> !image-2020-05-12-14-18-33-313.png!
>
> 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"?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
