[jira] [Resolved] (PROTON-1373) Clean up C++ API docs

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross resolved PROTON-1373.
-
Resolution: Fixed

> Clean up C++ API docs
> -
>
> Key: PROTON-1373
> URL: https://issues.apache.org/jira/browse/PROTON-1373
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Justin Ross
>Assignee: Justin Ross
> Fix For: 0.16.0
>
>
> - Eliminate warnings
> - Use modules to organize the docs
> - Improve consistency



--
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-1373) Clean up C++ API docs

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15730871#comment-15730871
 ] 

ASF subversion and git services commented on PROTON-1373:
-

Commit bea617333ec36a97fc3079375d2574ea28de6b7e in qpid-proton's branch 
refs/heads/master from [~jr...@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=bea6173 ]

PROTON-1373: C++ API doc improvements

 - Fix all warnings
 - Expose C++11 API elements
 - Improve presentation in class list
 - Some simple corrections


> Clean up C++ API docs
> -
>
> Key: PROTON-1373
> URL: https://issues.apache.org/jira/browse/PROTON-1373
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Justin Ross
>Assignee: Justin Ross
> Fix For: 0.16.0
>
>
> - Eliminate warnings
> - Use modules to organize the docs
> - Improve consistency



--
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] (PROTON-1372) Use PIMPL, not an interface, for event_loop

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1372:

Description: 
This represents the event_loop aspect of the work below.

---
Original issue description:

If you have a libqpid-proton-cpp compiled with C\+\+11 and then link to it 
using a C\+\+03 and use the {{proton::container::schedule}} API then the 
application will crash. This is because there is an extra virtual function 
present in the middle of the C\+\+11 vtable compared to the C\+\+03 vtable. So 
that when used from '03 the wrong member function gets called.

The extra member function is present because of conditional compilation 
dependent on the C\+\+ version doing the compilation.

This should also be a problem the other way round too, so using a 
libqpid-proton-cpp compiled with C\+\+03 from C\+\+11 will cause there to be 
one fewer entry in the vtable, and using schedule will either get the wrong 
version of schedule or call an entry of the end of the vtable.

  was:
If you have a libqpid-proton-cpp compiled with C\+\+11 and then link to it 
using a C\+\+03 and use the {{proton::container::schedule}} API then the 
application will crash. This is because there is an extra virtual function 
present in the middle of the C\+\+11 vtable compared to the C\+\+03 vtable. So 
that when used from '03 the wrong member function gets called.

The extra member function is present because of conditional compilation 
dependent on the C\+\+ version doing the compilation.

This should also be a problem the other way round too, so using a 
libqpid-proton-cpp compiled with C\+\+03 from C\+\+11 will cause there to be 
one fewer entry in the vtable, and using schedule will either get the wrong 
version of schedule or call an entry of the end of the vtable.


> Use PIMPL, not an interface, for event_loop
> ---
>
> Key: PROTON-1372
> URL: https://issues.apache.org/jira/browse/PROTON-1372
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.14.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Blocker
> Fix For: 0.17.0
>
>
> This represents the event_loop aspect of the work below.
> ---
> Original issue description:
> If you have a libqpid-proton-cpp compiled with C\+\+11 and then link to it 
> using a C\+\+03 and use the {{proton::container::schedule}} API then the 
> application will crash. This is because there is an extra virtual function 
> present in the middle of the C\+\+11 vtable compared to the C\+\+03 vtable. 
> So that when used from '03 the wrong member function gets called.
> The extra member function is present because of conditional compilation 
> dependent on the C\+\+ version doing the compilation.
> This should also be a problem the other way round too, so using a 
> libqpid-proton-cpp compiled with C\+\+03 from C\+\+11 will cause there to be 
> one fewer entry in the vtable, and using schedule will either get the wrong 
> version of schedule or call an entry of the end of the vtable.



--
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] (PROTON-1372) Use PIMPL, not an interface, for event_loop

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1372:

Fix Version/s: (was: 0.16.0)
   0.17.0

> Use PIMPL, not an interface, for event_loop
> ---
>
> Key: PROTON-1372
> URL: https://issues.apache.org/jira/browse/PROTON-1372
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.14.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Blocker
> Fix For: 0.17.0
>
>
> If you have a libqpid-proton-cpp compiled with C\+\+11 and then link to it 
> using a C\+\+03 and use the {{proton::container::schedule}} API then the 
> application will crash. This is because there is an extra virtual function 
> present in the middle of the C\+\+11 vtable compared to the C\+\+03 vtable. 
> So that when used from '03 the wrong member function gets called.
> The extra member function is present because of conditional compilation 
> dependent on the C\+\+ version doing the compilation.
> This should also be a problem the other way round too, so using a 
> libqpid-proton-cpp compiled with C\+\+03 from C\+\+11 will cause there to be 
> one fewer entry in the vtable, and using schedule will either get the wrong 
> version of schedule or call an entry of the end of the vtable.



--
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-1373) Clean up C++ API docs

[Justin Ross (JIRA)]

Justin Ross created PROTON-1373:
---

 Summary: Clean up C++ API docs
 Key: PROTON-1373
 URL: https://issues.apache.org/jira/browse/PROTON-1373
 Project: Qpid Proton
  Issue Type: Improvement
  Components: proton-c
Reporter: Justin Ross
Assignee: Justin Ross
 Fix For: 0.16.0


- Eliminate warnings
- Use modules to organize the docs
- Improve consistency



--
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-1371) proton::container::schedule crashes when mixing different language versions

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross resolved PROTON-1371.
-
Resolution: Fixed

> proton::container::schedule crashes when mixing different language versions
> ---
>
> Key: PROTON-1371
> URL: https://issues.apache.org/jira/browse/PROTON-1371
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.14.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Blocker
> Fix For: 0.16.0
>
>
> If you have a libqpid-proton-cpp compiled with C\+\+11 and then link to it 
> using a C\+\+03 and use the {{proton::container::schedule}} API then the 
> application will crash. This is because there is an extra virtual function 
> present in the middle of the C\+\+11 vtable compared to the C\+\+03 vtable. 
> So that when used from '03 the wrong member function gets called.
> The extra member function is present because of conditional compilation 
> dependent on the C\+\+ version doing the compilation.
> This should also be a problem the other way round too, so using a 
> libqpid-proton-cpp compiled with C\+\+03 from C\+\+11 will cause there to be 
> one fewer entry in the vtable, and using schedule will either get the wrong 
> version of schedule or call an entry of the end of the vtable.



--
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-1372) Use PIMPL, not an interface, for event_loop

[Justin Ross (JIRA)]

Justin Ross created PROTON-1372:
---

 Summary: Use PIMPL, not an interface, for event_loop
 Key: PROTON-1372
 URL: https://issues.apache.org/jira/browse/PROTON-1372
 Project: Qpid Proton
  Issue Type: Bug
  Components: cpp-binding
Affects Versions: 0.14.0
Reporter: Andrew Stitcher
Assignee: Andrew Stitcher
Priority: Blocker
 Fix For: 0.16.0


If you have a libqpid-proton-cpp compiled with C\+\+11 and then link to it 
using a C\+\+03 and use the {{proton::container::schedule}} API then the 
application will crash. This is because there is an extra virtual function 
present in the middle of the C\+\+11 vtable compared to the C\+\+03 vtable. So 
that when used from '03 the wrong member function gets called.

The extra member function is present because of conditional compilation 
dependent on the C\+\+ version doing the compilation.

This should also be a problem the other way round too, so using a 
libqpid-proton-cpp compiled with C\+\+03 from C\+\+11 will cause there to be 
one fewer entry in the vtable, and using schedule will either get the wrong 
version of schedule or call an entry of the end of the vtable.



--
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-1371) proton::container::schedule crashes when mixing different language versions

[Justin Ross (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15730832#comment-15730832
 ] 

Justin Ross commented on PROTON-1371:
-

The blocking part of this is resolved.  The work remaining is for event_loop, 
which is marked experimental and can wait for the next release.


> proton::container::schedule crashes when mixing different language versions
> ---
>
> Key: PROTON-1371
> URL: https://issues.apache.org/jira/browse/PROTON-1371
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.14.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Blocker
> Fix For: 0.16.0
>
>
> If you have a libqpid-proton-cpp compiled with C\+\+11 and then link to it 
> using a C\+\+03 and use the {{proton::container::schedule}} API then the 
> application will crash. This is because there is an extra virtual function 
> present in the middle of the C\+\+11 vtable compared to the C\+\+03 vtable. 
> So that when used from '03 the wrong member function gets called.
> The extra member function is present because of conditional compilation 
> dependent on the C\+\+ version doing the compilation.
> This should also be a problem the other way round too, so using a 
> libqpid-proton-cpp compiled with C\+\+03 from C\+\+11 will cause there to be 
> one fewer entry in the vtable, and using schedule will either get the wrong 
> version of schedule or call an entry of the end of the vtable.



--
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

Re: [jira] [Commented] (DISPATCH-103) Websocket Listeners

[Ted Ross]

I have reverted this commit.  It caused the build to fail if websockets 
was disabled and caused the tests to fail if it was enabled.


-Ted

On 12/07/2016 06:19 PM, ASF subversion and git services (JIRA) wrote:


[ 
https://issues.apache.org/jira/browse/DISPATCH-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15730260#comment-15730260
 ]

ASF subversion and git services commented on DISPATCH-103:
--

Commit cc4c82502025de74e8e703fb614d2195babf8a47 in qpid-dispatch's branch 
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=cc4c825 ]

DISPATCH-103: Refactor to use LWS context per listener.

Preparing for SSL support, use a context per listener so each can have separate
SSL configuration.



Websocket Listeners
---

Key: DISPATCH-103
URL: https://issues.apache.org/jira/browse/DISPATCH-103
Project: Qpid Dispatch
 Issue Type: New Feature
 Components: Container
   Reporter: Ted Ross
   Assignee: Alan Conway

Add an option in configured listeners to use websockets encapsulation.  This 
will allow AMQP clients inside web browsers to directly connect to the message 
bus.




--
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



-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-103) Websocket Listeners

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15730699#comment-15730699
 ] 

ASF subversion and git services commented on DISPATCH-103:
--

Commit b794973ebcf145a9a8a1f314ed66c019d19e98f4 in qpid-dispatch's branch 
refs/heads/master from [~tr...@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=b794973 ]

Revert "DISPATCH-103: Refactor to use LWS context per listener."

This reverts commit cc4c82502025de74e8e703fb614d2195babf8a47.


> Websocket Listeners
> ---
>
> Key: DISPATCH-103
> URL: https://issues.apache.org/jira/browse/DISPATCH-103
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Container
>Reporter: Ted Ross
>Assignee: Alan Conway
>
> Add an option in configured listeners to use websockets encapsulation.  This 
> will allow AMQP clients inside web browsers to directly connect to the 
> message bus.



--
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-103) Websocket Listeners

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15730260#comment-15730260
 ] 

ASF subversion and git services commented on DISPATCH-103:
--

Commit cc4c82502025de74e8e703fb614d2195babf8a47 in qpid-dispatch's branch 
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=cc4c825 ]

DISPATCH-103: Refactor to use LWS context per listener.

Preparing for SSL support, use a context per listener so each can have separate
SSL configuration.


> Websocket Listeners
> ---
>
> Key: DISPATCH-103
> URL: https://issues.apache.org/jira/browse/DISPATCH-103
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Container
>Reporter: Ted Ross
>Assignee: Alan Conway
>
> Add an option in configured listeners to use websockets encapsulation.  This 
> will allow AMQP clients inside web browsers to directly connect to the 
> message bus.



--
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-556) qdstat fails at high scale

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15730018#comment-15730018
 ] 

ASF GitHub Bot commented on DISPATCH-556:
-

GitHub user ganeshmurthy opened a pull request:

https://github.com/apache/qpid-dispatch/pull/122

DISPATCH-556 - Default limit of rows obtained by qdstat to 1000



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-556-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-dispatch/pull/122.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #122


commit 87507a098b0deffdc05f5480b1c46db0ca23f6db
Author: Ganesh Murthy 
Date:   2016-12-07T21:33:44Z

DISPATCH-556 - Default limit of rows obtained by qdstat to 1000




> qdstat fails at high scale
> --
>
> Key: DISPATCH-556
> URL: https://issues.apache.org/jira/browse/DISPATCH-556
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Tools
>Affects Versions: 0.7.0
>Reporter: Ted Ross
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
>
> qdstat times out waiting for a response when there are very large numbers of 
> management entities.  It needs a way to provide summary counts and it needs 
> to take advantage of pagination for large results.



--
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

[GitHub] qpid-dispatch pull request #122: DISPATCH-556 - Default limit of rows obtain...

[ganeshmurthy]

GitHub user ganeshmurthy opened a pull request:

https://github.com/apache/qpid-dispatch/pull/122

DISPATCH-556 - Default limit of rows obtained by qdstat to 1000



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-556-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-dispatch/pull/122.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #122


commit 87507a098b0deffdc05f5480b1c46db0ca23f6db
Author: Ganesh Murthy 
Date:   2016-12-07T21:33:44Z

DISPATCH-556 - Default limit of rows obtained by qdstat to 1000




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-dispatch pull request #121: DISPATCH-209 : targeted sender test

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/qpid-dispatch/pull/121


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

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

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729937#comment-15729937
 ] 

ASF GitHub Bot commented on DISPATCH-209:
-

Github user asfgit closed the pull request at:

https://github.com/apache/qpid-dispatch/pull/121


> Three+ router test is needed in the system test suite.
> --
>
> Key: DISPATCH-209
> URL: https://issues.apache.org/jira/browse/DISPATCH-209
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Tests
>Reporter: Ted Ross
>Assignee: michael goulish
>
> There have arisen some issues that would have been caught had there been a 
> three-router test in the regression suite.  This test should be added.



--
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-209) Three+ router test is needed in the system test suite.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729936#comment-15729936
 ] 

ASF subversion and git services commented on DISPATCH-209:
--

Commit 49fe290d65a3517a9927586301420842df654f12 in qpid-dispatch's branch 
refs/heads/master from mick
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=49fe290 ]

DISPATCH-209 : targeted sender test


> Three+ router test is needed in the system test suite.
> --
>
> Key: DISPATCH-209
> URL: https://issues.apache.org/jira/browse/DISPATCH-209
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Tests
>Reporter: Ted Ross
>Assignee: michael goulish
>
> There have arisen some issues that would have been caught had there been a 
> three-router test in the regression suite.  This test should be added.



--
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-209) Three+ router test is needed in the system test suite.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729920#comment-15729920
 ] 

ASF GitHub Bot commented on DISPATCH-209:
-

GitHub user mgoulish opened a pull request:

https://github.com/apache/qpid-dispatch/pull/121

DISPATCH-209 : targeted sender test

second try -- deleted previous branch because it went mad and tried to take 
over world.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mgoulish/qpid-dispatch DISPATCH-209-B

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-dispatch/pull/121.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #121


commit 49fe290d65a3517a9927586301420842df654f12
Author: mick 
Date:   2016-12-07T21:00:26Z

DISPATCH-209 : targeted sender test




> Three+ router test is needed in the system test suite.
> --
>
> Key: DISPATCH-209
> URL: https://issues.apache.org/jira/browse/DISPATCH-209
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Tests
>Reporter: Ted Ross
>Assignee: michael goulish
>
> There have arisen some issues that would have been caught had there been a 
> three-router test in the regression suite.  This test should be added.



--
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

[GitHub] qpid-dispatch pull request #121: DISPATCH-209 : targeted sender test

[mgoulish]

GitHub user mgoulish opened a pull request:

https://github.com/apache/qpid-dispatch/pull/121

DISPATCH-209 : targeted sender test

second try -- deleted previous branch because it went mad and tried to take 
over world.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mgoulish/qpid-dispatch DISPATCH-209-B

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-dispatch/pull/121.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #121


commit 49fe290d65a3517a9927586301420842df654f12
Author: mick 
Date:   2016-12-07T21:00:26Z

DISPATCH-209 : targeted sender test




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-dispatch issue #120: Dispatch 209

[mgoulish]

Github user mgoulish commented on the issue:

https://github.com/apache/qpid-dispatch/pull/120
  
Something is badly messed up here, even though the diff looks correct.  I 
will delete this branch and try again.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-dispatch pull request #120: Dispatch 209

[mgoulish]

Github user mgoulish closed the pull request at:

https://github.com/apache/qpid-dispatch/pull/120


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPIDJMS-207) Implement the JMS 2.0 API

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDJMS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729814#comment-15729814
 ] 

ASF subversion and git services commented on QPIDJMS-207:
-

Commit 88a77984d8ad17ba926dc184e50ba128f218c61a in qpid-jms's branch 
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=88a7798 ]

QPIDJMS-207 Clean up resource close handling

In some cases timeouts, connection drops, or close of a resource can
leave sync requests or async completions blocked or unanswered.  Clean
up the close handling in the AMQP layer to give child resources the
chance to unpark or signal failure to pending operations.


> Implement the JMS 2.0 API
> -
>
> Key: QPIDJMS-207
> URL: https://issues.apache.org/jira/browse/QPIDJMS-207
> Project: Qpid JMS
>  Issue Type: New Feature
>  Components: qpid-jms-client
>Affects Versions: 0.11.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
> Fix For: 0.20.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] [Created] (DISPATCH-590) List of log modules on the overview page is occationally doubled

[Ernest Allen (JIRA)]

Ernest Allen created DISPATCH-590:
-

 Summary: List of log modules on the overview page is occationally 
doubled
 Key: DISPATCH-590
 URL: https://issues.apache.org/jira/browse/DISPATCH-590
 Project: Qpid Dispatch
  Issue Type: Bug
  Components: Console
Reporter: Ernest Allen
Assignee: Ernest Allen


The list of log modules on the overview page is sometimes duplicated.
If you quickly jump between tree nodes on the left of the page, the list of log 
modules gets doubled.



--
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-358) Intermittent crashes in qdrouterd under load from parallel senders

[Vishal Sharda (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729662#comment-15729662
 ] 

Vishal Sharda commented on DISPATCH-358:


What you said seems to be the case.  These crashes have not been observed after 
upgrading to Proton 0.13.0 and later.

> Intermittent crashes in qdrouterd under load from parallel senders
> --
>
> Key: DISPATCH-358
> URL: https://issues.apache.org/jira/browse/DISPATCH-358
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Routing Engine
>Affects Versions: 0.6.0
> Environment: Debian 8.3, Apache Qpid Proton 0.12.2 for drivers and 
> dependencies, Hardware: 2 CPUs, 15 GB RAM, 60 GB HDD on 2 separate machines
>Reporter: Vishal Sharda
>Assignee: Ted Ross
>Priority: Critical
> Attachments: Crash_EXTERNAL.png, Crash_Java_Router_3.png, 
> Crash_Java_Send.png, Crash_Java_free_qd_connection.png, 
> Crash_Java_same_router.png, Crash_Java_same_router_another.png, 
> Crash_Java_same_router_another_bt.png, Crash_SASL.png, Crash_SASL_2.png, 
> Crash_SR_1.png, Crash_SR_2.png, Crash_bt_double_free_Java_RES_266MB.png, 
> Crash_double_free_Java_RES_266MB.png, Crash_free.png, 
> Crash_sasl_server_done.png, Crash_watch_qdstat.png, Overflow_Error.png
>
>
> In my setup of two inter-connected routers, several senders connecting to one 
> router while few receivers connecting to the other router, I see several 
> crashes in the router to which senders connect.  These crashes are 
> intermittent and happen once in every 10 runs or so.  I have collected the 
> backtraces of all the crashes but do not yet have a test case that can 
> reliably reproduce any of them.



--
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-1371) proton::container::schedule crashes when mixing different language versions

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729603#comment-15729603
 ] 

ASF subversion and git services commented on PROTON-1371:
-

Commit 5147ed30303a4ef8510a78b0e214fd954811193c in qpid-proton's branch 
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=5147ed3 ]

PROTON-1371: [C++ binding] Large header file cleanup
- Introduce  header to forward declare types
- Remove a lot of unnecessary includes in C++ header files


> proton::container::schedule crashes when mixing different language versions
> ---
>
> Key: PROTON-1371
> URL: https://issues.apache.org/jira/browse/PROTON-1371
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.14.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Blocker
> Fix For: 0.16.0
>
>
> If you have a libqpid-proton-cpp compiled with C\+\+11 and then link to it 
> using a C\+\+03 and use the {{proton::container::schedule}} API then the 
> application will crash. This is because there is an extra virtual function 
> present in the middle of the C\+\+11 vtable compared to the C\+\+03 vtable. 
> So that when used from '03 the wrong member function gets called.
> The extra member function is present because of conditional compilation 
> dependent on the C\+\+ version doing the compilation.
> This should also be a problem the other way round too, so using a 
> libqpid-proton-cpp compiled with C\+\+03 from C\+\+11 will cause there to be 
> one fewer entry in the vtable, and using schedule will either get the wrong 
> version of schedule or call an entry of the end of the vtable.



--
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-1371) proton::container::schedule crashes when mixing different language versions

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729604#comment-15729604
 ] 

ASF subversion and git services commented on PROTON-1371:
-

Commit 1c7e70a28e547a393eea0522290d95d5d38fb7fd in qpid-proton's branch 
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=1c7e70a ]

PROTON-1371: [C++ binding] Change container implementation to use handle-body
- This avoids the problem of a virtual member functions in the vtable being
  different depending on whether compiled with C++11 or C++03.


> proton::container::schedule crashes when mixing different language versions
> ---
>
> Key: PROTON-1371
> URL: https://issues.apache.org/jira/browse/PROTON-1371
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.14.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Blocker
> Fix For: 0.16.0
>
>
> If you have a libqpid-proton-cpp compiled with C\+\+11 and then link to it 
> using a C\+\+03 and use the {{proton::container::schedule}} API then the 
> application will crash. This is because there is an extra virtual function 
> present in the middle of the C\+\+11 vtable compared to the C\+\+03 vtable. 
> So that when used from '03 the wrong member function gets called.
> The extra member function is present because of conditional compilation 
> dependent on the C\+\+ version doing the compilation.
> This should also be a problem the other way round too, so using a 
> libqpid-proton-cpp compiled with C\+\+03 from C\+\+11 will cause there to be 
> one fewer entry in the vtable, and using schedule will either get the wrong 
> version of schedule or call an entry of the end of the vtable.



--
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-103) Websocket Listeners

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729584#comment-15729584
 ] 

ASF subversion and git services commented on DISPATCH-103:
--

Commit fbe70e2c239beb1afe543b440b0bc24d56efb19d in qpid-dispatch's branch 
refs/heads/master from [~tr...@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=fbe70e2 ]

DISPATCH-103 - Added libwebsockets include path to the set of includes.


> Websocket Listeners
> ---
>
> Key: DISPATCH-103
> URL: https://issues.apache.org/jira/browse/DISPATCH-103
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Container
>Reporter: Ted Ross
>Assignee: Alan Conway
>
> Add an option in configured listeners to use websockets encapsulation.  This 
> will allow AMQP clients inside web browsers to directly connect to the 
> message bus.



--
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-526) Coverity scan reported memory leaks in Qpid Dispatch 0.7.0

[Ganesh Murthy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DISPATCH-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ganesh Murthy resolved DISPATCH-526.

   Resolution: Fixed
 Assignee: Ganesh Murthy
Fix Version/s: 0.8.0

> Coverity scan reported memory leaks in Qpid Dispatch 0.7.0 
> ---
>
> Key: DISPATCH-526
> URL: https://issues.apache.org/jira/browse/DISPATCH-526
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 0.7.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
>
> kguisti ran the coverity scan on 0.7.0 RC1 which found a few memory leaks. 
> These will need to be fixed - 
> https://scan4.coverity.com/reports.htm#v24864/p10022



--
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

Re: Issue with prefetched messages not being released immediately on consumer close

[Robbie Gemmell]

On 7 December 2016 at 16:27, Oleksandr Rudyy  wrote:
> Hi ,
>
> We were looking into failing  system tests for AMQP 1.0 and discovered
> that transacted Consumer#close() does not release any prefetched
> messages immediately. It seems that transactions needs to be finished
> (committed/rolled back). As result, if another consumer is created
> before the transaction end, it will not see the acquired messages by
> closed consumer. Because of this issue the test
> org.apache.qpid.test.unit.transacted.CommitRollbackTest#testSend2ThenCloseAfter1andTryAgain
> is failing, as it creates a second consumer and tries to consume the
> message with this consumer before the transaction for the first closed
> consumer is committed.
>
> It is unclear whether it is a correct behavior or not. However, the
> legacy JMS client for AMQP 0.x is passing the test. We have to exclude
> the test from running on AMQP 1.0 profile.
>
> Shall I raise a JIRA about this issue?
>
> Kind Regards,
> Alex
>

Yes, please raise a JIRA. It isnt explicitly releasing messages on
closing the links...and its handling that particular situation by not
actually closing the link yet, thus it will currently act as the test
has found.

Robbie

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-7580) [Java Broker] Expose the type of message (AMQP 0-9-1/0-10/1-0/Non-AMQP) through REST/Management

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729373#comment-15729373
 ] 

ASF subversion and git services commented on QPID-7580:
---

Commit 1773126 from [~godfrer] in branch 'java/trunk'
[ https://svn.apache.org/r1773126 ]

QPID-7580 : expose the message type in MessageInfo

> [Java Broker] Expose the type of message (AMQP 0-9-1/0-10/1-0/Non-AMQP) 
> through REST/Management
> ---
>
> Key: QPID-7580
> URL: https://issues.apache.org/jira/browse/QPID-7580
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
> Fix For: qpid-java-6.2
>
>
> Currently when viewing message info it is impossible to tell what "type" of 
> message it is - i.e. the underlying representation that is stored in the 
> broker (AMQP 0-9-1, AMQP 0-10, AMQP 1.0 or "internal").
> We should add this information to MessageInfo(Impl) and the HTML management 
> console.



--
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-7580) [Java Broker] Expose the type of message (AMQP 0-9-1/0-10/1-0/Non-AMQP) through REST/Management

[Rob Godfrey (JIRA)]

Rob Godfrey created QPID-7580:
-

 Summary: [Java Broker] Expose the type of message (AMQP 
0-9-1/0-10/1-0/Non-AMQP) through REST/Management
 Key: QPID-7580
 URL: https://issues.apache.org/jira/browse/QPID-7580
 Project: Qpid
  Issue Type: Improvement
  Components: Java Broker
Reporter: Rob Godfrey
Assignee: Rob Godfrey
 Fix For: qpid-java-6.2


Currently when viewing message info it is impossible to tell what "type" of 
message it is - i.e. the underlying representation that is stored in the broker 
(AMQP 0-9-1, AMQP 0-10, AMQP 1.0 or "internal").

We should add this information to MessageInfo(Impl) and the HTML management 
console.



--
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-7486) [Java Broker] Refactor broker startup code, remove BrokerOptions

[Alex Rudyy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy resolved QPID-7486.
--
Resolution: Fixed

I reviewed the changes committed against this JIRA. They look Ok to me but I 
made a small improvement in [ https://svn.apache.org/r1773056 ] to initialize 
and upgrade configuration store on activation rather then doing it twice on 
activation and stop

> [Java Broker] Refactor broker startup code, remove BrokerOptions
> 
>
> Key: QPID-7486
> URL: https://issues.apache.org/jira/browse/QPID-7486
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
> Fix For: qpid-java-6.2
>
>
> The code relating to the initial construction of the broker has evolved over 
> time leaving functionality spread across a number of different classes with 
> no clear division of responsibilities.
> Refactor so that Main in the broker module has responsibility for parsing of 
> command line arguments and conversion into SystemConfig attributes, as well 
> as providing the hooks into the desired logging provider.
> SystemLauncher (renamed from Broker) provides a thin layer of state 
> management (shutdown/startup) on top of the SystemConfig configured 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] [Commented] (DISPATCH-103) Websocket Listeners

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729309#comment-15729309
 ] 

ASF subversion and git services commented on DISPATCH-103:
--

Commit 4fb102058f0695e357859f281ac9723b519ad1c3 in qpid-dispatch's branch 
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=4fb1020 ]

DISPATCH-103: Router serves standalone console files, stability fixes.

The router now serves the standalone console files so you can connect a browser
direct to a HTTP-enabled router port to use the console.

- requires libwebsockets 2.1 - packaged on fedora 25, build from source
  elsewhere.
- router must be installed `make install` to find the console files.

Fixed some stability and performance issues, currently appears to be stable and
reasonably fast.


> Websocket Listeners
> ---
>
> Key: DISPATCH-103
> URL: https://issues.apache.org/jira/browse/DISPATCH-103
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Container
>Reporter: Ted Ross
>Assignee: Alan Conway
>
> Add an option in configured listeners to use websockets encapsulation.  This 
> will allow AMQP clients inside web browsers to directly connect to the 
> message bus.



--
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-7579) AMQP 1.0 - settled flag set incorrectly for transactional sessions in mode rcvSettleMode FIRST

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729296#comment-15729296
 ] 

ASF subversion and git services commented on QPID-7579:
---

Commit 1773123 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1773123 ]

QPID-7579: [AMQP1.0] Fix the setting of the settle flag in disposition updates 
on transaction sessions where the client has requested rcvSettleMode FIRST

>  AMQP 1.0 - settled flag set incorrectly for transactional sessions in mode 
> rcvSettleMode FIRST
> ---
>
> Key: QPID-7579
> URL: https://issues.apache.org/jira/browse/QPID-7579
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Reporter: Keith Wall
> Fix For: qpid-java-6.2
>
>
> The current AMQP 1.0 implementation incorrectly sets the {{settled}} flag 
> incorrectly.  This causes the client to need to send an additional 
> (unnecessary) disposition. 



--
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-7579) AMQP 1.0 - settled flag set incorrectly for transactional sessions in mode rcvSettleMode FIRST

[Keith Wall (JIRA)]

Keith Wall created QPID-7579:


 Summary:  AMQP 1.0 - settled flag set incorrectly for 
transactional sessions in mode rcvSettleMode FIRST
 Key: QPID-7579
 URL: https://issues.apache.org/jira/browse/QPID-7579
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Reporter: Keith Wall
 Fix For: qpid-java-6.2


The current AMQP 1.0 implementation incorrectly sets the {{settled}} flag 
incorrectly.  This causes the client to need to send an additional 
(unnecessary) disposition. 





--
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-7546) [Java Broker] Allow the system tests to be run using the Qpid JMS client for AMQP 1.0 testing

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729273#comment-15729273
 ] 

ASF subversion and git services commented on QPID-7546:
---

Commit 1773119 from oru...@apache.org in branch 'java/trunk'
[ https://svn.apache.org/r1773119 ]

QPID-7546: Fix CommitRollbackTest#testRollbackSoak by closing the 'default' 
consumer as it was receiving all the messages whilst the test is expecting to 
receive all messages with two other consumers

> [Java Broker] Allow the system tests to be run using the Qpid JMS client for 
> AMQP 1.0 testing
> -
>
> Key: QPID-7546
> URL: https://issues.apache.org/jira/browse/QPID-7546
> Project: Qpid
>  Issue Type: Test
>  Components: Java Tests
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
>
> Currently the system tests use the JMS client for AMQP 0-8/9/10 and so the 
> AMQP 1.0 protocol implementation does not get as thoroughly tested.
> We should aim to move all the system tests such that they can be run with 
> either client



--
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-1140) [proton-c] Always set process name and process id as connection properties

[Gordon Sim (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729235#comment-15729235
 ] 

Gordon Sim commented on PROTON-1140:


For me, the engine is supposed to be free from this sort of policy type 
decision, as it is intended to be used in diverse situations. As an example, if 
you changed the engine to add this information, that would impact qpidd and 
qpid::messaging which already do the same thing themselves. I'm neutral on 
whether the reactor/container/??? api in python or c++ should do it 
automatically by default, but I'm uncomfortable with the engine itself doing it.

> [proton-c] Always set process name and process id as connection properties 
> ---
>
> Key: PROTON-1140
> URL: https://issues.apache.org/jira/browse/PROTON-1140
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: 0.12.0
>Reporter: Ganesh Murthy
>Priority: Minor
> Fix For: 0.17.0
>
>
> The connection initiating peer must set message properties of process name 
> and process id. The receiving peer will be able to access these properties 
> using pn_connection_remote_properties(connection)



--
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-59) Create a HOWTO file on writing a new shim

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDIT-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729213#comment-15729213
 ] 

ASF subversion and git services commented on QPIDIT-59:
---

Commit 2ce7f69704ef18005ae471649577f437ff9a85c2 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=2ce7f69 ]

QPIDIT-59: Added a HOWTO for writing shims


> Create a HOWTO file on writing a new shim
> -
>
> Key: QPIDIT-59
> URL: https://issues.apache.org/jira/browse/QPIDIT-59
> Project: Apache QPID IT
>  Issue Type: Task
>  Components: Documentation
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>
> Create a file which lays out how to write a shim.



--
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-1140) [proton-c] Always set process name and process id as connection properties

[Justin Ross (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729196#comment-15729196
 ] 

Justin Ross commented on PROTON-1140:
-

Our reactive bindings on top of the C core are not *especially* high-level 
clients.  People pick the C++ or the Python binding because it's their desired 
language.  They will often find use in low-level integrations.

We might in the future have some much higher-level APIs, and then perhaps 
things would be different.  But for most of the APIs we have, I'm not sure 
there's a meaningful distinction to be made.

For me, the question of whether to have default process name and ID is 
independent of C core versus bindings.

> [proton-c] Always set process name and process id as connection properties 
> ---
>
> Key: PROTON-1140
> URL: https://issues.apache.org/jira/browse/PROTON-1140
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: 0.12.0
>Reporter: Ganesh Murthy
>Priority: Minor
> Fix For: 0.17.0
>
>
> The connection initiating peer must set message properties of process name 
> and process id. The receiving peer will be able to access these properties 
> using pn_connection_remote_properties(connection)



--
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

Issue with prefetched messages not being released immediately on consumer close

[Oleksandr Rudyy]

Hi ,

We were looking into failing  system tests for AMQP 1.0 and discovered
that transacted Consumer#close() does not release any prefetched
messages immediately. It seems that transactions needs to be finished
(committed/rolled back). As result, if another consumer is created
before the transaction end, it will not see the acquired messages by
closed consumer. Because of this issue the test
org.apache.qpid.test.unit.transacted.CommitRollbackTest#testSend2ThenCloseAfter1andTryAgain
is failing, as it creates a second consumer and tries to consume the
message with this consumer before the transaction for the first closed
consumer is committed.

It is unclear whether it is a correct behavior or not. However, the
legacy JMS client for AMQP 0.x is passing the test. We have to exclude
the test from running on AMQP 1.0 profile.

Shall I raise a JIRA about this issue?

Kind Regards,
Alex

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Comment Edited] (PROTON-1140) [proton-c] Always set process name and process id as connection properties

[Gordon Sim (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729092#comment-15729092
 ] 

Gordon Sim edited comment on PROTON-1140 at 12/7/16 4:01 PM:
-

+1, I don't think this should be done automatically at the engine level. Having 
higher level clients do it is less objectionable, though it might be prudent 
also to provide some way of disabling that.


was (Author: gsim):
+1

> [proton-c] Always set process name and process id as connection properties 
> ---
>
> Key: PROTON-1140
> URL: https://issues.apache.org/jira/browse/PROTON-1140
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: 0.12.0
>Reporter: Ganesh Murthy
>Priority: Minor
> Fix For: 0.17.0
>
>
> The connection initiating peer must set message properties of process name 
> and process id. The receiving peer will be able to access these properties 
> using pn_connection_remote_properties(connection)



--
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-1140) [proton-c] Always set process name and process id as connection properties

[Gordon Sim (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729092#comment-15729092
 ] 

Gordon Sim commented on PROTON-1140:


+1

> [proton-c] Always set process name and process id as connection properties 
> ---
>
> Key: PROTON-1140
> URL: https://issues.apache.org/jira/browse/PROTON-1140
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: 0.12.0
>Reporter: Ganesh Murthy
>Priority: Minor
> Fix For: 0.17.0
>
>
> The connection initiating peer must set message properties of process name 
> and process id. The receiving peer will be able to access these properties 
> using pn_connection_remote_properties(connection)



--
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-1140) [proton-c] Always set process name and process id as connection properties

[Ken Giusti (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15728984#comment-15728984
 ] 

Ken Giusti commented on PROTON-1140:


Is this a request to have the proton-c pn_connection_t constructor create a 
default a connection (not message) property value containing process id and 
name? 

Not sure if want.

IMHO this should be left to the user of the library to determine what should go 
into the connection properties.  Automagically stuffing in the process name and 
id could result in an information leak that would be undesirable in some 
applications.



> [proton-c] Always set process name and process id as connection properties 
> ---
>
> Key: PROTON-1140
> URL: https://issues.apache.org/jira/browse/PROTON-1140
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: 0.12.0
>Reporter: Ganesh Murthy
>Priority: Minor
> Fix For: 0.17.0
>
>
> The connection initiating peer must set message properties of process name 
> and process id. The receiving peer will be able to access these properties 
> using pn_connection_remote_properties(connection)



--
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-7578) [Java Broker] make AMQP 1.0 temporary queues globally addressable

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15728921#comment-15728921
 ] 

ASF subversion and git services commented on QPID-7578:
---

Commit 1773089 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1773089 ]

QPID-7578: [Java Broker] make AMQP 1.0 temporary queues globally addressable

> [Java Broker] make AMQP 1.0 temporary queues globally addressable 
> --
>
> Key: QPID-7578
> URL: https://issues.apache.org/jira/browse/QPID-7578
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.2
>
>
> In AMQP 1.0 temporary queues currently have a random UUID as name.
> In the other protocols we prefix that with the primary global domain of the 
> virtual host to make it globally addressable. We should do the same for AMQP 
> 1.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] (QPID-7575) [Java Broker] Improve AMQP 1.0 codec to retain encoded message data

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15728911#comment-15728911
 ] 

ASF subversion and git services commented on QPID-7575:
---

Commit 1773086 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1773086 ]

QPID-7575 : [Java Broker] Refactor the AMQP 1.0 MessageMetaData

> [Java Broker] Improve AMQP 1.0 codec to retain encoded message data
> ---
>
> Key: QPID-7575
> URL: https://issues.apache.org/jira/browse/QPID-7575
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
> Fix For: qpid-java-6.2
>
>
> Currently the AMQP 1.0 path through the broker stores all message data in 
> both the meta data and the message content and requires repeated parsing of 
> the message.  We can improve performance by retaining the association between 
> sections and their encoded form at the point they are parsed, and only parse 
> sections if we require to inspect their contents



--
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-7578) [Java Broker] make AMQP 1.0 temporary queues globally addressable

[Lorenz Quack (JIRA)]

Lorenz Quack created QPID-7578:
--

 Summary: [Java Broker] make AMQP 1.0 temporary queues globally 
addressable 
 Key: QPID-7578
 URL: https://issues.apache.org/jira/browse/QPID-7578
 Project: Qpid
  Issue Type: Improvement
  Components: Java Broker
Reporter: Lorenz Quack
 Fix For: qpid-java-6.2


In AMQP 1.0 temporary queues currently have a random UUID as name.
In the other protocols we prefix that with the primary global domain of the 
virtual host to make it globally addressable. We should do the same for AMQP 1.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] [Resolved] (DISPATCH-566) Message annotations are not propagated to brokers on a linkRoute

[Ted Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DISPATCH-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Ross resolved DISPATCH-566.
---
Resolution: Fixed

> Message annotations are not propagated to brokers on a linkRoute
> 
>
> Key: DISPATCH-566
> URL: https://issues.apache.org/jira/browse/DISPATCH-566
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Router Node
>Affects Versions: 0.7.0
>Reporter: Kim van der Riet
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
> Attachments: dispatch-annotations-over-link.pcapng
>
>
> When a message containing a custom annotation (such as is used for JMS 
> messages) is passed to a broker on a linkRoute, the annotation is not 
> attached to the message.
> This issue is similar to that in DISPATCH-160, but the case for a single-node 
> dispatch router in which the message is passed directly from one client to 
> another works correctly.



--
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-566) Message annotations are not propagated to brokers on a linkRoute

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15728856#comment-15728856
 ] 

ASF GitHub Bot commented on DISPATCH-566:
-

Github user asfgit closed the pull request at:

https://github.com/apache/qpid-dispatch/pull/113


> Message annotations are not propagated to brokers on a linkRoute
> 
>
> Key: DISPATCH-566
> URL: https://issues.apache.org/jira/browse/DISPATCH-566
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Router Node
>Affects Versions: 0.7.0
>Reporter: Kim van der Riet
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
> Attachments: dispatch-annotations-over-link.pcapng
>
>
> When a message containing a custom annotation (such as is used for JMS 
> messages) is passed to a broker on a linkRoute, the annotation is not 
> attached to the message.
> This issue is similar to that in DISPATCH-160, but the case for a single-node 
> dispatch router in which the message is passed directly from one client to 
> another works correctly.



--
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-566) Message annotations are not propagated to brokers on a linkRoute

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15728855#comment-15728855
 ] 

ASF subversion and git services commented on DISPATCH-566:
--

Commit 4ae3c161d2d4a903c170554251ede3d915493a5a in qpid-dispatch's branch 
refs/heads/master from [~tr...@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=4ae3c16 ]

DISPATCH-566 - From Ganesh Murthy.  Propagate message-annotations over link 
routes.  This closes #113.


> Message annotations are not propagated to brokers on a linkRoute
> 
>
> Key: DISPATCH-566
> URL: https://issues.apache.org/jira/browse/DISPATCH-566
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Router Node
>Affects Versions: 0.7.0
>Reporter: Kim van der Riet
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
> Attachments: dispatch-annotations-over-link.pcapng
>
>
> When a message containing a custom annotation (such as is used for JMS 
> messages) is passed to a broker on a linkRoute, the annotation is not 
> attached to the message.
> This issue is similar to that in DISPATCH-160, but the case for a single-node 
> dispatch router in which the message is passed directly from one client to 
> another works correctly.



--
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

[GitHub] qpid-dispatch pull request #113: DISPATCH-566 - Allow message annotations to...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/qpid-dispatch/pull/113


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-7577) [Java Broker] Generic JDBC configuration store mistakenly is put into OPEN state in init

[Rob Godfrey (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-7577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rob Godfrey updated QPID-7577:
--
Summary: [Java Broker] Generic JDBC configuration store mistakenly is put 
into OPEN state in init  (was: [Java Broker] Generic JDMC configuration store 
mistakenly is put into OPEN state in init)

> [Java Broker] Generic JDBC configuration store mistakenly is put into OPEN 
> state in init
> 
>
> Key: QPID-7577
> URL: https://issues.apache.org/jira/browse/QPID-7577
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: qpid-java-6.1
>Reporter: Alex Rudyy
>
> The state is set mistakenly to OPEN in init method of generic JDMC 
> configuration store. As result, the exception about unexpected store state is 
> thrown on activation of JDBC VHN preventing it from becoming ACTIVE. JDBC 
> System config also cannot be used because of the same reason.



--
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-7577) [Java Broker] Generic JDMC configuration store mistakenly is put into OPEN state in init

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15728531#comment-15728531
 ] 

ASF subversion and git services commented on QPID-7577:
---

Commit 1773057 from oru...@apache.org in branch 'java/trunk'
[ https://svn.apache.org/r1773057 ]

QPID-7577: [Java Broker] Set correct state on initialization of generic JDBC 
configuration store

> [Java Broker] Generic JDMC configuration store mistakenly is put into OPEN 
> state in init
> 
>
> Key: QPID-7577
> URL: https://issues.apache.org/jira/browse/QPID-7577
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: qpid-java-6.1
>Reporter: Alex Rudyy
>
> The state is set mistakenly to OPEN in init method of generic JDMC 
> configuration store. As result, the exception about unexpected store state is 
> thrown on activation of JDBC VHN preventing it from becoming ACTIVE. JDBC 
> System config also cannot be used because of the same reason.



--
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-7486) [Java Broker] Refactor broker startup code, remove BrokerOptions

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15728530#comment-15728530
 ] 

ASF subversion and git services commented on QPID-7486:
---

Commit 1773056 from oru...@apache.org in branch 'java/trunk'
[ https://svn.apache.org/r1773056 ]

QPID-7486: [Java Broker] Initialize and upgrade configuration store structure 
on activation of system config

> [Java Broker] Refactor broker startup code, remove BrokerOptions
> 
>
> Key: QPID-7486
> URL: https://issues.apache.org/jira/browse/QPID-7486
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
> Fix For: qpid-java-6.2
>
>
> The code relating to the initial construction of the broker has evolved over 
> time leaving functionality spread across a number of different classes with 
> no clear division of responsibilities.
> Refactor so that Main in the broker module has responsibility for parsing of 
> command line arguments and conversion into SystemConfig attributes, as well 
> as providing the hooks into the desired logging provider.
> SystemLauncher (renamed from Broker) provides a thin layer of state 
> management (shutdown/startup) on top of the SystemConfig configured 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] (QPID-7577) [Java Broker] Generic JDMC configuration store mistakenly is put into OPEN state in init

[Alex Rudyy (JIRA)]

Alex Rudyy created QPID-7577:


 Summary: [Java Broker] Generic JDMC configuration store mistakenly 
is put into OPEN state in init
 Key: QPID-7577
 URL: https://issues.apache.org/jira/browse/QPID-7577
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: qpid-java-6.1
Reporter: Alex Rudyy


The state is set mistakenly to OPEN in init method of generic JDMC 
configuration store. As result, the exception about unexpected store state is 
thrown on activation of JDBC VHN preventing it from becoming ACTIVE. JDBC 
System config also cannot be used because of the same reason.



--
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-7529) [Java Broker] Implement producer flow control in AMQP 1.0

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15728251#comment-15728251
 ] 

ASF subversion and git services commented on QPID-7529:
---

Commit 1773035 from [~godfrer] in branch 'java/trunk'
[ https://svn.apache.org/r1773035 ]

QPID-7529 : revert accidentially committed change

> [Java Broker] Implement producer flow control in AMQP 1.0
> -
>
> Key: QPID-7529
> URL: https://issues.apache.org/jira/browse/QPID-7529
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Rob Godfrey
> Fix For: qpid-java-6.2
>
>
> Implement producer flow control in AMQP 1.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] (QPID-7529) [Java Broker] Implement producer flow control in AMQP 1.0

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15728246#comment-15728246
 ] 

ASF subversion and git services commented on QPID-7529:
---

Commit 1773033 from [~godfrer] in branch 'java/trunk'
[ https://svn.apache.org/r1773033 ]

QPID-7529 : add actions to ensure producer flow control is activated when 
queues become oversized

> [Java Broker] Implement producer flow control in AMQP 1.0
> -
>
> Key: QPID-7529
> URL: https://issues.apache.org/jira/browse/QPID-7529
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Rob Godfrey
> Fix For: qpid-java-6.2
>
>
> Implement producer flow control in AMQP 1.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