[
https://issues.apache.org/jira/browse/DISPATCH-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated DISPATCH-912:
Environment: (was: Appears to be a result of changes in
https://issues.apache.org/jira/browse
On 10/01/18 10:19, Gordon Sim wrote:
I see two if the dispatch system tests failing after the following
commit to proton (they all when run against a proton lib before this
patch). Subsequent commits to proton don't help either - dispatch tests
fail against latest proton master also
[
https://issues.apache.org/jira/browse/PROTON-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved PROTON-1742.
Resolution: Fixed
> there is no send example that works well with selected_r
[
https://issues.apache.org/jira/browse/PROTON-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324137#comment-16324137
]
Gordon Sim commented on PROTON-1742:
variant of simple_Send added for python and c++ that sets
[
https://issues.apache.org/jira/browse/PROTON-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated PROTON-1742:
---
Attachment: selected_recv_cpp_test.patch
> there is no send example that works w
[
https://issues.apache.org/jira/browse/PROTON-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved PROTON-1741.
Resolution: Fixed
> selected_recv example doesn't w
Gordon Sim created PROTON-1742:
--
Summary: there is no send example that works well with
selected_recv
Key: PROTON-1742
URL: https://issues.apache.org/jira/browse/PROTON-1742
Project: Qpid Proton
Gordon Sim created PROTON-1741:
--
Summary: selected_recv example doesn't work
Key: PROTON-1741
URL: https://issues.apache.org/jira/browse/PROTON-1741
Project: Qpid Proton
Issue Type: Bug
I see two if the dispatch system tests failing after the following
commit to proton (they all when run against a proton lib before this
patch). Subsequent commits to proton don't help either - dispatch tests
fail against latest proton master also.
The tests that fail are
lugin
> > authService port for authentication and authz. In the current policy scheme
> > the policy is decided later when the AMQP Open frame's hostname field is
> > used as the name of the vhost policy. Then the user name is looked up in
> > that vhost policy section.
>
--
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/64645/#review194246
-------
On Dec. 20, 2017, 5:40 p.m., Gordon Sim wrote:
>
>
/
Testing
---
Added new systems tests using proton python based dummy auth service.
Thanks,
Gordon Sim
systems tests using proton python based dummy auth service.
Thanks,
Gordon Sim
Process.RUNNING)
> >
> > and having 'chmod +x authservice.py'
Thanks so much Chuck! Will get those fixed.
- Gordon
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.ap
dummy auth service.
Thanks,
Gordon Sim
[
https://issues.apache.org/jira/browse/DISPATCH-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292346#comment-16292346
]
Gordon Sim commented on DISPATCH-901:
-
Initial patch for review and comments: https
,
Gordon Sim
[
https://issues.apache.org/jira/browse/DISPATCH-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated DISPATCH-901:
Description: It would be more useful to have the auth service provide a set
of permissions
Gordon Sim created DISPATCH-901:
---
Summary: add authz support to auth service plugin
Key: DISPATCH-901
URL: https://issues.apache.org/jira/browse/DISPATCH-901
Project: Qpid Dispatch
Issue Type
[
https://issues.apache.org/jira/browse/DISPATCH-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262469#comment-16262469
]
Gordon Sim commented on DISPATCH-882:
-
Yes, if the receiver is receiving unsettled transfers
Gordon Sim created DISPATCH-882:
---
Summary: router buffers messages for slow presettled receiver
Key: DISPATCH-882
URL: https://issues.apache.org/jira/browse/DISPATCH-882
Project: Qpid Dispatch
On 02/11/17 17:57, Robbie Gemmell wrote:
Right, and it isnt really trying to, but thats the concern as the
broker doesnt necessarily think it wont.
I think question is whether or not the terminus is shared. The terminus
expiration/durability is the only way the client and server can
On 02/11/17 15:10, Robbie Gemmell wrote:
I think you might be approaching this from a slightly different view
than what Lorenz originally was.
Oops, sorry!
The '|suffix' bit of the name isn't the main thing Lorenz is raising I
believe, but rather that the container-id associated with a
On 02/11/17 08:56, Lorenz Quack wrote:
On Wed, 2017-11-01 at 12:10 +, Gordon Sim wrote:
On 01/11/17 10:16, Lorenz Quack wrote:
For global subscription on the other hand the client uses a random
UUID associated with the connection as its own container-id. This
means that on every new
On 01/11/17 10:16, Lorenz Quack wrote:
For global subscription on the other hand the client uses a random
UUID associated with the connection as its own container-id. This
means that on every new connection a new link is being estblished
rather than recovering an existing one. Over time these
[
https://issues.apache.org/jira/browse/QPID-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215778#comment-16215778
]
Gordon Sim commented on QPID-7981:
--
{quote}It is the only meaning when speaking of the local terminus
[
https://issues.apache.org/jira/browse/QPID-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215719#comment-16215719
]
Gordon Sim commented on QPID-7981:
--
{quote}You are viewing this as a request-response protocol
[
https://issues.apache.org/jira/browse/QPID-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215461#comment-16215461
]
Gordon Sim commented on QPID-7981:
--
Fixed rhea in
https://github.com/grs/rhea/commit
[
https://issues.apache.org/jira/browse/QPID-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215428#comment-16215428
]
Gordon Sim commented on QPID-7981:
--
I'll add that I think the broker is wrong also. The apparent protocol
[
https://issues.apache.org/jira/browse/QPID-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215420#comment-16215420
]
Gordon Sim commented on QPID-7981:
--
{quote}the meaning is noticed (I think) by clients detecting
[
https://issues.apache.org/jira/browse/QPID-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215367#comment-16215367
]
Gordon Sim commented on QPID-7981:
--
{quote}not setting a source has a very specific meaning if you
[
https://issues.apache.org/jira/browse/QPID-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215360#comment-16215360
]
Gordon Sim commented on QPID-7981:
--
bq. a peer (client) sending messages must provide a non-null source
[
https://issues.apache.org/jira/browse/QPID-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215349#comment-16215349
]
Gordon Sim commented on QPID-7981:
--
{quote}Depending on the perspective of which end you are at, a single
[
https://issues.apache.org/jira/browse/QPID-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215231#comment-16215231
]
Gordon Sim commented on QPID-7981:
--
I believe that the source *is* set for the 'outgoing' link, i.e
[
https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205680#comment-16205680
]
Gordon Sim commented on PROTON-1542:
The fix for PROTON-1535 allows a sasl plugin to set the hostname
[
https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184285#comment-16184285
]
Gordon Sim commented on PROTON-1542:
I think this is very much like the SNI. In general the SNI
[
https://issues.apache.org/jira/browse/DISPATCH-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim closed DISPATCH-297.
---
Resolution: Cannot Reproduce
assume fixed
> router goes into infinite l
[
https://issues.apache.org/jira/browse/PROTON-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated PROTON-1587:
---
Attachment: proton-1587.tgz
Reproducer:
1. compile the tls_client.c example
2. start three versions
Gordon Sim created PROTON-1587:
--
Summary: failure on one SSL connection causes error:140E0197:SSL
routines:SSL_shutdown:shutdown while in init
Key: PROTON-1587
URL: https://issues.apache.org/jira/browse/PROTON-1587
[
https://issues.apache.org/jira/browse/DISPATCH-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved DISPATCH-823.
-
Resolution: Fixed
> Improve logging for lost connecti
[
https://issues.apache.org/jira/browse/DISPATCH-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16162880#comment-16162880
]
Gordon Sim commented on DISPATCH-822:
-
Yes, it sounds exactly like that. It is not fixed
[
https://issues.apache.org/jira/browse/DISPATCH-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated DISPATCH-823:
Attachment: DISPATCH-823.patch
This ensures that:
(a) any underlying transport error is reported
[
https://issues.apache.org/jira/browse/DISPATCH-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim reassigned DISPATCH-823:
---
Assignee: (was: Gordon Sim)
> Improve logging for lost connecti
Gordon Sim created DISPATCH-823:
---
Summary: Improve logging for lost connections
Key: DISPATCH-823
URL: https://issues.apache.org/jira/browse/DISPATCH-823
Project: Qpid Dispatch
Issue Type: Bug
[
https://issues.apache.org/jira/browse/DISPATCH-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated DISPATCH-822:
Attachment: DISPATCH-822-reproducer.tgz
Reproducer attached. Untar the archive, then:
(1) start
Gordon Sim created DISPATCH-822:
---
Summary: loss of SSL connection breaks other SSL connections
Key: DISPATCH-822
URL: https://issues.apache.org/jira/browse/DISPATCH-822
Project: Qpid Dispatch
[
https://issues.apache.org/jira/browse/DISPATCH-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated DISPATCH-821:
Attachment: dispatch_821.py
Reproducer. Run against a router, to (a) create and address, foo, (b
Gordon Sim created DISPATCH-821:
---
Summary: recreating an address immediately after deleting it,
results in error
Key: DISPATCH-821
URL: https://issues.apache.org/jira/browse/DISPATCH-821
Project: Qpid
[
https://issues.apache.org/jira/browse/DISPATCH-820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated DISPATCH-820:
Description:
(1) start two connected routers
(2) connect to one and open a sending link
Gordon Sim created DISPATCH-820:
---
Summary: double delete of address hash
Key: DISPATCH-820
URL: https://issues.apache.org/jira/browse/DISPATCH-820
Project: Qpid Dispatch
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PROTON-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim closed PROTON-1555.
--
Resolution: Not A Bug
> SASL External and missing initial-respo
[
https://issues.apache.org/jira/browse/PROTON-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim reassigned PROTON-1555:
--
Assignee: Gordon Sim
> SASL External and missing initial-respo
On 24/08/17 16:38, Alan Conway wrote:
What I'm getting at is if we have an AMQP server that acts as multiple
hosts, then you probably want to co-ordinate between whatever you
regard as the 'host' (SNI, SASL, AMQP, please God let them be the same)
and SASL realms.
Agreed. SNI, sasl-init and
On 24/08/17 13:42, Alan Conway wrote:
On Thu, 2017-08-24 at 08:17 +0100, Gordon Sim wrote:
On Tue, Aug 22, 2017, at 11:15 AM, Alan Conway wrote:
Reading the SASL docs I think we also need to allow SASL realm to be
set on a per-connection basis, in CONNECTION_BOUND - and expose that in
all
On 24/08/17 05:53, Andrew Stitcher wrote:
I think connection bound is after authentication - unless I'm forgetting
things due to vacation all events are after authentication.
Having been poking around in this area recently, I can confirm that
CONNECTION_BOUND will occur *before* the
[
https://issues.apache.org/jira/browse/DISPATCH-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved DISPATCH-810.
-
Resolution: Fixed
> auto link fails to trig
[
https://issues.apache.org/jira/browse/QPID-7859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16135298#comment-16135298
]
Gordon Sim commented on QPID-7859:
--
[~gemmellr] No, it should not! I'll fix that now.
> [AMQP
[
https://issues.apache.org/jira/browse/DISPATCH-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133154#comment-16133154
]
Gordon Sim commented on DISPATCH-810:
-
See https://reviews.apache.org/r/61741/ for fix.
> auto l
Gordon Sim created DISPATCH-810:
---
Summary: auto link fails to trigger
Key: DISPATCH-810
URL: https://issues.apache.org/jira/browse/DISPATCH-810
Project: Qpid Dispatch
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim reassigned PROTON-1542:
--
Assignee: (was: Gordon Sim)
> hostname should be set on sasl-i
[
https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim reassigned PROTON-1542:
--
Assignee: Gordon Sim (was: Justin Ross)
> hostname should be set on sasl-i
[
https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16130139#comment-16130139
]
Gordon Sim commented on PROTON-1542:
https://issues.apache.org/jira/browse/PROTON-1535 allows
[
https://issues.apache.org/jira/browse/PROTON-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16130138#comment-16130138
]
Gordon Sim commented on PROTON-1535:
See https://issues.apache.org/jira/browse/PROTON-1542
[
https://issues.apache.org/jira/browse/PROTON-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16130137#comment-16130137
]
Gordon Sim commented on PROTON-1500:
See https://issues.apache.org/jira/browse/PROTON-1542 for a JIRA
[
https://issues.apache.org/jira/browse/PROTON-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated PROTON-1500:
---
Comment: was deleted
(was: See https://issues.apache.org/jira/browse/PROTON-1542 for a JIRA covering
Gordon Sim created PROTON-1542:
--
Summary: hostname should be set on sasl-init
Key: PROTON-1542
URL: https://issues.apache.org/jira/browse/PROTON-1542
Project: Qpid Proton
Issue Type: Bug
[
https://issues.apache.org/jira/browse/DISPATCH-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved DISPATCH-775.
-
Resolution: Fixed
> allow authentication against a remote ser
[
https://issues.apache.org/jira/browse/PROTON-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved PROTON-1535.
Resolution: Fixed
> Can't set hostname on SASL-INIT through sasl plugin interf
[
https://issues.apache.org/jira/browse/PROTON-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123867#comment-16123867
]
Gordon Sim commented on PROTON-1535:
Yes, it is compliant. By 'doing this in general' do you mean
[
https://issues.apache.org/jira/browse/PROTON-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated PROTON-1535:
---
Summary: Can't set hostname on SASL-INIT through sasl plugin interface
(was: Can't set hostname
> On Aug. 11, 2017, 5:46 p.m., Andrew Stitcher wrote:
> > This looks fine.
> >
> > Can you just confirm that adding this extra field to the frame is still
> > amqp 1.0 protocol compliant (I dont have time to check that today).
>
> Gordon Sim wrote:
>
ply, visit:
https://reviews.apache.org/r/61596/#review182725
-------
On Aug. 11, 2017, 5:24 p.m., Gordon Sim wrote:
>
> ---
> This is an automatically generated e-mail. To r
[
https://issues.apache.org/jira/browse/PROTON-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123677#comment-16123677
]
Gordon Sim commented on PROTON-1535:
Possible fix: https://reviews.apache.org/r/61596/
> Can't
://reviews.apache.org/r/61596/diff/1/
Testing
---
Thanks,
Gordon Sim
[
https://issues.apache.org/jira/browse/DISPATCH-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated DISPATCH-804:
Priority: Major (was: Blocker)
Downgrading. Blocker was a bit of an extreme reaction, hadn't
[
https://issues.apache.org/jira/browse/DISPATCH-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved DISPATCH-804.
-
Resolution: Fixed
> connectors ignore addr
> --
>
>
[
https://issues.apache.org/jira/browse/DISPATCH-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123536#comment-16123536
]
Gordon Sim commented on DISPATCH-804:
-
Possible fix:
{noformat}
diff --git a/src
[
https://issues.apache.org/jira/browse/DISPATCH-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123519#comment-16123519
]
Gordon Sim commented on DISPATCH-804:
-
Looks to be related to https://issues.apache.org/jira/browse
Gordon Sim created DISPATCH-804:
---
Summary: connectors ignore addr
Key: DISPATCH-804
URL: https://issues.apache.org/jira/browse/DISPATCH-804
Project: Qpid Dispatch
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/PROTON-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated PROTON-927:
--
Description: They should instead be encoded as null (since there is no
default). (Possibly affects all
Gordon Sim created PROTON-1535:
--
Summary: Can't set hostname on SASL-INIT
Key: PROTON-1535
URL: https://issues.apache.org/jira/browse/PROTON-1535
Project: Qpid Proton
Issue Type: Bug
[
https://issues.apache.org/jira/browse/DISPATCH-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16120513#comment-16120513
]
Gordon Sim commented on DISPATCH-803:
-
[~aconway]:
> The original requirement is to prevent a
Gordon Sim created DISPATCH-803:
---
Summary: refuse attach to undefined addresses
Key: DISPATCH-803
URL: https://issues.apache.org/jira/browse/DISPATCH-803
Project: Qpid Dispatch
Issue Type
[
https://issues.apache.org/jira/browse/DISPATCH-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated DISPATCH-803:
Fix Version/s: 1.0.0
> refuse attach to undefined addres
[
https://issues.apache.org/jira/browse/QPID-7876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved QPID-7876.
--
Resolution: Fixed
> qpid-route does not properly consider src-local when matching brid
[
https://issues.apache.org/jira/browse/PROTON-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved PROTON-1530.
Resolution: Fixed
> python client does not delegate unhandled events on txn controller l
Gordon Sim created PROTON-1530:
--
Summary: python client does not delegate unhandled events on txn
controller link
Key: PROTON-1530
URL: https://issues.apache.org/jira/browse/PROTON-1530
Project: Qpid
[
https://issues.apache.org/jira/browse/QPID-7876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114611#comment-16114611
]
Gordon Sim commented on QPID-7876:
--
Thanks Chris, that's a useful test! Ran before and after your latest
[
https://issues.apache.org/jira/browse/QPID-7876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16112530#comment-16112530
]
Gordon Sim commented on QPID-7876:
--
Sorry! I should have spotted that before committing. (A gap
[
https://issues.apache.org/jira/browse/QPID-7876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16112517#comment-16112517
]
Gordon Sim commented on QPID-7876:
--
Yes, I think that name should be fine. Its better than what the broker
[
https://issues.apache.org/jira/browse/QPID-7874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved QPID-7874.
--
Resolution: Fixed
> qpid-route performs an unnecessary link check when adding rou
[
https://issues.apache.org/jira/browse/QPID-7874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16112275#comment-16112275
]
Gordon Sim commented on QPID-7874:
--
Thanks again Chris!
> qpid-route performs an unnecessary link ch
[
https://issues.apache.org/jira/browse/QPID-7876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16111716#comment-16111716
]
Gordon Sim commented on QPID-7876:
--
Thanks again Chris!
> qpid-route does not properly consider src-lo
[
https://issues.apache.org/jira/browse/QPID-7876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved QPID-7876.
--
Resolution: Fixed
> qpid-route does not properly consider src-local when matching brid
[
https://issues.apache.org/jira/browse/QPID-7875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16111714#comment-16111714
]
Gordon Sim commented on QPID-7875:
--
Thanks Chris!
> qpid-route fetches links multiple times when delet
[
https://issues.apache.org/jira/browse/QPID-7875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved QPID-7875.
--
Resolution: Fixed
> qpid-route fetches links multiple times when deleting rou
[
https://issues.apache.org/jira/browse/QPID-7874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16111622#comment-16111622
]
Gordon Sim commented on QPID-7874:
--
I think it might be good to make it configurable. Though as you say
[
https://issues.apache.org/jira/browse/QPID-7859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved QPID-7859.
--
Resolution: Fixed
> [AMQP 1.0]: sending message to an exchange that exceeds the limit of a qu
Gordon Sim created QPID-7859:
Summary: [AMQP 1.0]: sending message to an exchange that exceeds
the limit of a queue with reject policy results in connection being closed
Key: QPID-7859
URL: https://issues.apache.org
On 12/07/17 14:40, Mestiri Meher wrote:
Hello,
How are you doing ?
I'm new to qpid and facing some issues with the basics;
I don't find a tuto or a step by step example using java to create :
Exchange zone, queues, binding, consumer, producer.
The most important thing that i can't find is
401 - 500 of 3830 matches
Mail list logo
