[jira] [Resolved] (DISPATCH-571) Driver spins when a listener accepts a socket while FDs are all in use

[ https://issues.apache.org/jira/browse/DISPATCH-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved DISPATCH-571. -- Resolution: Fixed Fixed by PROTON-1495 > Driver spins when a listener accepts a socket while

Re: Proposal to create Docker images for Qpid components.

I think the small images have their pros and cons. When I run into problems I find it always great to have something like CentOS, Fedora or Ubuntu as the base image. You can easily install many tools to debug the problems etc. And often the size doesn't have to be that big. It depends how minimal

Re: Proposal to create Docker images for Qpid components.

Definitely a good idea. I have my own images for C++ broker (https://hub.docker.com/r/ scholzj/qpid-cpp/) / Dispatch (https://hub.docker.com/r/ scholzj/qpid-dispatch/) / GUI for the C++ broker ( https://hub.docker.com/r/scholzj/qpid-cpp-gui/) and since I built them for the first time I probably

[jira] [Commented] (DISPATCH-209) Three+ router test is needed in the system test suite.

[ https://issues.apache.org/jira/browse/DISPATCH-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048251#comment-16048251 ] ASF GitHub Bot commented on DISPATCH-209: - Github user ted-ross commented on a diff in the pull

[jira] [Commented] (DISPATCH-209) Three+ router test is needed in the system test suite.

[ https://issues.apache.org/jira/browse/DISPATCH-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048253#comment-16048253 ] ASF GitHub Bot commented on DISPATCH-209: - Github user ted-ross commented on a diff in the pull

[jira] [Commented] (DISPATCH-209) Three+ router test is needed in the system test suite.

[ https://issues.apache.org/jira/browse/DISPATCH-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048254#comment-16048254 ] ASF GitHub Bot commented on DISPATCH-209: - Github user ted-ross commented on a diff in the pull

[jira] [Commented] (DISPATCH-209) Three+ router test is needed in the system test suite.

[ https://issues.apache.org/jira/browse/DISPATCH-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048252#comment-16048252 ] ASF GitHub Bot commented on DISPATCH-209: - Github user ted-ross commented on a diff in the pull

[jira] [Commented] (DISPATCH-209) Three+ router test is needed in the system test suite.

[ https://issues.apache.org/jira/browse/DISPATCH-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048255#comment-16048255 ] ASF GitHub Bot commented on DISPATCH-209: - Github user ted-ross commented on a diff in the pull

[GitHub] qpid-dispatch pull request #165: DISPATCH-209 : add a linear 3-router linkro...

Github user ted-ross commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/165#discussion_r121760979 --- Diff: tests/system_tests_three_routers.py --- @@ -335,36 +417,124 @@ def on_start ( self, event ): self.client_receiver =

[GitHub] qpid-dispatch pull request #165: DISPATCH-209 : add a linear 3-router linkro...

Github user ted-ross commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/165#discussion_r121759130 --- Diff: tests/system_tests_three_routers.py --- @@ -96,10 +124,24 @@ def router ( name, connection_1, connection_2=None ):

[GitHub] qpid-dispatch pull request #165: DISPATCH-209 : add a linear 3-router linkro...

Github user ted-ross commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/165#discussion_r121760200 --- Diff: tests/system_tests_three_routers.py --- @@ -335,36 +417,124 @@ def on_start ( self, event ): self.client_receiver =

[GitHub] qpid-dispatch pull request #165: DISPATCH-209 : add a linear 3-router linkro...

Github user ted-ross commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/165#discussion_r121765790 --- Diff: tests/system_tests_three_routers.py --- @@ -335,36 +417,124 @@ def on_start ( self, event ): self.client_receiver =

[GitHub] qpid-dispatch pull request #165: DISPATCH-209 : add a linear 3-router linkro...

Github user ted-ross commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/165#discussion_r121764581 --- Diff: tests/system_tests_three_routers.py --- @@ -335,36 +417,124 @@ def on_start ( self, event ): self.client_receiver =

Re: Proposal to create Docker images for Qpid components.

Thank you for excellent remarks. I will take a look at your work and what can be done to minimise images, although I must admit it is easier to layer on top of official images produced by the distros. On Tue, Jun 13, 2017 at 11:36 AM, Fraser Adams < fraser.ad...@blueyonder.co.uk> wrote: > Hi

Re: Proposal to create Docker images for Qpid components.

As many as I can. Currently we do not package java broker as an RPM for Fedora/CentOS, nor do we have it packaged for Ubuntu. On Tue, Jun 13, 2017 at 12:03 PM, Lorenz Quack wrote: > Hello Irina, > > Sounds like a good idea. > > Do you plan on providing docker images of

[jira] [Commented] (QPID-7817) [Java Broker] [WebSocket] Websocket implementation must not assume that web socket frame contains a whole AMQP frame

[ https://issues.apache.org/jira/browse/QPID-7817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048126#comment-16048126 ] ASF subversion and git services commented on QPID-7817: --- Commit

Re: Proposal to create Docker images for Qpid components.

Hello Irina, Sounds like a good idea. Do you plan on providing docker images of all Qpid components? Would be good to have for example the cpp and the java broker available to easily evaluate and compare them. Kind regards, Lorenz On Tue, 2017-06-13 at 10:13 -0400, Irina Boverman wrote: > Hi

Re: Proposal to create Docker images for Qpid components.

Hi Irina, I think that this is an excellent idea and I totally agree with the sentiment "Availability of Qpid images will make it easier to consume/deploy Qpid components and promote Qpid visibility." I think that in 2017 it's really important for the project to be providing official

[jira] [Commented] (QPID-7805) [Java Broker] [Websocket] Utilize jetty streaming API in implementation of wesocket transport support

[ https://issues.apache.org/jira/browse/QPID-7805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047991#comment-16047991 ] Keith Wall commented on QPID-7805: -- I don't think this is suitable for AMQP web socket use. Jetty's

[jira] [Updated] (QPID-7817) [Java Broker] [WebSocket] Websocket implementation must not assume that web socket frame contains a whole AMQP frame

[ https://issues.apache.org/jira/browse/QPID-7817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7817: - Status: Reviewable (was: In Progress) > [Java Broker] [WebSocket] Websocket implementation must not

[jira] [Updated] (QPID-7817) [Java Broker] [WebSocket] Websocket implementation must not assume that web socket frame contains a whole AMQP frame

[ https://issues.apache.org/jira/browse/QPID-7817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7817: - Fix Version/s: qpid-java-broker-7.0.0 > [Java Broker] [WebSocket] Websocket implementation must not assume

[jira] [Assigned] (QPID-7820) Extend AMQP 1.0 protocol tests to support web socket tests too

[ https://issues.apache.org/jira/browse/QPID-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-7820: Assignee: Keith Wall > Extend AMQP 1.0 protocol tests to support web socket tests too >

[jira] [Commented] (QPID-7817) [Java Broker] [WebSocket] Websocket implementation must not assume that web socket frame contains a whole AMQP frame

[ https://issues.apache.org/jira/browse/QPID-7817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047981#comment-16047981 ] ASF subversion and git services commented on QPID-7817: --- Commit

[jira] [Resolved] (QPID-7805) [Java Broker] [Websocket] Utilize jetty streaming API in implementation of wesocket transport support

[ https://issues.apache.org/jira/browse/QPID-7805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7805. -- Resolution: Invalid > [Java Broker] [Websocket] Utilize jetty streaming API in implementation of >

[jira] [Updated] (QPID-7820) Extend AMQP 1.0 protocol tests to support web socket tests too

[ https://issues.apache.org/jira/browse/QPID-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7820: - Status: Reviewable (was: In Progress) > Extend AMQP 1.0 protocol tests to support web socket tests too >

[jira] [Assigned] (QPID-7817) [Java Broker] [WebSocket] Websocket implementation must not assume that web socket frame contains a whole AMQP frame

[ https://issues.apache.org/jira/browse/QPID-7817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-7817: Assignee: Keith Wall > [Java Broker] [WebSocket] Websocket implementation must not assume that web

RE: Proposal to create Docker images for Qpid components.

+1 I think it's a great idea to make Docker images available. Not sure it makes sense to package client(s) as images, but overall I think the idea would help make Qpid more easily accessible to users and help ease deployment. -Steve > -Original Message- > From: Irina Boverman

Proposal to create Docker images for Qpid components.

Hi everyone, I would like to propose creating Docker images for Qpid components hosted in Docker Hub, updated upon component release and maintained by the project, and I would like to contribute to doing this. Availability of Qpid images will make it easier to consume/deploy Qpid components and

[jira] [Resolved] (DISPATCH-787) c epoll proactor can raise SIGPIPE

[ https://issues.apache.org/jira/browse/DISPATCH-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved DISPATCH-787. -- Resolution: Fixed Fixed by fix to PROTON-1501 > c epoll proactor can raise SIGPIPE >

[jira] [Resolved] (PROTON-1501) c epoll proactor can raise SIGPIPE

[ https://issues.apache.org/jira/browse/PROTON-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1501. - Resolution: Fixed > c epoll proactor can raise SIGPIPE > -- > >

[jira] [Updated] (QPID-7606) Generalise Queue|Exchange#alternateExchange as alternateBinding

[ https://issues.apache.org/jira/browse/QPID-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7606: - Attachment: wip-alternate-binding.tar.gz > Generalise Queue|Exchange#alternateExchange as alternateBinding

[jira] [Updated] (QPID-7606) Generalise Queue|Exchange#alternateExchange as alternateBinding

[ https://issues.apache.org/jira/browse/QPID-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7606: - Attachment: (was: wip-alternate-binding.tar.gz) > Generalise Queue|Exchange#alternateExchange as

[jira] [Resolved] (QPID-7316) WMC should permit the navigation from a consumer on a queue back to the connection

[ https://issues.apache.org/jira/browse/QPID-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack resolved QPID-7316. Resolution: Fixed Thanks for the clarification > WMC should permit the navigation from a consumer

[jira] [Resolved] (QPID-7616) VirtualHostNode name is not expanded before creating thread

[ https://issues.apache.org/jira/browse/QPID-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack resolved QPID-7616. Resolution: Fixed looks good to me > VirtualHostNode name is not expanded before creating thread >

[jira] [Resolved] (QPID-7811) [Java Broker] Asynchronous message store recoverer can delete message content for the message enqueued after broker startup

[ https://issues.apache.org/jira/browse/QPID-7811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack resolved QPID-7811. Resolution: Fixed > [Java Broker] Asynchronous message store recoverer can delete message content >

[jira] [Commented] (QPID-7811) [Java Broker] Asynchronous message store recoverer can delete message content for the message enqueued after broker startup

[ https://issues.apache.org/jira/browse/QPID-7811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047681#comment-16047681 ] Lorenz Quack commented on QPID-7811: I squashed the three commits together for the backport. On the

[jira] [Commented] (QPID-7811) [Java Broker] Asynchronous message store recoverer can delete message content for the message enqueued after broker startup

[ https://issues.apache.org/jira/browse/QPID-7811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047676#comment-16047676 ] ASF subversion and git services commented on QPID-7811: --- Commit

[jira] [Commented] (QPID-7811) [Java Broker] Asynchronous message store recoverer can delete message content for the message enqueued after broker startup

[ https://issues.apache.org/jira/browse/QPID-7811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047675#comment-16047675 ] ASF subversion and git services commented on QPID-7811: --- Commit

[jira] [Created] (QPID-7822) Derby NPE during Broker startup

Keith Wall created QPID-7822: Summary: Derby NPE during Broker startup Key: QPID-7822 URL: https://issues.apache.org/jira/browse/QPID-7822 Project: Qpid Issue Type: Bug Components:

[jira] [Issue Comment Deleted] (QPID-7606) Generalise Queue|Exchange#alternateExchange as alternateBinding

[ https://issues.apache.org/jira/browse/QPID-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7606: - Comment: was deleted (was: This feature allows for the support of RabbitMQ's exchange.bind AMQP 0-91

[jira] [Commented] (QPID-7606) Generalise Queue|Exchange#alternateExchange as alternateBinding

[ https://issues.apache.org/jira/browse/QPID-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047532#comment-16047532 ] Keith Wall commented on QPID-7606: -- This feature allows for the support of RabbitMQ's exchange.bind AMQP