[
https://issues.apache.org/jira/browse/DISPATCH-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216936#comment-15216936
]
ASF GitHub Bot commented on DISPATCH-200:
-
GitHub user ganeshmurthy opened a pul
GitHub user ganeshmurthy opened a pull request:
https://github.com/apache/qpid-dispatch/pull/61
DISPATCH-200 - Add a flexible mapping from x.509 certificate fields tâ¦
â¦o an identity
You can merge this pull request into a Git repository by running:
$ git pull https://github.
[
https://issues.apache.org/jira/browse/DISPATCH-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned DISPATCH-242:
-
Assignee: Ted Ross
> Add options to qdstat to display autoLinks and linkRoutes
> --
[
https://issues.apache.org/jira/browse/DISPATCH-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned DISPATCH-237:
-
Assignee: Ted Ross
> Dispatch Router overwrites delivery tag for link-routed deliveries
> -
[
https://issues.apache.org/jira/browse/DISPATCH-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-55:
-
Fix Version/s: (was: 0.6)
0.7
> Qdrouterd does not exit when service port is unava
[
https://issues.apache.org/jira/browse/DISPATCH-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-158:
--
Fix Version/s: (was: 0.6)
> Dispatch should ignore frames after receiving close frame
> --
[
https://issues.apache.org/jira/browse/DISPATCH-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-177:
--
Assignee: Ken Giusti
> Valgrind finds leaks when running dispatch w/SSL
>
[
https://issues.apache.org/jira/browse/DISPATCH-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-187:
--
Fix Version/s: (was: 0.6)
> CMake must choose the Python2 libraries when Python3 is available
> --
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/45389/#review125953
---
This looks good to me (and from what I can see is largely backward
[
https://issues.apache.org/jira/browse/DISPATCH-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-120:
--
Fix Version/s: (was: 0.6)
> qdrouterd command line improvements
>
[
https://issues.apache.org/jira/browse/DISPATCH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross resolved DISPATCH-57.
--
Resolution: Fixed
> Balance deliveries adaptively across all competing consumers in the network
> -
[
https://issues.apache.org/jira/browse/DISPATCH-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross closed DISPATCH-236.
-
Resolution: Won't Fix
Consider re-raising in the future when the thread-sanitize feature is more
mature
[
https://issues.apache.org/jira/browse/DISPATCH-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-70:
-
Fix Version/s: (was: 0.6)
> Configurable initial-credit and credit batching needed for incoming links
[
https://issues.apache.org/jira/browse/DISPATCH-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-227:
--
Fix Version/s: (was: 0.6)
> Independent filtering of logging to consoles and log files.
>
[
https://issues.apache.org/jira/browse/DISPATCH-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-185:
--
Fix Version/s: (was: 0.6)
> Support for management notifications, log messages as notifications
>
[
https://issues.apache.org/jira/browse/DISPATCH-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross resolved DISPATCH-166.
---
Resolution: Fixed
> Use test-controlled SASL configuration for system tests
> --
[
https://issues.apache.org/jira/browse/DISPATCH-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-157:
--
Fix Version/s: (was: 0.6)
> add sasl tests to dispatch unit tests
> --
[
https://issues.apache.org/jira/browse/QPIDJMS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish reassigned QPIDJMS-163:
Assignee: Timothy Bish
> support populating the user-id field on produced messages
> -
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/45389/
---
(Updated March 29, 2016, 8:27 p.m.)
Review request for qpid, Gordon Sim, Justin
[
https://issues.apache.org/jira/browse/DISPATCH-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-241.
Resolution: Fixed
> Bias "spread" config with leading "/" on address has a "multicast" beh
[
https://issues.apache.org/jira/browse/DISPATCH-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-240.
Resolution: Fixed
> qdstat : leading "/" character effects a wrong showed address
> --
[
https://issues.apache.org/jira/browse/DISPATCH-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway closed DISPATCH-244.
Resolution: Fixed
Not a dispatch bug, this appears to be a problem with cyrus SASL in general.
Ha
[
https://issues.apache.org/jira/browse/DISPATCH-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway closed DISPATCH-218.
Resolution: Fixed
Not a dispatch bug, this appears to be a problem with cyrus SASL in general.
Ha
[
https://issues.apache.org/jira/browse/DISPATCH-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-194:
--
Assignee: Chuck Rolke
> Move libqpid-dispatch.so out of /lib
>
>
[
https://issues.apache.org/jira/browse/DISPATCH-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross resolved DISPATCH-191.
---
Resolution: Fixed
> router not replying to detach frame
> ---
>
>
[
https://issues.apache.org/jira/browse/QPID-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7168:
-
Fix Version/s: qpid-java-6.1
> Allow authentication providers to resolve a realm qualified user identity
>
Keith Wall created QPID-7168:
Summary: Allow authentication providers to resolve a realm
qualified user identity into a displayable name
Key: QPID-7168
URL: https://issues.apache.org/jira/browse/QPID-7168
[
https://issues.apache.org/jira/browse/QPIDJMS-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved QPIDJMS-159.
Resolution: Fixed
Fix Version/s: 0.9.0
> support producers having their existing cre
[
https://issues.apache.org/jira/browse/QPID-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Scholz updated QPID-7159:
---
Attachment: QPID-7159-conn-option.patch
Alternative patch which uses connection option instead of syste
[
https://issues.apache.org/jira/browse/QPID-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216282#comment-15216282
]
Jakub Scholz commented on QPID-7159:
Hi Alex,
You are right, connection option would b
Robbie Gemmell created QPIDJMS-163:
--
Summary: support populating the user-id field on produced messages
Key: QPIDJMS-163
URL: https://issues.apache.org/jira/browse/QPIDJMS-163
Project: Qpid JMS
[
https://issues.apache.org/jira/browse/QPID-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216182#comment-15216182
]
Keith Wall edited comment on QPID-7116 at 3/29/16 4:18 PM:
---
There
[
https://issues.apache.org/jira/browse/QPIDJMS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved QPIDJMS-157.
--
Resolution: Fixed
> Add support for send timeout and request timeout options
>
[
https://issues.apache.org/jira/browse/QPID-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7167:
-
Description:
For the LDAP provider, identities (users/groups) produced should be in the form:
{noformat}{i
[
https://issues.apache.org/jira/browse/QPID-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7167:
-
Description:
For the LDAP provider, identities produced should be in the form:
{noformat}{identity}@{realm
[
https://issues.apache.org/jira/browse/QPID-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216245#comment-15216245
]
Rob Godfrey commented on QPID-6984:
---
So, I don't really think that Queries are managed/co
[
https://issues.apache.org/jira/browse/QPID-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7167:
-
Description: For the LDAP provider, identities produced should be in the
form {norma
> Make user/group nam
Keith Wall created QPID-7167:
Summary: Make user/group names produced by LDAP authentication and
group provider be realm qualified
Key: QPID-7167
URL: https://issues.apache.org/jira/browse/QPID-7167
Proje
[
https://issues.apache.org/jira/browse/QPID-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7166:
-
Description:
Change the existing authentication providers/group providers to produce
principals contain a
Keith Wall created QPID-7166:
Summary: Make user/group names produced by authentication and
group providers realm qualified
Key: QPID-7166
URL: https://issues.apache.org/jira/browse/QPID-7166
Project: Qpi
[
https://issues.apache.org/jira/browse/QPID-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216182#comment-15216182
]
Keith Wall commented on QPID-7116:
--
There is also a second common way of representing grou
[
https://issues.apache.org/jira/browse/QPID-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7116:
-
Description:
The Java Broker can already authenticate users against an LDAP compatible
directory. It shou
[
https://issues.apache.org/jira/browse/QPID-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216123#comment-15216123
]
Alex Rudyy commented on QPID-7159:
--
Hi Jakub,
The requested feature looks really useful
[
https://issues.apache.org/jira/browse/QPID-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7116:
-
Description:
The Java Broker can already authenticate users against an LDAP compatible
directory. It shou
[
https://issues.apache.org/jira/browse/DISPATCH-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216110#comment-15216110
]
ASF subversion and git services commented on DISPATCH-201:
--
Com
[
https://issues.apache.org/jira/browse/DISPATCH-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-200:
--
Fix Version/s: (was: 0.7)
0.6
> Flexible mapping from x.509 certificates to an
[
https://issues.apache.org/jira/browse/DISPATCH-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-188:
--
Fix Version/s: (was: 0.7)
0.6
> Dispatch needs a policy mechanism to limit user
[
https://issues.apache.org/jira/browse/QPID-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7165:
-
Issue Type: New Feature (was: Bug)
> Allow query results to be sorted and paginated
>
Keith Wall created QPID-7165:
Summary: Allow query results to be sorted and paginated
Key: QPID-7165
URL: https://issues.apache.org/jira/browse/QPID-7165
Project: Qpid
Issue Type: Bug
C
[
https://issues.apache.org/jira/browse/QPID-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216016#comment-15216016
]
Keith Wall edited comment on QPID-6984 at 3/29/16 1:46 PM:
---
Perha
[
https://issues.apache.org/jira/browse/QPID-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216016#comment-15216016
]
Keith Wall commented on QPID-6984:
--
Perhaps the model should have a {{Query}} object that
[
https://issues.apache.org/jira/browse/QPID-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-6984:
-
Description:
After defining a query (QPID-6969) the user should be able to save query so it
may be conveni
[
https://issues.apache.org/jira/browse/QPID-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-6984:
-
Description:
After defining a query (QPID-6969) the user should be able to save query so it
may be conveni
[
https://issues.apache.org/jira/browse/DISPATCH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215991#comment-15215991
]
ASF subversion and git services commented on DISPATCH-57:
-
Commit
[
https://issues.apache.org/jira/browse/QPID-7082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7082:
-
Fix Version/s: qpid-java-6.1
> [Java Broker] Created AccessControllerContext for SystemTasks should not
>
[
https://issues.apache.org/jira/browse/QPID-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7037:
-
Attachment: 0001-QPID-7037-Add-ability-into-Web-Management-Console-to.patch
Attached a patch with possible
[
https://issues.apache.org/jira/browse/QPID-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7023:
-
Fix Version/s: qpid-java-6.0.2
> BDB HA: JE Cleaner warnings written to qpid log during apparently normal
[
https://issues.apache.org/jira/browse/QPID-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7155:
-
Fix Version/s: qpid-java-6.1
qpid-java-6.0.2
> [Java Broker] Idle timeout ticker times o
[
https://issues.apache.org/jira/browse/QPID-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7160:
-
Fix Version/s: qpid-java-6.1
> No X509TrustManager implementation available when using truststore captured
On 29/03/16 12:22, Keith W wrote:
On 29 March 2016 at 09:13, Gordon Sim wrote:
On 28/03/16 08:57, Keith W wrote:
Hi all,
I am trying to automate the running of the existing Python AMQP 1.0
broker tests against the Java Broker with the proton-c/cpp binary
dependencies built from their respect
[
https://issues.apache.org/jira/browse/QPID-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7164:
-
Fix Version/s: Future
> Python test
> qpid_tests.broker_0_10.new_api.GeneralTests.test_qpid_3481_acquired_
[
https://issues.apache.org/jira/browse/QPID-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall resolved QPID-6995.
--
Resolution: Fixed
> [Java Broker] Keystores should warn of pending certificate expiration
> -
On 29 March 2016 at 09:13, Gordon Sim wrote:
> On 28/03/16 08:57, Keith W wrote:
>>
>> Hi all,
>>
>> I am trying to automate the running of the existing Python AMQP 1.0
>> broker tests against the Java Broker with the proton-c/cpp binary
>> dependencies built from their respective trunks.
>>
>> I
[
https://issues.apache.org/jira/browse/QPID-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201507#comment-15201507
]
Keith Wall edited comment on QPID-7154 at 3/29/16 11:12 AM:
(P
[
https://issues.apache.org/jira/browse/QPID-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215859#comment-15215859
]
ASF subversion and git services commented on QPID-6995:
---
Commit 17369
[
https://issues.apache.org/jira/browse/QPIDJMS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215853#comment-15215853
]
ASF subversion and git services commented on QPIDJMS-157:
-
Commit
[
https://issues.apache.org/jira/browse/QPIDJMS-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215854#comment-15215854
]
ASF subversion and git services commented on QPIDJMS-159:
-
Commit
[
https://issues.apache.org/jira/browse/QPID-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy reassigned QPID-7037:
Assignee: Alex Rudyy
> [Java Broker] Add UI for exposing trust stores as message sources
> -
[
https://issues.apache.org/jira/browse/QPID-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7154:
-
Affects Version/s: (was: 0.22)
(was: 0.18)
> Dead lettering of a message may
[
https://issues.apache.org/jira/browse/QPID-7095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey resolved QPID-7095.
---
Resolution: Fixed
> [Java Broker] Add mechanism to extract meta data for context variables
> describin
[
https://issues.apache.org/jira/browse/QPID-7095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey updated QPID-7095:
--
Description: Currently there is no way to discover which context variables
are used by the broker, and th
[
https://issues.apache.org/jira/browse/QPID-7095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey updated QPID-7095:
--
Summary: [Java Broker] Add mechanism to extract meta data for context
variables describing their usage (
[
https://issues.apache.org/jira/browse/QPID-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7154:
-
Summary: Dead lettering of a message may timeout at store level, causing
unexpected Broker shutdown (was:
[
https://issues.apache.org/jira/browse/QPID-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7154:
-
Summary: Dead lettering of a message may timeout (was: JMX
QueueMBean#clearQueue operation does not acquir
[
https://issues.apache.org/jira/browse/QPID-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7157:
-
Description: metadata information should drive implementation of UI widgets
for rendering attribute values.
[
https://issues.apache.org/jira/browse/QPID-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7157:
-
Summary: [Java Broker] Change metadata for management attributes having
enum types to list all possible enu
[
https://issues.apache.org/jira/browse/QPID-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215765#comment-15215765
]
Keith Wall commented on QPID-7157:
--
For enums, we will automatically populate valid values
[
https://issues.apache.org/jira/browse/QPID-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7158:
-
Fix Version/s: qpid-java-6.1
> [Java Broker] Change type of datetime management attributes from Long to
>
[
https://issues.apache.org/jira/browse/QPID-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7157:
-
Fix Version/s: qpid-java-6.1
> [Java Broker] Enhance metadata service to provide more information about
>
[
https://issues.apache.org/jira/browse/QPID-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7158:
-
Summary: [Java Broker] Change type of datetime management attributes from
Long to java.util.Date (was: [Ja
[
https://issues.apache.org/jira/browse/QPID-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7158:
-
Description: It is unclear from metadata that datetime attribute having
type Long actually represent date
[
https://issues.apache.org/jira/browse/QPID-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7158:
-
Summary: [Java Broker] Change datetime management attributes to have Date
type rather then Long (was: [Jav
[
https://issues.apache.org/jira/browse/QPIDJMS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215710#comment-15215710
]
ASF subversion and git services commented on QPIDJMS-157:
-
Commit
[
https://issues.apache.org/jira/browse/QPID-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack resolved QPID-7161.
Resolution: Fixed
looks good to me
> System test output lost owing to orphaned shutdown hooks
>
On 28/03/16 08:57, Keith W wrote:
Hi all,
I am trying to automate the running of the existing Python AMQP 1.0
broker tests against the Java Broker with the proton-c/cpp binary
dependencies built from their respective trunks.
I am installing the Python modules to a private site-package
directory
[
https://issues.apache.org/jira/browse/QPID-7149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215607#comment-15215607
]
Pavel Moravec commented on QPID-7149:
-
It allows everything:
acl allow all all
I expl
86 matches
Mail list logo