[jira] [Commented] (PROTON-1848) [Python] Update to only support versions 2.6, 2.7 and 3.3 onwards

[ASF subversion and git services (JIRA)]

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

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

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

PROTON-1848: [Python] Remove Python 2.5 and earlier compatibility
- Remove need for most compatibility hacks
- Fix some seemingly odd conversion functions
- Hidden all compatibility code in _compat module
  - will probably get rid of raise_ when rewriting reactor
  - can get rid of string_type by doing unicode type hack in reactor.py
  - leaving iteritems & unichr


> [Python] Update to only support versions 2.6, 2.7 and 3.3 onwards
> -
>
> Key: PROTON-1848
> URL: https://issues.apache.org/jira/browse/PROTON-1848
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: python-binding
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.24.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (PROTON-1850) [Python] Split up monolithic proton __init__.py

[ASF subversion and git services (JIRA)]

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

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

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

PROTON-1850: Split up proton __init__.py into multiple files
- Reformatted python source to (mostly) PEP-8 standards
- Control what gets exported from __init__ by restricting what it imports
- Move most of the reactor implementation specific code into _reactor_impl.py


> [Python] Split up monolithic proton __init__.py
> ---
>
> Key: PROTON-1850
> URL: https://issues.apache.org/jira/browse/PROTON-1850
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: python-binding
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.24.0
>
>
> Nearly the entire implementation of the proton python binding is in 
> __init__.py (except for the reactive API). This has several unfortunate 
> effects:
>  * It can be hard to find your way around the source except by simply 
> searching.
>  * There is no way to restrict the export of symbols from the proton module - 
> anything in the module can be explicitly imported (although {{__all__}} does 
> restrict what gets imported with {{from proton import *}}).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[GitHub] qpid-proton pull request #144: Python proactor

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/qpid-proton/pull/144


---

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

[jira] [Assigned] (PROTON-1683) support static library output

[Alan Conway (JIRA)]

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

Alan Conway reassigned PROTON-1683:
---

Assignee: Alan Conway

> support static library output
> -
>
> Key: PROTON-1683
> URL: https://issues.apache.org/jira/browse/PROTON-1683
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: build
> Environment: centos 6u5
>Reporter: WangYao
>Assignee: Alan Conway
>Priority: Major
>
> My company get used to link application using static library, will proton 
> support static library output?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (DISPATCH-992) System test is failing in some scenarios - system_tests_delivery_abort.py

[ASF subversion and git services (JIRA)]

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

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

Commit 57d36b8362d62a4324a99be36b804cf69f570ac2 in qpid-dispatch's branch 
refs/heads/1.1.x from [~fgiorget]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=57d36b8 ]

DISPATCH-992: Fix for system_tests_delivery_abort.py

(cherry picked from commit 95d1ba5e1d8882dd624b451072837396f201baa5)


> System test is failing in some scenarios - system_tests_delivery_abort.py
> -
>
> Key: DISPATCH-992
> URL: https://issues.apache.org/jira/browse/DISPATCH-992
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Tests
>Reporter: Fernando Giorgetti
>Priority: Major
> Fix For: 1.1.0
>
>
> In some machines, we were able to see that system_tests_delivery_abort.py 
> test is failing (only the truncate tests) as on_aborted() method is not being 
> invoked.
> After debugging the test and along with the router code, it ended out being a 
> timing issue on some machines. Basically when the sender's close() method is 
> called (like at line 218), the headers have not yet been sent from the router 
> (with aborted=true), so on_aborted is never invoked on the test.
> Using a bigger data to stream, like 100 instead of 10 (or even 
> sleeping for 1 second before closing the sender), it gives enough time for 
> the headers to be sent and then test passes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (DISPATCH-992) System test is failing in some scenarios - system_tests_delivery_abort.py

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy updated DISPATCH-992:
---
Fix Version/s: (was: 1.2.0)
   1.1.0

> System test is failing in some scenarios - system_tests_delivery_abort.py
> -
>
> Key: DISPATCH-992
> URL: https://issues.apache.org/jira/browse/DISPATCH-992
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Tests
>Reporter: Fernando Giorgetti
>Priority: Major
> Fix For: 1.1.0
>
>
> In some machines, we were able to see that system_tests_delivery_abort.py 
> test is failing (only the truncate tests) as on_aborted() method is not being 
> invoked.
> After debugging the test and along with the router code, it ended out being a 
> timing issue on some machines. Basically when the sender's close() method is 
> called (like at line 218), the headers have not yet been sent from the router 
> (with aborted=true), so on_aborted is never invoked on the test.
> Using a bigger data to stream, like 100 instead of 10 (or even 
> sleeping for 1 second before closing the sender), it gives enough time for 
> the headers to be sent and then test passes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (DISPATCH-980) Allow address translation on link routes

[Gordon Sim (JIRA)]

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

Gordon Sim updated DISPATCH-980:

Fix Version/s: 1.2.0

> Allow address translation on link routes
> 
>
> Key: DISPATCH-980
> URL: https://issues.apache.org/jira/browse/DISPATCH-980
> Project: Qpid Dispatch
>  Issue Type: New Feature
>Reporter: Gordon Sim
>Assignee: Gordon Sim
>Priority: Major
> Fix For: 1.2.0
>
>
> With auto-links there is an externalAddr field that allows the node on the 
> route-container to have a different name than that the clients see through 
> the router. This is very useful. It would be nice to have a similar feature 
> for link-routes also.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (DISPATCH-941) Router is returning incorrect files from http get requests.

[Alan Conway (JIRA)]

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

Alan Conway commented on DISPATCH-941:
--

I'm still seeing problems - tested on bare-metal f26, 27, 28

All built from dispatch master c7478cc0 
 
Fedora 26 - works perfectly
libwebsockets-2.2.1-1.fc26.x86_64
Fedora 27 - complains of missing files

libwebsockets-2.3.0-2.fc27.x86_64
 
2018-05-25 16:30:18.958818 -0400 SERVER (info) Accepted connection to : 
from 192.168.2.152018-05-25 16:30:44.526050 -0400 HTTP (error) Unable to open 
'/usr/local/share/qpid-dispatch/console/stand-alone/plugin/fonts/OpenSans-Regular-webfont.woff2'
2018-05-25 16:30:45.086603 -0400 HTTP (error) Unable to open 
'/usr/local/share/qpid-dispatch/console/stand-alone/node_modules/fonts/OpenSans-Regular-webfont.woff'


Those files are missing, on all of my installs including the f26 one that 
works! There is no such plugin/fonts or fonts directory on any of my 
installations. No idea why this works on 26 but not 27.
 
Fedora 28 - broken in new and exciting way
libwebsockets-2.4.2-1.fc28.x86_64
 
2018-05-25 16:37:22.574904 -0400 HTTP (warning) More hdr frags than we can deal 
with
 
I get the same behavior with a localhost or remote browser. Firefox or chromium.
 

> Router is returning incorrect files from http get requests.
> ---
>
> Key: DISPATCH-941
> URL: https://issues.apache.org/jira/browse/DISPATCH-941
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Routing Engine
>Affects Versions: 1.0.1
>Reporter: Ernest Allen
>Priority: Major
> Fix For: Backlog
>
> Attachments: CaptureApache_angular.PNG, CaptureApache_angular.PNG, 
> CaptureApache_woff2.PNG, CaptureApache_woff2.PNG, CaptureApache_woff2.PNG, 
> CaptureDispatch_angular.PNG, CaptureDispatch_angular.PNG, 
> CaptureDispatch_woff2.PNG
>
>
> When http requests are made from a Windows machine, the http response headers 
> appear to be mixed up or for a different request. For example, when the 
> browser requests the file OpenSans-Regular-webfont.woff2, the response has a 
> content-type of text/javascript and an incorrect content-length. Here is the 
> bad response: !CaptureDispatch_woff2.PNG!
> When the same browser on the same machine requests the same file from Apache 
> tomcat, the response is correct:
> !CaptureApache_woff2.PNG!
> Another example: This time the request is for the javascript file angular.js. 
> Here is the bad response from the router:
> !CaptureDispatch_angular.PNG!
>  
> And here is the correct response from tomcat for the same file:
> !CaptureApache_angular.PNG!
> The incorrect content-types and content-lengths returned by the router lead 
> me to believe that the responses are getting mixed up.
> Possibly important note: Which requests are mixed up varies each time I 
> reload the page. Sometimes files that failed on a previous page load will 
> come down just fine. It doesn't always happen on the same files.
> This happens for all browsers I've tried on Windows. It does not happen for 
> any browser when the request comes from my linux box.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (QPID-8196) [Broker-J] [WMC] Edit form controls are not populated with current values

[ASF subversion and git services (JIRA)]

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

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

Commit 4ac5997f450d167d8afbe2f3a49f7a7414c21656 in qpid-broker-j's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=4ac5997 ]

QPID-8196) [Broker-J] [WMC] Make sure that edit form controls are populated 
with current values for type-based UI fragments loaded dynamically into editing 
form


> [Broker-J] [WMC] Edit form controls are not populated with current values
> -
>
> Key: QPID-8196
> URL: https://issues.apache.org/jira/browse/QPID-8196
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>Reporter: Alex Rudyy
>Priority: Major
> Attachments: 
> 0001-QPID-8196-Broker-J-WMC-Make-sure-that-edit-form-cont.patch
>
>
> The form for editing BDB HA VHN does not populate reliably the UI controls 
> with current attribute values. Some of the attribute controls can be left 
> unset. As result, on submitting the form, null/empty values can be sent as 
> part of update request to the broker.
> User impact:
> Editing of attributes cannot be done reliably from WVM, as when the issue 
> occurs, the update requests from VMC fail due to broker side validation. 
> There is a possibility of unexpected change of attribute value to null.
> Work around: REST API can be used to change the attribute values.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (QPID-7830) Heap dominated by duplicates of common routing values / header values etc

[ASF subversion and git services (JIRA)]

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

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

Commit 57bda83de7fbe6291aea507b5c1098fda5cf130d in qpid-broker-j's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=57bda83 ]

QPID-7830: [Broker-J] Simplify string caching functionality


> Heap dominated by duplicates of common routing values / header values etc
> -
>
> Key: QPID-7830
> URL: https://issues.apache.org/jira/browse/QPID-7830
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Reporter: Keith Wall
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
> Attachments: 
> 0001-QPID-7830-Broker-J-Simplify-string-caching-functiona.patch
>
>
> When used for store and forwarding, in some use cases the Broker's heap can 
> become dominated by duplicates of common values such as routing information 
> (e.g. {{amq.direct}} or an application's queue name) or common header values 
> (e.g a application/octet-stream or an application's user id).
> On the 0-8..0-91 paths, every enqueued message gets its own 
> {{MessagePublishInfo}} referencing its own {{AMQShortString}} exchange and 
> routing keys.  For some use-cases, these are drawn from a small set. On the 
> AMQP 1.0 path, {{Properties#to}} is an example.   0-10 is probably affected 
> too.
> This unnecessarily increases the heap requirements of the Broker.
> The Broker should adopt a sensible intern/caching policy with the same policy 
> applying regardless of whether messages follow the on-line enqueue or 
> recovery path.  Note that in AMQP 1.0, values which are {{Symbols}} have 
> their underlying String automatically interned.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[GitHub] qpid-dispatch pull request #309: DISPATCH-1013 - Enable vhost policies to be...

[fgiorgetti]

GitHub user fgiorgetti opened a pull request:

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

DISPATCH-1013 - Enable vhost policies to be defined on router config



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

$ git pull https://github.com/fgiorgetti/qpid-dispatch 
fgiorgetti-DISPATCH-1013

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

https://github.com/apache/qpid-dispatch/pull/309.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 #309


commit 389e23eb3e8f3af8f4e710c1d9bc81de5ceb6b75
Author: Fernando Giorgetti 
Date:   2018-05-25T20:02:52Z

DISPATCH-1013 - Enable vhost policies to be defined on router config




---

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

[jira] [Commented] (DISPATCH-1013) Enable vhost policies to be used in the router config file (not just through separate JSON files)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on DISPATCH-1013:
--

GitHub user fgiorgetti opened a pull request:

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

DISPATCH-1013 - Enable vhost policies to be defined on router config



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

$ git pull https://github.com/fgiorgetti/qpid-dispatch 
fgiorgetti-DISPATCH-1013

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

https://github.com/apache/qpid-dispatch/pull/309.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 #309


commit 389e23eb3e8f3af8f4e710c1d9bc81de5ceb6b75
Author: Fernando Giorgetti 
Date:   2018-05-25T20:02:52Z

DISPATCH-1013 - Enable vhost policies to be defined on router config




> Enable vhost policies to be used in the router config file (not just through 
> separate JSON files)
> -
>
> Key: DISPATCH-1013
> URL: https://issues.apache.org/jira/browse/DISPATCH-1013
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Management Agent
>Reporter: Fernando Giorgetti
>Priority: Major
>
> Enable vhost policies/groups to be defined through the router configuration 
> file as well.
> Following a sample of what should be allowed:
> {code:java}
> vhost {
>  hostname: 0.0.0.0
>  maxConnections: 15
>  maxConnectionsPerUser: 10
>  maxConnectionsPerHost: 10
>  allowUnknownUser: true
>  groups: {
>   anonymous: {
>users: anonymous
>remoteHosts: 127.0.0.1, 10.0.0.1
>targets: *
>sources: *
>maxSessions: 100
>allowDynamicSource: true
>   }
>   $default: {
>users: *
>remoteHosts: *
>targets: public private
>sources: public, private
>   }
>  }
> }{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Created] (DISPATCH-1013) Enable vhost policies to be used in the router config file (not just through separate JSON files)

[Fernando Giorgetti (JIRA)]

Fernando Giorgetti created DISPATCH-1013:


 Summary: Enable vhost policies to be used in the router config 
file (not just through separate JSON files)
 Key: DISPATCH-1013
 URL: https://issues.apache.org/jira/browse/DISPATCH-1013
 Project: Qpid Dispatch
  Issue Type: Improvement
  Components: Management Agent
Reporter: Fernando Giorgetti


Enable vhost policies/groups to be defined through the router configuration 
file as well.
Following a sample of what should be allowed:
{code:java}
vhost {
 hostname: 0.0.0.0
 maxConnections: 15
 maxConnectionsPerUser: 10
 maxConnectionsPerHost: 10
 allowUnknownUser: true
 groups: {
  anonymous: {
   users: anonymous
   remoteHosts: 127.0.0.1, 10.0.0.1
   targets: *
   sources: *
   maxSessions: 100
   allowDynamicSource: true
  }
  $default: {
   users: *
   remoteHosts: *
   targets: public private
   sources: public, private
  }
 }
}{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (DISPATCH-1012) Release undeliverable deliveries, don't hold them

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy commented on DISPATCH-1012:
-

Hi [~sophokles73] our 1.1.0 release has been long delayed. We are planning on 
doing a 1.1.0 release immediately. We are planning on doing a 1.2.0 release 
pretty soon and that release will have a fix for this issue. Thanks.

> Release undeliverable deliveries, don't hold them
> -
>
> Key: DISPATCH-1012
> URL: https://issues.apache.org/jira/browse/DISPATCH-1012
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Router Node
>Reporter: Ted Ross
>Assignee: Ted Ross
>Priority: Major
> Fix For: 1.2.0
>
>
> In 1.1.0, deliveries that are produced into the router network that are 
> undeliverable (i.e. the last consumer for the address has detached) are held 
> in the ingress link's undelivered list.  There is no limit to the amount of 
> time that a delivery can remain in this list.
> Rather than hold undeliverable messages in the undelivered list, the router 
> should return them to the sender with RELEASED disposition.  Furthermore, 
> once released, credit should not be replenished to the sender until there is 
> a consumer attached to receive the deliveries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Assigned] (DISPATCH-1012) Release undeliverable deliveries, don't hold them

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy reassigned DISPATCH-1012:
---

Assignee: Ted Ross

> Release undeliverable deliveries, don't hold them
> -
>
> Key: DISPATCH-1012
> URL: https://issues.apache.org/jira/browse/DISPATCH-1012
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Router Node
>Reporter: Ted Ross
>Assignee: Ted Ross
>Priority: Major
> Fix For: 1.2.0
>
>
> In 1.1.0, deliveries that are produced into the router network that are 
> undeliverable (i.e. the last consumer for the address has detached) are held 
> in the ingress link's undelivered list.  There is no limit to the amount of 
> time that a delivery can remain in this list.
> Rather than hold undeliverable messages in the undelivered list, the router 
> should return them to the sender with RELEASED disposition.  Furthermore, 
> once released, credit should not be replenished to the sender until there is 
> a consumer attached to receive the deliveries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (QPID-8200) [linearstore] Compile error when compiling on Fedora 28

[Kim van der Riet (JIRA)]

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

Kim van der Riet updated QPID-8200:
---
Status: Reviewable  (was: In Progress)

> [linearstore] Compile error when compiling on Fedora 28
> ---
>
> Key: QPID-8200
> URL: https://issues.apache.org/jira/browse/QPID-8200
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
>
> When compiling on Fedora 28, a compile warning {{-Werror=class-memaccess}} is 
> seen when compiling {{qpid::linearstore::journal::pmgr}} , and which was not 
> seen on Fedora 27:
> {noformat}
> qpid::linearstore::journal::pmgr::initialize(qpid::linearstore::journal::aio_callback*,
>  uint32_t, uint16_t)':
> /foo/cpp/src/qpid/linearstore/journal/pmgr.cpp:115:68: error: 'void* 
> memset(void*, int, size_t)' clearing an object of non-trivial type 'struct 
> qpid::linearstore::journal::pmgr::page_cb'; use assignment instead 
> [-Werror=class-memaccess]
>  std::memset(_page_cb_arr, 0, _cache_num_pages * sizeof(page_cb));
> ^
> In file included from /foo/cpp/src/qpid/linearstore/journal/pmgr.cpp:22:
> /foo/cpp/src/qpid/linearstore/journal/pmgr.h:63:12: note: 'struct 
> qpid::linearstore::journal::pmgr::page_cb' declared here
>  struct page_cb
> ^~~
> cc1plus: all warnings being treated as errors{noformat}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (QPID-8200) [linearstore] Compile error when compiling on Fedora 28

[ASF subversion and git services (JIRA)]

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

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

Commit a3a77949ec491ad9f7ef7c4c0261be6d032d5974 in qpid-cpp's branch 
refs/heads/master from [~kpvdr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-cpp.git;h=a3a7794 ]

QPID-8200: Fix for -Wclass-memaccess compile error on Fedora 28


> [linearstore] Compile error when compiling on Fedora 28
> ---
>
> Key: QPID-8200
> URL: https://issues.apache.org/jira/browse/QPID-8200
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
>
> When compiling on Fedora 28, a compile warning {{-Werror=class-memaccess}} is 
> seen when compiling {{qpid::linearstore::journal::pmgr}} , and which was not 
> seen on Fedora 27:
> {noformat}
> qpid::linearstore::journal::pmgr::initialize(qpid::linearstore::journal::aio_callback*,
>  uint32_t, uint16_t)':
> /foo/cpp/src/qpid/linearstore/journal/pmgr.cpp:115:68: error: 'void* 
> memset(void*, int, size_t)' clearing an object of non-trivial type 'struct 
> qpid::linearstore::journal::pmgr::page_cb'; use assignment instead 
> [-Werror=class-memaccess]
>  std::memset(_page_cb_arr, 0, _cache_num_pages * sizeof(page_cb));
> ^
> In file included from /foo/cpp/src/qpid/linearstore/journal/pmgr.cpp:22:
> /foo/cpp/src/qpid/linearstore/journal/pmgr.h:63:12: note: 'struct 
> qpid::linearstore::journal::pmgr::page_cb' declared here
>  struct page_cb
> ^~~
> cc1plus: all warnings being treated as errors{noformat}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (QPID-8200) [linearstore] Compile error when compiling on Fedora 28

[Kim van der Riet (JIRA)]

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

Kim van der Riet commented on QPID-8200:


This post provides some insight into the {{-Wclass-memaccess}} warning:

[https://gcc.gnu.org/ml/gcc-patches/2017-06/msg01527.html|https://gcc.gnu.org/ml/gcc-patches/2017-06/msg01527.html]

> [linearstore] Compile error when compiling on Fedora 28
> ---
>
> Key: QPID-8200
> URL: https://issues.apache.org/jira/browse/QPID-8200
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
>
> When compiling on Fedora 28, a compile warning {{-Werror=class-memaccess}} is 
> seen when compiling {{qpid::linearstore::journal::pmgr}} , and which was not 
> seen on Fedora 27:
> {noformat}
> qpid::linearstore::journal::pmgr::initialize(qpid::linearstore::journal::aio_callback*,
>  uint32_t, uint16_t)':
> /foo/cpp/src/qpid/linearstore/journal/pmgr.cpp:115:68: error: 'void* 
> memset(void*, int, size_t)' clearing an object of non-trivial type 'struct 
> qpid::linearstore::journal::pmgr::page_cb'; use assignment instead 
> [-Werror=class-memaccess]
>  std::memset(_page_cb_arr, 0, _cache_num_pages * sizeof(page_cb));
> ^
> In file included from /foo/cpp/src/qpid/linearstore/journal/pmgr.cpp:22:
> /foo/cpp/src/qpid/linearstore/journal/pmgr.h:63:12: note: 'struct 
> qpid::linearstore::journal::pmgr::page_cb' declared here
>  struct page_cb
> ^~~
> cc1plus: all warnings being treated as errors{noformat}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Created] (QPID-8200) [linearstore] Compile error when compiling on Fedora 28

[Kim van der Riet (JIRA)]

Kim van der Riet created QPID-8200:
--

 Summary: [linearstore] Compile error when compiling on Fedora 28
 Key: QPID-8200
 URL: https://issues.apache.org/jira/browse/QPID-8200
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
Reporter: Kim van der Riet
Assignee: Kim van der Riet


When compiling on Fedora 28, a compile warning {{-Werror=class-memaccess}} is 
seen when compiling {{qpid::linearstore::journal::pmgr}} , and which was not 
seen on Fedora 27:
{noformat}
qpid::linearstore::journal::pmgr::initialize(qpid::linearstore::journal::aio_callback*,
 uint32_t, uint16_t)':
/foo/cpp/src/qpid/linearstore/journal/pmgr.cpp:115:68: error: 'void* 
memset(void*, int, size_t)' clearing an object of non-trivial type 'struct 
qpid::linearstore::journal::pmgr::page_cb'; use assignment instead 
[-Werror=class-memaccess]
 std::memset(_page_cb_arr, 0, _cache_num_pages * sizeof(page_cb));
^
In file included from /foo/cpp/src/qpid/linearstore/journal/pmgr.cpp:22:
/foo/cpp/src/qpid/linearstore/journal/pmgr.h:63:12: note: 'struct 
qpid::linearstore::journal::pmgr::page_cb' declared here
 struct page_cb
^~~
cc1plus: all warnings being treated as errors{noformat}
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Resolved] (DISPATCH-990) Use patterns for policy vhost hostnames

[Chuck Rolke (JIRA)]

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

Chuck Rolke resolved DISPATCH-990.
--
   Resolution: Fixed
Fix Version/s: 1.2.0

> Use patterns for policy vhost hostnames
> ---
>
> Key: DISPATCH-990
> URL: https://issues.apache.org/jira/browse/DISPATCH-990
> Project: Qpid Dispatch
>  Issue Type: Bug
>Reporter: Chuck Rolke
>Priority: Major
> Fix For: 1.2.0
>
>
> Currently policy vhost hostnames identify a single host. Vhost policy would 
> be much more flexible if the hostnames could be specified with pattern 
> matching wildcards:
> {{  #.corporate.example.com}}
> {{  #.labs.example.com}}
> {{  *.users.example.com}}
> {{  #.example.com}}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (DISPATCH-941) Router is returning incorrect files from http get requests.

[Ernest Allen (JIRA)]

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

Ernest Allen commented on DISPATCH-941:
---

I'm not seeing this anymore. I'm running the router on fedora 28 with 
libwebsockets-2.4.2-1.fc28.x86_64.

I'm able to load the current console from Windows:Chrome/FF/Edge, and 
Android:Chrome.

I was seeing the problem on fedora 27, but I'm not sure of the libwebsockets 
version.

At first, I suspected that DISPATCH-1000 might have "fixed/masked/avoided" the 
problem. That Jira shortened the path from where a large number of files were 
loaded. However, to test that theory I reverted the console to load the css/js 
files from their pre-DISPATCH-1000 locations and the problem did not re-appear.

I'll try on a fedora 27 VM and see what I get with the latest stand-alone 
console directory structure.

 

> Router is returning incorrect files from http get requests.
> ---
>
> Key: DISPATCH-941
> URL: https://issues.apache.org/jira/browse/DISPATCH-941
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Routing Engine
>Affects Versions: 1.0.1
>Reporter: Ernest Allen
>Priority: Major
> Fix For: Backlog
>
> Attachments: CaptureApache_angular.PNG, CaptureApache_angular.PNG, 
> CaptureApache_woff2.PNG, CaptureApache_woff2.PNG, CaptureApache_woff2.PNG, 
> CaptureDispatch_angular.PNG, CaptureDispatch_angular.PNG, 
> CaptureDispatch_woff2.PNG
>
>
> When http requests are made from a Windows machine, the http response headers 
> appear to be mixed up or for a different request. For example, when the 
> browser requests the file OpenSans-Regular-webfont.woff2, the response has a 
> content-type of text/javascript and an incorrect content-length. Here is the 
> bad response: !CaptureDispatch_woff2.PNG!
> When the same browser on the same machine requests the same file from Apache 
> tomcat, the response is correct:
> !CaptureApache_woff2.PNG!
> Another example: This time the request is for the javascript file angular.js. 
> Here is the bad response from the router:
> !CaptureDispatch_angular.PNG!
>  
> And here is the correct response from tomcat for the same file:
> !CaptureApache_angular.PNG!
> The incorrect content-types and content-lengths returned by the router lead 
> me to believe that the responses are getting mixed up.
> Possibly important note: Which requests are mixed up varies each time I 
> reload the page. Sometimes files that failed on a previous page load will 
> come down just fine. It doesn't always happen on the same files.
> This happens for all browsers I've tried on Windows. It does not happen for 
> any browser when the request comes from my linux box.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (DISPATCH-1012) Release undeliverable deliveries, don't hold them

[Kai Hudalla (JIRA)]

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

Kai Hudalla commented on DISPATCH-1012:
---

 Any chance this can make it into the 1.1.0 release?

> Release undeliverable deliveries, don't hold them
> -
>
> Key: DISPATCH-1012
> URL: https://issues.apache.org/jira/browse/DISPATCH-1012
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Router Node
>Reporter: Ted Ross
>Priority: Major
> Fix For: 1.2.0
>
>
> In 1.1.0, deliveries that are produced into the router network that are 
> undeliverable (i.e. the last consumer for the address has detached) are held 
> in the ingress link's undelivered list.  There is no limit to the amount of 
> time that a delivery can remain in this list.
> Rather than hold undeliverable messages in the undelivered list, the router 
> should return them to the sender with RELEASED disposition.  Furthermore, 
> once released, credit should not be replenished to the sender until there is 
> a consumer attached to receive the deliveries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Created] (DISPATCH-1012) Release undeliverable deliveries, don't hold them

[Ted Ross (JIRA)]

Ted Ross created DISPATCH-1012:
--

 Summary: Release undeliverable deliveries, don't hold them
 Key: DISPATCH-1012
 URL: https://issues.apache.org/jira/browse/DISPATCH-1012
 Project: Qpid Dispatch
  Issue Type: Improvement
  Components: Router Node
Reporter: Ted Ross
 Fix For: 1.2.0


In 1.1.0, deliveries that are produced into the router network that are 
undeliverable (i.e. the last consumer for the address has detached) are held in 
the ingress link's undelivered list.  There is no limit to the amount of time 
that a delivery can remain in this list.

Rather than hold undeliverable messages in the undelivered list, the router 
should return them to the sender with RELEASED disposition.  Furthermore, once 
released, credit should not be replenished to the sender until there is a 
consumer attached to receive the deliveries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (QPID-8199) [Broker-J] Improve description for bind/unbind operations

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-8199:
-
Summary: [Broker-J] Improve description for bind/unbind operations  (was: 
[Broker-J] Improved description for bind/unbind operations)

> [Broker-J] Improve description for bind/unbind operations
> -
>
> Key: QPID-8199
> URL: https://issues.apache.org/jira/browse/QPID-8199
> Project: Qpid
>  Issue Type: Improvement
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, 
> qpid-java-broker-7.0.0, qpid-java-broker-7.0.1
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
>
> The description for unbind operation is misleading. It should be improved to 
> state that only one binding with given queue name and given binding key would 
> be deleted



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (QPID-8199) [Broker-J] Improved description for bind/unbind operations

[ASF subversion and git services (JIRA)]

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

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

Commit 43aa29ec193f1b6748fe72417e8f27c50d0a59ac in qpid-broker-j's branch 
refs/heads/7.0.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=43aa29e ]

QPID-8199: [Broker-J] Fix unbind/bind operation descriptions

(cherry picked from commit 5ccf63f06f218c11af549823ff6ca25585c5fad5)


> [Broker-J] Improved description for bind/unbind operations
> --
>
> Key: QPID-8199
> URL: https://issues.apache.org/jira/browse/QPID-8199
> Project: Qpid
>  Issue Type: Improvement
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, 
> qpid-java-broker-7.0.0, qpid-java-broker-7.0.1
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
>
> The description for unbind operation is misleading. It should be improved to 
> state that only one binding with given queue name and given binding key would 
> be deleted



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (QPID-8192) [Broker-J] Make bindingKey parameter mandatory in exchange bind/unbind operations

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-8192:
-
Status: Reviewable  (was: In Progress)

> [Broker-J] Make bindingKey parameter mandatory in exchange bind/unbind 
> operations
> -
>
> Key: QPID-8192
> URL: https://issues.apache.org/jira/browse/QPID-8192
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, 
> qpid-java-broker-7.0.0, qpid-java-broker-7.0.1
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0
>
> Attachments: 
> 0001-QPID-8192-Broker-J-Make-bindingKey-parameter-mandato.patch
>
>
> Make bindingKey parameter mandatory in exchange bind/unbind operations but 
> allow the value of the binding key to be the empty string. Optional 
> bindingKey parameter causes confusions in understanding how bind/unbind 
> operations works, as omitting  bindingKey in unbind operation could be 
> misinterpreted as bulk bindings deletion for the given destination. The 
> unbind operation description text should be fixed as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (QPID-8198) [Broker-J][Documentation] Account headers in formula for estimation of heap size

[ASF subversion and git services (JIRA)]

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

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

Commit 21aabcd9c67dbbecda6856eea135e62ce041a59c in qpid-broker-j's branch 
refs/heads/7.0.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=21aabcd ]

QPID-8198: [Broker-J[Documentation] Account headers in formula for estimation 
of heap size

(cherry picked from commit db971ea2ba02f9f5128daac0ab310dad5c8f8fba)


> [Broker-J][Documentation] Account headers in formula for estimation of heap 
> size
> 
>
> Key: QPID-8198
> URL: https://issues.apache.org/jira/browse/QPID-8198
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J, Java Documentation
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
>
> The formula for estimation of required heap size should allow to specify 
> variables for message headers. Otherwise, the estimated value would be far 
> from required. For example, in Broker with 1G of heap it is possible to 
> publish 568920 AMQP 1-0 messages without application properties. However, it 
> is possible to publish around 208700 messages if each message contains 20 
> application specific properties with average size of 20 bytes for name and 
> value.
> The formula for estimation of required heap size should allow to specify the 
> following:
> * average size of property name and value
> * average number of application properties per message



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (QPID-8199) [Broker-J] Improved description for bind/unbind operations

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-8199:
-
Status: Reviewable  (was: In Progress)

> [Broker-J] Improved description for bind/unbind operations
> --
>
> Key: QPID-8199
> URL: https://issues.apache.org/jira/browse/QPID-8199
> Project: Qpid
>  Issue Type: Improvement
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, 
> qpid-java-broker-7.0.0, qpid-java-broker-7.0.1
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
>
> The description for unbind operation is misleading. It should be improved to 
> state that only one binding with given queue name and given binding key would 
> be deleted



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (QPID-8198) [Broker-J][Documentation] Account headers in formula for estimation of heap size

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-8198:
-
Status: Reviewable  (was: In Progress)

> [Broker-J][Documentation] Account headers in formula for estimation of heap 
> size
> 
>
> Key: QPID-8198
> URL: https://issues.apache.org/jira/browse/QPID-8198
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J, Java Documentation
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
>
> The formula for estimation of required heap size should allow to specify 
> variables for message headers. Otherwise, the estimated value would be far 
> from required. For example, in Broker with 1G of heap it is possible to 
> publish 568920 AMQP 1-0 messages without application properties. However, it 
> is possible to publish around 208700 messages if each message contains 20 
> application specific properties with average size of 20 bytes for name and 
> value.
> The formula for estimation of required heap size should allow to specify the 
> following:
> * average size of property name and value
> * average number of application properties per message



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (QPID-8139) [Broker-J] [AMQP1-0] [JMSBINDMAP] JMS selectors using JMSMessageID or JMSCorrelationID expressed using the AMQP type encoded form values fail to select target message

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-8139:
-
Fix Version/s: qpid-java-broker-7.1.0

> [Broker-J] [AMQP1-0] [JMSBINDMAP]  JMS selectors using JMSMessageID or 
> JMSCorrelationID expressed using the AMQP type encoded form values fail to 
> select target message
> ---
>
> Key: QPID-8139
> URL: https://issues.apache.org/jira/browse/QPID-8139
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.2, qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0
>
> Attachments: 
> 0001-QPID-8139-Broker-J-AMQP-1.0-Make-sure-that-selector-.patch
>
>
> When using the Qpid JMS AMQP 1.0 Client with Broker-J, if the consumer 
> specifies a JMS message selectors including a {{JMSMessageID}} or 
> {{JMSCorrelationID}} predicate, the selector can fail to find the target 
> message in some circumstances.  This occurs when the message producer is 
> configured to use one of the following {{jms.messageIDPolicy.messageIDType}} 
> modes: {{UUID}}. {{UUID_STRING}}, {{PREFIXED_UUID_STRING}}.   In the default 
> mode, {{BUILTIN}} the problem does not manifest.
> The issue is the Broker-J JMS selector implementation does not understand the 
> AMQP type encoded forms specified by 3.2.1.1 of the Advanced Message Queuing 
> Protocol (AMQP) JMS Mapping Version 1.0 [WD9].
> The problem also manifests when the Broker's message conversion feature is in 
> use.   For instance, a message produced by a AMQP 0-10 producer cannot be 
> selected by an consumer using a Qpid JMS Client 1.0 using a  {{JMSMessageID}} 
> or {{JMSCorrelationID}} predicate.  This was originally highlighted by the 
> following user list post:
> http://qpid.2158936.n2.nabble.com/JMSMessageID-differences-in-JMS-0-30-0-and-JMS-AMQP-0-x-6-3-0-clients-td7674019.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (QPID-8198) [Broker-J][Documentation] Account headers in formula for estimation of heap size

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-8198:
-
Summary: [Broker-J][Documentation] Account headers in formula for 
estimation of heap size  (was: [Broker-J[Documentation] Account headers in 
formula for estimation of heap size)

> [Broker-J][Documentation] Account headers in formula for estimation of heap 
> size
> 
>
> Key: QPID-8198
> URL: https://issues.apache.org/jira/browse/QPID-8198
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J, Java Documentation
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
>
> The formula for estimation of required heap size should allow to specify 
> variables for message headers. Otherwise, the estimated value would be far 
> from required. For example, in Broker with 1G of heap it is possible to 
> publish 568920 AMQP 1-0 messages without application properties. However, it 
> is possible to publish around 208700 messages if each message contains 20 
> application specific properties with average size of 20 bytes for name and 
> value.
> The formula for estimation of required heap size should allow to specify the 
> following:
> * average size of property name and value
> * average number of application properties per message



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (QPID-8199) [Broker-J] Improved description for bind/unbind operations

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-8199:
-
Summary: [Broker-J] Improved description for bind/unbind operations  (was: 
[Broker] Improved description for bind/unbind operations)

> [Broker-J] Improved description for bind/unbind operations
> --
>
> Key: QPID-8199
> URL: https://issues.apache.org/jira/browse/QPID-8199
> Project: Qpid
>  Issue Type: Improvement
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, 
> qpid-java-broker-7.0.0, qpid-java-broker-7.0.1
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
>
> The description for unbind operation is misleading. It should be improved to 
> state that only one binding with given queue name and given binding key would 
> be deleted



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Assigned] (QPID-8192) [Broker-J] Make bindingKey parameter mandatory in exchange bind/unbind operations

[Alex Rudyy (JIRA)]

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

Alex Rudyy reassigned QPID-8192:


Assignee: Alex Rudyy

> [Broker-J] Make bindingKey parameter mandatory in exchange bind/unbind 
> operations
> -
>
> Key: QPID-8192
> URL: https://issues.apache.org/jira/browse/QPID-8192
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, 
> qpid-java-broker-7.0.0, qpid-java-broker-7.0.1
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0
>
> Attachments: 
> 0001-QPID-8192-Broker-J-Make-bindingKey-parameter-mandato.patch
>
>
> Make bindingKey parameter mandatory in exchange bind/unbind operations but 
> allow the value of the binding key to be the empty string. Optional 
> bindingKey parameter causes confusions in understanding how bind/unbind 
> operations works, as omitting  bindingKey in unbind operation could be 
> misinterpreted as bulk bindings deletion for the given destination. The 
> unbind operation description text should be fixed as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Assigned] (QPID-8199) [Broker] Improved description for bind/unbind operations

[Alex Rudyy (JIRA)]

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

Alex Rudyy reassigned QPID-8199:


Assignee: Alex Rudyy

> [Broker] Improved description for bind/unbind operations
> 
>
> Key: QPID-8199
> URL: https://issues.apache.org/jira/browse/QPID-8199
> Project: Qpid
>  Issue Type: Improvement
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, 
> qpid-java-broker-7.0.0, qpid-java-broker-7.0.1
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
>
> The description for unbind operation is misleading. It should be improved to 
> state that only one binding with given queue name and given binding key would 
> be deleted



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Assigned] (QPID-8198) [Broker-J[Documentation] Account headers in formula for estimation of heap size

[Alex Rudyy (JIRA)]

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

Alex Rudyy reassigned QPID-8198:


Assignee: Alex Rudyy

> [Broker-J[Documentation] Account headers in formula for estimation of heap 
> size
> ---
>
> Key: QPID-8198
> URL: https://issues.apache.org/jira/browse/QPID-8198
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J, Java Documentation
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
>
> The formula for estimation of required heap size should allow to specify 
> variables for message headers. Otherwise, the estimated value would be far 
> from required. For example, in Broker with 1G of heap it is possible to 
> publish 568920 AMQP 1-0 messages without application properties. However, it 
> is possible to publish around 208700 messages if each message contains 20 
> application specific properties with average size of 20 bytes for name and 
> value.
> The formula for estimation of required heap size should allow to specify the 
> following:
> * average size of property name and value
> * average number of application properties per message



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (QPID-8192) [Broker-J] Make bindingKey parameter mandatory in exchange bind/unbind operations

[ASF subversion and git services (JIRA)]

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

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

Commit bb2adc3ae4756f0ecb88ddf2e770c1bd7976d63c in qpid-broker-j's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=bb2adc3 ]

QPID-8192: [Broker-J] Make bindingKey parameter mandatory in exchange 
bind/unbind operations (WIP)


> [Broker-J] Make bindingKey parameter mandatory in exchange bind/unbind 
> operations
> -
>
> Key: QPID-8192
> URL: https://issues.apache.org/jira/browse/QPID-8192
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, 
> qpid-java-broker-7.0.0, qpid-java-broker-7.0.1
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0
>
> Attachments: 
> 0001-QPID-8192-Broker-J-Make-bindingKey-parameter-mandato.patch
>
>
> Make bindingKey parameter mandatory in exchange bind/unbind operations but 
> allow the value of the binding key to be the empty string. Optional 
> bindingKey parameter causes confusions in understanding how bind/unbind 
> operations works, as omitting  bindingKey in unbind operation could be 
> misinterpreted as bulk bindings deletion for the given destination. The 
> unbind operation description text should be fixed as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (QPID-8198) [Broker-J[Documentation] Account headers in formula for estimation of heap size

[ASF subversion and git services (JIRA)]

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

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

Commit db971ea2ba02f9f5128daac0ab310dad5c8f8fba in qpid-broker-j's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=db971ea ]

QPID-8198: [Broker-J[Documentation] Account headers in formula for estimation 
of heap size


> [Broker-J[Documentation] Account headers in formula for estimation of heap 
> size
> ---
>
> Key: QPID-8198
> URL: https://issues.apache.org/jira/browse/QPID-8198
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J, Java Documentation
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
>
> The formula for estimation of required heap size should allow to specify 
> variables for message headers. Otherwise, the estimated value would be far 
> from required. For example, in Broker with 1G of heap it is possible to 
> publish 568920 AMQP 1-0 messages without application properties. However, it 
> is possible to publish around 208700 messages if each message contains 20 
> application specific properties with average size of 20 bytes for name and 
> value.
> The formula for estimation of required heap size should allow to specify the 
> following:
> * average size of property name and value
> * average number of application properties per message



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (QPID-8139) [Broker-J] [AMQP1-0] [JMSBINDMAP] JMS selectors using JMSMessageID or JMSCorrelationID expressed using the AMQP type encoded form values fail to select target message

[ASF subversion and git services (JIRA)]

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

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

Commit f1ce8666b80aa1ddd30445a6b2ce47db6b6943e9 in qpid-broker-j's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=f1ce866 ]

QPID-8139: [Broker-J][AMQP 1.0] Make sure that selector filter can handle 
JMSMessageID and JMSCorrelationID values with prefixes as defined in AMQP JMS 
mapping specification


> [Broker-J] [AMQP1-0] [JMSBINDMAP]  JMS selectors using JMSMessageID or 
> JMSCorrelationID expressed using the AMQP type encoded form values fail to 
> select target message
> ---
>
> Key: QPID-8139
> URL: https://issues.apache.org/jira/browse/QPID-8139
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.2, qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Attachments: 
> 0001-QPID-8139-Broker-J-AMQP-1.0-Make-sure-that-selector-.patch
>
>
> When using the Qpid JMS AMQP 1.0 Client with Broker-J, if the consumer 
> specifies a JMS message selectors including a {{JMSMessageID}} or 
> {{JMSCorrelationID}} predicate, the selector can fail to find the target 
> message in some circumstances.  This occurs when the message producer is 
> configured to use one of the following {{jms.messageIDPolicy.messageIDType}} 
> modes: {{UUID}}. {{UUID_STRING}}, {{PREFIXED_UUID_STRING}}.   In the default 
> mode, {{BUILTIN}} the problem does not manifest.
> The issue is the Broker-J JMS selector implementation does not understand the 
> AMQP type encoded forms specified by 3.2.1.1 of the Advanced Message Queuing 
> Protocol (AMQP) JMS Mapping Version 1.0 [WD9].
> The problem also manifests when the Broker's message conversion feature is in 
> use.   For instance, a message produced by a AMQP 0-10 producer cannot be 
> selected by an consumer using a Qpid JMS Client 1.0 using a  {{JMSMessageID}} 
> or {{JMSCorrelationID}} predicate.  This was originally highlighted by the 
> following user list post:
> http://qpid.2158936.n2.nabble.com/JMSMessageID-differences-in-JMS-0-30-0-and-JMS-AMQP-0-x-6-3-0-clients-td7674019.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (QPID-8199) [Broker] Improved description for bind/unbind operations

[ASF subversion and git services (JIRA)]

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

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

Commit 5ccf63f06f218c11af549823ff6ca25585c5fad5 in qpid-broker-j's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=5ccf63f ]

QPID-8199: [Broker-J] Fix unbind/bind operation descriptions


> [Broker] Improved description for bind/unbind operations
> 
>
> Key: QPID-8199
> URL: https://issues.apache.org/jira/browse/QPID-8199
> Project: Qpid
>  Issue Type: Improvement
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, 
> qpid-java-broker-7.0.0, qpid-java-broker-7.0.1
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
>
> The description for unbind operation is misleading. It should be improved to 
> state that only one binding with given queue name and given binding key would 
> be deleted



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Created] (QPID-8199) [Broker] Improved description for bind/unbind operations

[Alex Rudyy (JIRA)]

Alex Rudyy created QPID-8199:


 Summary: [Broker] Improved description for bind/unbind operations
 Key: QPID-8199
 URL: https://issues.apache.org/jira/browse/QPID-8199
 Project: Qpid
  Issue Type: Improvement
  Components: Broker-J
Affects Versions: qpid-java-broker-7.0.1, qpid-java-broker-7.0.0, 
qpid-java-broker-7.0.2, qpid-java-broker-7.0.3
Reporter: Alex Rudyy
 Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4


The description for unbind operation is misleading. It should be improved to 
state that only one binding with given queue name and given binding key would 
be deleted



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Created] (QPID-8198) [Broker-J[Documentation] Account headers in formula for estimation of heap size

[Alex Rudyy (JIRA)]

Alex Rudyy created QPID-8198:


 Summary: [Broker-J[Documentation] Account headers in formula for 
estimation of heap size
 Key: QPID-8198
 URL: https://issues.apache.org/jira/browse/QPID-8198
 Project: Qpid
  Issue Type: Bug
  Components: Broker-J, Java Documentation
Reporter: Alex Rudyy
 Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4


The formula for estimation of required heap size should allow to specify 
variables for message headers. Otherwise, the estimated value would be far from 
required. For example, in Broker with 1G of heap it is possible to publish 
568920 AMQP 1-0 messages without application properties. However, it is 
possible to publish around 208700 messages if each message contains 20 
application specific properties with average size of 20 bytes for name and 
value.
The formula for estimation of required heap size should allow to specify the 
following:
* average size of property name and value
* average number of application properties per message



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (DISPATCH-1009) _qd_policy_link_user_name_subst can return an unterminated string

[Chuck Rolke (JIRA)]

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

Chuck Rolke commented on DISPATCH-1009:
---

This issue will be fixed in the context of DISPATCH-1011. The offending 
function with strncpy will be replaced.

> _qd_policy_link_user_name_subst can return an unterminated string
> -
>
> Key: DISPATCH-1009
> URL: https://issues.apache.org/jira/browse/DISPATCH-1009
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Policy Engine
>Affects Versions: 1.0.1
>Reporter: Alan Conway
>Assignee: Chuck Rolke
>Priority: Major
>
> On fedora 28 the gcc 8.1.1 compiler gives this warning-as-error:
> /home/aconway/dispatch/src/policy.c: In function 
> '_qd_policy_link_user_name_subst':
> /home/aconway/dispatch/src/policy.c:541:9: error: 'strncpy' output may be 
> truncated copying between 0 and 8 bytes from a string of length 7 
> [-Werror=stringop-truncation]
>  strncpy(obuf, duser, copysize);
>  ^~
> cc1: all warnings being treated as errors
>  
> The error is correct: the function is using strncpy to copy a string into a 
> space that may be too small for it, resulting in an un-terminated string.
> I fixed some similar issues already but I'm confused by what's going on here: 
> it looks like we are searching for the uname parameter and replacing it with 
> "${user}" which seems backwards.
> The function would be simpler and clearer if it used snprintf rather than 
> successive strncpy, i.e.
>     n = snprintf(obuf, osize, "%s%s%s", leading, duser, trailing);
> but the problem of properly handling the error if the resulting string is too 
> big for obuf remains.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Created] (DISPATCH-1011) Policy username substitution fails to match certain user names

[Chuck Rolke (JIRA)]

Chuck Rolke created DISPATCH-1011:
-

 Summary: Policy username substitution fails to match certain user 
names
 Key: DISPATCH-1011
 URL: https://issues.apache.org/jira/browse/DISPATCH-1011
 Project: Qpid Dispatch
  Issue Type: Bug
  Components: Policy Engine
Affects Versions: 1.0.1
Reporter: Chuck Rolke
Assignee: Chuck Rolke


If a username is a substring of a policy rule's static text then the username 
substitution fails. For example:

{{    if (!_qd_policy_approve_link_name("em", "temp-${user}", "temp-em"))}}
{{    return "proposed link 'temp-em' should match allowed links with 
${user} but does not";}}

Since the username *em* is found in the fixed text of *temp-* then the 
substitution logic goes awry and the match fails. Thanks to aconway for making 
this observation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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