[jira] [Commented] (PROTON-1200) Improve the C++ binding documentation, round two
[ https://issues.apache.org/jira/browse/PROTON-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290139#comment-15290139 ] Justin Ross commented on PROTON-1200: - Reviewed by me. Approved for 0.13.0. > Improve the C++ binding documentation, round two > > > Key: PROTON-1200 > URL: https://issues.apache.org/jira/browse/PROTON-1200 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross > Fix For: 0.13.0 > > -- 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] (PROTON-1203) Improve header file usage consistency
[ https://issues.apache.org/jira/browse/PROTON-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289979#comment-15289979 ] ASF subversion and git services commented on PROTON-1203: - Commit e80f6a51dab9879645d2621346ea1d0a6616db1f in qpid-proton's branch refs/heads/0.13.x from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=e80f6a5 ] PROTON-1203: Change header files include usage: - In exported headers always use #include "" and relative paths to other proton-cpp include files - In exported headers always use #include <> for proton-c includes - Only use #include "" for proton cpp files from within cpp implementation - Always use #include <> for proton-c header files within cpp implementation - Make all examples use #include <> for proton cpp includes - Move the exported header files config.hpp and export.hpp to internal - Don't include config.hpp directly in examples as it is an internal header file - Reinstate a more compatible version of fake_cpp11.hpp > Improve header file usage consistency > - > > Key: PROTON-1203 > URL: https://issues.apache.org/jira/browse/PROTON-1203 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > -- 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] (PROTON-1203) Improve header file usage consistency
[ https://issues.apache.org/jira/browse/PROTON-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289980#comment-15289980 ] ASF subversion and git services commented on PROTON-1203: - Commit 7c9731496337a5228202f550334afb84abcc2a8e in qpid-proton's branch refs/heads/0.13.x from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=7c97314 ] PROTON-1203: Small header file fixes > Improve header file usage consistency > - > > Key: PROTON-1203 > URL: https://issues.apache.org/jira/browse/PROTON-1203 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > -- 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] (PROTON-1200) Improve the C++ binding documentation, round two
[ https://issues.apache.org/jira/browse/PROTON-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289953#comment-15289953 ] Alan Conway commented on PROTON-1200: - Request to include in 0.13.0: doc changes in [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=1510882 ] > Improve the C++ binding documentation, round two > > > Key: PROTON-1200 > URL: https://issues.apache.org/jira/browse/PROTON-1200 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross > Fix For: 0.13.0 > > -- 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] (PROTON-1200) Improve the C++ binding documentation, round two
[ https://issues.apache.org/jira/browse/PROTON-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289948#comment-15289948 ] ASF subversion and git services commented on PROTON-1200: - Commit 15108822e71699826b8ec84eabe5314fc8dd6ce5 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=1510882 ] PROTON-1200: c++ multi-threaded and IO integration documentation. - updated documentation - removed/privatized unused functions in thread_safe.hpp > Improve the C++ binding documentation, round two > > > Key: PROTON-1200 > URL: https://issues.apache.org/jira/browse/PROTON-1200 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross > Fix For: 0.13.0 > > -- 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] (PROTON-1203) Improve header file usage consistency
[ https://issues.apache.org/jira/browse/PROTON-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289938#comment-15289938 ] Justin Ross commented on PROTON-1203: - Reviewed by Alan. Approved for 0.13.0. > Improve header file usage consistency > - > > Key: PROTON-1203 > URL: https://issues.apache.org/jira/browse/PROTON-1203 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > -- 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] (PROTON-1203) Improve header file usage consistency
[ https://issues.apache.org/jira/browse/PROTON-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289903#comment-15289903 ] Alan Conway commented on PROTON-1203: - Approved for 0.13.0 > Improve header file usage consistency > - > > Key: PROTON-1203 > URL: https://issues.apache.org/jira/browse/PROTON-1203 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > -- 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] (PROTON-1202) The python setup script should only extract the C sources from the dist tar
[ https://issues.apache.org/jira/browse/PROTON-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289811#comment-15289811 ] Justin Ross commented on PROTON-1202: - Reviewed by Alan. Approved for 0.13.0. > The python setup script should only extract the C sources from the dist tar > --- > > Key: PROTON-1202 > URL: https://issues.apache.org/jira/browse/PROTON-1202 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.11.1, 0.12.2 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Blocker > Fix For: 0.13.0 > > > The python setup.py script extracts the entire downloaded proton source tar > file. We only need the relevant C files to build the shared object. -- 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] (PROTON-1207) c++: Add timed tasks to container API
Alan Conway created PROTON-1207: --- Summary: c++: Add timed tasks to container API Key: PROTON-1207 URL: https://issues.apache.org/jira/browse/PROTON-1207 Project: Qpid Proton Issue Type: Bug Components: cpp-binding Affects Versions: 0.12.2 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.13.0 The new container interface does not provide timers, need to restore this functionality. -- 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] [Resolved] (QPID-7268) message sent over 0-10 can't be received over 1.0
[ https://issues.apache.org/jira/browse/QPID-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-7268. -- Resolution: Fixed > message sent over 0-10 can't be received over 1.0 > - > > Key: QPID-7268 > URL: https://issues.apache.org/jira/browse/QPID-7268 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: qpid-java-6.0.3 >Reporter: Gordon Sim >Assignee: Alex Rudyy > Fix For: qpid-java-6.0.3, qpid-java-6.1 > > > To reproduce, define a queue to which a message is sent over AMQP 0-10 then > try to receive it using AMQP 1.0. A transfer frame is sent, but ot appears > (base don proton-c's tracing at least) to have no payload. -- 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] [Resolved] (QPID-7271) Improve exception handling for PlainSaslServer
[ https://issues.apache.org/jira/browse/QPID-7271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-7271. -- Resolution: Fixed Assignee: (was: Rob Godfrey) > Improve exception handling for PlainSaslServer > -- > > Key: QPID-7271 > URL: https://issues.apache.org/jira/browse/QPID-7271 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey > Fix For: qpid-java-6.0.3, qpid-java-6.1 > > > Rather than let the IllegalArgumentException fall through to be dealt with by > the next level up, throw an explicit SaslException. -- 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-7268) message sent over 0-10 can't be received over 1.0
[ https://issues.apache.org/jira/browse/QPID-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289731#comment-15289731 ] ASF subversion and git services commented on QPID-7268: --- Commit 175 from oru...@apache.org in branch 'java/branches/6.0.x' [ https://svn.apache.org/r175 ] QPID-7268 : Messages converted to AMQP 1.0 lose their body merged from trunk using svn merge -c 1744157 ^/qpid/java/trunk conflicts resolved manually > message sent over 0-10 can't be received over 1.0 > - > > Key: QPID-7268 > URL: https://issues.apache.org/jira/browse/QPID-7268 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: qpid-java-6.0.3 >Reporter: Gordon Sim >Assignee: Alex Rudyy > Fix For: qpid-java-6.0.3, qpid-java-6.1 > > > To reproduce, define a queue to which a message is sent over AMQP 0-10 then > try to receive it using AMQP 1.0. A transfer frame is sent, but ot appears > (base don proton-c's tracing at least) to have no payload. -- 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] (PROTON-1206) c++ core dump in modified helloworld.cpp example
Alan Conway created PROTON-1206:
---
Summary: c++ core dump in modified helloworld.cpp example
Key: PROTON-1206
URL: https://issues.apache.org/jira/browse/PROTON-1206
Project: Qpid Proton
Issue Type: Bug
Components: cpp-binding
Affects Versions: 0.12.2
Reporter: Alan Conway
Assignee: Alan Conway
Fix For: 0.13.0
With the following change the helloworld.cpp example core dumps:
{code}
modified examples/cpp/helloworld.cpp
@@ -38,10 +38,6 @@ class hello_world : public proton::messaging_handler {
hello_world(const std::string& u) : url(u) {}
void on_container_start(proton::container& c) OVERRIDE {
-c.connect(url);
-}
-
-void on_connection_open(proton::connection& c) OVERRIDE {
c.open_receiver(url.path());
c.open_sender(url.path());
}
{code}
--
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] (PROTON-1203) Improve header file usage consistency
[ https://issues.apache.org/jira/browse/PROTON-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289696#comment-15289696 ] ASF subversion and git services commented on PROTON-1203: - Commit 906881bf5d4c4ccf4ffbb8dd550a1dd2794835cf in qpid-proton's branch refs/heads/master from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=906881b ] PROTON-1203: Small header file fixes > Improve header file usage consistency > - > > Key: PROTON-1203 > URL: https://issues.apache.org/jira/browse/PROTON-1203 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > -- 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] (PROTON-1205) c++: Replace default arguments with multiple overloads in container API
[ https://issues.apache.org/jira/browse/PROTON-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289621#comment-15289621 ] ASF subversion and git services commented on PROTON-1205: - Commit 4ce66bd3014651c8d528d3cdb9519121b9fb98f5 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=4ce66bd ] PROTON-1205: c++ change default arguments to multiple overloads > c++: Replace default arguments with multiple overloads in container API > > > Key: PROTON-1205 > URL: https://issues.apache.org/jira/browse/PROTON-1205 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: 0.12.2 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.13.0 > > > Summary says it all. -- 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] (PROTON-1205) c++: Replace default arguments with multiple overloads in container API
Alan Conway created PROTON-1205: --- Summary: c++: Replace default arguments with multiple overloads in container API Key: PROTON-1205 URL: https://issues.apache.org/jira/browse/PROTON-1205 Project: Qpid Proton Issue Type: Improvement Components: cpp-binding Affects Versions: 0.12.2 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.13.0 Summary says it all. -- 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] (PROTON-1202) The python setup script should only extract the C sources from the dist tar
[ https://issues.apache.org/jira/browse/PROTON-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289523#comment-15289523 ] Alan Conway commented on PROTON-1202: - Approved for 0.13.0 > The python setup script should only extract the C sources from the dist tar > --- > > Key: PROTON-1202 > URL: https://issues.apache.org/jira/browse/PROTON-1202 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.11.1, 0.12.2 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Blocker > Fix For: 0.13.0 > > > The python setup.py script extracts the entire downloaded proton source tar > file. We only need the relevant C files to build the shared object. -- 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] [Updated] (DISPATCH-339) The change from 'routerId' to 'id' and 'addr' to 'host' configuration option is not backwards compatible
[
https://issues.apache.org/jira/browse/DISPATCH-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek updated DISPATCH-339:
Attachment: rb_local.conf
ra_local.conf
Attaching ra_local.conf and rb_local.conf. Variants of ra.conf and rb.conf
changed that both routers can run on the same machine.
> The change from 'routerId' to 'id' and 'addr' to 'host' configuration option
> is not backwards compatible
>
>
> Key: DISPATCH-339
> URL: https://issues.apache.org/jira/browse/DISPATCH-339
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 0.6.0
>Reporter: Jiri Danek
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
> Attachments: ra.conf, ra_.conf, ra_local.conf, rb.conf, rb_.conf,
> rb_local.conf
>
>
> I started qdrouterd with the following configuration
> {noformat}
> router {
> mode: interior
> routerId: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> {noformat}
> Running qdstat then prints that Router id is None.
> {code:title=qdstat -g|borderStyle=solid}
> Router Statistics
> attr value
> =
> Mode interior
> Area 0
> Router Id None
> Address Count 0
> Link Count 0
> Node Count 0
> {code}
> Other commands, for example
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> work correctly in this respect.
> If I update my config and use {{id}} instead of {{routerId}}, then qdstat
> prints correct information.
> I'd expect that the config that worked before the routerId/id change would
> continue working.
> If I use {{addr}} in my connectors, then my router does not connect to other
> routers. I had to update the config to using {{host}} and only then it worked
> for me.
> {noformat}
> router {
> mode: interior
> id: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> connector {
> name: to.r.b
> addr: {{ rb_ip }}
> port: 50001
> role: inter-router
> }
> {noformat}
> {noformat}
> router {
> mode: interior
> id: r.b
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> listener {
> role: inter-router
> addr: 0.0.0.0
> port: 50001
> authenticatePeer: no
> }
> {noformat}
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> After I change addr to host and restart both routers,
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)-
> r.b- 1
> {code}
> NOTE: I noticed that if I use routerId or addr, no deprecation warning is
> shown in qdrouterd output with the default log level. As far as I can
> remember, there are deprecation warnings for some features like fixedAddress,
> I think.
--
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] [Reopened] (DISPATCH-339) The change from 'routerId' to 'id' and 'addr' to 'host' configuration option is not backwards compatible
[
https://issues.apache.org/jira/browse/DISPATCH-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek reopened DISPATCH-339:
-
I compiled from git. I can confirm that the routerId/id part is solved. Command
qdstat -n prints what it should print and routerId deprecation message shows.
What is not solved is the second part, the addr/host part. The situation there
is still the way I described in previous comment.
I think that it is important to really use two machines the way I have it set
up. Since @Ganesh could not reproduce this second part on his machine (he is
using single machine), I now tried running it on single machine as well using
the same config as he did (ra_local.conf and rb_local.conf) and I was not able
to replicate it that way either.
> The change from 'routerId' to 'id' and 'addr' to 'host' configuration option
> is not backwards compatible
>
>
> Key: DISPATCH-339
> URL: https://issues.apache.org/jira/browse/DISPATCH-339
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 0.6.0
>Reporter: Jiri Danek
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
> Attachments: ra.conf, ra_.conf, rb.conf, rb_.conf
>
>
> I started qdrouterd with the following configuration
> {noformat}
> router {
> mode: interior
> routerId: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> {noformat}
> Running qdstat then prints that Router id is None.
> {code:title=qdstat -g|borderStyle=solid}
> Router Statistics
> attr value
> =
> Mode interior
> Area 0
> Router Id None
> Address Count 0
> Link Count 0
> Node Count 0
> {code}
> Other commands, for example
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> work correctly in this respect.
> If I update my config and use {{id}} instead of {{routerId}}, then qdstat
> prints correct information.
> I'd expect that the config that worked before the routerId/id change would
> continue working.
> If I use {{addr}} in my connectors, then my router does not connect to other
> routers. I had to update the config to using {{host}} and only then it worked
> for me.
> {noformat}
> router {
> mode: interior
> id: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> connector {
> name: to.r.b
> addr: {{ rb_ip }}
> port: 50001
> role: inter-router
> }
> {noformat}
> {noformat}
> router {
> mode: interior
> id: r.b
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> listener {
> role: inter-router
> addr: 0.0.0.0
> port: 50001
> authenticatePeer: no
> }
> {noformat}
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> After I change addr to host and restart both routers,
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)-
> r.b- 1
> {code}
> NOTE: I noticed that if I use routerId or addr, no deprecation warning is
> shown in qdrouterd output with the default log level. As far as I can
> remember, there are deprecation warnings for some features like fixedAddress,
> I think.
--
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-7271) Improve exception handling for PlainSaslServer
[ https://issues.apache.org/jira/browse/QPID-7271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289205#comment-15289205 ] ASF subversion and git services commented on QPID-7271: --- Commit 1744430 from oru...@apache.org in branch 'java/branches/6.0.x' [ https://svn.apache.org/r1744430 ] QPID-7271 : Improve exception handling merged from trunk using svn merge -c 1744403 ^/qpid/java/trunk > Improve exception handling for PlainSaslServer > -- > > Key: QPID-7271 > URL: https://issues.apache.org/jira/browse/QPID-7271 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: qpid-java-6.0.3, qpid-java-6.1 > > > Rather than let the IllegalArgumentException fall through to be dealt with by > the next level up, throw an explicit SaslException. -- 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] [Resolved] (QPID-6096) java broker doesn't indicate that port is already in use
[ https://issues.apache.org/jira/browse/QPID-6096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-6096. -- Resolution: Fixed > java broker doesn't indicate that port is already in use > > > Key: QPID-6096 > URL: https://issues.apache.org/jira/browse/QPID-6096 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.30, 0.31 >Reporter: Gordon Sim >Assignee: Rob Godfrey >Priority: Minor > Fix For: qpid-java-6.0.3, qpid-java-6.1 > > > If you have something listening on 5672 when you start the java broker, it > will start but won't indicate that it can't listen to that port. Would be > nice to have an error or something as it will I suspect be an increasingly > common issue as more things may be listening on that port. -- 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] [Issue Comment Deleted] (QPID-7269) broker issues disposition for delivery that is already settled
[
https://issues.apache.org/jira/browse/QPID-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7269:
-
Comment: was deleted
(was: Merged into 6.0.x in commit under revision
[https://svn.apache.org/r1744426])
> broker issues disposition for delivery that is already settled
> --
>
> Key: QPID-7269
> URL: https://issues.apache.org/jira/browse/QPID-7269
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0.3
>Reporter: Gordon Sim
>Assignee: Alex Rudyy
> Fix For: qpid-java-6.0.3, qpid-java-6.1
>
>
> E.g. for proton python helloworld example:
> {noformat}
> [0x55610aa0de20]: <- AMQP
> [0x55610aa0de20]: -> AMQP
> [0x55610aa0de20]:0 -> @open(16)
> [container-id="1cc695d7-3588-4730-848e-1047eda87f8b", hostname="localhost",
> channel-max=32767]
> [0x55610aa0de20]:0 -> @begin(17) [next-outgoing-id=1,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x55610aa0de20]:0 -> @attach(18)
> [name="1cc695d7-3588-4730-848e-1047eda87f8b-examples", handle=0, role=true,
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples",
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0,
> timeout=0, dynamic=false], initial-delivery-count=0]
> [0x55610aa0de20]:0 -> @flow(19) [incoming-window=2147483647,
> next-outgoing-id=1, outgoing-window=2147483647, handle=0, delivery-count=0,
> link-credit=10, drain=false]
> [0x55610aa0de20]:0 <- @open(16)
> [container-id="21188a24-ee12-45d2-a027-a630d7e3f10c", max-frame-size=32768,
> channel-max=255, idle-time-out=0, properties={:product="qpid",
> :version="6.0.3", :"qpid.build"="Unversioned directory",
> :"qpid.instance_name"="Broker"}]
> [0x55610aa0de20]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
> incoming-window=2048, outgoing-window=2048]
> [0x55610aa0de20]:0 <- @attach(18)
> [name="1cc695d7-3588-4730-848e-1047eda87f8b-examples", handle=0, role=false,
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples",
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0,
> timeout=0, dynamic=false], initial-delivery-count=0]
> [0x55610aa0de20]:0 <- @transfer(20) [handle=0, delivery-id=0,
> delivery-tag=b"\x00\x00\x00\x00\x00\x00\x00\x00", message-format=0] (78)
> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa1\x0cHello
> World!"
> Hello World!
> [0x55610aa0de20]:0 -> @disposition(21) [role=true, first=0, last=0,
> settled=true, state=@accepted(36) []]
> [0x55610aa0de20]:0 -> @close(24) []
> [0x55610aa0de20]: -> EOS
> [0x55610aa0de20]:0 <- @disposition(21) [role=false, first=0, last=0,
> settled=true, state=@accepted(36) []]
> [0x55610aa0de20]:0 <- @flow(19) [next-incoming-id=1, incoming-window=2048,
> next-outgoing-id=1, outgoing-window=2048, handle=0, delivery-count=1,
> link-credit=9, available=0, drain=false, echo=false]
> [0x55610aa0de20]:0 <- @close(24) []
> [0x55610aa0de20]: <- EOS
> {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-7269) broker issues disposition for delivery that is already settled
[
https://issues.apache.org/jira/browse/QPID-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289183#comment-15289183
]
ASF subversion and git services commented on QPID-7269:
---
Commit 1744429 from oru...@apache.org in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1744429 ]
QPID-7269 : Do not issue a disposition update from a sending link when the peer
has already settled the disposition
merged from trunk using
svn merge -c 1744276 ^/qpid/java/trunk
> broker issues disposition for delivery that is already settled
> --
>
> Key: QPID-7269
> URL: https://issues.apache.org/jira/browse/QPID-7269
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0.3
>Reporter: Gordon Sim
>Assignee: Alex Rudyy
> Fix For: qpid-java-6.0.3, qpid-java-6.1
>
>
> E.g. for proton python helloworld example:
> {noformat}
> [0x55610aa0de20]: <- AMQP
> [0x55610aa0de20]: -> AMQP
> [0x55610aa0de20]:0 -> @open(16)
> [container-id="1cc695d7-3588-4730-848e-1047eda87f8b", hostname="localhost",
> channel-max=32767]
> [0x55610aa0de20]:0 -> @begin(17) [next-outgoing-id=1,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x55610aa0de20]:0 -> @attach(18)
> [name="1cc695d7-3588-4730-848e-1047eda87f8b-examples", handle=0, role=true,
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples",
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0,
> timeout=0, dynamic=false], initial-delivery-count=0]
> [0x55610aa0de20]:0 -> @flow(19) [incoming-window=2147483647,
> next-outgoing-id=1, outgoing-window=2147483647, handle=0, delivery-count=0,
> link-credit=10, drain=false]
> [0x55610aa0de20]:0 <- @open(16)
> [container-id="21188a24-ee12-45d2-a027-a630d7e3f10c", max-frame-size=32768,
> channel-max=255, idle-time-out=0, properties={:product="qpid",
> :version="6.0.3", :"qpid.build"="Unversioned directory",
> :"qpid.instance_name"="Broker"}]
> [0x55610aa0de20]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
> incoming-window=2048, outgoing-window=2048]
> [0x55610aa0de20]:0 <- @attach(18)
> [name="1cc695d7-3588-4730-848e-1047eda87f8b-examples", handle=0, role=false,
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples",
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0,
> timeout=0, dynamic=false], initial-delivery-count=0]
> [0x55610aa0de20]:0 <- @transfer(20) [handle=0, delivery-id=0,
> delivery-tag=b"\x00\x00\x00\x00\x00\x00\x00\x00", message-format=0] (78)
> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa1\x0cHello
> World!"
> Hello World!
> [0x55610aa0de20]:0 -> @disposition(21) [role=true, first=0, last=0,
> settled=true, state=@accepted(36) []]
> [0x55610aa0de20]:0 -> @close(24) []
> [0x55610aa0de20]: -> EOS
> [0x55610aa0de20]:0 <- @disposition(21) [role=false, first=0, last=0,
> settled=true, state=@accepted(36) []]
> [0x55610aa0de20]:0 <- @flow(19) [next-incoming-id=1, incoming-window=2048,
> next-outgoing-id=1, outgoing-window=2048, handle=0, delivery-count=1,
> link-credit=9, available=0, drain=false, echo=false]
> [0x55610aa0de20]:0 <- @close(24) []
> [0x55610aa0de20]: <- EOS
> {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] [Resolved] (QPID-7255) Support delivery delay
[ https://issues.apache.org/jira/browse/QPID-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack resolved QPID-7255. Resolution: Fixed > Support delivery delay > -- > > Key: QPID-7255 > URL: https://issues.apache.org/jira/browse/QPID-7255 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Reporter: Keith Wall > Fix For: qpid-java-6.0.3, qpid-java-6.1 > > Attachments: QPID-7255.diff > > > Some enterprise messaging systems provide a delayed delivery feature whereby > a publisher can provide a delivery time when sending the message, with the > Broker taking care of not making the message available to consumers until > that time is reached. The Java Broker should provide the same feature. > In the Java space, JMS 2.0 has standardised this feature, however there is > no reason why the feature could not be made available to older JMS 1.1 > clients using a Qpid specific header. Also if the BURL or ADDR address > could hint to the Producer that delivery delay was required for all messages > produced by it, this would mean message delay could be turned on from > configuration alone. -- 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] (DISPATCH-339) The change from 'routerId' to 'id' and 'addr' to 'host' configuration option is not backwards compatible
[
https://issues.apache.org/jira/browse/DISPATCH-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289174#comment-15289174
]
Ganesh Murthy commented on DISPATCH-339:
At this time, we are unable to add log warning messages if addr is used instead
of host. But the rest of this issue has been fixed.
> The change from 'routerId' to 'id' and 'addr' to 'host' configuration option
> is not backwards compatible
>
>
> Key: DISPATCH-339
> URL: https://issues.apache.org/jira/browse/DISPATCH-339
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 0.6.0
>Reporter: Jiri Danek
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
> Attachments: ra.conf, ra_.conf, rb.conf, rb_.conf
>
>
> I started qdrouterd with the following configuration
> {noformat}
> router {
> mode: interior
> routerId: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> {noformat}
> Running qdstat then prints that Router id is None.
> {code:title=qdstat -g|borderStyle=solid}
> Router Statistics
> attr value
> =
> Mode interior
> Area 0
> Router Id None
> Address Count 0
> Link Count 0
> Node Count 0
> {code}
> Other commands, for example
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> work correctly in this respect.
> If I update my config and use {{id}} instead of {{routerId}}, then qdstat
> prints correct information.
> I'd expect that the config that worked before the routerId/id change would
> continue working.
> If I use {{addr}} in my connectors, then my router does not connect to other
> routers. I had to update the config to using {{host}} and only then it worked
> for me.
> {noformat}
> router {
> mode: interior
> id: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> connector {
> name: to.r.b
> addr: {{ rb_ip }}
> port: 50001
> role: inter-router
> }
> {noformat}
> {noformat}
> router {
> mode: interior
> id: r.b
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> listener {
> role: inter-router
> addr: 0.0.0.0
> port: 50001
> authenticatePeer: no
> }
> {noformat}
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> After I change addr to host and restart both routers,
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)-
> r.b- 1
> {code}
> NOTE: I noticed that if I use routerId or addr, no deprecation warning is
> shown in qdrouterd output with the default log level. As far as I can
> remember, there are deprecation warnings for some features like fixedAddress,
> I think.
--
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] (DISPATCH-339) The change from 'routerId' to 'id' and 'addr' to 'host' configuration option is not backwards compatible
[
https://issues.apache.org/jira/browse/DISPATCH-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289171#comment-15289171
]
ASF subversion and git services commented on DISPATCH-339:
--
Commit 0cc6b2ca6701e24161781c01a33c92ab9ef16aa7 in qpid-dispatch's branch
refs/heads/master from [~ganeshmurthy]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=0cc6b2c ]
DISPATCH-339 - Modified tools/qdstat to display proper router_id. Added warning
log message if routerId is used
> The change from 'routerId' to 'id' and 'addr' to 'host' configuration option
> is not backwards compatible
>
>
> Key: DISPATCH-339
> URL: https://issues.apache.org/jira/browse/DISPATCH-339
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 0.6.0
>Reporter: Jiri Danek
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
> Attachments: ra.conf, ra_.conf, rb.conf, rb_.conf
>
>
> I started qdrouterd with the following configuration
> {noformat}
> router {
> mode: interior
> routerId: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> {noformat}
> Running qdstat then prints that Router id is None.
> {code:title=qdstat -g|borderStyle=solid}
> Router Statistics
> attr value
> =
> Mode interior
> Area 0
> Router Id None
> Address Count 0
> Link Count 0
> Node Count 0
> {code}
> Other commands, for example
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> work correctly in this respect.
> If I update my config and use {{id}} instead of {{routerId}}, then qdstat
> prints correct information.
> I'd expect that the config that worked before the routerId/id change would
> continue working.
> If I use {{addr}} in my connectors, then my router does not connect to other
> routers. I had to update the config to using {{host}} and only then it worked
> for me.
> {noformat}
> router {
> mode: interior
> id: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> connector {
> name: to.r.b
> addr: {{ rb_ip }}
> port: 50001
> role: inter-router
> }
> {noformat}
> {noformat}
> router {
> mode: interior
> id: r.b
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> listener {
> role: inter-router
> addr: 0.0.0.0
> port: 50001
> authenticatePeer: no
> }
> {noformat}
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> After I change addr to host and restart both routers,
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)-
> r.b- 1
> {code}
> NOTE: I noticed that if I use routerId or addr, no deprecation warning is
> shown in qdrouterd output with the default log level. As far as I can
> remember, there are deprecation warnings for some features like fixedAddress,
> I think.
--
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] [Resolved] (DISPATCH-339) The change from 'routerId' to 'id' and 'addr' to 'host' configuration option is not backwards compatible
[
https://issues.apache.org/jira/browse/DISPATCH-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-339.
Resolution: Fixed
Fix Version/s: 0.6.0
> The change from 'routerId' to 'id' and 'addr' to 'host' configuration option
> is not backwards compatible
>
>
> Key: DISPATCH-339
> URL: https://issues.apache.org/jira/browse/DISPATCH-339
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 0.6.0
>Reporter: Jiri Danek
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
> Attachments: ra.conf, ra_.conf, rb.conf, rb_.conf
>
>
> I started qdrouterd with the following configuration
> {noformat}
> router {
> mode: interior
> routerId: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> {noformat}
> Running qdstat then prints that Router id is None.
> {code:title=qdstat -g|borderStyle=solid}
> Router Statistics
> attr value
> =
> Mode interior
> Area 0
> Router Id None
> Address Count 0
> Link Count 0
> Node Count 0
> {code}
> Other commands, for example
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> work correctly in this respect.
> If I update my config and use {{id}} instead of {{routerId}}, then qdstat
> prints correct information.
> I'd expect that the config that worked before the routerId/id change would
> continue working.
> If I use {{addr}} in my connectors, then my router does not connect to other
> routers. I had to update the config to using {{host}} and only then it worked
> for me.
> {noformat}
> router {
> mode: interior
> id: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> connector {
> name: to.r.b
> addr: {{ rb_ip }}
> port: 50001
> role: inter-router
> }
> {noformat}
> {noformat}
> router {
> mode: interior
> id: r.b
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> listener {
> role: inter-router
> addr: 0.0.0.0
> port: 50001
> authenticatePeer: no
> }
> {noformat}
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> After I change addr to host and restart both routers,
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)-
> r.b- 1
> {code}
> NOTE: I noticed that if I use routerId or addr, no deprecation warning is
> shown in qdrouterd output with the default log level. As far as I can
> remember, there are deprecation warnings for some features like fixedAddress,
> I think.
--
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-7269) broker issues disposition for delivery that is already settled
[
https://issues.apache.org/jira/browse/QPID-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289165#comment-15289165
]
Alex Rudyy commented on QPID-7269:
--
Merged into 6.0.x in commit under revision [https://svn.apache.org/r1744426]
> broker issues disposition for delivery that is already settled
> --
>
> Key: QPID-7269
> URL: https://issues.apache.org/jira/browse/QPID-7269
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0.3
>Reporter: Gordon Sim
>Assignee: Alex Rudyy
> Fix For: qpid-java-6.0.3, qpid-java-6.1
>
>
> E.g. for proton python helloworld example:
> {noformat}
> [0x55610aa0de20]: <- AMQP
> [0x55610aa0de20]: -> AMQP
> [0x55610aa0de20]:0 -> @open(16)
> [container-id="1cc695d7-3588-4730-848e-1047eda87f8b", hostname="localhost",
> channel-max=32767]
> [0x55610aa0de20]:0 -> @begin(17) [next-outgoing-id=1,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x55610aa0de20]:0 -> @attach(18)
> [name="1cc695d7-3588-4730-848e-1047eda87f8b-examples", handle=0, role=true,
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples",
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0,
> timeout=0, dynamic=false], initial-delivery-count=0]
> [0x55610aa0de20]:0 -> @flow(19) [incoming-window=2147483647,
> next-outgoing-id=1, outgoing-window=2147483647, handle=0, delivery-count=0,
> link-credit=10, drain=false]
> [0x55610aa0de20]:0 <- @open(16)
> [container-id="21188a24-ee12-45d2-a027-a630d7e3f10c", max-frame-size=32768,
> channel-max=255, idle-time-out=0, properties={:product="qpid",
> :version="6.0.3", :"qpid.build"="Unversioned directory",
> :"qpid.instance_name"="Broker"}]
> [0x55610aa0de20]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
> incoming-window=2048, outgoing-window=2048]
> [0x55610aa0de20]:0 <- @attach(18)
> [name="1cc695d7-3588-4730-848e-1047eda87f8b-examples", handle=0, role=false,
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples",
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0,
> timeout=0, dynamic=false], initial-delivery-count=0]
> [0x55610aa0de20]:0 <- @transfer(20) [handle=0, delivery-id=0,
> delivery-tag=b"\x00\x00\x00\x00\x00\x00\x00\x00", message-format=0] (78)
> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa1\x0cHello
> World!"
> Hello World!
> [0x55610aa0de20]:0 -> @disposition(21) [role=true, first=0, last=0,
> settled=true, state=@accepted(36) []]
> [0x55610aa0de20]:0 -> @close(24) []
> [0x55610aa0de20]: -> EOS
> [0x55610aa0de20]:0 <- @disposition(21) [role=false, first=0, last=0,
> settled=true, state=@accepted(36) []]
> [0x55610aa0de20]:0 <- @flow(19) [next-incoming-id=1, incoming-window=2048,
> next-outgoing-id=1, outgoing-window=2048, handle=0, delivery-count=1,
> link-credit=9, available=0, drain=false, echo=false]
> [0x55610aa0de20]:0 <- @close(24) []
> [0x55610aa0de20]: <- EOS
> {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] [Closed] (QPID-7269) broker issues disposition for delivery that is already settled
[
https://issues.apache.org/jira/browse/QPID-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy closed QPID-7269.
Resolution: Fixed
> broker issues disposition for delivery that is already settled
> --
>
> Key: QPID-7269
> URL: https://issues.apache.org/jira/browse/QPID-7269
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0.3
>Reporter: Gordon Sim
>Assignee: Alex Rudyy
> Fix For: qpid-java-6.0.3, qpid-java-6.1
>
>
> E.g. for proton python helloworld example:
> {noformat}
> [0x55610aa0de20]: <- AMQP
> [0x55610aa0de20]: -> AMQP
> [0x55610aa0de20]:0 -> @open(16)
> [container-id="1cc695d7-3588-4730-848e-1047eda87f8b", hostname="localhost",
> channel-max=32767]
> [0x55610aa0de20]:0 -> @begin(17) [next-outgoing-id=1,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x55610aa0de20]:0 -> @attach(18)
> [name="1cc695d7-3588-4730-848e-1047eda87f8b-examples", handle=0, role=true,
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples",
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0,
> timeout=0, dynamic=false], initial-delivery-count=0]
> [0x55610aa0de20]:0 -> @flow(19) [incoming-window=2147483647,
> next-outgoing-id=1, outgoing-window=2147483647, handle=0, delivery-count=0,
> link-credit=10, drain=false]
> [0x55610aa0de20]:0 <- @open(16)
> [container-id="21188a24-ee12-45d2-a027-a630d7e3f10c", max-frame-size=32768,
> channel-max=255, idle-time-out=0, properties={:product="qpid",
> :version="6.0.3", :"qpid.build"="Unversioned directory",
> :"qpid.instance_name"="Broker"}]
> [0x55610aa0de20]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
> incoming-window=2048, outgoing-window=2048]
> [0x55610aa0de20]:0 <- @attach(18)
> [name="1cc695d7-3588-4730-848e-1047eda87f8b-examples", handle=0, role=false,
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples",
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0,
> timeout=0, dynamic=false], initial-delivery-count=0]
> [0x55610aa0de20]:0 <- @transfer(20) [handle=0, delivery-id=0,
> delivery-tag=b"\x00\x00\x00\x00\x00\x00\x00\x00", message-format=0] (78)
> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa1\x0cHello
> World!"
> Hello World!
> [0x55610aa0de20]:0 -> @disposition(21) [role=true, first=0, last=0,
> settled=true, state=@accepted(36) []]
> [0x55610aa0de20]:0 -> @close(24) []
> [0x55610aa0de20]: -> EOS
> [0x55610aa0de20]:0 <- @disposition(21) [role=false, first=0, last=0,
> settled=true, state=@accepted(36) []]
> [0x55610aa0de20]:0 <- @flow(19) [next-incoming-id=1, incoming-window=2048,
> next-outgoing-id=1, outgoing-window=2048, handle=0, delivery-count=1,
> link-credit=9, available=0, drain=false, echo=false]
> [0x55610aa0de20]:0 <- @close(24) []
> [0x55610aa0de20]: <- EOS
> {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-6096) java broker doesn't indicate that port is already in use
[ https://issues.apache.org/jira/browse/QPID-6096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289162#comment-15289162 ] ASF subversion and git services commented on QPID-6096: --- Commit 1744426 from oru...@apache.org in branch 'java/branches/6.0.x' [ https://svn.apache.org/r1744426 ] QPID-6096 : Add more obvious logging on failure to bind ports / other broker child failures merged from trunk using svn merge -c 1744123 ^/qpid/java/trunk > java broker doesn't indicate that port is already in use > > > Key: QPID-6096 > URL: https://issues.apache.org/jira/browse/QPID-6096 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.30, 0.31 >Reporter: Gordon Sim >Assignee: Rob Godfrey >Priority: Minor > Fix For: qpid-java-6.0.3, qpid-java-6.1 > > > If you have something listening on 5672 when you start the java broker, it > will start but won't indicate that it can't listen to that port. Would be > nice to have an error or something as it will I suspect be an increasingly > common issue as more things may be listening on that port. -- 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-7268) message sent over 0-10 can't be received over 1.0
[ https://issues.apache.org/jira/browse/QPID-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289144#comment-15289144 ] Alex Rudyy commented on QPID-7268: -- The changes look reasonable. We should port them into 6.0.3 > message sent over 0-10 can't be received over 1.0 > - > > Key: QPID-7268 > URL: https://issues.apache.org/jira/browse/QPID-7268 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: qpid-java-6.0.3 >Reporter: Gordon Sim >Assignee: Rob Godfrey > Fix For: qpid-java-6.0.3, qpid-java-6.1 > > > To reproduce, define a queue to which a message is sent over AMQP 0-10 then > try to receive it using AMQP 1.0. A transfer frame is sent, but ot appears > (base don proton-c's tracing at least) to have no payload. -- 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] [Reopened] (QPID-7268) message sent over 0-10 can't be received over 1.0
[ https://issues.apache.org/jira/browse/QPID-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reopened QPID-7268: -- Assignee: Alex Rudyy (was: Rob Godfrey) Reopening the issue for merging into 6.0.x branch > message sent over 0-10 can't be received over 1.0 > - > > Key: QPID-7268 > URL: https://issues.apache.org/jira/browse/QPID-7268 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: qpid-java-6.0.3 >Reporter: Gordon Sim >Assignee: Alex Rudyy > Fix For: qpid-java-6.0.3, qpid-java-6.1 > > > To reproduce, define a queue to which a message is sent over AMQP 0-10 then > try to receive it using AMQP 1.0. A transfer frame is sent, but ot appears > (base don proton-c's tracing at least) to have no payload. -- 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] [Updated] (QPID-7269) broker issues disposition for delivery that is already settled
[
https://issues.apache.org/jira/browse/QPID-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7269:
-
Fix Version/s: qpid-java-6.0.3
> broker issues disposition for delivery that is already settled
> --
>
> Key: QPID-7269
> URL: https://issues.apache.org/jira/browse/QPID-7269
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0.3
>Reporter: Gordon Sim
>Assignee: Rob Godfrey
> Fix For: qpid-java-6.0.3, qpid-java-6.1
>
>
> E.g. for proton python helloworld example:
> {noformat}
> [0x55610aa0de20]: <- AMQP
> [0x55610aa0de20]: -> AMQP
> [0x55610aa0de20]:0 -> @open(16)
> [container-id="1cc695d7-3588-4730-848e-1047eda87f8b", hostname="localhost",
> channel-max=32767]
> [0x55610aa0de20]:0 -> @begin(17) [next-outgoing-id=1,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x55610aa0de20]:0 -> @attach(18)
> [name="1cc695d7-3588-4730-848e-1047eda87f8b-examples", handle=0, role=true,
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples",
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0,
> timeout=0, dynamic=false], initial-delivery-count=0]
> [0x55610aa0de20]:0 -> @flow(19) [incoming-window=2147483647,
> next-outgoing-id=1, outgoing-window=2147483647, handle=0, delivery-count=0,
> link-credit=10, drain=false]
> [0x55610aa0de20]:0 <- @open(16)
> [container-id="21188a24-ee12-45d2-a027-a630d7e3f10c", max-frame-size=32768,
> channel-max=255, idle-time-out=0, properties={:product="qpid",
> :version="6.0.3", :"qpid.build"="Unversioned directory",
> :"qpid.instance_name"="Broker"}]
> [0x55610aa0de20]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
> incoming-window=2048, outgoing-window=2048]
> [0x55610aa0de20]:0 <- @attach(18)
> [name="1cc695d7-3588-4730-848e-1047eda87f8b-examples", handle=0, role=false,
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples",
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0,
> timeout=0, dynamic=false], initial-delivery-count=0]
> [0x55610aa0de20]:0 <- @transfer(20) [handle=0, delivery-id=0,
> delivery-tag=b"\x00\x00\x00\x00\x00\x00\x00\x00", message-format=0] (78)
> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa1\x0cHello
> World!"
> Hello World!
> [0x55610aa0de20]:0 -> @disposition(21) [role=true, first=0, last=0,
> settled=true, state=@accepted(36) []]
> [0x55610aa0de20]:0 -> @close(24) []
> [0x55610aa0de20]: -> EOS
> [0x55610aa0de20]:0 <- @disposition(21) [role=false, first=0, last=0,
> settled=true, state=@accepted(36) []]
> [0x55610aa0de20]:0 <- @flow(19) [next-incoming-id=1, incoming-window=2048,
> next-outgoing-id=1, outgoing-window=2048, handle=0, delivery-count=1,
> link-credit=9, available=0, drain=false, echo=false]
> [0x55610aa0de20]:0 <- @close(24) []
> [0x55610aa0de20]: <- EOS
> {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] [Reopened] (QPID-7269) broker issues disposition for delivery that is already settled
[
https://issues.apache.org/jira/browse/QPID-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy reopened QPID-7269:
--
Assignee: Alex Rudyy (was: Rob Godfrey)
Reopening this issue for merging into 6.0.x branch
> broker issues disposition for delivery that is already settled
> --
>
> Key: QPID-7269
> URL: https://issues.apache.org/jira/browse/QPID-7269
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0.3
>Reporter: Gordon Sim
>Assignee: Alex Rudyy
> Fix For: qpid-java-6.0.3, qpid-java-6.1
>
>
> E.g. for proton python helloworld example:
> {noformat}
> [0x55610aa0de20]: <- AMQP
> [0x55610aa0de20]: -> AMQP
> [0x55610aa0de20]:0 -> @open(16)
> [container-id="1cc695d7-3588-4730-848e-1047eda87f8b", hostname="localhost",
> channel-max=32767]
> [0x55610aa0de20]:0 -> @begin(17) [next-outgoing-id=1,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x55610aa0de20]:0 -> @attach(18)
> [name="1cc695d7-3588-4730-848e-1047eda87f8b-examples", handle=0, role=true,
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples",
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0,
> timeout=0, dynamic=false], initial-delivery-count=0]
> [0x55610aa0de20]:0 -> @flow(19) [incoming-window=2147483647,
> next-outgoing-id=1, outgoing-window=2147483647, handle=0, delivery-count=0,
> link-credit=10, drain=false]
> [0x55610aa0de20]:0 <- @open(16)
> [container-id="21188a24-ee12-45d2-a027-a630d7e3f10c", max-frame-size=32768,
> channel-max=255, idle-time-out=0, properties={:product="qpid",
> :version="6.0.3", :"qpid.build"="Unversioned directory",
> :"qpid.instance_name"="Broker"}]
> [0x55610aa0de20]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
> incoming-window=2048, outgoing-window=2048]
> [0x55610aa0de20]:0 <- @attach(18)
> [name="1cc695d7-3588-4730-848e-1047eda87f8b-examples", handle=0, role=false,
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples",
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0,
> timeout=0, dynamic=false], initial-delivery-count=0]
> [0x55610aa0de20]:0 <- @transfer(20) [handle=0, delivery-id=0,
> delivery-tag=b"\x00\x00\x00\x00\x00\x00\x00\x00", message-format=0] (78)
> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa1\x0cHello
> World!"
> Hello World!
> [0x55610aa0de20]:0 -> @disposition(21) [role=true, first=0, last=0,
> settled=true, state=@accepted(36) []]
> [0x55610aa0de20]:0 -> @close(24) []
> [0x55610aa0de20]: -> EOS
> [0x55610aa0de20]:0 <- @disposition(21) [role=false, first=0, last=0,
> settled=true, state=@accepted(36) []]
> [0x55610aa0de20]:0 <- @flow(19) [next-incoming-id=1, incoming-window=2048,
> next-outgoing-id=1, outgoing-window=2048, handle=0, delivery-count=1,
> link-credit=9, available=0, drain=false, echo=false]
> [0x55610aa0de20]:0 <- @close(24) []
> [0x55610aa0de20]: <- EOS
> {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-7269) broker issues disposition for delivery that is already settled
[
https://issues.apache.org/jira/browse/QPID-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289150#comment-15289150
]
Alex Rudyy commented on QPID-7269:
--
The change look reasonable to me. We should port it into 6.0.3
> broker issues disposition for delivery that is already settled
> --
>
> Key: QPID-7269
> URL: https://issues.apache.org/jira/browse/QPID-7269
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0.3
>Reporter: Gordon Sim
>Assignee: Rob Godfrey
> Fix For: qpid-java-6.1
>
>
> E.g. for proton python helloworld example:
> {noformat}
> [0x55610aa0de20]: <- AMQP
> [0x55610aa0de20]: -> AMQP
> [0x55610aa0de20]:0 -> @open(16)
> [container-id="1cc695d7-3588-4730-848e-1047eda87f8b", hostname="localhost",
> channel-max=32767]
> [0x55610aa0de20]:0 -> @begin(17) [next-outgoing-id=1,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x55610aa0de20]:0 -> @attach(18)
> [name="1cc695d7-3588-4730-848e-1047eda87f8b-examples", handle=0, role=true,
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples",
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0,
> timeout=0, dynamic=false], initial-delivery-count=0]
> [0x55610aa0de20]:0 -> @flow(19) [incoming-window=2147483647,
> next-outgoing-id=1, outgoing-window=2147483647, handle=0, delivery-count=0,
> link-credit=10, drain=false]
> [0x55610aa0de20]:0 <- @open(16)
> [container-id="21188a24-ee12-45d2-a027-a630d7e3f10c", max-frame-size=32768,
> channel-max=255, idle-time-out=0, properties={:product="qpid",
> :version="6.0.3", :"qpid.build"="Unversioned directory",
> :"qpid.instance_name"="Broker"}]
> [0x55610aa0de20]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
> incoming-window=2048, outgoing-window=2048]
> [0x55610aa0de20]:0 <- @attach(18)
> [name="1cc695d7-3588-4730-848e-1047eda87f8b-examples", handle=0, role=false,
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples",
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0,
> timeout=0, dynamic=false], initial-delivery-count=0]
> [0x55610aa0de20]:0 <- @transfer(20) [handle=0, delivery-id=0,
> delivery-tag=b"\x00\x00\x00\x00\x00\x00\x00\x00", message-format=0] (78)
> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa1\x0cHello
> World!"
> Hello World!
> [0x55610aa0de20]:0 -> @disposition(21) [role=true, first=0, last=0,
> settled=true, state=@accepted(36) []]
> [0x55610aa0de20]:0 -> @close(24) []
> [0x55610aa0de20]: -> EOS
> [0x55610aa0de20]:0 <- @disposition(21) [role=false, first=0, last=0,
> settled=true, state=@accepted(36) []]
> [0x55610aa0de20]:0 <- @flow(19) [next-incoming-id=1, incoming-window=2048,
> next-outgoing-id=1, outgoing-window=2048, handle=0, delivery-count=1,
> link-credit=9, available=0, drain=false, echo=false]
> [0x55610aa0de20]:0 <- @close(24) []
> [0x55610aa0de20]: <- EOS
> {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] (QPIDIT-21) Add shims for C++ client
[ https://issues.apache.org/jira/browse/QPIDIT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289140#comment-15289140 ] ASF subversion and git services commented on QPIDIT-21: --- Commit f33dffc47f56b1361e3dfaf4c2041463d27701d7 in qpid-interop-test's branch refs/heads/master from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=f33dffc ] QPIDIT-21: Uptaded for latest changes to Proton C++ API > Add shims for C++ client > > > Key: QPIDIT-21 > URL: https://issues.apache.org/jira/browse/QPIDIT-21 > Project: Apache QPID IT > Issue Type: New Feature > Components: JmsMessageTest, SimpleTypeTest >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > Add a set of shims for the Proton C++ client: > * Sender for SimpeTypeTest > * Receiver for SimpleTypeTest > * Sender for JmsMessageTest > * Receiver for JmsMessageTest -- 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-6096) java broker doesn't indicate that port is already in use
[ https://issues.apache.org/jira/browse/QPID-6096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289105#comment-15289105 ] Alex Rudyy commented on QPID-6096: -- The change look good to me. We should port it into 6.0.3 > java broker doesn't indicate that port is already in use > > > Key: QPID-6096 > URL: https://issues.apache.org/jira/browse/QPID-6096 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.30, 0.31 >Reporter: Gordon Sim >Assignee: Rob Godfrey >Priority: Minor > Fix For: qpid-java-6.0.3, qpid-java-6.1 > > > If you have something listening on 5672 when you start the java broker, it > will start but won't indicate that it can't listen to that port. Would be > nice to have an error or something as it will I suspect be an increasingly > common issue as more things may be listening on that port. -- 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] [Updated] (QPID-7268) message sent over 0-10 can't be received over 1.0
[ https://issues.apache.org/jira/browse/QPID-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7268: - Fix Version/s: (was: qpid-java-6.0.4) qpid-java-6.0.3 > message sent over 0-10 can't be received over 1.0 > - > > Key: QPID-7268 > URL: https://issues.apache.org/jira/browse/QPID-7268 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: qpid-java-6.0.3 >Reporter: Gordon Sim >Assignee: Rob Godfrey > Fix For: qpid-java-6.0.3, qpid-java-6.1 > > > To reproduce, define a queue to which a message is sent over AMQP 0-10 then > try to receive it using AMQP 1.0. A transfer frame is sent, but ot appears > (base don proton-c's tracing at least) to have no payload. -- 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] [Updated] (QPID-7255) Support delivery delay
[ https://issues.apache.org/jira/browse/QPID-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack updated QPID-7255: --- Fix Version/s: qpid-java-6.1 qpid-java-6.0.3 > Support delivery delay > -- > > Key: QPID-7255 > URL: https://issues.apache.org/jira/browse/QPID-7255 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Reporter: Keith Wall > Fix For: qpid-java-6.0.3, qpid-java-6.1 > > Attachments: QPID-7255.diff > > > Some enterprise messaging systems provide a delayed delivery feature whereby > a publisher can provide a delivery time when sending the message, with the > Broker taking care of not making the message available to consumers until > that time is reached. The Java Broker should provide the same feature. > In the Java space, JMS 2.0 has standardised this feature, however there is > no reason why the feature could not be made available to older JMS 1.1 > clients using a Qpid specific header. Also if the BURL or ADDR address > could hint to the Producer that delivery delay was required for all messages > produced by it, this would mean message delay could be turned on from > configuration alone. -- 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] [Updated] (QPID-6096) java broker doesn't indicate that port is already in use
[ https://issues.apache.org/jira/browse/QPID-6096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-6096: - Fix Version/s: qpid-java-6.0.3 > java broker doesn't indicate that port is already in use > > > Key: QPID-6096 > URL: https://issues.apache.org/jira/browse/QPID-6096 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.30, 0.31 >Reporter: Gordon Sim >Assignee: Rob Godfrey >Priority: Minor > Fix For: qpid-java-6.0.3, qpid-java-6.1 > > > If you have something listening on 5672 when you start the java broker, it > will start but won't indicate that it can't listen to that port. Would be > nice to have an error or something as it will I suspect be an increasingly > common issue as more things may be listening on that port. -- 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-7271) Improve exception handling for PlainSaslServer
[ https://issues.apache.org/jira/browse/QPID-7271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289090#comment-15289090 ] Alex Rudyy commented on QPID-7271: -- The fix looks good to me. We should include it into 6.0.3 > Improve exception handling for PlainSaslServer > -- > > Key: QPID-7271 > URL: https://issues.apache.org/jira/browse/QPID-7271 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: qpid-java-6.0.3, qpid-java-6.1 > > > Rather than let the IllegalArgumentException fall through to be dealt with by > the next level up, throw an explicit SaslException. -- 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] [Updated] (QPID-7271) Improve exception handling for PlainSaslServer
[ https://issues.apache.org/jira/browse/QPID-7271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7271: - Fix Version/s: qpid-java-6.0.3 > Improve exception handling for PlainSaslServer > -- > > Key: QPID-7271 > URL: https://issues.apache.org/jira/browse/QPID-7271 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: qpid-java-6.0.3, qpid-java-6.1 > > > Rather than let the IllegalArgumentException fall through to be dealt with by > the next level up, throw an explicit SaslException. -- 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] [Resolved] (PROTON-1133) Proton C includes port number in AMQP Open hostname
[
https://issues.apache.org/jira/browse/PROTON-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved PROTON-1133.
Resolution: Fixed
> Proton C includes port number in AMQP Open hostname
> ---
>
> Key: PROTON-1133
> URL: https://issues.apache.org/jira/browse/PROTON-1133
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c, python-binding
>Affects Versions: 0.12.0
>Reporter: Chuck Rolke
>Assignee: Ken Giusti
> Fix For: 0.13.0
>
>
> A command like:
> {noformat}
> qdmanage -b amqp://u1:password@photoserver:21000 --type policyStats query
> {noformat}
> sends the port number in the hostname field of the AMQP Open:
> {noformat}
> Mon Feb 8 11:37:46 2016 SERVER (trace) [2]:0 <- @open(16)
> [container-id="34e49947-b4df-4a01-9570-0a74e9e57b5b",
> hostname="photoserver:21000", channel-max=32767]
> (/home/chug/git/qpid-dispatch/src/server.c:75)
> {noformat}
> Built in C example code using Proton only does the same thing.
> This bug originally reported at
> https://issues.apache.org/jira/browse/DISPATCH-214
--
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] [Assigned] (DISPATCH-341) router did not respond to request to drain a message-routed consumers link credit
[
https://issues.apache.org/jira/browse/DISPATCH-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-341:
--
Assignee: Ganesh Murthy
> router did not respond to request to drain a message-routed consumers link
> credit
> -
>
> Key: DISPATCH-341
> URL: https://issues.apache.org/jira/browse/DISPATCH-341
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 0.6.0
> Environment: Qpid Dispatch 0.6.0 RC3
> Qpid JMS 0.10.0-SNAPSHOT
>Reporter: Robbie Gemmell
>Assignee: Ganesh Murthy
>
> With a router using the provided default config (updated only to set
> saslMechanisms to ANONYMOUS), and attaching a sender and receiver (using the
> JMS client Sender and Receiver examples) to the address "queue" (so
> presumably using messge routing), it could be seen that Dispatch didn't
> respond to requests to drain the receivers link.
> In one case, after receiving some messages, a 'drain requst' flow is issued,
> but neither enough messages to use the credit (expected since no more were
> sent) or a 'drain reponse' flow are received, just heartbeating back and
> forth.
> {noformat}
> [1925974223:1] -> Disposition{role=RECEIVER, first=8, last=8, settled=true,
> state=Accepted{}, batchable=false}
> [1925974223:1] -> Flow{nextIncomingId=9, incomingWindow=2047,
> nextOutgoingId=1, outgoingWindow=2147483647, handle=0, deliveryCount=9,
> linkCredit=991, available=null, drain=true, echo=false, properties=null}
> [1925974223:0] -> Empty Frame
> [1925974223:0] -> Empty Frame
> [1925974223:0] <- Empty Frame
> {noformat}
> In another case, after flowing some credit but not receiving any messages, a
> 'drain request' is issued, but neither enough messages to use the credit
> (expected since none were sent) or a 'drain reponse' flow are received, just
> heartbeating back and forth.
> {noformat}
> [2111953084:1] -> Flow{nextIncomingId=0, incomingWindow=2047,
> nextOutgoingId=1, outgoingWindow=2147483647, handle=0, deliveryCount=0,
> linkCredit=1000, available=null, drain=false, echo=false, properties=null}
> [2111953084:1] -> Flow{nextIncomingId=0, incomingWindow=2047,
> nextOutgoingId=1, outgoingWindow=2147483647, handle=0, deliveryCount=0,
> linkCredit=1000, available=null, drain=true, echo=false, properties=null}
> [2111953084:0] -> Empty Frame
> [2111953084:0] -> Empty Frame
> [2111953084:0] <- Empty Frame
> {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] [Updated] (DISPATCH-339) The change from 'routerId' to 'id' and 'addr' to 'host' configuration option is not backwards compatible
[
https://issues.apache.org/jira/browse/DISPATCH-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek updated DISPATCH-339:
Attachment: rb_.conf
ra_.conf
ra.conf
rb.conf
I am adding my config files for the second sub-issue (addr/host) just for
completeness. I should've done that right in the beginning, to make the
description more clear.
Files ra.conf and rb.conf use addr and do not work for me (qdstat -n on ra
prints only ra). Files ra_.conf and rb_.conf use host and do work for me.
> The change from 'routerId' to 'id' and 'addr' to 'host' configuration option
> is not backwards compatible
>
>
> Key: DISPATCH-339
> URL: https://issues.apache.org/jira/browse/DISPATCH-339
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 0.6.0
>Reporter: Jiri Danek
>Assignee: Ganesh Murthy
> Attachments: ra.conf, ra_.conf, rb.conf, rb_.conf
>
>
> I started qdrouterd with the following configuration
> {noformat}
> router {
> mode: interior
> routerId: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> {noformat}
> Running qdstat then prints that Router id is None.
> {code:title=qdstat -g|borderStyle=solid}
> Router Statistics
> attr value
> =
> Mode interior
> Area 0
> Router Id None
> Address Count 0
> Link Count 0
> Node Count 0
> {code}
> Other commands, for example
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> work correctly in this respect.
> If I update my config and use {{id}} instead of {{routerId}}, then qdstat
> prints correct information.
> I'd expect that the config that worked before the routerId/id change would
> continue working.
> If I use {{addr}} in my connectors, then my router does not connect to other
> routers. I had to update the config to using {{host}} and only then it worked
> for me.
> {noformat}
> router {
> mode: interior
> id: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> connector {
> name: to.r.b
> addr: {{ rb_ip }}
> port: 50001
> role: inter-router
> }
> {noformat}
> {noformat}
> router {
> mode: interior
> id: r.b
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> listener {
> role: inter-router
> addr: 0.0.0.0
> port: 50001
> authenticatePeer: no
> }
> {noformat}
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> After I change addr to host and restart both routers,
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)-
> r.b- 1
> {code}
> NOTE: I noticed that if I use routerId or addr, no deprecation warning is
> shown in qdrouterd output with the default log level. As far as I can
> remember, there are deprecation warnings for some features like fixedAddress,
> I think.
--
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-7271) Improve exception handling for PlainSaslServer
[ https://issues.apache.org/jira/browse/QPID-7271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15288878#comment-15288878 ] ASF subversion and git services commented on QPID-7271: --- Commit 1744403 from [~godfrer] in branch 'java/trunk' [ https://svn.apache.org/r1744403 ] QPID-7271 : Improve exception handling > Improve exception handling for PlainSaslServer > -- > > Key: QPID-7271 > URL: https://issues.apache.org/jira/browse/QPID-7271 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: qpid-java-6.1 > > > Rather than let the IllegalArgumentException fall through to be dealt with by > the next level up, throw an explicit SaslException. -- 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-7271) Improve exception handling for PlainSaslServer
Rob Godfrey created QPID-7271: - Summary: Improve exception handling for PlainSaslServer Key: QPID-7271 URL: https://issues.apache.org/jira/browse/QPID-7271 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Rob Godfrey Assignee: Rob Godfrey Fix For: qpid-java-6.1 Rather than let the IllegalArgumentException fall through to be dealt with by the next level up, throw an explicit SaslException. -- 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] [Assigned] (QPID-7270) [Java Broker] Fix broker side TLS cipher suite order
[
https://issues.apache.org/jira/browse/QPID-7270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack reassigned QPID-7270:
--
Assignee: Lorenz Quack
> [Java Broker] Fix broker side TLS cipher suite order
>
>
> Key: QPID-7270
> URL: https://issues.apache.org/jira/browse/QPID-7270
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Environment: Java 8
>Reporter: Lorenz Quack
>Assignee: Lorenz Quack
> Fix For: qpid-java-6.1
>
>
> currently on java 8 we try to enable broker side TLS cipher suite ordering by
> calling {{SSLParameter#setUseCipherSuitesOrder}}. However these parameters do
> not affect the {{SSLEngine}} unless they are set on it using
> {{SSLEngine#setSSLParameters}}.
--
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] [Updated] (QPID-7270) [Java Broker] Fix broker side TLS cipher suite order
[
https://issues.apache.org/jira/browse/QPID-7270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack updated QPID-7270:
---
Status: Reviewable (was: In Progress)
> [Java Broker] Fix broker side TLS cipher suite order
>
>
> Key: QPID-7270
> URL: https://issues.apache.org/jira/browse/QPID-7270
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Environment: Java 8
>Reporter: Lorenz Quack
>Assignee: Lorenz Quack
> Fix For: qpid-java-6.1
>
>
> currently on java 8 we try to enable broker side TLS cipher suite ordering by
> calling {{SSLParameter#setUseCipherSuitesOrder}}. However these parameters do
> not affect the {{SSLEngine}} unless they are set on it using
> {{SSLEngine#setSSLParameters}}.
--
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] [Updated] (QPID-7270) [Java Broker] Fix broker side TLS cipher suite order
[
https://issues.apache.org/jira/browse/QPID-7270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack updated QPID-7270:
---
Assignee: Rob Godfrey (was: Lorenz Quack)
> [Java Broker] Fix broker side TLS cipher suite order
>
>
> Key: QPID-7270
> URL: https://issues.apache.org/jira/browse/QPID-7270
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Environment: Java 8
>Reporter: Lorenz Quack
>Assignee: Rob Godfrey
> Fix For: qpid-java-6.1
>
>
> currently on java 8 we try to enable broker side TLS cipher suite ordering by
> calling {{SSLParameter#setUseCipherSuitesOrder}}. However these parameters do
> not affect the {{SSLEngine}} unless they are set on it using
> {{SSLEngine#setSSLParameters}}.
--
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] [Updated] (QPID-7270) [Java Broker] Fix broker side TLS cipher suite order
[
https://issues.apache.org/jira/browse/QPID-7270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack updated QPID-7270:
---
Fix Version/s: qpid-java-6.1
> [Java Broker] Fix broker side TLS cipher suite order
>
>
> Key: QPID-7270
> URL: https://issues.apache.org/jira/browse/QPID-7270
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Environment: Java 8
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.1
>
>
> currently on java 8 we try to enable broker side TLS cipher suite ordering by
> calling {{SSLParameter#setUseCipherSuitesOrder}}. However these parameters do
> not affect the {{SSLEngine}} unless they are set on it using
> {{SSLEngine#setSSLParameters}}.
--
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] (DISPATCH-341) router did not respond to request to drain a message-routed consumers link credit
Robbie Gemmell created DISPATCH-341:
---
Summary: router did not respond to request to drain a
message-routed consumers link credit
Key: DISPATCH-341
URL: https://issues.apache.org/jira/browse/DISPATCH-341
Project: Qpid Dispatch
Issue Type: Bug
Affects Versions: 0.6.0
Environment: Qpid Dispatch 0.6.0 RC3
Qpid JMS 0.10.0-SNAPSHOT
Reporter: Robbie Gemmell
With a router using the provided default config (updated only to set
saslMechanisms to ANONYMOUS), and attaching a sender and receiver (using the
JMS client Sender and Receiver examples) to the address "queue" (so presumably
using messge routing), it could be seen that Dispatch didn't respond to
requests to drain the receivers link.
In one case, after receiving some messages, a 'drain requst' flow is issued,
but neither enough messages to use the credit (expected since no more were
sent) or a 'drain reponse' flow are received, just heartbeating back and forth.
{noformat}
[1925974223:1] -> Disposition{role=RECEIVER, first=8, last=8, settled=true,
state=Accepted{}, batchable=false}
[1925974223:1] -> Flow{nextIncomingId=9, incomingWindow=2047, nextOutgoingId=1,
outgoingWindow=2147483647, handle=0, deliveryCount=9, linkCredit=991,
available=null, drain=true, echo=false, properties=null}
[1925974223:0] -> Empty Frame
[1925974223:0] -> Empty Frame
[1925974223:0] <- Empty Frame
{noformat}
In another case, after flowing some credit but not receiving any messages, a
'drain request' is issued, but neither enough messages to use the credit
(expected since none were sent) or a 'drain reponse' flow are received, just
heartbeating back and forth.
{noformat}
[2111953084:1] -> Flow{nextIncomingId=0, incomingWindow=2047, nextOutgoingId=1,
outgoingWindow=2147483647, handle=0, deliveryCount=0, linkCredit=1000,
available=null, drain=false, echo=false, properties=null}
[2111953084:1] -> Flow{nextIncomingId=0, incomingWindow=2047, nextOutgoingId=1,
outgoingWindow=2147483647, handle=0, deliveryCount=0, linkCredit=1000,
available=null, drain=true, echo=false, properties=null}
[2111953084:0] -> Empty Frame
[2111953084:0] -> Empty Frame
[2111953084:0] <- Empty Frame
{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] [Updated] (DISPATCH-339) The change from 'routerId' to 'id' and 'addr' to 'host' configuration option is not backwards compatible
[
https://issues.apache.org/jira/browse/DISPATCH-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-339:
--
Assignee: Ganesh Murthy
> The change from 'routerId' to 'id' and 'addr' to 'host' configuration option
> is not backwards compatible
>
>
> Key: DISPATCH-339
> URL: https://issues.apache.org/jira/browse/DISPATCH-339
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 0.6.0
>Reporter: Jiri Danek
>Assignee: Ganesh Murthy
>
> I started qdrouterd with the following configuration
> {noformat}
> router {
> mode: interior
> routerId: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> {noformat}
> Running qdstat then prints that Router id is None.
> {code:title=qdstat -g|borderStyle=solid}
> Router Statistics
> attr value
> =
> Mode interior
> Area 0
> Router Id None
> Address Count 0
> Link Count 0
> Node Count 0
> {code}
> Other commands, for example
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> work correctly in this respect.
> If I update my config and use {{id}} instead of {{routerId}}, then qdstat
> prints correct information.
> I'd expect that the config that worked before the routerId/id change would
> continue working.
> If I use {{addr}} in my connectors, then my router does not connect to other
> routers. I had to update the config to using {{host}} and only then it worked
> for me.
> {noformat}
> router {
> mode: interior
> id: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> connector {
> name: to.r.b
> addr: {{ rb_ip }}
> port: 50001
> role: inter-router
> }
> {noformat}
> {noformat}
> router {
> mode: interior
> id: r.b
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> listener {
> role: inter-router
> addr: 0.0.0.0
> port: 50001
> authenticatePeer: no
> }
> {noformat}
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> After I change addr to host and restart both routers,
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)-
> r.b- 1
> {code}
> NOTE: I noticed that if I use routerId or addr, no deprecation warning is
> shown in qdrouterd output with the default log level. As far as I can
> remember, there are deprecation warnings for some features like fixedAddress,
> I think.
--
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-7270) [Java Broker] Fix broker side TLS cipher suite order
[
https://issues.apache.org/jira/browse/QPID-7270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15288678#comment-15288678
]
ASF subversion and git services commented on QPID-7270:
---
Commit 1744368 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1744368 ]
QPID-7270: [Java Broker] Fix broker side TLS cipher suite ordering
> [Java Broker] Fix broker side TLS cipher suite order
>
>
> Key: QPID-7270
> URL: https://issues.apache.org/jira/browse/QPID-7270
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Environment: Java 8
>Reporter: Lorenz Quack
>
> currently on java 8 we try to enable broker side TLS cipher suite ordering by
> calling {{SSLParameter#setUseCipherSuitesOrder}}. However these parameters do
> not affect the {{SSLEngine}} unless they are set on it using
> {{SSLEngine#setSSLParameters}}.
--
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-7270) [Java Broker] Fix broker side TLS cipher suite order
Lorenz Quack created QPID-7270:
--
Summary: [Java Broker] Fix broker side TLS cipher suite order
Key: QPID-7270
URL: https://issues.apache.org/jira/browse/QPID-7270
Project: Qpid
Issue Type: Bug
Components: Java Broker
Environment: Java 8
Reporter: Lorenz Quack
currently on java 8 we try to enable broker side TLS cipher suite ordering by
calling {{SSLParameter#setUseCipherSuitesOrder}}. However these parameters do
not affect the {{SSLEngine}} unless they are set on it using
{{SSLEngine#setSSLParameters}}.
--
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] [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=15288609#comment-15288609 ] Jiri Danek edited comment on DISPATCH-138 at 5/18/16 8:37 AM: -- It is possible that DISPATCH-187 is a duplicate of this. As of now, that issue was not closed and I still had problems compiling with Python 3 present. was (Author: jdanek): It is possible that DISPATCH-187 is a duplicate of this. As of now, that issue was not closed, yet I had no problems compiling with Python 3 present. So maybe it is fixed. > 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 (v6.3.4#6332) - 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=15288609#comment-15288609 ] Jiri Danek edited comment on DISPATCH-138 at 5/18/16 8:17 AM: -- It is possible that DISPATCH-187 is a duplicate of this. As of now, that issue was not closed, yet I had no problems compiling with Python 3 present. So maybe it is fixed. was (Author: jdanek): It is possible that DISPATCH-187 is a duplicate of this. As of now, that issue was not closed. > 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 (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] (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=15288609#comment-15288609 ] Jiri Danek commented on DISPATCH-138: - It is possible that DISPATCH-187 is a duplicate. This issue is probably fixed since that issue was resolved. > 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 (v6.3.4#6332) - 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=15288609#comment-15288609 ] Jiri Danek edited comment on DISPATCH-138 at 5/18/16 8:15 AM: -- It is possible that DISPATCH-187 is a duplicate of this. As of now, that issue was not closed. was (Author: jdanek): It is possible that DISPATCH-187 is a duplicate. This issue is probably fixed since that issue was resolved. > 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 (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] (DISPATCH-224) Default installed configuration fails without error message.
[
https://issues.apache.org/jira/browse/DISPATCH-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15288589#comment-15288589
]
Jiri Danek commented on DISPATCH-224:
-
Isn't the issue fixed already? Installing from git with prefix ~/local and then
running {{qdstat -g}} works for me. As far as I can tell, it was solved by
having the "insecure" config as default.
> Default installed configuration fails without error message.
>
>
> Key: DISPATCH-224
> URL: https://issues.apache.org/jira/browse/DISPATCH-224
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 0.5
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.7.0
>
>
> A simple test of a default install of dispatch in /usr/local does not work:
> {code}
> $ make install
> $ qdrouterd&
> $ qdstat -g
> ConnectionException: Connection amqp://0.0.0.0:amqp/$management disconnected
> {code}
> The exception gives no hint why we were disconnected, and the router log file
> has no entries at all regarding the disconnection. The actual cause is a SASL
> rejection due to invalid configuration. There are several issues that need
> fixing:
> - The router log should show an error if SASL cant find/parse its config file.
> - The router log should show an error if a connection is rejected for
> security reasons.
> - The client exception should indicate that the disconnect was caused by a
> security problem.
> - The router should look for SASL configuration under its install prefix
> since that is where it is installed.
> - The default router configuration needs to be updated to either be
> functional or clearly NON functional.
> Question is is what should the default configuration allow? IMO it should at
> least allow you to use the tools shipped with qdrouterd to verify that it is
> running and working.
> The alternative is don't ship a default config at all. In that case the
> router should fail to start at all with a clear message "you must configure
> me first, see $prefix/share/doc/qdrouter/config-examples." We can provide a
> sample "qdrouterd-insecure.conf" to get developers started quickly without
> forcing them to learn SASL first. We can add other example configs for
> different scenarios as we go.
--
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
