[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105782#comment-17105782
]
Angelo Mendonca commented on PROTON-2218:
-
The copy paste was not so good...
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png,
> image-2020-05-12-17-01-10-260.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105781#comment-17105781
]
Angelo Mendonca commented on PROTON-2218:
-
{code:java}
from proton.handlers import MessagingHandler
from proton.reactor import Container
from proton import Message
import jsonclass FailOverHandler(MessagingHandler):
def __init__(self, url_one, url_two, queue, message):
super(FailOverHandler, self).__init__()
self.url_one = url_one
self.url_two = url_two
self.queue = queue
self.sender = None
self.conn = None
self.message = message
self.count = 0def on_sendable(self, event):
print("On Sendable")
self.send()def on_connection_error(self,event):
print(event)
event.connection.close()
def on_transport_error(self, event):
print(event)
event.connection.close()
print(event.transport.condition)def send(self):
while self.sender.credit and self.count < 200:
body = json.dumps(self.message)
self.sender.send(Message(durable=True, body=body))
self.count +=1
print("Sent message")def on_accepted(self, event):
print("Accepted")
event.connection.close()def on_start(self, event):
print("Starting")
self.conn = event.container.connect(urls=[self.url_one, self.url_two],
address=self.queue,
sasl_enabled=True,
allow_insecure_mechs=False,password='DFfoSQM2ZYlLqCLm',
user='DsWPjfKALYgKmtwsVGHBceceygn', reconnect=True)
self.conn.state
print("Creating Sender")
self.sender = event.container.create_sender(self.conn,
self.queue)url_one='amqps://b-4655a180-9a2d-4c67-99aa-bbe51f58b963-1.mq.us-east-1.amazonaws.com:5671'
url_two='amqps://b-4655a180-9a2d-4c67-99aa-bbe51f58b963-2.mq.us-east-1.amazonaws.com:5671'
hdl=FailOverHandler(url_one,url_two,'test', '{"Name":"Test Data"}')
c=Container(hdl)
c.run()
{code}
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png,
> image-2020-05-12-17-01-10-260.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk closed PROTON-2218.
--
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png,
> image-2020-05-12-17-01-10-260.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105779#comment-17105779
]
Jiri Daněk commented on PROTON-2218:
Just say no to code pasted as screenshot! How am I supposed to copypaste from
that? I don't always have OCR program at hand :P
Jira has code highlighting, btw, and anyways, fancy colours are not that
important, anyways.
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png,
> image-2020-05-12-17-01-10-260.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105778#comment-17105778
]
Angelo Mendonca commented on PROTON-2218:
-
{noformat}
{noformat}
!image-2020-05-12-17-01-10-260.png!
{noformat}
Then hats all the code I have.{noformat}
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png,
> image-2020-05-12-17-01-10-260.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Angelo Mendonca updated PROTON-2218:
Attachment: image-2020-05-12-17-01-10-260.png
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png,
> image-2020-05-12-17-01-10-260.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105769#comment-17105769
]
Angelo Mendonca edited comment on PROTON-2218 at 5/12/20, 9:58 PM:
---
Whats the proton email list? And I am passing in the urls...It also shows that
its getting the urls..
{noformat}
url_one='amqps://b-SOME-9a2d-4c67-99aa-bbe51f58b963-1.mq.us-east-1.amazonaws.com:5671'url_two='amqps://b-SOME-9a2d-4c67-99aa-bbe51f58b963-2.mq.us-east-1.amazonaws.com:5671'{noformat}
{noformat}
hdl=FailOverHandler(url_one,url_two,'test', '{"Name":"Test Data"}'){noformat}
{noformat}
Container(hdl).run(){noformat}
was (Author: angelomendonca):
Whats the proton email list? And I am passing in the urls...It also shows that
its getting the urls..
{noformat}
url_one='amqps://b-SOME-9a2d-4c67-99aa-bbe51f58b963-1.mq.us-east-1.amazonaws.com:5671'url_two='amqps://b-SOME-9a2d-4c67-99aa-bbe51f58b963-2.mq.us-east-1.amazonaws.com:5671'{noformat}
{noformat}
hdl=FailOverHandler(url_one,url_two,'test', '{"Name":"Test Data"}'){noformat}
{noformat}
c=Container(hdl).run(){noformat}
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105774#comment-17105774
]
Jiri Daněk commented on PROTON-2218:
bq. Whats the proton email list?
https://qpid.apache.org/discussion.html
bq. And I am passing in the urls...It also shows that its getting the urls..
Well, {{c=Container(hdl).run()}} is nonsense. run() returns {{None}}, so why
are you assigning it to {{c}}? You may have more mistakes like that in your
program, which somehow result in not connecting where you intend to.
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105773#comment-17105773
]
Angelo Mendonca commented on PROTON-2218:
-
Thanks [~jdanek]
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105771#comment-17105771
]
Angelo Mendonca commented on PROTON-2218:
-
And then if I change the order of the urls with the broker that is active to
the first element in the urls=[...] list..I get
{noformat}
Condition('amqp:unauthorized-access', 'Authentication failed
[mech=PLAIN]')...{noformat}
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105769#comment-17105769
]
Angelo Mendonca edited comment on PROTON-2218 at 5/12/20, 9:47 PM:
---
Whats the proton email list? And I am passing in the urls...It also shows that
its getting the urls..
{noformat}
url_one='amqps://b-SOME-9a2d-4c67-99aa-bbe51f58b963-1.mq.us-east-1.amazonaws.com:5671'url_two='amqps://b-SOME-9a2d-4c67-99aa-bbe51f58b963-2.mq.us-east-1.amazonaws.com:5671'{noformat}
{noformat}
hdl=FailOverHandler(url_one,url_two,'test', '{"Name":"Test Data"}'){noformat}
{noformat}
c=Container(hdl).run(){noformat}
was (Author: angelomendonca):
Whats the proton email list? And I am passing in the urls...It also shows that
its getting the urls..
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105769#comment-17105769
]
Angelo Mendonca edited comment on PROTON-2218 at 5/12/20, 9:46 PM:
---
Whats the proton email list? And I am passing in the urls...It also shows that
its getting the urls..
was (Author: angelomendonca):
Whats the proton email list?
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105769#comment-17105769
]
Angelo Mendonca commented on PROTON-2218:
-
Whats the proton email list?
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105765#comment-17105765
]
Jiri Daněk commented on PROTON-2218:
bq. I have 2 servers in AWS MQ. I can netcat to one of them from the EC2
instance but when I try to connect using proton I get
`Condition('proton.pythonio', 'Connection refused to all addresses')`. Anything
that I should be looking into...Mind you I can connect to the broker from
telnet...
I'd try to check where it is actually connecting. I have a feeling that it will
default to amqp://localhost:5672 if you do not pass it url, or you pass url
incorrectly. Not sure what would be an easy way to check. Run the program under
{{strace}}, or whatever Windows uses instead of it, if you are on Windows? Step
through it in debugger?
Anyways, we got pretty far from the original Jira ticket. This would be best to
take to proton e-mail list.
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105763#comment-17105763
]
Angelo Mendonca commented on PROTON-2218:
-
{noformat}
{
"scheme": "amqps",
"user": "SOME",
"password": "SOME",
"sasl": {
"enable": true,
"allow_insecure": false
},
"tls": {
"enable": true,
"ca": null,
"cert": "/root/certificate.pem",
"key": "/root/privateKey.key",
"verify": false
}
}{noformat}
This is my connect.json.
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105761#comment-17105761
]
Jiri Daněk commented on PROTON-2218:
bq. Without calling container.run() can I just use the connection that
container.connect returns?
Yes, but you can only use it from the {{on_...}} handlers, and you need the
proton eventloop running, which means calling {{container.run()}}.
bq. What If I want to setup a connection only when a rest endpoint gets called
and then send a message?
This sounds like the the interactive example,
https://github.com/apache/qpid-proton/blob/7abcfc7aba6cfd1c938324cf34a51555c845a589/python/examples/tx_recv_interactive.py#L76-L83.
You'd have your rest endpoint triggering events inside the proton eventloop
using EventInjector.
bq. Problem is the rest of the team is using BlockingConnection for dev
purposes and I have been tasked to add the failover with.
How do you know you need to failover, when using BlockingConnection? You get an
exception that you were disconnected. So add a try: except block, catch the
exception, and connect again, essentially. That way you can keep using
BlockingConnection.
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105759#comment-17105759
]
Angelo Mendonca commented on PROTON-2218:
-
I have 2 servers in AWS MQ. I can netcat to one of them from the EC2 instance
but when I try to connect using proton I get `Condition('proton.pythonio',
'Connection refused to all addresses')`. Anything that I should be looking
into...Mind you I can connect to the broker from telnet...
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105754#comment-17105754
]
Angelo Mendonca commented on PROTON-2218:
-
ok will give that a shot...Problem is the rest of the team is using
BlockingConnection for dev purposes and I have been tasked to add the failover
with. Without calling container.run() can I just use the connection that
container.connect returns? Most of the example code is showing to pass messages
when the process starts..What If I want to setup a connection only when a rest
endpoint gets called and then send a message?
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk resolved PROTON-2218.
Resolution: Not A Bug
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105748#comment-17105748
]
Jiri Daněk commented on PROTON-2218:
You can either catch the exception when the broker disconnects you and then
reconnect yourself. Or you can use `proton.Container` directly, call
{{.connect}} with {{urls=[...], reconnect=True...}} Essentially the code you
had above, your {{def on_start}} and so on. BlockingConnection is just a
wrapper around proton.Container.
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105748#comment-17105748
]
Jiri Daněk edited comment on PROTON-2218 at 5/12/20, 9:18 PM:
--
You can either keep using BlockingConnection, catch the exception when the
broker disconnects you and then reconnect yourself. Or you can use
`proton.Container` directly, call {{.connect}} with {{urls=[...],
reconnect=True...}} Essentially the code you had above, your {{def on_start}}
and so on. BlockingConnection is just a wrapper around proton.Container.
was (Author: jdanek):
You can either catch the exception when the broker disconnects you and then
reconnect yourself. Or you can use `proton.Container` directly, call
{{.connect}} with {{urls=[...], reconnect=True...}} Essentially the code you
had above, your {{def on_start}} and so on. BlockingConnection is just a
wrapper around proton.Container.
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105738#comment-17105738
]
Angelo Mendonca commented on PROTON-2218:
-
So what do you suggest I use for failover with AmazonMQ? I am banging on my
head on trying to figure this out...
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105734#comment-17105734
]
Jiri Daněk commented on PROTON-2218:
You cannot specify multiple urls, because you cannot do failover with
BlockingConnection. If you take a look how it is defined, it explicitly
connects with {{reconnect=False}}.
https://github.com/apache/qpid-proton/blob/3075d7a6aff6d6419e48a30b428299aa899e3d79/python/proton/_utils.py#L359-L360
There was a similar issue about connecting to Azure IoT ServiceBuss,
PROTON-2044. Blocking connection may not be flexible enough for you.
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105719#comment-17105719
]
Angelo Mendonca commented on PROTON-2218:
-
Oh ok..Thank you[~jdanek]
Is there documentation to use multiple urls for failover with
BlockingConnection. I dont see any example of using multiple url..
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk reassigned PROTON-2218:
--
Assignee: Jiri Daněk
> 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
>Assignee: Jiri Daněk
>Priority: Major
> Attachments: image-2020-05-12-14-18-33-313.png, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105693#comment-17105693
]
Jiri Daněk edited comment on PROTON-2218 at 5/12/20, 7:48 PM:
--
The way {{**kwargs}} works in Python is that it collects all keyword arguments
which are not named explicitly in function definition.
bq. When a final formal parameter of the form **name is present, it receives a
dictionary (see Mapping Types — dict) containing all keyword arguments except
for those corresponding to a formal parameter.
https://docs.python.org/3/tutorial/controlflow.html#keyword-arguments
You do not specify a {{kwargs}} parameter explicitly, as a dictionary. Instead,
you just pass the keys as keyword arguments, and Python collects them into the
{{kwargs}}.
!jd_answer_1.png!
was (Author: jdanek):
The way {{**kwargs}} works in Python is that it collects all keyword parameters
which are not given explicitly in function definition.
bq. When a final formal parameter of the form **name is present, it receives a
dictionary (see Mapping Types — dict) containing all keyword arguments except
for those corresponding to a formal parameter.
https://docs.python.org/3/tutorial/controlflow.html#keyword-arguments
You do not specify a {{kwargs}} parameter explicitly, as a dictionary. Instead,
you just pass the keys as keyword arguments, and Python collects them into the
{{kwargs}}.
!jd_answer_1.png!
> 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, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105693#comment-17105693
]
Jiri Daněk commented on PROTON-2218:
The way {{**kwargs}} works in Python is that it collects all keyword parameters
which are not given explicitly in function definition.
bq. When a final formal parameter of the form **name is present, it receives a
dictionary (see Mapping Types — dict) containing all keyword arguments except
for those corresponding to a formal parameter.
https://docs.python.org/3/tutorial/controlflow.html#keyword-arguments
You do not specify a {{kwargs}} parameter explicitly, as a dictionary. Instead,
you just pass the keys as keyword arguments, and Python collects them into the
{{kwargs}}.
!jd_answer_1.png!
> 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, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2218) Connector.user and Connector.Password are None
[
https://issues.apache.org/jira/browse/PROTON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk updated PROTON-2218:
---
Attachment: jd_answer_1.png
> 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, jd_answer_1.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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2218) Connector.user and Connector.Password are None
[
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 keysI 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 keysI 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2218) Connector.user and Connector.Password are None
[
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
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!
> 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
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2218) Connector.user and Connector.Password are None
Angelo Mendonca created PROTON-2218:
---
Summary: 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
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!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1649) Tox failure, Python Checker error in config.py
[
https://issues.apache.org/jira/browse/DISPATCH-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved DISPATCH-1649.
--
Fix Version/s: 1.13.0
Resolution: Fixed
updated python checker linter configuration - not a bug.
> Tox failure, Python Checker error in config.py
> --
>
> Key: DISPATCH-1649
> URL: https://issues.apache.org/jira/browse/DISPATCH-1649
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Management Agent
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ken Giusti
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> st 67
> Start 67: python-checker
> 67: Test command: /usr/local/bin/tox
> 67: Test timeout computed to be: 600
> 67: py27 create: /foo/qpid-dispatch/build/tests/.tox/py27
> 67: py27 installdeps: hacking>=1.1.0
> 67: WARNING: Discarding $PYTHONPATH from environment, to override specify
> PYTHONPATH in 'passenv' in your configuration.
> 67: py27 installed: DEPRECATION: Python 2.7 reached the end of its life on
> January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer
> maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More
> details about Python 2 support in pip, can be found at
> https://pip.pypa.io/en/latest/development/release-process/#python-2-support,configparser==4.0.2,contextlib2==0.6.0.post1,enum34==1.1.10,flake8==3.8.1,functools32==3.2.3.post2,hacking==2.0.0,importlib-metadata==1.6.0,mccabe==0.6.1,pathlib2==2.3.5,pycodestyle==2.6.0,pyflakes==2.2.0,qpid-dispatch===1.13.0-SNAPSHOT,scandir==1.10.0,six==1.14.0,typing==3.7.4.1,zipp==1.2.0
> 67: py27 run-test-pre: PYTHONHASHSEED='1454137866'
> 67: py27 run-test: commands[0] | flake8 --count --show-source
> /foo/qpid-dispatch/python /foo/qpid-dispatch/console /foo/qpid-dispatch/docs
> /foo/qpid-dispatch/tests /foo/qpid-dispatch/tools
> /foo/qpid-dispatch/tools/qdstat /foo/qpid-dispatch/tools/qdmanage
> --ignore=E111,E114,E121,E122,E123,E124,E126,E127,E128,E129,E131,E201,E202,E203,E211,E221,E222,E225,E226,E228,E231,E241,E251,E261,E266,E265,E271,E272,E301,E302,E303,E305,E306,E401,E402,E501,E502,E701,E702,E703,E704,E711,E712,E713,E714,E731,E722,F401,F403,F405,F811,F841,H101,H102,H104,H201,H202,H234,H237,H238,H301,H306,H401,H403,H404,H405,W291,W292,W293,W391,W503,W504
> 67:
> /foo/qpid-dispatch/python/qpid_dispatch_internal/management/config.py:107:49:
> E741 ambiguous variable name 'l'
> 67: js_text = "[%s]"%("\n".join([sub(l) for l in lines]))
> 67: ^
> 67:
> /foo/qpid-dispatch/python/qpid_dispatch_internal/management/config.py:122:47:
> E741 ambiguous variable name 'l'
> 67: js_text = "%s"%("\n".join([sub(l) for l in lines]))
> 67: ^
> 67:
> /foo/qpid-dispatch/python/qpid_dispatch_internal/management/config.py:182:9:
> E741 ambiguous variable name 'l'
> 67: for l in config.by_type('log'):
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_test.py:378:26: E741 ambiguous variable
> name 'l'
> 67: def sub_elem(l, level):
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_test.py:407:30: E741 ambiguous variable
> name 'l'
> 67: default_log = [l for l in config if (l[0] == 'log' and
> l[1]['module'] == 'DEFAULT')]
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_test.py:466:13: E741 ambiguous variable
> name 'l'
> 67: for l in self.config.sections('listener'):
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_test.py:477:31: E741 ambiguous variable
> name 'l'
> 67: return [l['port'] for l in self.config.sections('listener')]
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_test.py:493:60: E741 ambiguous variable
> name 'l'
> 67: return ["amqp://%s" % self._cfg_2_host_port(l) for l in cfg]
> 67:^
> 67: /foo/qpid-dispatch/tests/system_test.py:504:46: E741 ambiguous variable
> name 'l'
> 67: return [self._cfg_2_host_port(l) for l in
> self.config.sections('listener')]
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1653:28: E741
> ambiguous variable name 'l'
> 67: lines = [l for l in inta_log.read().split("\n")
> 67:^
> 67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1666:17: E741
> ambiguous variable name 'l'
> 67: for l in lines:
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1682:17: E741
> ambiguous variable name 'l'
> 67: for l in lines:
> 67: ^
> 67:
[jira] [Assigned] (DISPATCH-1649) Tox failure, Python Checker error in config.py
[
https://issues.apache.org/jira/browse/DISPATCH-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-1649:
---
Assignee: Ken Giusti
> Tox failure, Python Checker error in config.py
> --
>
> Key: DISPATCH-1649
> URL: https://issues.apache.org/jira/browse/DISPATCH-1649
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Management Agent
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ken Giusti
>Priority: Major
>
> {noformat}
> st 67
> Start 67: python-checker
> 67: Test command: /usr/local/bin/tox
> 67: Test timeout computed to be: 600
> 67: py27 create: /foo/qpid-dispatch/build/tests/.tox/py27
> 67: py27 installdeps: hacking>=1.1.0
> 67: WARNING: Discarding $PYTHONPATH from environment, to override specify
> PYTHONPATH in 'passenv' in your configuration.
> 67: py27 installed: DEPRECATION: Python 2.7 reached the end of its life on
> January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer
> maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More
> details about Python 2 support in pip, can be found at
> https://pip.pypa.io/en/latest/development/release-process/#python-2-support,configparser==4.0.2,contextlib2==0.6.0.post1,enum34==1.1.10,flake8==3.8.1,functools32==3.2.3.post2,hacking==2.0.0,importlib-metadata==1.6.0,mccabe==0.6.1,pathlib2==2.3.5,pycodestyle==2.6.0,pyflakes==2.2.0,qpid-dispatch===1.13.0-SNAPSHOT,scandir==1.10.0,six==1.14.0,typing==3.7.4.1,zipp==1.2.0
> 67: py27 run-test-pre: PYTHONHASHSEED='1454137866'
> 67: py27 run-test: commands[0] | flake8 --count --show-source
> /foo/qpid-dispatch/python /foo/qpid-dispatch/console /foo/qpid-dispatch/docs
> /foo/qpid-dispatch/tests /foo/qpid-dispatch/tools
> /foo/qpid-dispatch/tools/qdstat /foo/qpid-dispatch/tools/qdmanage
> --ignore=E111,E114,E121,E122,E123,E124,E126,E127,E128,E129,E131,E201,E202,E203,E211,E221,E222,E225,E226,E228,E231,E241,E251,E261,E266,E265,E271,E272,E301,E302,E303,E305,E306,E401,E402,E501,E502,E701,E702,E703,E704,E711,E712,E713,E714,E731,E722,F401,F403,F405,F811,F841,H101,H102,H104,H201,H202,H234,H237,H238,H301,H306,H401,H403,H404,H405,W291,W292,W293,W391,W503,W504
> 67:
> /foo/qpid-dispatch/python/qpid_dispatch_internal/management/config.py:107:49:
> E741 ambiguous variable name 'l'
> 67: js_text = "[%s]"%("\n".join([sub(l) for l in lines]))
> 67: ^
> 67:
> /foo/qpid-dispatch/python/qpid_dispatch_internal/management/config.py:122:47:
> E741 ambiguous variable name 'l'
> 67: js_text = "%s"%("\n".join([sub(l) for l in lines]))
> 67: ^
> 67:
> /foo/qpid-dispatch/python/qpid_dispatch_internal/management/config.py:182:9:
> E741 ambiguous variable name 'l'
> 67: for l in config.by_type('log'):
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_test.py:378:26: E741 ambiguous variable
> name 'l'
> 67: def sub_elem(l, level):
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_test.py:407:30: E741 ambiguous variable
> name 'l'
> 67: default_log = [l for l in config if (l[0] == 'log' and
> l[1]['module'] == 'DEFAULT')]
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_test.py:466:13: E741 ambiguous variable
> name 'l'
> 67: for l in self.config.sections('listener'):
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_test.py:477:31: E741 ambiguous variable
> name 'l'
> 67: return [l['port'] for l in self.config.sections('listener')]
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_test.py:493:60: E741 ambiguous variable
> name 'l'
> 67: return ["amqp://%s" % self._cfg_2_host_port(l) for l in cfg]
> 67:^
> 67: /foo/qpid-dispatch/tests/system_test.py:504:46: E741 ambiguous variable
> name 'l'
> 67: return [self._cfg_2_host_port(l) for l in
> self.config.sections('listener')]
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1653:28: E741
> ambiguous variable name 'l'
> 67: lines = [l for l in inta_log.read().split("\n")
> 67:^
> 67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1666:17: E741
> ambiguous variable name 'l'
> 67: for l in lines:
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1682:17: E741
> ambiguous variable name 'l'
> 67: for l in lines:
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1794:29: E741
> ambiguous variable name 'l'
> 67: test_links = [l for l in ll if
> 67:
[jira] [Resolved] (DISPATCH-1650) test_01_parallel_link_routes failure in system_tests_link_route
[
https://issues.apache.org/jira/browse/DISPATCH-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved DISPATCH-1650.
--
Fix Version/s: 1.13.0
Resolution: Fixed
> test_01_parallel_link_routes failure in system_tests_link_route
>
>
> Key: DISPATCH-1650
> URL: https://issues.apache.org/jira/browse/DISPATCH-1650
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ken Giusti
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> 14: ==
> 14: ERROR: test_01_parallel_link_routes
> (system_tests_link_routes.LinkRoute3Hop)
> 14: --
> 14: Traceback (most recent call last):
> 14: File "/foo/qpid-dispatch/tests/system_tests_link_routes.py", line 2499,
> in test_01_parallel_link_routes
> 14: if rx.wait(timeout=TIMEOUT):
> 14: File "/foo/qpid-dispatch/tests/system_test.py", line 311, in wait
> 14: raise Exception("Process did not terminate")
> 14: Exception: Process did not terminate
> 14:
> 14: ==
> 14: ERROR: test_01_parallel_link_routes
> (system_tests_link_routes.LinkRoute3Hop)
> 14: --
> 14: Traceback (most recent call last):
> 14: File "/foo/qpid-dispatch/tests/system_test.py", line 713, in tearDown
> 14: Tester.teardown(self)
> 14: File "/foo/qpid-dispatch/tests/system_test.py", line 637, in teardown
> 14: raise RuntimeError("Errors during teardown: \n\n%s" %
> "\n\n".join([str(e) for e in errors]))
> 14: RuntimeError: Errors during teardown:
> 14:
> 14: Process 2743 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-9 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-24.cmd
> 14:
> 14:
> 14:
> 14: Process 2742 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-8 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-23.cmd
> 14:
> 14:
> 14:
> 14: Process 2741 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-7 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-22.cmd
> 14:
> 14:
> 14:
> 14: Process 2740 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-6 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-21.cmd
> 14:
> 14:
> 14:
> 14: Process 2739 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-5 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-20.cmd
> 14:
> 14:
> 14:
> 14: Process 2738 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-4 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-19.cmd
> 14:
> 14:
> 14:
> 14: Process 2737 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-3 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-18.cmd
> 14:
> 14:
> 14:
> 14: Process 2736 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-2 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-17.cmd
> 14:
> 14:
> 14:
> 14: Process 2735 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-1 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-16.cmd
> 14:
> 14:
> 14:
> 14: Process 2734 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-0 -sx -t
> closest/test-client
> 14:
>
[jira] [Commented] (DISPATCH-1650) test_01_parallel_link_routes failure in system_tests_link_route
[
https://issues.apache.org/jira/browse/DISPATCH-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105671#comment-17105671
]
ASF subversion and git services commented on DISPATCH-1650:
---
Commit 807ca7f2001b28fb6c5c48afdf51643841990909 in qpid-dispatch's branch
refs/heads/master from Ken Giusti
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=807ca7f ]
DISPATCH-1650: fix flaky test_01_parallel_link_routes
> test_01_parallel_link_routes failure in system_tests_link_route
>
>
> Key: DISPATCH-1650
> URL: https://issues.apache.org/jira/browse/DISPATCH-1650
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ken Giusti
>Priority: Major
>
> {noformat}
> 14: ==
> 14: ERROR: test_01_parallel_link_routes
> (system_tests_link_routes.LinkRoute3Hop)
> 14: --
> 14: Traceback (most recent call last):
> 14: File "/foo/qpid-dispatch/tests/system_tests_link_routes.py", line 2499,
> in test_01_parallel_link_routes
> 14: if rx.wait(timeout=TIMEOUT):
> 14: File "/foo/qpid-dispatch/tests/system_test.py", line 311, in wait
> 14: raise Exception("Process did not terminate")
> 14: Exception: Process did not terminate
> 14:
> 14: ==
> 14: ERROR: test_01_parallel_link_routes
> (system_tests_link_routes.LinkRoute3Hop)
> 14: --
> 14: Traceback (most recent call last):
> 14: File "/foo/qpid-dispatch/tests/system_test.py", line 713, in tearDown
> 14: Tester.teardown(self)
> 14: File "/foo/qpid-dispatch/tests/system_test.py", line 637, in teardown
> 14: raise RuntimeError("Errors during teardown: \n\n%s" %
> "\n\n".join([str(e) for e in errors]))
> 14: RuntimeError: Errors during teardown:
> 14:
> 14: Process 2743 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-9 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-24.cmd
> 14:
> 14:
> 14:
> 14: Process 2742 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-8 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-23.cmd
> 14:
> 14:
> 14:
> 14: Process 2741 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-7 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-22.cmd
> 14:
> 14:
> 14:
> 14: Process 2740 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-6 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-21.cmd
> 14:
> 14:
> 14:
> 14: Process 2739 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-5 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-20.cmd
> 14:
> 14:
> 14:
> 14: Process 2738 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-4 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-19.cmd
> 14:
> 14:
> 14:
> 14: Process 2737 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-3 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-18.cmd
> 14:
> 14:
> 14:
> 14: Process 2736 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-2 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-17.cmd
> 14:
> 14:
> 14:
> 14: Process 2735 error: still running
> 14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-1 -sx -t
> closest/test-client
> 14:
> /foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-16.cmd
> 14:
> 14:
> 14:
[jira] [Created] (DISPATCH-1654) tcp protocol bridging (ingress and egress)
Gordon Sim created DISPATCH-1654: Summary: tcp protocol bridging (ingress and egress) Key: DISPATCH-1654 URL: https://issues.apache.org/jira/browse/DISPATCH-1654 Project: Qpid Dispatch Issue Type: Improvement Reporter: Gordon Sim -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1655) http2 protocol bridging (ingress and egress)
Gordon Sim created DISPATCH-1655: Summary: http2 protocol bridging (ingress and egress) Key: DISPATCH-1655 URL: https://issues.apache.org/jira/browse/DISPATCH-1655 Project: Qpid Dispatch Issue Type: Improvement Reporter: Gordon Sim -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1653) http protocol bridging (ingress and egress)
Gordon Sim created DISPATCH-1653: Summary: http protocol bridging (ingress and egress) Key: DISPATCH-1653 URL: https://issues.apache.org/jira/browse/DISPATCH-1653 Project: Qpid Dispatch Issue Type: Improvement Reporter: Gordon Sim -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1652) Define internal interfaces for protocol plugins
Gordon Sim created DISPATCH-1652: Summary: Define internal interfaces for protocol plugins Key: DISPATCH-1652 URL: https://issues.apache.org/jira/browse/DISPATCH-1652 Project: Qpid Dispatch Issue Type: Improvement Reporter: Gordon Sim -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1651) Update management schema to include protocol bridges
Gordon Sim created DISPATCH-1651: Summary: Update management schema to include protocol bridges Key: DISPATCH-1651 URL: https://issues.apache.org/jira/browse/DISPATCH-1651 Project: Qpid Dispatch Issue Type: Improvement Reporter: Gordon Sim -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDJMS-504) Connections hangs when trying to connect to a RabbitMQ persistent queue
[
https://issues.apache.org/jira/browse/QPIDJMS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy A. Bish closed QPIDJMS-504.
---
Resolution: Not A Bug
Client is following specification for link attach, remote either not sending
response is the apparent cause of the hang. Workaround is to use the request
timeout. More information on what is going on at the wire level is available
via the AMQP frame tracing options.
> Connections hangs when trying to connect to a RabbitMQ persistent queue
> ---
>
> Key: QPIDJMS-504
> URL: https://issues.apache.org/jira/browse/QPIDJMS-504
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
>Affects Versions: 0.51.0
>Reporter: Stephan Siano
>Priority: Major
>
> When I try to connect to a persistent queue on a RabbitMQ broker with
> activated AMQP 1.0 plugin, the connection hangs for an infinite time (or at
> least for a very long time).
> There is no error, the connection just hangs. The tack trace in this
> situation for a producer is:
> {noformat}
> BalancedProviderFuture(Object).wait() line: 502
> BalancedProviderFuture.sync() line: 136
> JmsConnection.createResource(JmsResource, ProviderSynchronization) line: 693
> JmsMessageProducer.(JmsProducerId, JmsSession, JmsDestination) line: 73
> JmsQueueSession(JmsSession).createProducer(Destination) line: 664
> JmsQueueSession.createProducer(Destination) line: 97
> {noformat}
> The stack trace for a consumer is:
> {noformat}
> BalancedProviderFuture(Object).wait() line: 502
> BalancedProviderFuture.sync() line: 136
> JmsConnection.createResource(JmsResource, ProviderSynchronization) line: 693
> JmsMessageConsumer.(JmsConsumerId, JmsSession, JmsDestination, String,
> String, boolean) line: 125
> JmsMessageConsumer.(JmsConsumerId, JmsSession, JmsDestination, String,
> boolean) line: 82
> JmsQueueSession(JmsSession).createConsumer(Destination, String, boolean)
> line: 478
> JmsQueueSession.createConsumer(Destination, String, boolean) line: 70
> JmsQueueSession(JmsSession).createConsumer(Destination, String) line: 466
> JmsQueueSession.createConsumer(Destination, String) line: 59
> JmsQueueSession(JmsSession).createConsumer(Destination) line: 458
> JmsQueueSession.createConsumer(Destination) line: 48
> {noformat}
> I am aware that the AMQP 1.0 plugin in RabbitMQ is not very mature, but I
> don't think that the client threads should be blocked forever even when
> trying to communicate with misbehaving servers.
> The issue will not happen with transient queues on RabbitMQ (here everything
> works as expected).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-504) Connections hangs when trying to connect to a RabbitMQ persistent queue
[
https://issues.apache.org/jira/browse/QPIDJMS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105598#comment-17105598
]
Stephan Siano commented on QPIDJMS-504:
---
Oh, thanks. This parameter helps a lot. Nevertheless, it would be good if there
was a way to find out why the persistent queues in RabbitMQ don't work with
qpid-jms.
> Connections hangs when trying to connect to a RabbitMQ persistent queue
> ---
>
> Key: QPIDJMS-504
> URL: https://issues.apache.org/jira/browse/QPIDJMS-504
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
>Affects Versions: 0.51.0
>Reporter: Stephan Siano
>Priority: Major
>
> When I try to connect to a persistent queue on a RabbitMQ broker with
> activated AMQP 1.0 plugin, the connection hangs for an infinite time (or at
> least for a very long time).
> There is no error, the connection just hangs. The tack trace in this
> situation for a producer is:
> {noformat}
> BalancedProviderFuture(Object).wait() line: 502
> BalancedProviderFuture.sync() line: 136
> JmsConnection.createResource(JmsResource, ProviderSynchronization) line: 693
> JmsMessageProducer.(JmsProducerId, JmsSession, JmsDestination) line: 73
> JmsQueueSession(JmsSession).createProducer(Destination) line: 664
> JmsQueueSession.createProducer(Destination) line: 97
> {noformat}
> The stack trace for a consumer is:
> {noformat}
> BalancedProviderFuture(Object).wait() line: 502
> BalancedProviderFuture.sync() line: 136
> JmsConnection.createResource(JmsResource, ProviderSynchronization) line: 693
> JmsMessageConsumer.(JmsConsumerId, JmsSession, JmsDestination, String,
> String, boolean) line: 125
> JmsMessageConsumer.(JmsConsumerId, JmsSession, JmsDestination, String,
> boolean) line: 82
> JmsQueueSession(JmsSession).createConsumer(Destination, String, boolean)
> line: 478
> JmsQueueSession.createConsumer(Destination, String, boolean) line: 70
> JmsQueueSession(JmsSession).createConsumer(Destination, String) line: 466
> JmsQueueSession.createConsumer(Destination, String) line: 59
> JmsQueueSession(JmsSession).createConsumer(Destination) line: 458
> JmsQueueSession.createConsumer(Destination) line: 48
> {noformat}
> I am aware that the AMQP 1.0 plugin in RabbitMQ is not very mature, but I
> don't think that the client threads should be blocked forever even when
> trying to communicate with misbehaving servers.
> The issue will not happen with transient queues on RabbitMQ (here everything
> works as expected).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (DISPATCH-138) Python3 is selected default when compiling with both installed
[ https://issues.apache.org/jira/browse/DISPATCH-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105558#comment-17105558 ] Jiri Daněk edited comment on DISPATCH-138 at 5/12/20, 4:05 PM: --- My experience is that CMake likes to choose Python2, when both 2 and 3 are available (PROTON-2217), which is the opposite finding than on this Jira. I was thinking DISPATCH-187 could be outdated, given the Python 3 work on the router, but I am not sure. was (Author: jdanek): My experience is that CMake likes to chose Python2, when both 2 and 3 are available (PROTON-2217), which is the opposite finding than on this Jira. I was thinking DISPATCH-187 could be outdated, given the Python 3 work on the router, but I am not sure. > Python3 is selected default when compiling with both installed > -- > > Key: DISPATCH-138 > URL: https://issues.apache.org/jira/browse/DISPATCH-138 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.4 > Environment: Gentoo Linux x86_64 > Python 2.7.9 (default) > Python 3.3.5 > cmake version 2.8.12.2 >Reporter: Zdenek Kraus >Priority: Minor > > Steps to reproduce: > 1. cmake .. > 2. set proton_include and proton_library paths > 3. cmake .. > 4. make > Actual Results: > [ 2%] Generating schema_enum.h, schema_enum.c > Scanning dependencies of target qpid-dispatch > [ 4%] Building C object src/CMakeFiles/qpid-dispatch.dir/alloc.c.o > [ 7%] Building C object src/CMakeFiles/qpid-dispatch.dir/amqp.c.o > [ 9%] Building C object src/CMakeFiles/qpid-dispatch.dir/bitmask.c.o > [ 12%] Building C object src/CMakeFiles/qpid-dispatch.dir/buffer.c.o > [ 14%] Building C object src/CMakeFiles/qpid-dispatch.dir/error.c.o > /home/aranel/src/dispatch/src/error.c: In function 'py_set_item': > /home/aranel/src/dispatch/src/error.c:100:5: error: implicit declaration of > function 'PyString_FromString' [-Werror=implicit-function-declaration] > PyObject *py_name = PyString_FromString(name); > ^ > /home/aranel/src/dispatch/src/error.c:100:25: error: initialization makes > pointer from integer without a cast [-Werror] > PyObject *py_name = PyString_FromString(name); > ^ > /home/aranel/src/dispatch/src/error.c: In function 'log_trace_py': > /home/aranel/src/dispatch/src/error.c:130:9: error: implicit declaration of > function 'PyString_AsString' [-Werror=implicit-function-declaration] > const char* trace = PyString_AsString(result); > ^ > /home/aranel/src/dispatch/src/error.c:130:29: error: initialization makes > pointer from integer without a cast [-Werror] > const char* trace = PyString_AsString(result); > ^ > /home/aranel/src/dispatch/src/error.c: In function 'qd_error_py_impl': > /home/aranel/src/dispatch/src/error.c:153:80: error: pointer/integer type > mismatch in conditional expression [-Werror] > const char *type_name = py_type_name ? > PyString_AsString(py_type_name) : NULL; > > ^ > /home/aranel/src/dispatch/src/error.c:156:80: error: pointer/integer type > mismatch in conditional expression [-Werror] > const char *value_str = py_value_str ? > PyString_AsString(py_value_str) : NULL; > > ^ > cc1: all warnings being treated as errors > src/CMakeFiles/qpid-dispatch.dir/build.make:167: recipe for target > 'src/CMakeFiles/qpid-dispatch.dir/error.c.o' failed > make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/error.c.o] Error 1 > CMakeFiles/Makefile2:946: recipe for target > 'src/CMakeFiles/qpid-dispatch.dir/all' failed > make[1]: *** [src/CMakeFiles/qpid-dispatch.dir/all] Error 2 > Makefile:126: recipe for target 'all' failed > make: *** [all] Error 2 > Expected results: > dispatch will compile using python2 > Notes: > after removing python3 from system, dispatch will compile without any > problems. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-138) Python3 is selected default when compiling with both installed
[ https://issues.apache.org/jira/browse/DISPATCH-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105558#comment-17105558 ] Jiri Daněk commented on DISPATCH-138: - My experience is that CMake likes to chose Python2, when both 2 and 3 are available (PROTON-2217), which is the opposite finding than on this Jira. I was thinking DISPATCH-187 could be outdated, given the Python 3 work on the router, but I am not sure. > Python3 is selected default when compiling with both installed > -- > > Key: DISPATCH-138 > URL: https://issues.apache.org/jira/browse/DISPATCH-138 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.4 > Environment: Gentoo Linux x86_64 > Python 2.7.9 (default) > Python 3.3.5 > cmake version 2.8.12.2 >Reporter: Zdenek Kraus >Priority: Minor > > Steps to reproduce: > 1. cmake .. > 2. set proton_include and proton_library paths > 3. cmake .. > 4. make > Actual Results: > [ 2%] Generating schema_enum.h, schema_enum.c > Scanning dependencies of target qpid-dispatch > [ 4%] Building C object src/CMakeFiles/qpid-dispatch.dir/alloc.c.o > [ 7%] Building C object src/CMakeFiles/qpid-dispatch.dir/amqp.c.o > [ 9%] Building C object src/CMakeFiles/qpid-dispatch.dir/bitmask.c.o > [ 12%] Building C object src/CMakeFiles/qpid-dispatch.dir/buffer.c.o > [ 14%] Building C object src/CMakeFiles/qpid-dispatch.dir/error.c.o > /home/aranel/src/dispatch/src/error.c: In function 'py_set_item': > /home/aranel/src/dispatch/src/error.c:100:5: error: implicit declaration of > function 'PyString_FromString' [-Werror=implicit-function-declaration] > PyObject *py_name = PyString_FromString(name); > ^ > /home/aranel/src/dispatch/src/error.c:100:25: error: initialization makes > pointer from integer without a cast [-Werror] > PyObject *py_name = PyString_FromString(name); > ^ > /home/aranel/src/dispatch/src/error.c: In function 'log_trace_py': > /home/aranel/src/dispatch/src/error.c:130:9: error: implicit declaration of > function 'PyString_AsString' [-Werror=implicit-function-declaration] > const char* trace = PyString_AsString(result); > ^ > /home/aranel/src/dispatch/src/error.c:130:29: error: initialization makes > pointer from integer without a cast [-Werror] > const char* trace = PyString_AsString(result); > ^ > /home/aranel/src/dispatch/src/error.c: In function 'qd_error_py_impl': > /home/aranel/src/dispatch/src/error.c:153:80: error: pointer/integer type > mismatch in conditional expression [-Werror] > const char *type_name = py_type_name ? > PyString_AsString(py_type_name) : NULL; > > ^ > /home/aranel/src/dispatch/src/error.c:156:80: error: pointer/integer type > mismatch in conditional expression [-Werror] > const char *value_str = py_value_str ? > PyString_AsString(py_value_str) : NULL; > > ^ > cc1: all warnings being treated as errors > src/CMakeFiles/qpid-dispatch.dir/build.make:167: recipe for target > 'src/CMakeFiles/qpid-dispatch.dir/error.c.o' failed > make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/error.c.o] Error 1 > CMakeFiles/Makefile2:946: recipe for target > 'src/CMakeFiles/qpid-dispatch.dir/all' failed > make[1]: *** [src/CMakeFiles/qpid-dispatch.dir/all] Error 2 > Makefile:126: recipe for target 'all' failed > make: *** [all] Error 2 > Expected results: > dispatch will compile using python2 > Notes: > after removing python3 from system, dispatch will compile without any > problems. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-138) Python3 is selected default when compiling with both installed
[ https://issues.apache.org/jira/browse/DISPATCH-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105556#comment-17105556 ] Robbie Gemmell commented on DISPATCH-138: - Plus maybe these days its more feature-not-bug? ;) > Python3 is selected default when compiling with both installed > -- > > Key: DISPATCH-138 > URL: https://issues.apache.org/jira/browse/DISPATCH-138 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.4 > Environment: Gentoo Linux x86_64 > Python 2.7.9 (default) > Python 3.3.5 > cmake version 2.8.12.2 >Reporter: Zdenek Kraus >Priority: Minor > > Steps to reproduce: > 1. cmake .. > 2. set proton_include and proton_library paths > 3. cmake .. > 4. make > Actual Results: > [ 2%] Generating schema_enum.h, schema_enum.c > Scanning dependencies of target qpid-dispatch > [ 4%] Building C object src/CMakeFiles/qpid-dispatch.dir/alloc.c.o > [ 7%] Building C object src/CMakeFiles/qpid-dispatch.dir/amqp.c.o > [ 9%] Building C object src/CMakeFiles/qpid-dispatch.dir/bitmask.c.o > [ 12%] Building C object src/CMakeFiles/qpid-dispatch.dir/buffer.c.o > [ 14%] Building C object src/CMakeFiles/qpid-dispatch.dir/error.c.o > /home/aranel/src/dispatch/src/error.c: In function 'py_set_item': > /home/aranel/src/dispatch/src/error.c:100:5: error: implicit declaration of > function 'PyString_FromString' [-Werror=implicit-function-declaration] > PyObject *py_name = PyString_FromString(name); > ^ > /home/aranel/src/dispatch/src/error.c:100:25: error: initialization makes > pointer from integer without a cast [-Werror] > PyObject *py_name = PyString_FromString(name); > ^ > /home/aranel/src/dispatch/src/error.c: In function 'log_trace_py': > /home/aranel/src/dispatch/src/error.c:130:9: error: implicit declaration of > function 'PyString_AsString' [-Werror=implicit-function-declaration] > const char* trace = PyString_AsString(result); > ^ > /home/aranel/src/dispatch/src/error.c:130:29: error: initialization makes > pointer from integer without a cast [-Werror] > const char* trace = PyString_AsString(result); > ^ > /home/aranel/src/dispatch/src/error.c: In function 'qd_error_py_impl': > /home/aranel/src/dispatch/src/error.c:153:80: error: pointer/integer type > mismatch in conditional expression [-Werror] > const char *type_name = py_type_name ? > PyString_AsString(py_type_name) : NULL; > > ^ > /home/aranel/src/dispatch/src/error.c:156:80: error: pointer/integer type > mismatch in conditional expression [-Werror] > const char *value_str = py_value_str ? > PyString_AsString(py_value_str) : NULL; > > ^ > cc1: all warnings being treated as errors > src/CMakeFiles/qpid-dispatch.dir/build.make:167: recipe for target > 'src/CMakeFiles/qpid-dispatch.dir/error.c.o' failed > make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/error.c.o] Error 1 > CMakeFiles/Makefile2:946: recipe for target > 'src/CMakeFiles/qpid-dispatch.dir/all' failed > make[1]: *** [src/CMakeFiles/qpid-dispatch.dir/all] Error 2 > Makefile:126: recipe for target 'all' failed > make: *** [all] Error 2 > Expected results: > dispatch will compile using python2 > Notes: > after removing python3 from system, dispatch will compile without any > problems. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-138) Python3 is selected default when compiling with both installed
[ https://issues.apache.org/jira/browse/DISPATCH-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated DISPATCH-138: Fix Version/s: (was: Backlog) > Python3 is selected default when compiling with both installed > -- > > Key: DISPATCH-138 > URL: https://issues.apache.org/jira/browse/DISPATCH-138 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.4 > Environment: Gentoo Linux x86_64 > Python 2.7.9 (default) > Python 3.3.5 > cmake version 2.8.12.2 >Reporter: Zdenek Kraus >Priority: Minor > > Steps to reproduce: > 1. cmake .. > 2. set proton_include and proton_library paths > 3. cmake .. > 4. make > Actual Results: > [ 2%] Generating schema_enum.h, schema_enum.c > Scanning dependencies of target qpid-dispatch > [ 4%] Building C object src/CMakeFiles/qpid-dispatch.dir/alloc.c.o > [ 7%] Building C object src/CMakeFiles/qpid-dispatch.dir/amqp.c.o > [ 9%] Building C object src/CMakeFiles/qpid-dispatch.dir/bitmask.c.o > [ 12%] Building C object src/CMakeFiles/qpid-dispatch.dir/buffer.c.o > [ 14%] Building C object src/CMakeFiles/qpid-dispatch.dir/error.c.o > /home/aranel/src/dispatch/src/error.c: In function 'py_set_item': > /home/aranel/src/dispatch/src/error.c:100:5: error: implicit declaration of > function 'PyString_FromString' [-Werror=implicit-function-declaration] > PyObject *py_name = PyString_FromString(name); > ^ > /home/aranel/src/dispatch/src/error.c:100:25: error: initialization makes > pointer from integer without a cast [-Werror] > PyObject *py_name = PyString_FromString(name); > ^ > /home/aranel/src/dispatch/src/error.c: In function 'log_trace_py': > /home/aranel/src/dispatch/src/error.c:130:9: error: implicit declaration of > function 'PyString_AsString' [-Werror=implicit-function-declaration] > const char* trace = PyString_AsString(result); > ^ > /home/aranel/src/dispatch/src/error.c:130:29: error: initialization makes > pointer from integer without a cast [-Werror] > const char* trace = PyString_AsString(result); > ^ > /home/aranel/src/dispatch/src/error.c: In function 'qd_error_py_impl': > /home/aranel/src/dispatch/src/error.c:153:80: error: pointer/integer type > mismatch in conditional expression [-Werror] > const char *type_name = py_type_name ? > PyString_AsString(py_type_name) : NULL; > > ^ > /home/aranel/src/dispatch/src/error.c:156:80: error: pointer/integer type > mismatch in conditional expression [-Werror] > const char *value_str = py_value_str ? > PyString_AsString(py_value_str) : NULL; > > ^ > cc1: all warnings being treated as errors > src/CMakeFiles/qpid-dispatch.dir/build.make:167: recipe for target > 'src/CMakeFiles/qpid-dispatch.dir/error.c.o' failed > make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/error.c.o] Error 1 > CMakeFiles/Makefile2:946: recipe for target > 'src/CMakeFiles/qpid-dispatch.dir/all' failed > make[1]: *** [src/CMakeFiles/qpid-dispatch.dir/all] Error 2 > Makefile:126: recipe for target 'all' failed > make: *** [all] Error 2 > Expected results: > dispatch will compile using python2 > Notes: > after removing python3 from system, dispatch will compile without any > problems. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-8439) Stack overflow during logging
Thorsten Meinl created QPID-8439:
Summary: Stack overflow during logging
Key: QPID-8439
URL: https://issues.apache.org/jira/browse/QPID-8439
Project: Qpid
Issue Type: Bug
Components: Broker-J
Affects Versions: qpid-java-broker-7.0.6
Reporter: Thorsten Meinl
Attachments: catalina.out
We are occasionally seeing stack overflow during logging in QPid. This
completely kills the broker because some data structure are not initialized
correctly any more afterwards. The problems lies in the combination of SLf4j
use in QPid and the logging in the BDB implementation. BDB is configured using
the Slf4jLoggingHandler in
{{org.apache.qpid.server.store.berkeleydb.StandardEnvironmentFacade.StandardEnvironmentFacade(StandardEnvironmentConfiguration)}}
which eventually ends up at the JDK logger (at least in our setup). However,
BDB has a {{com.sleepycat.je.utilint.ConfiguredRedirectHandler}} which is
appended to the the JDK logger and logs records from it to the configured
Slf4jLoggingHandler. Which in turn forwards them to the JDK logger and there it
starts again. The error is so obvious which makes me wonder why nobody else has
reported it before. Is there some kind of configuration that we have set wrong?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-504) Connections hangs when trying to connect to a RabbitMQ persistent queue
[
https://issues.apache.org/jira/browse/QPIDJMS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105467#comment-17105467
]
Timothy A. Bish commented on QPIDJMS-504:
-
The client is stuck waiting for the remote to respond to an attach request.
For remote peers that misbehave you can configure the client request timeout to
some value that you are willing to accept as the remote not being response and
it will fail the create process. See the client documentation for [URI
configuration
option|http://qpid.apache.org/releases/qpid-jms-0.51.0/docs/index.html#jms-configuration-options]
'jms.requestTimeout'
> Connections hangs when trying to connect to a RabbitMQ persistent queue
> ---
>
> Key: QPIDJMS-504
> URL: https://issues.apache.org/jira/browse/QPIDJMS-504
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
>Affects Versions: 0.51.0
>Reporter: Stephan Siano
>Priority: Major
>
> When I try to connect to a persistent queue on a RabbitMQ broker with
> activated AMQP 1.0 plugin, the connection hangs for an infinite time (or at
> least for a very long time).
> There is no error, the connection just hangs. The tack trace in this
> situation for a producer is:
> {noformat}
> BalancedProviderFuture(Object).wait() line: 502
> BalancedProviderFuture.sync() line: 136
> JmsConnection.createResource(JmsResource, ProviderSynchronization) line: 693
> JmsMessageProducer.(JmsProducerId, JmsSession, JmsDestination) line: 73
> JmsQueueSession(JmsSession).createProducer(Destination) line: 664
> JmsQueueSession.createProducer(Destination) line: 97
> {noformat}
> The stack trace for a consumer is:
> {noformat}
> BalancedProviderFuture(Object).wait() line: 502
> BalancedProviderFuture.sync() line: 136
> JmsConnection.createResource(JmsResource, ProviderSynchronization) line: 693
> JmsMessageConsumer.(JmsConsumerId, JmsSession, JmsDestination, String,
> String, boolean) line: 125
> JmsMessageConsumer.(JmsConsumerId, JmsSession, JmsDestination, String,
> boolean) line: 82
> JmsQueueSession(JmsSession).createConsumer(Destination, String, boolean)
> line: 478
> JmsQueueSession.createConsumer(Destination, String, boolean) line: 70
> JmsQueueSession(JmsSession).createConsumer(Destination, String) line: 466
> JmsQueueSession.createConsumer(Destination, String) line: 59
> JmsQueueSession(JmsSession).createConsumer(Destination) line: 458
> JmsQueueSession.createConsumer(Destination) line: 48
> {noformat}
> I am aware that the AMQP 1.0 plugin in RabbitMQ is not very mature, but I
> don't think that the client threads should be blocked forever even when
> trying to communicate with misbehaving servers.
> The issue will not happen with transient queues on RabbitMQ (here everything
> works as expected).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1650) test_01_parallel_link_routes failure in system_tests_link_route
Ganesh Murthy created DISPATCH-1650:
---
Summary: test_01_parallel_link_routes failure in
system_tests_link_route
Key: DISPATCH-1650
URL: https://issues.apache.org/jira/browse/DISPATCH-1650
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
Assignee: Ken Giusti
{noformat}
14: ==
14: ERROR: test_01_parallel_link_routes (system_tests_link_routes.LinkRoute3Hop)
14: --
14: Traceback (most recent call last):
14: File "/foo/qpid-dispatch/tests/system_tests_link_routes.py", line 2499,
in test_01_parallel_link_routes
14: if rx.wait(timeout=TIMEOUT):
14: File "/foo/qpid-dispatch/tests/system_test.py", line 311, in wait
14: raise Exception("Process did not terminate")
14: Exception: Process did not terminate
14:
14: ==
14: ERROR: test_01_parallel_link_routes (system_tests_link_routes.LinkRoute3Hop)
14: --
14: Traceback (most recent call last):
14: File "/foo/qpid-dispatch/tests/system_test.py", line 713, in tearDown
14: Tester.teardown(self)
14: File "/foo/qpid-dispatch/tests/system_test.py", line 637, in teardown
14: raise RuntimeError("Errors during teardown: \n\n%s" %
"\n\n".join([str(e) for e in errors]))
14: RuntimeError: Errors during teardown:
14:
14: Process 2743 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-9 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-24.cmd
14:
14:
14:
14: Process 2742 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-8 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-23.cmd
14:
14:
14:
14: Process 2741 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-7 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-22.cmd
14:
14:
14:
14: Process 2740 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-6 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-21.cmd
14:
14:
14:
14: Process 2739 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-5 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-20.cmd
14:
14:
14:
14: Process 2738 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-4 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-19.cmd
14:
14:
14:
14: Process 2737 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-3 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-18.cmd
14:
14:
14:
14: Process 2736 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-2 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-17.cmd
14:
14:
14:
14: Process 2735 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-1 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-16.cmd
14:
14:
14:
14: Process 2734 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-0 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-15.cmd
14:
14:
14:
14: Process 2733 error: still running
14: test-receiver -a amqp://0.0.0.0:25779 -c 250 -s closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-receiver-14.cmd
14:
14:
14:
14: --
14: Ran 36 tests in 113.953s {noformat}
--
This message was sent by Atlassian
[jira] [Created] (DISPATCH-1649) Tox failure, Python Checker error in config.py
Ganesh Murthy created DISPATCH-1649:
---
Summary: Tox failure, Python Checker error in config.py
Key: DISPATCH-1649
URL: https://issues.apache.org/jira/browse/DISPATCH-1649
Project: Qpid Dispatch
Issue Type: Bug
Components: Management Agent
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
{noformat}
st 67
Start 67: python-checker
67: Test command: /usr/local/bin/tox
67: Test timeout computed to be: 600
67: py27 create: /foo/qpid-dispatch/build/tests/.tox/py27
67: py27 installdeps: hacking>=1.1.0
67: WARNING: Discarding $PYTHONPATH from environment, to override specify
PYTHONPATH in 'passenv' in your configuration.
67: py27 installed: DEPRECATION: Python 2.7 reached the end of its life on
January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer
maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More
details about Python 2 support in pip, can be found at
https://pip.pypa.io/en/latest/development/release-process/#python-2-support,configparser==4.0.2,contextlib2==0.6.0.post1,enum34==1.1.10,flake8==3.8.1,functools32==3.2.3.post2,hacking==2.0.0,importlib-metadata==1.6.0,mccabe==0.6.1,pathlib2==2.3.5,pycodestyle==2.6.0,pyflakes==2.2.0,qpid-dispatch===1.13.0-SNAPSHOT,scandir==1.10.0,six==1.14.0,typing==3.7.4.1,zipp==1.2.0
67: py27 run-test-pre: PYTHONHASHSEED='1454137866'
67: py27 run-test: commands[0] | flake8 --count --show-source
/foo/qpid-dispatch/python /foo/qpid-dispatch/console /foo/qpid-dispatch/docs
/foo/qpid-dispatch/tests /foo/qpid-dispatch/tools
/foo/qpid-dispatch/tools/qdstat /foo/qpid-dispatch/tools/qdmanage
--ignore=E111,E114,E121,E122,E123,E124,E126,E127,E128,E129,E131,E201,E202,E203,E211,E221,E222,E225,E226,E228,E231,E241,E251,E261,E266,E265,E271,E272,E301,E302,E303,E305,E306,E401,E402,E501,E502,E701,E702,E703,E704,E711,E712,E713,E714,E731,E722,F401,F403,F405,F811,F841,H101,H102,H104,H201,H202,H234,H237,H238,H301,H306,H401,H403,H404,H405,W291,W292,W293,W391,W503,W504
67:
/foo/qpid-dispatch/python/qpid_dispatch_internal/management/config.py:107:49:
E741 ambiguous variable name 'l'
67: js_text = "[%s]"%("\n".join([sub(l) for l in lines]))
67: ^
67:
/foo/qpid-dispatch/python/qpid_dispatch_internal/management/config.py:122:47:
E741 ambiguous variable name 'l'
67: js_text = "%s"%("\n".join([sub(l) for l in lines]))
67: ^
67:
/foo/qpid-dispatch/python/qpid_dispatch_internal/management/config.py:182:9:
E741 ambiguous variable name 'l'
67: for l in config.by_type('log'):
67: ^
67: /foo/qpid-dispatch/tests/system_test.py:378:26: E741 ambiguous variable
name 'l'
67: def sub_elem(l, level):
67: ^
67: /foo/qpid-dispatch/tests/system_test.py:407:30: E741 ambiguous variable
name 'l'
67: default_log = [l for l in config if (l[0] == 'log' and
l[1]['module'] == 'DEFAULT')]
67: ^
67: /foo/qpid-dispatch/tests/system_test.py:466:13: E741 ambiguous variable
name 'l'
67: for l in self.config.sections('listener'):
67: ^
67: /foo/qpid-dispatch/tests/system_test.py:477:31: E741 ambiguous variable
name 'l'
67: return [l['port'] for l in self.config.sections('listener')]
67: ^
67: /foo/qpid-dispatch/tests/system_test.py:493:60: E741 ambiguous variable
name 'l'
67: return ["amqp://%s" % self._cfg_2_host_port(l) for l in cfg]
67:^
67: /foo/qpid-dispatch/tests/system_test.py:504:46: E741 ambiguous variable
name 'l'
67: return [self._cfg_2_host_port(l) for l in
self.config.sections('listener')]
67: ^
67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1653:28: E741
ambiguous variable name 'l'
67: lines = [l for l in inta_log.read().split("\n")
67:^
67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1666:17: E741
ambiguous variable name 'l'
67: for l in lines:
67: ^
67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1682:17: E741
ambiguous variable name 'l'
67: for l in lines:
67: ^
67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1794:29: E741
ambiguous variable name 'l'
67: test_links = [l for l in ll if
67: ^
67: /foo/qpid-dispatch/tests/system_tests_management.py:204:13: E741 ambiguous
variable name 'l'
67: for l in response.get_dicts():
67: ^
67: /foo/qpid-dispatch/tests/system_tests_management.py:363:25: E741 ambiguous
variable name 'l'
67: mylink = [l for l in response.get_dicts()
67: ^
67:
[jira] [Created] (PROTON-2217) Python detection logic prefers python2 over python3 when both are installed
Jiri Daněk created PROTON-2217:
--
Summary: Python detection logic prefers python2 over python3 when
both are installed
Key: PROTON-2217
URL: https://issues.apache.org/jira/browse/PROTON-2217
Project: Qpid Proton
Issue Type: Bug
Components: build, proton-c, python-binding
Affects Versions: proton-c-0.31.0
Reporter: Jiri Daněk
I have the same experience that was reported elsewhere:
bq. For me, the find_package(PythonInterp) call was always finding the older
interpreter (2.7) even though everything pointed to the newer one (3.6). (from
https://reviews.llvm.org/D64881)
This behavior is unfortunate on Ubuntu 20.04 Focal, where both python2 and
python3 are available, but pip for python2 is not packaged. Therefore it makes
sense to build proton with python3; which would make sense anyways, since it is
now the year 2020.
Besides removing python2 as discussed on the linked page, there is currently
nicer way to force python3 that worked for me, by setting
{{-DPYTHON_EXECUTABLE=/usr/bin/python3}} CMake variable.
Related dispatch issue, DISPATCH-187
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (DISPATCH-138) Python3 is selected default when compiling with both installed
[ https://issues.apache.org/jira/browse/DISPATCH-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk closed DISPATCH-138. --- Resolution: Duplicate Superceded by DISPATCH-187, there is more activity. > Python3 is selected default when compiling with both installed > -- > > Key: DISPATCH-138 > URL: https://issues.apache.org/jira/browse/DISPATCH-138 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.4 > Environment: Gentoo Linux x86_64 > Python 2.7.9 (default) > Python 3.3.5 > cmake version 2.8.12.2 >Reporter: Zdenek Kraus >Priority: Minor > Fix For: Backlog > > > Steps to reproduce: > 1. cmake .. > 2. set proton_include and proton_library paths > 3. cmake .. > 4. make > Actual Results: > [ 2%] Generating schema_enum.h, schema_enum.c > Scanning dependencies of target qpid-dispatch > [ 4%] Building C object src/CMakeFiles/qpid-dispatch.dir/alloc.c.o > [ 7%] Building C object src/CMakeFiles/qpid-dispatch.dir/amqp.c.o > [ 9%] Building C object src/CMakeFiles/qpid-dispatch.dir/bitmask.c.o > [ 12%] Building C object src/CMakeFiles/qpid-dispatch.dir/buffer.c.o > [ 14%] Building C object src/CMakeFiles/qpid-dispatch.dir/error.c.o > /home/aranel/src/dispatch/src/error.c: In function 'py_set_item': > /home/aranel/src/dispatch/src/error.c:100:5: error: implicit declaration of > function 'PyString_FromString' [-Werror=implicit-function-declaration] > PyObject *py_name = PyString_FromString(name); > ^ > /home/aranel/src/dispatch/src/error.c:100:25: error: initialization makes > pointer from integer without a cast [-Werror] > PyObject *py_name = PyString_FromString(name); > ^ > /home/aranel/src/dispatch/src/error.c: In function 'log_trace_py': > /home/aranel/src/dispatch/src/error.c:130:9: error: implicit declaration of > function 'PyString_AsString' [-Werror=implicit-function-declaration] > const char* trace = PyString_AsString(result); > ^ > /home/aranel/src/dispatch/src/error.c:130:29: error: initialization makes > pointer from integer without a cast [-Werror] > const char* trace = PyString_AsString(result); > ^ > /home/aranel/src/dispatch/src/error.c: In function 'qd_error_py_impl': > /home/aranel/src/dispatch/src/error.c:153:80: error: pointer/integer type > mismatch in conditional expression [-Werror] > const char *type_name = py_type_name ? > PyString_AsString(py_type_name) : NULL; > > ^ > /home/aranel/src/dispatch/src/error.c:156:80: error: pointer/integer type > mismatch in conditional expression [-Werror] > const char *value_str = py_value_str ? > PyString_AsString(py_value_str) : NULL; > > ^ > cc1: all warnings being treated as errors > src/CMakeFiles/qpid-dispatch.dir/build.make:167: recipe for target > 'src/CMakeFiles/qpid-dispatch.dir/error.c.o' failed > make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/error.c.o] Error 1 > CMakeFiles/Makefile2:946: recipe for target > 'src/CMakeFiles/qpid-dispatch.dir/all' failed > make[1]: *** [src/CMakeFiles/qpid-dispatch.dir/all] Error 2 > Makefile:126: recipe for target 'all' failed > make: *** [all] Error 2 > Expected results: > dispatch will compile using python2 > Notes: > after removing python3 from system, dispatch will compile without any > problems. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-187) CMake must choose the Python2 libraries when Python3 is available
[ https://issues.apache.org/jira/browse/DISPATCH-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk updated DISPATCH-187: Affects Version/s: 0.4 > CMake must choose the Python2 libraries when Python3 is available > - > > Key: DISPATCH-187 > URL: https://issues.apache.org/jira/browse/DISPATCH-187 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.4, 0.5 >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Major > Fix For: Backlog > > > If the python3 development packages are present, the Dispatch CMake file > chooses version 3 which fails to build. Dispatch uses the python2 extension > API. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1641) If an oversize transfer is rejected then provide details in rejected outcome error field
[ https://issues.apache.org/jira/browse/DISPATCH-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles E. Rolke resolved DISPATCH-1641. Fix Version/s: 1.13.0 Resolution: Fixed Fixed at Commit 54597db > If an oversize transfer is rejected then provide details in rejected outcome > error field > > > Key: DISPATCH-1641 > URL: https://issues.apache.org/jira/browse/DISPATCH-1641 > Project: Qpid Dispatch > Issue Type: Bug > Components: Policy Engine, Router Node >Affects Versions: 1.12.0 >Reporter: Charles E. Rolke >Assignee: Charles E. Rolke >Priority: Major > Fix For: 1.13.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1645) Max message size is demoted to INT from UINT64
[ https://issues.apache.org/jira/browse/DISPATCH-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles E. Rolke resolved DISPATCH-1645. Resolution: Fixed Fixed at Commit cd09cc0c > Max message size is demoted to INT from UINT64 > -- > > Key: DISPATCH-1645 > URL: https://issues.apache.org/jira/browse/DISPATCH-1645 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 1.12.0 >Reporter: Charles E. Rolke >Assignee: Charles E. Rolke >Priority: Major > Fix For: 1.13.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1645) Max message size is demoted to INT from UINT64
[ https://issues.apache.org/jira/browse/DISPATCH-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105373#comment-17105373 ] ASF subversion and git services commented on DISPATCH-1645: --- Commit cd09cc0c9fcee65f2d093c93a813d3a27ee0a28d in qpid-dispatch's branch refs/heads/master from Charles E. Rolke [ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=cd09cc0 ] DISPATCH-1645: Use uint64_t values for max message size enforcement Policy settings and statistics already use unsigned 64 bit values. Runtime code was demoting the settings to signed 32 bit values. Release 1.12 works correctly only for max message size limits less than 2^31, including values from 1 to 2147483647. This closes #734 > Max message size is demoted to INT from UINT64 > -- > > Key: DISPATCH-1645 > URL: https://issues.apache.org/jira/browse/DISPATCH-1645 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 1.12.0 >Reporter: Charles E. Rolke >Assignee: Charles E. Rolke >Priority: Major > Fix For: 1.13.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-220) Create a set of "glass box" tests to quantify the performance of the proton codebase
[ https://issues.apache.org/jira/browse/PROTON-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105352#comment-17105352 ] Jiri Daněk commented on PROTON-220: --- There is still more work to be done, based on ideas in issue summary, in comments on the PR, and in comparison to what proton-j is testing. > Create a set of "glass box" tests to quantify the performance of the proton > codebase > > > Key: PROTON-220 > URL: https://issues.apache.org/jira/browse/PROTON-220 > Project: Qpid Proton > Issue Type: Test > Components: proton-c, proton-j >Reporter: Ken Giusti >Assignee: Jiri Daněk >Priority: Major > Labels: perf, testing > Fix For: proton-j-0.24.0, proton-c-0.32.0 > > > The goal of these tests would be to detect any performance degradation > inadvertently introduced during development. These tests would not be > intended to provide any metrics regarding the "real world" behavior of > proton-based applications. Rather, these tests are targeted for use by the > proton developers to help gauge the effect their code changes may have on > performance. > These tests should require no special configuration or setup in order to run. > It should be easy to run these test as part of the development process. The > intent would be to have developer run the tests prior to making any code > changes, and record the metrics for comparison against the results obtained > after making changes to the code base. > As described by Rafi: > "I think it would be good to include some performance metrics that isolate > the various components of proton. For example having a metric that simply > repeatedly encodes/decodes a message would be quite useful in isolating the > message implementation. Setting up two engines in memory and using them to > blast zero sized messages back and forth as fast as possible would tell us > how much protocol overhead the engine is adding. Using the codec directly > to encode/decode data would also be a useful measure. Each of these would > probably want to have multiple profiles, different message content, > different acknowledgement/flow control patterns, and different kinds of > data. > I think breaking out the different dimensions of the implementation as > above would provide a very useful tool to run before/after any performance > sensitive changes to detect and isolate regressions, or to test potential > improvements." -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-220) Create a set of "glass box" tests to quantify the performance of the proton codebase
[ https://issues.apache.org/jira/browse/PROTON-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105349#comment-17105349 ] ASF subversion and git services commented on PROTON-220: Commit 7abcfc7aba6cfd1c938324cf34a51555c845a589 in qpid-proton's branch refs/heads/master from Jirka Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=7abcfc7 ] PROTON-220: Google Benchmark proton-c and proton-cpp microbenchmarks (#211) > Create a set of "glass box" tests to quantify the performance of the proton > codebase > > > Key: PROTON-220 > URL: https://issues.apache.org/jira/browse/PROTON-220 > Project: Qpid Proton > Issue Type: Test > Components: proton-c, proton-j >Reporter: Ken Giusti >Assignee: Jiri Daněk >Priority: Major > Labels: perf, testing > Fix For: proton-j-0.24.0, proton-c-0.32.0 > > > The goal of these tests would be to detect any performance degradation > inadvertently introduced during development. These tests would not be > intended to provide any metrics regarding the "real world" behavior of > proton-based applications. Rather, these tests are targeted for use by the > proton developers to help gauge the effect their code changes may have on > performance. > These tests should require no special configuration or setup in order to run. > It should be easy to run these test as part of the development process. The > intent would be to have developer run the tests prior to making any code > changes, and record the metrics for comparison against the results obtained > after making changes to the code base. > As described by Rafi: > "I think it would be good to include some performance metrics that isolate > the various components of proton. For example having a metric that simply > repeatedly encodes/decodes a message would be quite useful in isolating the > message implementation. Setting up two engines in memory and using them to > blast zero sized messages back and forth as fast as possible would tell us > how much protocol overhead the engine is adding. Using the codec directly > to encode/decode data would also be a useful measure. Each of these would > probably want to have multiple profiles, different message content, > different acknowledgement/flow control patterns, and different kinds of > data. > I think breaking out the different dimensions of the implementation as > above would provide a very useful tool to run before/after any performance > sensitive changes to detect and isolate regressions, or to test potential > improvements." -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2216) Support additional SASL mechanisms on Windows
[ https://issues.apache.org/jira/browse/PROTON-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk updated PROTON-2216: --- Labels: windows (was: ) > Support additional SASL mechanisms on Windows > - > > Key: PROTON-2216 > URL: https://issues.apache.org/jira/browse/PROTON-2216 > Project: Qpid Proton > Issue Type: New Feature > Components: proton-c >Affects Versions: proton-c-0.31.0 >Reporter: Jiri Daněk >Priority: Major > Labels: windows > > Only the ANONYMOUS and PLAIN SASL mechanisms are supported on Windows, > according to > https://github.com/apache/qpid-proton/blob/69f5dfe7eb22432dbec666b5c7a1dca786c93657/python/setup.py.in#L170-L184. > Apparently, Windows itself implements GSSAPI, GSS-SPNEGO, EXTERNAL and > DIGEST-MD5 > https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-adts/a98c1f56-8246-4212-8c4e-d92da1a9563b > in a C++ system library > https://stackoverflow.com/questions/43146229/example-of-c-client-digest-md5-sasl-auth-with-windows, > > https://docs.microsoft.com/en-us/previous-versions/ms995352(v=msdn.10)?redirectedfrom=MSDN. > Cyrus SASL can be built for Windows, according to its documentation. > https://wiki.mozilla.org/LDAP_C_SDK_SASL_Windows, > https://github.com/cyrusimap/cyrus-sasl/blob/a162471d0edb390f5b233b25067773df0b3b99a4/docsrc/sasl/windows.rst > The linked patch in GitHub PR enables building with Cyrus SASL. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2216) Support additional SASL mechanisms on Windows
Jiri Daněk created PROTON-2216: -- Summary: Support additional SASL mechanisms on Windows Key: PROTON-2216 URL: https://issues.apache.org/jira/browse/PROTON-2216 Project: Qpid Proton Issue Type: New Feature Components: proton-c Affects Versions: proton-c-0.31.0 Reporter: Jiri Daněk Only the ANONYMOUS and PLAIN SASL mechanisms are supported on Windows, according to https://github.com/apache/qpid-proton/blob/69f5dfe7eb22432dbec666b5c7a1dca786c93657/python/setup.py.in#L170-L184. Apparently, Windows itself implements GSSAPI, GSS-SPNEGO, EXTERNAL and DIGEST-MD5 https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-adts/a98c1f56-8246-4212-8c4e-d92da1a9563b in a C++ system library https://stackoverflow.com/questions/43146229/example-of-c-client-digest-md5-sasl-auth-with-windows, https://docs.microsoft.com/en-us/previous-versions/ms995352(v=msdn.10)?redirectedfrom=MSDN. Cyrus SASL can be built for Windows, according to its documentation. https://wiki.mozilla.org/LDAP_C_SDK_SASL_Windows, https://github.com/cyrusimap/cyrus-sasl/blob/a162471d0edb390f5b233b25067773df0b3b99a4/docsrc/sasl/windows.rst The linked patch in GitHub PR enables building with Cyrus SASL. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2154) 0.31.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-2154. Resolution: Done > 0.31.0 release tasks > > > Key: PROTON-2154 > URL: https://issues.apache.org/jira/browse/PROTON-2154 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-c-0.31.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2215) Windows build fails if CMAKE_MODULE_PATH is not empty
[
https://issues.apache.org/jira/browse/PROTON-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk updated PROTON-2215:
---
Description:
In {{tools/cmake/Modules/WindowsC99CheckDef.cmake}}:
{code}
COMMAND ${PYTHON_EXECUTABLE}
${CMAKE_MODULE_PATH}/WindowsC99SymbolCheck.py
$
{code}
This is wrong, if only because {{CMAKE_MODULE_PATH}} is a list of directories,
not a single directory.
was:
In {{tools/cmake/Modules/WindowsC99CheckDef.cmake}}:
{code}
COMMAND ${PYTHON_EXECUTABLE}COMMAND ${PYTHON_EXECUTABLE}
${CMAKE_MODULE_PATH}/WindowsC99SymbolCheck.py
$
{code}
This is wrong, if only because {{CMAKE_MODULE_PATH}} is a list of directories,
not a single directory.
> Windows build fails if CMAKE_MODULE_PATH is not empty
> -
>
> Key: PROTON-2215
> URL: https://issues.apache.org/jira/browse/PROTON-2215
> Project: Qpid Proton
> Issue Type: Bug
> Components: build
>Reporter: Jiri Daněk
>Assignee: Jiri Daněk
>Priority: Major
> Fix For: proton-c-0.32.0
>
>
> In {{tools/cmake/Modules/WindowsC99CheckDef.cmake}}:
> {code}
> COMMAND ${PYTHON_EXECUTABLE}
> ${CMAKE_MODULE_PATH}/WindowsC99SymbolCheck.py
> $
> {code}
> This is wrong, if only because {{CMAKE_MODULE_PATH}} is a list of
> directories, not a single directory.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2215) Windows build fails if CMAKE_MODULE_PATH is not empty
[
https://issues.apache.org/jira/browse/PROTON-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk updated PROTON-2215:
---
Fix Version/s: proton-c-0.32.0
> Windows build fails if CMAKE_MODULE_PATH is not empty
> -
>
> Key: PROTON-2215
> URL: https://issues.apache.org/jira/browse/PROTON-2215
> Project: Qpid Proton
> Issue Type: Bug
> Components: build
>Reporter: Jiri Daněk
>Assignee: Jiri Daněk
>Priority: Major
> Fix For: proton-c-0.32.0
>
>
> In {{tools/cmake/Modules/WindowsC99CheckDef.cmake}}:
> {code}
> COMMAND ${PYTHON_EXECUTABLE} COMMAND ${PYTHON_EXECUTABLE}
> ${CMAKE_MODULE_PATH}/WindowsC99SymbolCheck.py
> $
> {code}
> This is wrong, if only because {{CMAKE_MODULE_PATH}} is a list of
> directories, not a single directory.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2215) Windows build fails if CMAKE_MODULE_PATH is not empty
Jiri Daněk created PROTON-2215:
--
Summary: Windows build fails if CMAKE_MODULE_PATH is not empty
Key: PROTON-2215
URL: https://issues.apache.org/jira/browse/PROTON-2215
Project: Qpid Proton
Issue Type: Bug
Reporter: Jiri Daněk
Assignee: Jiri Daněk
In {{tools/cmake/Modules/WindowsC99CheckDef.cmake}}:
{code}
COMMAND ${PYTHON_EXECUTABLE}COMMAND ${PYTHON_EXECUTABLE}
${CMAKE_MODULE_PATH}/WindowsC99SymbolCheck.py
$
{code}
This is wrong, if only because {{CMAKE_MODULE_PATH}} is a list of directories,
not a single directory.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2215) Windows build fails if CMAKE_MODULE_PATH is not empty
[
https://issues.apache.org/jira/browse/PROTON-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk updated PROTON-2215:
---
Component/s: build
> Windows build fails if CMAKE_MODULE_PATH is not empty
> -
>
> Key: PROTON-2215
> URL: https://issues.apache.org/jira/browse/PROTON-2215
> Project: Qpid Proton
> Issue Type: Bug
> Components: build
>Reporter: Jiri Daněk
>Assignee: Jiri Daněk
>Priority: Major
>
> In {{tools/cmake/Modules/WindowsC99CheckDef.cmake}}:
> {code}
> COMMAND ${PYTHON_EXECUTABLE} COMMAND ${PYTHON_EXECUTABLE}
> ${CMAKE_MODULE_PATH}/WindowsC99SymbolCheck.py
> $
> {code}
> This is wrong, if only because {{CMAKE_MODULE_PATH}} is a list of
> directories, not a single directory.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2199) memory leak in c++ object inspect
[
https://issues.apache.org/jira/browse/PROTON-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk resolved PROTON-2199.
Resolution: Fixed
> memory leak in c++ object inspect
> -
>
> Key: PROTON-2199
> URL: https://issues.apache.org/jira/browse/PROTON-2199
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
>Reporter: Jeff Eaton
>Assignee: Jiri Daněk
>Priority: Major
> Labels: easyfix
> Fix For: proton-c-0.32.0
>
>
> The {{pn_ptr_base::inspect()}} function in {{cpp/src/object.cpp}} calls
> {{pn_string(NULL)}} on line 36 and never frees the allocated memory with
> {{pn_free()}}.
> The fix is to create the std::string as a temporary variable, then free the
> pn_string_t, then return the temporary std::string, like this:
> {{std::string tmp(pn_string_get(s));}}
> {{pn_free(s);}}
> {{return tmp;}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2199) memory leak in c++ object inspect
[
https://issues.apache.org/jira/browse/PROTON-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105264#comment-17105264
]
ASF subversion and git services commented on PROTON-2199:
-
Commit 625dec907e116a627893b4e7f90be01e6f988f5d in qpid-proton's branch
refs/heads/master from Jiri Daněk
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=625dec9 ]
PROTON-2199 fix memory leak in C++ object inspect (#244)
> memory leak in c++ object inspect
> -
>
> Key: PROTON-2199
> URL: https://issues.apache.org/jira/browse/PROTON-2199
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
>Reporter: Jeff Eaton
>Assignee: Jiri Daněk
>Priority: Major
> Labels: easyfix
> Fix For: proton-c-0.32.0
>
>
> The {{pn_ptr_base::inspect()}} function in {{cpp/src/object.cpp}} calls
> {{pn_string(NULL)}} on line 36 and never frees the allocated memory with
> {{pn_free()}}.
> The fix is to create the std::string as a temporary variable, then free the
> pn_string_t, then return the temporary std::string, like this:
> {{std::string tmp(pn_string_get(s));}}
> {{pn_free(s);}}
> {{return tmp;}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDJMS-504) Connections hangs when trying to connect to a RabbitMQ persistent queue
[
https://issues.apache.org/jira/browse/QPIDJMS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Siano updated QPIDJMS-504:
--
Description:
When I try to connect to a persistent queue on a RabbitMQ broker with activated
AMQP 1.0 plugin, the connection hangs for an infinite time (or at least for a
very long time).
There is no error, the connection just hangs. The tack trace in this situation
for a producer is:
{noformat}
BalancedProviderFuture(Object).wait() line: 502
BalancedProviderFuture.sync() line: 136
JmsConnection.createResource(JmsResource, ProviderSynchronization) line: 693
JmsMessageProducer.(JmsProducerId, JmsSession, JmsDestination) line: 73
JmsQueueSession(JmsSession).createProducer(Destination) line: 664
JmsQueueSession.createProducer(Destination) line: 97
{noformat}
The stack trace for a consumer is:
{noformat}
BalancedProviderFuture(Object).wait() line: 502
BalancedProviderFuture.sync() line: 136
JmsConnection.createResource(JmsResource, ProviderSynchronization) line: 693
JmsMessageConsumer.(JmsConsumerId, JmsSession, JmsDestination, String,
String, boolean) line: 125
JmsMessageConsumer.(JmsConsumerId, JmsSession, JmsDestination, String,
boolean) line: 82
JmsQueueSession(JmsSession).createConsumer(Destination, String, boolean) line:
478
JmsQueueSession.createConsumer(Destination, String, boolean) line: 70
JmsQueueSession(JmsSession).createConsumer(Destination, String) line: 466
JmsQueueSession.createConsumer(Destination, String) line: 59
JmsQueueSession(JmsSession).createConsumer(Destination) line: 458
JmsQueueSession.createConsumer(Destination) line: 48
{noformat}
I am aware that the AMQP 1.0 plugin in RabbitMQ is not very mature, but I don't
think that the client threads should be blocked forever even when trying to
communicate with misbehaving servers.
The issue will not happen with transient queues on RabbitMQ (here everything
works as expected).
was:
When I try to connect to a persistent queue on a RabbitMQ broker with activated
AMQP 1.0 plugin, the connection hangs for an infinite time (or at least for a
very long time).
There is no error, the connection just hangs. The tack trace in this situation
for a producer is:
{noformat}
BalancedProviderFuture(Object).wait() line: 502
BalancedProviderFuture.sync() line: 136
JmsConnection.createResource(JmsResource, ProviderSynchronization) line: 693
JmsMessageProducer.(JmsProducerId, JmsSession, JmsDestination) line: 73
JmsQueueSession(JmsSession).createProducer(Destination) line: 664
JmsQueueSession.createProducer(Destination) line: 97
{noformat}
The stack trace for a consumer is:
{noformat}
BalancedProviderFuture(Object).wait() line: 502
BalancedProviderFuture.sync() line: 136
JmsConnection.createResource(JmsResource, ProviderSynchronization) line: 693
JmsMessageConsumer.(JmsConsumerId, JmsSession, JmsDestination, String,
String, boolean) line: 125
JmsMessageConsumer.(JmsConsumerId, JmsSession, JmsDestination, String,
boolean) line: 82
JmsQueueSession(JmsSession).createConsumer(Destination, String, boolean) line:
478
JmsQueueSession.createConsumer(Destination, String, boolean) line: 70
JmsQueueSession(JmsSession).createConsumer(Destination, String) line: 466
JmsQueueSession.createConsumer(Destination, String) line: 59
JmsQueueSession(JmsSession).createConsumer(Destination) line: 458
JmsQueueSession.createConsumer(Destination) line: 48
{noformat}
I am aware that the AMQP 1.0 plugin in RabbitMQ is not very mature, but I don't
think that the client threads should be blocked forever even when trying to
communicate with misbehaving servers.
> Connections hangs when trying to connect to a RabbitMQ persistent queue
> ---
>
> Key: QPIDJMS-504
> URL: https://issues.apache.org/jira/browse/QPIDJMS-504
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
>Affects Versions: 0.51.0
>Reporter: Stephan Siano
>Priority: Major
>
> When I try to connect to a persistent queue on a RabbitMQ broker with
> activated AMQP 1.0 plugin, the connection hangs for an infinite time (or at
> least for a very long time).
> There is no error, the connection just hangs. The tack trace in this
> situation for a producer is:
> {noformat}
> BalancedProviderFuture(Object).wait() line: 502
> BalancedProviderFuture.sync() line: 136
> JmsConnection.createResource(JmsResource, ProviderSynchronization) line: 693
> JmsMessageProducer.(JmsProducerId, JmsSession, JmsDestination) line: 73
> JmsQueueSession(JmsSession).createProducer(Destination) line: 664
> JmsQueueSession.createProducer(Destination) line: 97
> {noformat}
> The stack trace for a consumer is:
> {noformat}
> BalancedProviderFuture(Object).wait() line: 502
[jira] [Created] (QPIDJMS-504) Connections hangs when trying to connect to a RabbitMQ persistent queue
Stephan Siano created QPIDJMS-504:
-
Summary: Connections hangs when trying to connect to a RabbitMQ
persistent queue
Key: QPIDJMS-504
URL: https://issues.apache.org/jira/browse/QPIDJMS-504
Project: Qpid JMS
Issue Type: Bug
Components: qpid-jms-client
Affects Versions: 0.51.0
Reporter: Stephan Siano
When I try to connect to a persistent queue on a RabbitMQ broker with activated
AMQP 1.0 plugin, the connection hangs for an infinite time (or at least for a
very long time).
There is no error, the connection just hangs. The tack trace in this situation
for a producer is:
{noformat}
BalancedProviderFuture(Object).wait() line: 502
BalancedProviderFuture.sync() line: 136
JmsConnection.createResource(JmsResource, ProviderSynchronization) line: 693
JmsMessageProducer.(JmsProducerId, JmsSession, JmsDestination) line: 73
JmsQueueSession(JmsSession).createProducer(Destination) line: 664
JmsQueueSession.createProducer(Destination) line: 97
{noformat}
The stack trace for a consumer is:
{noformat}
BalancedProviderFuture(Object).wait() line: 502
BalancedProviderFuture.sync() line: 136
JmsConnection.createResource(JmsResource, ProviderSynchronization) line: 693
JmsMessageConsumer.(JmsConsumerId, JmsSession, JmsDestination, String,
String, boolean) line: 125
JmsMessageConsumer.(JmsConsumerId, JmsSession, JmsDestination, String,
boolean) line: 82
JmsQueueSession(JmsSession).createConsumer(Destination, String, boolean) line:
478
JmsQueueSession.createConsumer(Destination, String, boolean) line: 70
JmsQueueSession(JmsSession).createConsumer(Destination, String) line: 466
JmsQueueSession.createConsumer(Destination, String) line: 59
JmsQueueSession(JmsSession).createConsumer(Destination) line: 458
JmsQueueSession.createConsumer(Destination) line: 48
{noformat}
I am aware that the AMQP 1.0 plugin in RabbitMQ is not very mature, but I don't
think that the client threads should be blocked forever even when trying to
communicate with misbehaving servers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
