[jira] [Created] (PROTON-2110) [Python] Expand tilde symbol as user's home directory when searching for connect.json file
Radim Kubis created PROTON-2110:
---
Summary: [Python] Expand tilde symbol as user's home directory
when searching for connect.json file
Key: PROTON-2110
URL: https://issues.apache.org/jira/browse/PROTON-2110
Project: Qpid Proton
Issue Type: Bug
Components: python-binding
Reporter: Radim Kubis
Tilde ({{~}}) symbol is not expanded as user's home directory, but as a
directory named tilde in current working 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-2109) [Python] Correct default JSON schema to amqps
Radim Kubis created PROTON-2109:
---
Summary: [Python] Correct default JSON schema to amqps
Key: PROTON-2109
URL: https://issues.apache.org/jira/browse/PROTON-2109
Project: Qpid Proton
Issue Type: Bug
Components: python-binding
Reporter: Radim Kubis
According to
[connect-config.md|https://github.com/apache/qpid-proton/blob/master/docs/connect-config.md],
default port should be \{{amqps}}, but there is \{{amqp}} now.
--
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-1997) [Python] Urls class is not exported by reactor
Radim Kubis created PROTON-1997: --- Summary: [Python] Urls class is not exported by reactor Key: PROTON-1997 URL: https://issues.apache.org/jira/browse/PROTON-1997 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: proton-c-0.25.0 Reporter: Radim Kubis Assignee: Andrew Stitcher Fix For: proton-c-0.26.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1997) [Python] Urls class is not exported by reactor
[ https://issues.apache.org/jira/browse/PROTON-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radim Kubis updated PROTON-1997: Affects Version/s: (was: proton-c-0.25.0) proton-c-0.26.0 > [Python] Urls class is not exported by reactor > -- > > Key: PROTON-1997 > URL: https://issues.apache.org/jira/browse/PROTON-1997 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.26.0 >Reporter: Radim Kubis >Assignee: Andrew Stitcher >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1997) [Python] Urls class is not exported by reactor
[ https://issues.apache.org/jira/browse/PROTON-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radim Kubis updated PROTON-1997: Fix Version/s: (was: proton-c-0.26.0) > [Python] Urls class is not exported by reactor > -- > > Key: PROTON-1997 > URL: https://issues.apache.org/jira/browse/PROTON-1997 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.25.0 >Reporter: Radim Kubis >Assignee: Andrew Stitcher >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1809) [python, ruby] Unable to receive messages when max-frame-size is set to more than 2^20
[
https://issues.apache.org/jira/browse/PROTON-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411050#comment-16411050
]
Radim Kubis commented on PROTON-1809:
-
Strange thing is that _open_ frame (with setting max-frame-size to 4294967295)
looks the same as without setting max-frame-size.
{code:java}
-> @open(16) [container-id="", channel-max=32767]{code}
> [python, ruby] Unable to receive messages when max-frame-size is set to more
> than 2^20
> --
>
> Key: PROTON-1809
> URL: https://issues.apache.org/jira/browse/PROTON-1809
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding, ruby-binding
>Affects Versions: proton-c-0.22.0
> Environment: RHEL 7 x86_64
>Reporter: Radim Kubis
>Assignee: Alan Conway
>Priority: Major
>
> *Python:*
> {code:java}
> def on_session_init(self, event):
> event.transport._set_max_frame_size(VALUE)
> {code}
> I noticed that the receiver is not able to receive messages when the value
> for max-frame-size is larger than 2^20 (1048576) bytes (remote_max_frame_size
> is 4294967295). I'm not really sure if that is expected. This may be
> reproduced when adding the code above ie.: to simple_recv.py.
> Note: This is not a good use case as setting the max-frame-size in
> on_session_init is really too late. But given that it is too late to set the
> max-frame-size, I would expect it won't have any effect on the client.
>
> *Ruby:*
> From [https://github.com/rh-messaging/cli-proton-ruby]
> [cli-proton-ruby|https://github.com/rh-messaging/cli-proton-ruby]
> {{cli-proton-ruby-receiver -b -c --log-msgs dict
> --conn-max-frame-size 1048577}}
> Receiver is stuck.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (PROTON-1809) [python, ruby] Unable to receive messages when max-frame-size is set to more than 2^20
[
https://issues.apache.org/jira/browse/PROTON-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411050#comment-16411050
]
Radim Kubis edited comment on PROTON-1809 at 3/23/18 9:12 AM:
--
Strange thing is that _open_ frame (with setting max-frame-size to 4294967295)
looks the same as without setting max-frame-size.
{code:java}
-> @open(16) [container-id="", channel-max=32767]{code}
was (Author: rkubis):
Strange thing is that _open_ frame (with setting max-frame-size to 4294967295)
looks the same as without setting max-frame-size.
{code:java}
-> @open(16) [container-id="", channel-max=32767]{code}
> [python, ruby] Unable to receive messages when max-frame-size is set to more
> than 2^20
> --
>
> Key: PROTON-1809
> URL: https://issues.apache.org/jira/browse/PROTON-1809
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding, ruby-binding
>Affects Versions: proton-c-0.22.0
> Environment: RHEL 7 x86_64
>Reporter: Radim Kubis
>Assignee: Alan Conway
>Priority: Major
>
> *Python:*
> {code:java}
> def on_session_init(self, event):
> event.transport._set_max_frame_size(VALUE)
> {code}
> I noticed that the receiver is not able to receive messages when the value
> for max-frame-size is larger than 2^20 (1048576) bytes (remote_max_frame_size
> is 4294967295). I'm not really sure if that is expected. This may be
> reproduced when adding the code above ie.: to simple_recv.py.
> Note: This is not a good use case as setting the max-frame-size in
> on_session_init is really too late. But given that it is too late to set the
> max-frame-size, I would expect it won't have any effect on the client.
>
> *Ruby:*
> From [https://github.com/rh-messaging/cli-proton-ruby]
> [cli-proton-ruby|https://github.com/rh-messaging/cli-proton-ruby]
> {{cli-proton-ruby-receiver -b -c --log-msgs dict
> --conn-max-frame-size 1048577}}
> Receiver is stuck.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1809) [python, ruby] Unable to receive messages when max-frame-size is set to more than 2^20
[
https://issues.apache.org/jira/browse/PROTON-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radim Kubis updated PROTON-1809:
Description:
*Python:*
{code:java}
def on_session_init(self, event):
event.transport._set_max_frame_size(VALUE)
{code}
I noticed that the receiver is not able to receive messages when the value for
max-frame-size is larger than 2^20 (1048576) bytes (remote_max_frame_size is
4294967295). I'm not really sure if that is expected. This may be reproduced
when adding the code above ie.: to simple_recv.py.
Note: This is not a good use case as setting the max-frame-size in
on_session_init is really too late. But given that it is too late to set the
max-frame-size, I would expect it won't have any effect on the client.
*Ruby:*
>From [https://github.com/rh-messaging/cli-proton-ruby]
>[cli-proton-ruby|https://github.com/rh-messaging/cli-proton-ruby]
{{cli-proton-ruby-receiver -b -c --log-msgs dict
--conn-max-frame-size 1048577}}
Receiver is stuck.
was:
*Python:*
{code}
def on_session_init(self, event):
event.transport._set_max_frame_size(VALUE)
{code}
I noticed that the receiver is not able to receive messages when the value for
max-frame-size is larger than 2^20 (1048576) bytes (remote_max_frame_size is
4294967295). I'm not really sure if that is expected. This may be reproduced
when adding the code above ie.: to simple_recv.py.
Note: This is not a good use case as setting the max-frame-size in
on_session_init is really too late. But given that it is too late to set the
max-frame-size, I would expect it won't have any effect on the client.
*Ruby:*
>From [|https://github.com/rh-messaging/cli-proton-ruby]
>[cli-proton-ruby|https://github.com/rh-messaging/cli-proton-ruby]
{{cli-proton-ruby-receiver \-b \--c \-\-log-msgs dict
\-\-conn-max-frame-size 1048577}}-
Receiver is stuck.
> [python, ruby] Unable to receive messages when max-frame-size is set to more
> than 2^20
> --
>
> Key: PROTON-1809
> URL: https://issues.apache.org/jira/browse/PROTON-1809
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding, ruby-binding
>Affects Versions: proton-c-0.22.0
> Environment: RHEL 7 x86_64
>Reporter: Radim Kubis
>Assignee: Alan Conway
>Priority: Major
>
> *Python:*
> {code:java}
> def on_session_init(self, event):
> event.transport._set_max_frame_size(VALUE)
> {code}
> I noticed that the receiver is not able to receive messages when the value
> for max-frame-size is larger than 2^20 (1048576) bytes (remote_max_frame_size
> is 4294967295). I'm not really sure if that is expected. This may be
> reproduced when adding the code above ie.: to simple_recv.py.
> Note: This is not a good use case as setting the max-frame-size in
> on_session_init is really too late. But given that it is too late to set the
> max-frame-size, I would expect it won't have any effect on the client.
>
> *Ruby:*
> From [https://github.com/rh-messaging/cli-proton-ruby]
> [cli-proton-ruby|https://github.com/rh-messaging/cli-proton-ruby]
> {{cli-proton-ruby-receiver -b -c --log-msgs dict
> --conn-max-frame-size 1048577}}
> Receiver is stuck.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1809) [python, ruby] Unable to receive messages when max-frame-size is set to more than 2^20
Radim Kubis created PROTON-1809:
---
Summary: [python, ruby] Unable to receive messages when
max-frame-size is set to more than 2^20
Key: PROTON-1809
URL: https://issues.apache.org/jira/browse/PROTON-1809
Project: Qpid Proton
Issue Type: Bug
Components: python-binding, ruby-binding
Affects Versions: proton-c-0.22.0
Environment: RHEL 7 x86_64
Reporter: Radim Kubis
Assignee: Alan Conway
*Python:*
{code}
def on_session_init(self, event):
event.transport._set_max_frame_size(VALUE)
{code}
I noticed that the receiver is not able to receive messages when the value for
max-frame-size is larger than 2^20 (1048576) bytes (remote_max_frame_size is
4294967295). I'm not really sure if that is expected. This may be reproduced
when adding the code above ie.: to simple_recv.py.
Note: This is not a good use case as setting the max-frame-size in
on_session_init is really too late. But given that it is too late to set the
max-frame-size, I would expect it won't have any effect on the client.
*Ruby:*
>From [|https://github.com/rh-messaging/cli-proton-ruby]
>[cli-proton-ruby|https://github.com/rh-messaging/cli-proton-ruby]
{{cli-proton-ruby-receiver \-b \--c \-\-log-msgs dict
\-\-conn-max-frame-size 1048577}}-
Receiver is stuck.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1626) Incompatibilty of fdlimit test on RHEL 6 x64
[ https://issues.apache.org/jira/browse/PROTON-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radim Kubis updated PROTON-1626: Priority: Minor (was: Major) > Incompatibilty of fdlimit test on RHEL 6 x64 > > > Key: PROTON-1626 > URL: https://issues.apache.org/jira/browse/PROTON-1626 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.18.0 > Environment: RHEL 6 x64 >Reporter: Radim Kubis >Priority: Minor > > Test > [fdlimit|https://github.com/apache/qpid-proton/blob/master/proton-c/src/tests/fdlimit.py] > uses RHEL 6 x64 incompatible things: > * _skipTest_ (added in Python 2.7, but RHEL 6 has Python 2.6.6) > * _prlimit_ utility (unavailable on RHEL 6) -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1626) Incompatibilty of fdlimit test on RHEL 6 x64
Radim Kubis created PROTON-1626: --- Summary: Incompatibilty of fdlimit test on RHEL 6 x64 Key: PROTON-1626 URL: https://issues.apache.org/jira/browse/PROTON-1626 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: proton-c-0.18.0 Environment: RHEL 6 x64 Reporter: Radim Kubis Test [fdlimit|https://github.com/apache/qpid-proton/blob/master/proton-c/src/tests/fdlimit.py] uses RHEL 6 x64 incompatible things: * _skipTest_ (added in Python 2.7, but RHEL 6 has Python 2.6.6) * _prlimit_ utility (unavailable on RHEL 6) -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (PROTON-927) absolute-expiry-time and creation-time are encoded as 0 if not set
[ https://issues.apache.org/jira/browse/PROTON-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123191#comment-16123191 ] Radim Kubis edited comment on PROTON-927 at 8/11/17 11:13 AM: -- The same behaviour is for message priority. If message priority is not set in message, it is encoded as 0, but it means that priority has default value 4 according to specification of AMQP 1.0. was (Author: rkubis): The same behaviour is for message priority. > absolute-expiry-time and creation-time are encoded as 0 if not set > -- > > Key: PROTON-927 > URL: https://issues.apache.org/jira/browse/PROTON-927 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.9.1 >Reporter: Gordon Sim >Assignee: Andrew Stitcher > Fix For: proton-c-0.18.0 > > > They should instead be encoded as null (since there is no default). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-927) absolute-expiry-time and creation-time are encoded as 0 if not set
[ https://issues.apache.org/jira/browse/PROTON-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123191#comment-16123191 ] Radim Kubis commented on PROTON-927: The same behaviour is for message priority. > absolute-expiry-time and creation-time are encoded as 0 if not set > -- > > Key: PROTON-927 > URL: https://issues.apache.org/jira/browse/PROTON-927 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.9.1 >Reporter: Gordon Sim >Assignee: Andrew Stitcher > Fix For: proton-c-0.18.0 > > > They should instead be encoded as null (since there is no default). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6868) [AMQP 1.0 C++ Client] No errors for rejected messages.
[
https://issues.apache.org/jira/browse/QPID-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522426#comment-15522426
]
Radim Kubis commented on QPID-6868:
---
[~gsim] [~cliffjansen] Could you have a look on this item, please. This is
blocker for our JAMQ. Thanks.
> [AMQP 1.0 C++ Client] No errors for rejected messages.
> --
>
> Key: QPID-6868
> URL: https://issues.apache.org/jira/browse/QPID-6868
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
>Affects Versions: qpid-cpp-0.34
> Environment: Red Hat Enterprise Linux Server release 6.7 (Santiago)
> The _qpid-cpp_ code has been built with _qpid-proton_ version 0.10.
> The broker is ActiveMQ 5.12.1.
> The protocol used in AMQP 1.0.
>Reporter: Håkan Johansson
> Attachments: example.cc
>
>
> When using protocol AMQP 1.0 and non-syncing send calls it is impossible to
> know if a message was rejected by the broker. I get warnings in the log, but
> nothing else.
> I have created a short example that shows the issue (see attached file).
> If I call _send_ with _sync_ set to _true_, then I get an exception, just as
> expected.
> Expected behavior:
> I expect to get an exception when the failed send is first noticed, either in
> the _sender.send_ call itself, a subsequent _sender.send_ call, or when
> calling _session.sync_.
> Test program output (sync=false):
> {noformat}
> Writing message 1
> Writing message 2
> Writing message 3
> Writing message 4
> 2015-11-18 10:34:24 [Messaging] warning delivery 0 was rejected by peer
> 2015-11-18 10:34:24 [Messaging] warning delivery 1 was rejected by peer
> Writing message 5
> 2015-11-18 10:34:24 [Messaging] warning delivery 2 was rejected by peer
> Writing message 6
> 2015-11-18 10:34:24 [Messaging] warning delivery 3 was rejected by peer
> Writing message 7
> 2015-11-18 10:34:24 [Messaging] warning delivery 4 was rejected by peer
> Writing message 8
> 2015-11-18 10:34:24 [Messaging] warning delivery 5 was rejected by peer
> Writing message 9
> 2015-11-18 10:34:24 [Messaging] warning delivery 6 was rejected by peer
> Writing message 10
> 2015-11-18 10:34:24 [Messaging] warning delivery 7 was rejected by peer
> Syncing
> 2015-11-18 10:34:24 [Messaging] warning delivery 8 was rejected by peer
> 2015-11-18 10:34:24 [Messaging] warning delivery 9 was rejected by peer
> Closing
> Done
> {noformat}
> Test program output (sync=true):
> {noformat}
> Writing message 1
> Writing message 2
> 2015-11-18 10:30:10 [Messaging] warning delivery 1 was rejected by peer
> 2015-11-18 10:30:10 [Messaging] warning delivery 1 was rejected by peer
> Error: Message was rejected by peer
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7431) Support for message-annotations
[ https://issues.apache.org/jira/browse/QPID-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522424#comment-15522424 ] Radim Kubis commented on QPID-7431: --- [~gsim] [~cliffjansen] Could you have a look on this item, please. This is blocker for our JAMQ. Thanks. > Support for message-annotations > --- > > Key: QPID-7431 > URL: https://issues.apache.org/jira/browse/QPID-7431 > Project: Qpid > Issue Type: Improvement > Components: C++ Client >Reporter: Radim Kubis > > We would like to request support for message-annotations on the Qpid > messaging API. We have been working with Interconnect and needs to read/write > message-annotations. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7431) Support for message-annotations
Radim Kubis created QPID-7431: - Summary: Support for message-annotations Key: QPID-7431 URL: https://issues.apache.org/jira/browse/QPID-7431 Project: Qpid Issue Type: Improvement Components: C++ Client Reporter: Radim Kubis We would like to request support for message-annotations on the Qpid messaging API. We have been working with Interconnect and needs to read/write message-annotations. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
