date:20130730

[jira] [Assigned] (QPID-4875) [Java] The parsing logic for certificate subjects doesn't work properly in all cases

2013-07-30 Thread Rob Godfrey (JIRA)


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

Rob Godfrey reassigned QPID-4875:
-

Assignee: Rob Godfrey

> [Java] The parsing logic for certificate subjects doesn't work properly in 
> all cases
> 
>
> Key: QPID-4875
> URL: https://issues.apache.org/jira/browse/QPID-4875
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker, Java Client, Java Common
>Reporter: JAkub Scholz
>Assignee: Rob Godfrey
>Priority: Minor
> Fix For: Future
>
> Attachments: cert_parsing.patch
>
>
> The Java code seems to contain two places where the certificate subjects are 
> being parsed. One is used in the client:
> {{common/src/main/java/org/apache/qpid/transport/network/security/ssl/SSLUtil.java}}
> and the second is used in the broker:
> {{broker/src/main/java/org/apache/qpid/server/security/auth/sasl/external/ExternalSaslServer.java}}
> Both are actually doing the same - extracting the CN and DC components from 
> the subject and creating the username. It should be reconsidered whether we 
> want to reuse the SSLUtil functionality from the common part of the code in 
> the broker code as well.
> However, a bigger problem is that the implementation in both places are not 
> working correctly in all situations. One can very easily create a certificate 
> with a subject / DN like this:
> {{C=CZ,O=Scholz,OU="JAKUB CN=USER1"}}
> such certificate actually doesn't contain a CN. But both current 
> implementations will still identify the CN as {{USER1"}} in the code. I would 
> expect that this will happen only in very rare cases, but it should still be 
> handled properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Assigned] (QPID-4875) [Java] The parsing logic for certificate subjects doesn't work properly in all cases

2013-07-30 Thread Rob Godfrey (JIRA)


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

Rob Godfrey reassigned QPID-4875:
-

Assignee: Robbie Gemmell  (was: Rob Godfrey)

> [Java] The parsing logic for certificate subjects doesn't work properly in 
> all cases
> 
>
> Key: QPID-4875
> URL: https://issues.apache.org/jira/browse/QPID-4875
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker, Java Client, Java Common
>Reporter: JAkub Scholz
>Assignee: Robbie Gemmell
>Priority: Minor
> Fix For: Future
>
> Attachments: cert_parsing.patch
>
>
> The Java code seems to contain two places where the certificate subjects are 
> being parsed. One is used in the client:
> {{common/src/main/java/org/apache/qpid/transport/network/security/ssl/SSLUtil.java}}
> and the second is used in the broker:
> {{broker/src/main/java/org/apache/qpid/server/security/auth/sasl/external/ExternalSaslServer.java}}
> Both are actually doing the same - extracting the CN and DC components from 
> the subject and creating the username. It should be reconsidered whether we 
> want to reuse the SSLUtil functionality from the common part of the code in 
> the broker code as well.
> However, a bigger problem is that the implementation in both places are not 
> working correctly in all situations. One can very easily create a certificate 
> with a subject / DN like this:
> {{C=CZ,O=Scholz,OU="JAKUB CN=USER1"}}
> such certificate actually doesn't contain a CN. But both current 
> implementations will still identify the CN as {{USER1"}} in the code. I would 
> expect that this will happen only in very rare cases, but it should still be 
> handled properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (QPID-4875) [Java] The parsing logic for certificate subjects doesn't work properly in all cases

2013-07-30 Thread Rob Godfrey (JIRA)


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

Rob Godfrey commented on QPID-4875:
---

I've made a change using LdapName to parse the DNs but otherwise identical to 
the patch from Michal

> [Java] The parsing logic for certificate subjects doesn't work properly in 
> all cases
> 
>
> Key: QPID-4875
> URL: https://issues.apache.org/jira/browse/QPID-4875
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker, Java Client, Java Common
>Reporter: JAkub Scholz
>Priority: Minor
> Fix For: Future
>
> Attachments: cert_parsing.patch
>
>
> The Java code seems to contain two places where the certificate subjects are 
> being parsed. One is used in the client:
> {{common/src/main/java/org/apache/qpid/transport/network/security/ssl/SSLUtil.java}}
> and the second is used in the broker:
> {{broker/src/main/java/org/apache/qpid/server/security/auth/sasl/external/ExternalSaslServer.java}}
> Both are actually doing the same - extracting the CN and DC components from 
> the subject and creating the username. It should be reconsidered whether we 
> want to reuse the SSLUtil functionality from the common part of the code in 
> the broker code as well.
> However, a bigger problem is that the implementation in both places are not 
> working correctly in all situations. One can very easily create a certificate 
> with a subject / DN like this:
> {{C=CZ,O=Scholz,OU="JAKUB CN=USER1"}}
> such certificate actually doesn't contain a CN. But both current 
> implementations will still identify the CN as {{USER1"}} in the code. I would 
> expect that this will happen only in very rare cases, but it should still be 
> handled properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Updated] (QPID-4875) [Java] The parsing logic for certificate subjects doesn't work properly in all cases

2013-07-30 Thread Rob Godfrey (JIRA)


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

Rob Godfrey updated QPID-4875:
--

Status: Ready To Review  (was: In Progress)

> [Java] The parsing logic for certificate subjects doesn't work properly in 
> all cases
> 
>
> Key: QPID-4875
> URL: https://issues.apache.org/jira/browse/QPID-4875
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker, Java Client, Java Common
>Reporter: JAkub Scholz
>Assignee: Rob Godfrey
>Priority: Minor
> Fix For: Future
>
> Attachments: cert_parsing.patch
>
>
> The Java code seems to contain two places where the certificate subjects are 
> being parsed. One is used in the client:
> {{common/src/main/java/org/apache/qpid/transport/network/security/ssl/SSLUtil.java}}
> and the second is used in the broker:
> {{broker/src/main/java/org/apache/qpid/server/security/auth/sasl/external/ExternalSaslServer.java}}
> Both are actually doing the same - extracting the CN and DC components from 
> the subject and creating the username. It should be reconsidered whether we 
> want to reuse the SSLUtil functionality from the common part of the code in 
> the broker code as well.
> However, a bigger problem is that the implementation in both places are not 
> working correctly in all situations. One can very easily create a certificate 
> with a subject / DN like this:
> {{C=CZ,O=Scholz,OU="JAKUB CN=USER1"}}
> such certificate actually doesn't contain a CN. But both current 
> implementations will still identify the CN as {{USER1"}} in the code. I would 
> expect that this will happen only in very rare cases, but it should still be 
> handled properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (QPID-4875) [Java] The parsing logic for certificate subjects doesn't work properly in all cases

2013-07-30 Thread ASF subversion and git services (JIRA)


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

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

Commit 1508680 from [~godfrer] in branch 'qpid/trunk'
[ https://svn.apache.org/r1508680 ]

QPID-4875 : The parsing logic for certificate subjects does not work properly 
in all cases

> [Java] The parsing logic for certificate subjects doesn't work properly in 
> all cases
> 
>
> Key: QPID-4875
> URL: https://issues.apache.org/jira/browse/QPID-4875
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker, Java Client, Java Common
>Reporter: JAkub Scholz
>Priority: Minor
> Fix For: Future
>
> Attachments: cert_parsing.patch
>
>
> The Java code seems to contain two places where the certificate subjects are 
> being parsed. One is used in the client:
> {{common/src/main/java/org/apache/qpid/transport/network/security/ssl/SSLUtil.java}}
> and the second is used in the broker:
> {{broker/src/main/java/org/apache/qpid/server/security/auth/sasl/external/ExternalSaslServer.java}}
> Both are actually doing the same - extracting the CN and DC components from 
> the subject and creating the username. It should be reconsidered whether we 
> want to reuse the SSLUtil functionality from the common part of the code in 
> the broker code as well.
> However, a bigger problem is that the implementation in both places are not 
> working correctly in all situations. One can very easily create a certificate 
> with a subject / DN like this:
> {{C=CZ,O=Scholz,OU="JAKUB CN=USER1"}}
> such certificate actually doesn't contain a CN. But both current 
> implementations will still identify the CN as {{USER1"}} in the code. I would 
> expect that this will happen only in very rare cases, but it should still be 
> handled properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

AMQP Management Operations

2013-07-30 Thread Ted Ross


In reference to the AMQP Management Spec. v1.0 (wd02):

I see that for retrieving information about manageable objects in a 
container there are a few options:


 * Use the "READ" operation to query a specific object by name,
 * Use the "READALL" operation to query every object in the container,
 * Use the "DISCOVER-NAMES" operation to get the names of all objects
   and then "READ" to query individual objects.

I can envision situations where a given container may contain very large 
numbers of objects (possibly millions).  In this case, READALL and 
DISCOVER-NAMES will be impractical to use (i.e. they will return with 
"413 - Request entity Too Large").  Using the optional "limit" argument 
doesn't appear to help.  The thing I'm looking for may be beyond the 
limit and I'll never see it.


It would be good to have a way to query all objects of a particular 
type.  Can READALL and DISCOVER-NAMES be altered such that specific type 
names can be used, rather than only allowing "org.amqp.management"?


Thanks,

-Ted

[jira] [Created] (QPID-5029) WinSDK build tries to handle components that have been removed

2013-07-30 Thread Chuck Rolke (JIRA)

Chuck Rolke created QPID-5029:
-

 Summary: WinSDK build tries to handle components that have been 
removed
 Key: QPID-5029
 URL: https://issues.apache.org/jira/browse/QPID-5029
 Project: Qpid
  Issue Type: Bug
  Components: Packaging
Affects Versions: 0.22
 Environment: Windows cmake install
Reporter: Chuck Rolke
Assignee: Chuck Rolke


include/qpid/agent, include/qpid/amqp_0_10, include/qpid/management directories 
have been deleted.
include/qpid/CommonImportExport.h has been moved.

The build process must adjust.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Created] (QPID-5028) Qmf2 examples install script error

2013-07-30 Thread Chuck Rolke (JIRA)

Chuck Rolke created QPID-5028:
-

 Summary: Qmf2 examples install script error
 Key: QPID-5028
 URL: https://issues.apache.org/jira/browse/QPID-5028
 Project: Qpid
  Issue Type: Bug
  Components: Packaging
Affects Versions: 0.22
 Environment: Windows cmake install
Reporter: Chuck Rolke
Assignee: Chuck Rolke


Files are not located at CMAKE_CURRENT_SOURCE_DIR

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Created] (QPID-5027) Windows examples installed to wrong directory

2013-07-30 Thread Chuck Rolke (JIRA)

Chuck Rolke created QPID-5027:
-

 Summary: Windows examples installed to wrong directory
 Key: QPID-5027
 URL: https://issues.apache.org/jira/browse/QPID-5027
 Project: Qpid
  Issue Type: Bug
  Components: Packaging
Affects Versions: 0.22
 Environment: Windows cmake install
Reporter: Chuck Rolke
Assignee: Chuck Rolke


Example source files are installed to install-root\qpid\examples.
Windows-based scripts expect the files in install-root\examples.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Re: Review Request 13079: Modify Messenger credit distribution algorithm to support credit rebalancing

2013-07-30 Thread Kenneth Giusti


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13079/#review24279
---



/proton/trunk/proton-c/src/messenger/messenger.c


This seems incorrect: should the new value of N override the last value, or 
increase the last value by N?


- Kenneth Giusti


On July 30, 2013, 8:24 p.m., Kenneth Giusti wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13079/
> ---
> 
> (Updated July 30, 2013, 8:24 p.m.)
> 
> 
> Review request for qpid and Rafael Schloming.
> 
> 
> Bugs: proton-200
> https://issues.apache.org/jira/browse/proton-200
> 
> 
> Repository: qpid
> 
> 
> Description
> ---
> 
> This patch improves the existing credit allocation scheme used by messenger.
> 
> Currently passes the new python tests for proton-c, still need to fix the 
> tests for the other test targets.
> 
> 
> Diffs
> -
> 
>   /proton/trunk/proton-c/bindings/python/proton.py 1508023 
>   /proton/trunk/proton-c/include/proton/messenger.h 1508023 
>   /proton/trunk/proton-c/src/messenger/messenger.c 1508023 
>   /proton/trunk/tests/python/proton_tests/messenger.py 1508023 
> 
> Diff: https://reviews.apache.org/r/13079/diff/
> 
> 
> Testing
> ---
> 
> New unit tests added.  Additional work necessary to get the java/jni tests to 
> pass, which I will do before checking in the patch.
> 
> 
> Thanks,
> 
> Kenneth Giusti
> 
>

Review Request 13079: Modify Messenger credit distribution algorithm to support credit rebalancing

2013-07-30 Thread Kenneth Giusti


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13079/
---

Review request for qpid and Rafael Schloming.


Bugs: proton-200
https://issues.apache.org/jira/browse/proton-200


Repository: qpid


Description
---

This patch improves the existing credit allocation scheme used by messenger.

Currently passes the new python tests for proton-c, still need to fix the tests 
for the other test targets.


Diffs
-

  /proton/trunk/proton-c/bindings/python/proton.py 1508023 
  /proton/trunk/proton-c/include/proton/messenger.h 1508023 
  /proton/trunk/proton-c/src/messenger/messenger.c 1508023 
  /proton/trunk/tests/python/proton_tests/messenger.py 1508023 

Diff: https://reviews.apache.org/r/13079/diff/


Testing
---

New unit tests added.  Additional work necessary to get the java/jni tests to 
pass, which I will do before checking in the patch.


Thanks,

Kenneth Giusti

[jira] [Commented] (QPID-5025) DeliveryRecord::committed() doesn't check if delivery is already ended

2013-07-30 Thread ASF subversion and git services (JIRA)


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

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

Commit 1508516 from [~gsim] in branch 'qpid/trunk'
[ https://svn.apache.org/r1508516 ]

QPID-5025: check that delivery has not already been ended before signalling 
commit of dequeue

> DeliveryRecord::committed() doesn't check if delivery is already ended
> --
>
> Key: QPID-5025
> URL: https://issues.apache.org/jira/browse/QPID-5025
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Affects Versions: 0.18
>Reporter: Gordon Sim
>Assignee: Gordon Sim
>Priority: Minor
> Fix For: 0.25
>
>
> Prior to 0.20 this causes a segfault. Since 0.20 it is handled much better 
> but would be nice to fix for consistency (since e.g. dequeue() does do the 
> check). Marking as minor since it has not real impact on latest version.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Resolved] (QPID-5026) [AMQP 1.0] set address for 'local' terminus in attach

2013-07-30 Thread Gordon Sim (JIRA)


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

Gordon Sim resolved QPID-5026.
--

Resolution: Fixed

> [AMQP 1.0] set address for 'local' terminus in attach
> -
>
> Key: QPID-5026
> URL: https://issues.apache.org/jira/browse/QPID-5026
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Client
>Affects Versions: 0.24
>Reporter: Gordon Sim
>Assignee: Gordon Sim
> Fix For: 0.25
>
>
> I.e. the target for receivers, the source for senders... this may be useful 
> for some intermediaries (such as dispatch!).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (QPID-5026) [AMQP 1.0] set address for 'local' terminus in attach

2013-07-30 Thread ASF subversion and git services (JIRA)


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

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

Commit 1508523 from [~gsim] in branch 'qpid/trunk'
[ https://svn.apache.org/r1508523 ]

QPID-5026: match source with target and vice-versa

> [AMQP 1.0] set address for 'local' terminus in attach
> -
>
> Key: QPID-5026
> URL: https://issues.apache.org/jira/browse/QPID-5026
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Client
>Affects Versions: 0.24
>Reporter: Gordon Sim
>Assignee: Gordon Sim
> Fix For: 0.25
>
>
> I.e. the target for receivers, the source for senders... this may be useful 
> for some intermediaries (such as dispatch!).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (QPID-5019) Add flag to distinguish QMF v1 events

2013-07-30 Thread Justin Ross (JIRA)


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

Justin Ross commented on QPID-5019:
---

Reviewed by Ted.  Approved for 0.24.

> Add flag to distinguish QMF v1 events
> -
>
> Key: QPID-5019
> URL: https://issues.apache.org/jira/browse/QPID-5019
> Project: Qpid
>  Issue Type: Bug
>  Components: Qpid Managment Framework
>Affects Versions: 0.22
>Reporter: Ken Giusti
>Assignee: Ken Giusti
> Fix For: 0.24
>
> Attachments: qpid-5019.patch
>
>
> Older brokers issue two QMF events - one per format - per incident.  Add flag 
> to Event class to help distinguish (consistent with ObjectId class).
> Bug discovered by Bill Freeman.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Resolved] (QPID-5025) DeliveryRecord::committed() doesn't check if delivery is already ended

2013-07-30 Thread Gordon Sim (JIRA)


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

Gordon Sim resolved QPID-5025.
--

Resolution: Fixed

> DeliveryRecord::committed() doesn't check if delivery is already ended
> --
>
> Key: QPID-5025
> URL: https://issues.apache.org/jira/browse/QPID-5025
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Affects Versions: 0.18
>Reporter: Gordon Sim
>Assignee: Gordon Sim
>Priority: Minor
> Fix For: 0.25
>
>
> Prior to 0.20 this causes a segfault. Since 0.20 it is handled much better 
> but would be nice to fix for consistency (since e.g. dequeue() does do the 
> check). Marking as minor since it has not real impact on latest version.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Created] (QPID-5026) [AMQP 1.0] set address for 'local' terminus in attach

2013-07-30 Thread Gordon Sim (JIRA)

Gordon Sim created QPID-5026:


 Summary: [AMQP 1.0] set address for 'local' terminus in attach
 Key: QPID-5026
 URL: https://issues.apache.org/jira/browse/QPID-5026
 Project: Qpid
  Issue Type: Bug
  Components: C++ Client
Affects Versions: 0.24
Reporter: Gordon Sim
Assignee: Gordon Sim
 Fix For: 0.25


I.e. the target for receivers, the source for senders... this may be useful for 
some intermediaries (such as dispatch!).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Comment Edited] (QPID-4875) [Java] The parsing logic for certificate subjects doesn't work properly in all cases

2013-07-30 Thread Rob Godfrey (JIRA)


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

Rob Godfrey edited comment on QPID-4875 at 7/30/13 4:18 PM:


Rather than writing our own parser, did you try the approachsuggested here 

http://stackoverflow.com/questions/7933468/parsing-the-cn-out-of-a-certificate-dn

namely something like:

{code}
import javax.naming.ldap.LdapName;
{code}

{code}
LdapName ln = new LdapName(dn);
String cn = null;
for(Rdn rdn : ln.getRdns()) {
if(rdn.getType().equalsIgnoreCase("CN")) {
cn = rdn.getValue();
break;
}
}
{code}

  was (Author: rgodfrey):
Rather than writing our own parser, did you try the approachsuggested here 

http://stackoverflow.com/questions/7933468/parsing-the-cn-out-of-a-certificate-dn

namely something like:

import javax.naming.ldap.LdapName;

LdapName ln = new LdapName(dn);
String cn = null;
for(Rdn rdn : ln.getRdns()) {
if(rdn.getType().equalsIgnoreCase("CN")) {
cn = rdn.getValue();
break;
}
}
  
> [Java] The parsing logic for certificate subjects doesn't work properly in 
> all cases
> 
>
> Key: QPID-4875
> URL: https://issues.apache.org/jira/browse/QPID-4875
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker, Java Client, Java Common
>Reporter: JAkub Scholz
>Priority: Minor
> Fix For: Future
>
> Attachments: cert_parsing.patch
>
>
> The Java code seems to contain two places where the certificate subjects are 
> being parsed. One is used in the client:
> {{common/src/main/java/org/apache/qpid/transport/network/security/ssl/SSLUtil.java}}
> and the second is used in the broker:
> {{broker/src/main/java/org/apache/qpid/server/security/auth/sasl/external/ExternalSaslServer.java}}
> Both are actually doing the same - extracting the CN and DC components from 
> the subject and creating the username. It should be reconsidered whether we 
> want to reuse the SSLUtil functionality from the common part of the code in 
> the broker code as well.
> However, a bigger problem is that the implementation in both places are not 
> working correctly in all situations. One can very easily create a certificate 
> with a subject / DN like this:
> {{C=CZ,O=Scholz,OU="JAKUB CN=USER1"}}
> such certificate actually doesn't contain a CN. But both current 
> implementations will still identify the CN as {{USER1"}} in the code. I would 
> expect that this will happen only in very rare cases, but it should still be 
> handled properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (QPID-5024) [Java] README.txt is misleading

2013-07-30 Thread ASF subversion and git services (JIRA)


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

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

Commit 1508507 from [~gemmellr] in branch 'qpid/branches/0.24'
[ https://svn.apache.org/r1508507 ]

QPID-5024: updated README.txt to point at the current documentation rather than 
the stale wiki content

merged from trunk r1508478

> [Java] README.txt is misleading
> ---
>
> Key: QPID-5024
> URL: https://issues.apache.org/jira/browse/QPID-5024
> Project: Qpid
>  Issue Type: Bug
>Affects Versions: 0.22
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
> Fix For: 0.24
>
>
> The README.txt included in some of the binary release packages is misleading, 
> directing users at stale content on the wiki. It should be updated to point 
> to the current documentation on the website.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Resolved] (QPID-5024) [Java] README.txt is misleading

2013-07-30 Thread Robbie Gemmell (JIRA)


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

Robbie Gemmell resolved QPID-5024.
--

Resolution: Fixed

Closing out, now merged to 0.24.

> [Java] README.txt is misleading
> ---
>
> Key: QPID-5024
> URL: https://issues.apache.org/jira/browse/QPID-5024
> Project: Qpid
>  Issue Type: Bug
>Affects Versions: 0.22
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
> Fix For: 0.24
>
>
> The README.txt included in some of the binary release packages is misleading, 
> directing users at stale content on the wiki. It should be updated to point 
> to the current documentation on the website.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (QPID-4875) [Java] The parsing logic for certificate subjects doesn't work properly in all cases

2013-07-30 Thread Rob Godfrey (JIRA)


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

Rob Godfrey commented on QPID-4875:
---

Rather than writing our own parser, did you try the approachsuggested here 

http://stackoverflow.com/questions/7933468/parsing-the-cn-out-of-a-certificate-dn

namely something like:

import javax.naming.ldap.LdapName;

LdapName ln = new LdapName(dn);
String cn = null;
for(Rdn rdn : ln.getRdns()) {
if(rdn.getType().equalsIgnoreCase("CN")) {
cn = rdn.getValue();
break;
}
}

> [Java] The parsing logic for certificate subjects doesn't work properly in 
> all cases
> 
>
> Key: QPID-4875
> URL: https://issues.apache.org/jira/browse/QPID-4875
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker, Java Client, Java Common
>Reporter: JAkub Scholz
>Priority: Minor
> Fix For: Future
>
> Attachments: cert_parsing.patch
>
>
> The Java code seems to contain two places where the certificate subjects are 
> being parsed. One is used in the client:
> {{common/src/main/java/org/apache/qpid/transport/network/security/ssl/SSLUtil.java}}
> and the second is used in the broker:
> {{broker/src/main/java/org/apache/qpid/server/security/auth/sasl/external/ExternalSaslServer.java}}
> Both are actually doing the same - extracting the CN and DC components from 
> the subject and creating the username. It should be reconsidered whether we 
> want to reuse the SSLUtil functionality from the common part of the code in 
> the broker code as well.
> However, a bigger problem is that the implementation in both places are not 
> working correctly in all situations. One can very easily create a certificate 
> with a subject / DN like this:
> {{C=CZ,O=Scholz,OU="JAKUB CN=USER1"}}
> such certificate actually doesn't contain a CN. But both current 
> implementations will still identify the CN as {{USER1"}} in the code. I would 
> expect that this will happen only in very rare cases, but it should still be 
> handled properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (QPID-5019) Add flag to distinguish QMF v1 events

2013-07-30 Thread Ted Ross (JIRA)


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

Ted Ross commented on QPID-5019:


Reviewed for 0.24.

+1


> Add flag to distinguish QMF v1 events
> -
>
> Key: QPID-5019
> URL: https://issues.apache.org/jira/browse/QPID-5019
> Project: Qpid
>  Issue Type: Bug
>  Components: Qpid Managment Framework
>Affects Versions: 0.22
>Reporter: Ken Giusti
>Assignee: Ken Giusti
> Fix For: 0.24
>
> Attachments: qpid-5019.patch
>
>
> Older brokers issue two QMF events - one per format - per incident.  Add flag 
> to Event class to help distinguish (consistent with ObjectId class).
> Bug discovered by Bill Freeman.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Created] (QPID-5025) DeliveryRecord::committed() doesn't check if delivery is already ended

2013-07-30 Thread Gordon Sim (JIRA)

Gordon Sim created QPID-5025:


 Summary: DeliveryRecord::committed() doesn't check if delivery is 
already ended
 Key: QPID-5025
 URL: https://issues.apache.org/jira/browse/QPID-5025
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
Affects Versions: 0.18
Reporter: Gordon Sim
Assignee: Gordon Sim
Priority: Minor
 Fix For: 0.25


Prior to 0.20 this causes a segfault. Since 0.20 it is handled much better but 
would be nice to fix for consistency (since e.g. dequeue() does do the check). 
Marking as minor since it has not real impact on latest version.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (QPID-5024) [Java] README.txt is misleading

2013-07-30 Thread Justin Ross (JIRA)


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

Justin Ross commented on QPID-5024:
---

Thanks, Robbie.  Approved for 0.24.

> [Java] README.txt is misleading
> ---
>
> Key: QPID-5024
> URL: https://issues.apache.org/jira/browse/QPID-5024
> Project: Qpid
>  Issue Type: Bug
>Affects Versions: 0.22
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
> Fix For: 0.24
>
>
> The README.txt included in some of the binary release packages is misleading, 
> directing users at stale content on the wiki. It should be updated to point 
> to the current documentation on the website.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Request for inclusion in 0.24

2013-07-30 Thread Ken Giusti

Hi Justin,

Would it be possible to get this into 0.24?

https://issues.apache.org/jira/browse/QPID-5019

Bill Freeman requested it.  Very low risk.

thanks,

-K

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

Request for inclusion in 0.24

2013-07-30 Thread Robbie Gemmell

Hi Justin,

Trivial change for inclusion to stop confusion users (see IRC channel).

https://issues.apache.org/jira/browse/QPID-5024
[Java] README.txt is misleading

https://svn.apache.org/r1508478

Robbie

[jira] [Commented] (QPID-5024) [Java] README.txt is misleading

2013-07-30 Thread ASF subversion and git services (JIRA)


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

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

Commit 1508478 from [~gemmellr] in branch 'qpid/trunk'
[ https://svn.apache.org/r1508478 ]

QPID-5024: updated README.txt to point at the current documentation rather than 
the stale wiki content

> [Java] README.txt is misleading
> ---
>
> Key: QPID-5024
> URL: https://issues.apache.org/jira/browse/QPID-5024
> Project: Qpid
>  Issue Type: Bug
>Affects Versions: 0.22
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
> Fix For: 0.24
>
>
> The README.txt included in some of the binary release packages is misleading, 
> directing users at stale content on the wiki. It should be updated to point 
> to the current documentation on the website.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Created] (QPID-5024) [Java] README.txt is misleading

2013-07-30 Thread Robbie Gemmell (JIRA)

Robbie Gemmell created QPID-5024:


 Summary: [Java] README.txt is misleading
 Key: QPID-5024
 URL: https://issues.apache.org/jira/browse/QPID-5024
 Project: Qpid
  Issue Type: Bug
Affects Versions: 0.22
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
 Fix For: 0.24


The README.txt included in some of the binary release packages is misleading, 
directing users at stale content on the wiki. It should be updated to point to 
the current documentation on the website.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (QPIDJMS-2) [IGNORE ME] Subversion to JIRA integration test

2013-07-30 Thread ASF subversion and git services (JIRA)


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

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

Commit 1508379 from [~gemmellr] in branch 'jms/trunk'
[ https://svn.apache.org/r1508379 ]

QPIDJMS-2: remove test file

> [IGNORE ME] Subversion to JIRA integration test 
> 
>
> Key: QPIDJMS-2
> URL: https://issues.apache.org/jira/browse/QPIDJMS-2
> Project: Qpid JMS
>  Issue Type: Task
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>
> JIRA for testing gitsvn2jira integration, as with QPID-4891 and PROTON-321

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Resolved] (QPIDJMS-2) [IGNORE ME] Subversion to JIRA integration test

2013-07-30 Thread Robbie Gemmell (JIRA)


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

Robbie Gemmell resolved QPIDJMS-2.
--

Resolution: Not A Problem

> [IGNORE ME] Subversion to JIRA integration test 
> 
>
> Key: QPIDJMS-2
> URL: https://issues.apache.org/jira/browse/QPIDJMS-2
> Project: Qpid JMS
>  Issue Type: Task
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>
> JIRA for testing gitsvn2jira integration, as with QPID-4891 and PROTON-321

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (QPIDJMS-2) [IGNORE ME] Subversion to JIRA integration test

2013-07-30 Thread Robbie Gemmell (JIRA)


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

Robbie Gemmell commented on QPIDJMS-2:
--

The first cross-reference caused QPID-4891 to be updated, the second did not 
cause PROTON-321 to be updated, both as expected (the QPID- checking being 
performed in the parent dir, the PROTON- checking not being).

> [IGNORE ME] Subversion to JIRA integration test 
> 
>
> Key: QPIDJMS-2
> URL: https://issues.apache.org/jira/browse/QPIDJMS-2
> Project: Qpid JMS
>  Issue Type: Task
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>
> JIRA for testing gitsvn2jira integration, as with QPID-4891 and PROTON-321

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Updated] (QPID-4894) [Java Broker] Removal of exchange bindings from web management console does not work

2013-07-30 Thread Rob Godfrey (JIRA)


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

Rob Godfrey updated QPID-4894:
--

Fix Version/s: 0.24

> [Java Broker] Removal of exchange bindings from web management console does 
> not work
> 
>
> Key: QPID-4894
> URL: https://issues.apache.org/jira/browse/QPID-4894
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.22
>Reporter: Alex Rudyy
>Assignee: Philip Harvey
> Fix For: 0.24
>
>
> JavaScript Error is reported on trying to delete bindings from the exchange:
> dojo.js (line 15)
> ReferenceError: that is not defined
> [Break On This Error] 
> that.exchangeUpdater.bindingsGrid.grid,

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (QPIDJMS-2) [IGNORE ME] Subversion to JIRA integration test

2013-07-30 Thread ASF subversion and git services (JIRA)


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

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

Commit 1508361 from [~gemmellr] in branch 'jms/trunk'
[ https://svn.apache.org/r1508361 ]

QPIDJMS-2: test svn to JIRA integration with cross-project reference to 
PROTON-321

> [IGNORE ME] Subversion to JIRA integration test 
> 
>
> Key: QPIDJMS-2
> URL: https://issues.apache.org/jira/browse/QPIDJMS-2
> Project: Qpid JMS
>  Issue Type: Task
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>
> JIRA for testing gitsvn2jira integration, as with QPID-4891 and PROTON-321

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Updated] (QPID-4837) JDBC store should use connection pooler

2013-07-30 Thread Rob Godfrey (JIRA)


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

Rob Godfrey updated QPID-4837:
--

Fix Version/s: (was: 0.23)
   0.24

> JDBC store should use connection pooler
> ---
>
> Key: QPID-4837
> URL: https://issues.apache.org/jira/browse/QPID-4837
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Affects Versions: Future
>Reporter: Michal Zerola
>Priority: Minor
> Fix For: 0.24
>
> Attachments: qpid_jdbc_pooler.patch
>
>
> This JIRA discusses the possible improvement of the JDBC store as a follow-up 
> of the QPID-4763 issue. Since revision 1470549 the Java Qpid Broker can work 
> with JDBC compliant database store.
> However, our tests of the JDBC store (MySQL database was used as the backend) 
> showed that under the heavier load from the client (sending couple of 1000 
> persistence messages) the broker looses connection to the database. Closer 
> examination revealed that it was caused by the exceeded number of incoming 
> connections from the broker to the database server for which the server was 
> configured. The JDBC store was initiating the new connection many times, 
> instead of reusing already established one.
> We have extended the Java Broker for JDBC connection pool management using 
> the BoneCP library.
> http://jolbox.com/
> This library manages the connections returned by the underlying JDBC driver, 
> so available connections are reused by the broker.
> Plugging the connection pooling library is quite straight-forward as you can 
> see from the attached patch. With the connection pooler the JDBC store works 
> flawlessly (tested with MySQL) in our testing configuration.
> If using the above library would not be applicable because of some reason, 
> does it make sense to implement the connection pooling management directly 
> into the broker?
> Thank you,
> Michal

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Resolved] (QPID-4832) [Java Broker] Implement the default exchange as a facade on top of the queue registry

2013-07-30 Thread Rob Godfrey (JIRA)


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

Rob Godfrey resolved QPID-4832.
---

   Resolution: Fixed
Fix Version/s: (was: 0.23)
   0.24
 Assignee: Rob Godfrey

> [Java Broker] Implement the default exchange as a facade on top of the queue 
> registry
> -
>
> Key: QPID-4832
> URL: https://issues.apache.org/jira/browse/QPID-4832
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
> Fix For: 0.24
>
>
> Using an implementation of the direct exchange for the "default" anonymous 
> exchange causes issues such as attempts to bind/unbind to the anonymous 
> exchange, bindings being persisted, the default exchange showing up in 
> management UI views.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (QPID-4891) [IGNORE ME] Subversion to JIRA integration test

2013-07-30 Thread ASF subversion and git services (JIRA)


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

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

Commit 1508360 from [~gemmellr] in branch 'jms/trunk'
[ https://svn.apache.org/r1508360 ]

QPIDJMS-2: test svn to JIRA integration with cross-project reference to 
QPID-4891

> [IGNORE ME] Subversion to JIRA integration test
> ---
>
> Key: QPID-4891
> URL: https://issues.apache.org/jira/browse/QPID-4891
> Project: Qpid
>  Issue Type: Task
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>
> [IGNORE ME] Subversion to JIRA integration test 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (QPIDJMS-2) [IGNORE ME] Subversion to JIRA integration test

2013-07-30 Thread ASF subversion and git services (JIRA)


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

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

Commit 1508360 from [~gemmellr] in branch 'jms/trunk'
[ https://svn.apache.org/r1508360 ]

QPIDJMS-2: test svn to JIRA integration with cross-project reference to 
QPID-4891

> [IGNORE ME] Subversion to JIRA integration test 
> 
>
> Key: QPIDJMS-2
> URL: https://issues.apache.org/jira/browse/QPIDJMS-2
> Project: Qpid JMS
>  Issue Type: Task
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>
> JIRA for testing gitsvn2jira integration, as with QPID-4891 and PROTON-321

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (QPIDJMS-2) [IGNORE ME] Subversion to JIRA integration test

2013-07-30 Thread ASF subversion and git services (JIRA)


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

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

Commit 1508357 from [~gemmellr] in branch 'jms/trunk'
[ https://svn.apache.org/r1508357 ]

QPIDJMS-2: test svn to JIRA integration with basic commit message

> [IGNORE ME] Subversion to JIRA integration test 
> 
>
> Key: QPIDJMS-2
> URL: https://issues.apache.org/jira/browse/QPIDJMS-2
> Project: Qpid JMS
>  Issue Type: Task
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>
> JIRA for testing gitsvn2jira integration, as with QPID-4891 and PROTON-321

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Updated] (QPIDJMS-2) [IGNORE ME] Subversion to JIRA integration test

2013-07-30 Thread Robbie Gemmell (JIRA)


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

Robbie Gemmell updated QPIDJMS-2:
-

Description: JIRA for testing gitsvn2jira integration, as with QPID-4891 
and PROTON-321  (was: JIRA for testing gitsvn2jira integration.)

> [IGNORE ME] Subversion to JIRA integration test 
> 
>
> Key: QPIDJMS-2
> URL: https://issues.apache.org/jira/browse/QPIDJMS-2
> Project: Qpid JMS
>  Issue Type: Task
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>
> JIRA for testing gitsvn2jira integration, as with QPID-4891 and PROTON-321

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Updated] (QPIDJMS-2) [IGNORE ME] Subversion to JIRA integration test

2013-07-30 Thread Robbie Gemmell (JIRA)


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

Robbie Gemmell updated QPIDJMS-2:
-

Summary: [IGNORE ME] Subversion to JIRA integration test   (was: 
svngit2jira testing)

> [IGNORE ME] Subversion to JIRA integration test 
> 
>
> Key: QPIDJMS-2
> URL: https://issues.apache.org/jira/browse/QPIDJMS-2
> Project: Qpid JMS
>  Issue Type: Task
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>
> JIRA for testing gitsvn2jira integration.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Updated] (QPIDJMS-2) svngit2jira testing

2013-07-30 Thread Robbie Gemmell (JIRA)


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

Robbie Gemmell updated QPIDJMS-2:
-

Summary: svngit2jira testing  (was: gitsvn2jira testing)

> svngit2jira testing
> ---
>
> Key: QPIDJMS-2
> URL: https://issues.apache.org/jira/browse/QPIDJMS-2
> Project: Qpid JMS
>  Issue Type: Task
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>
> JIRA for testing gitsvn2jira integration.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Created] (QPIDJMS-2) gitsvn2jira testing

2013-07-30 Thread Robbie Gemmell (JIRA)

Robbie Gemmell created QPIDJMS-2:


 Summary: gitsvn2jira testing
 Key: QPIDJMS-2
 URL: https://issues.apache.org/jira/browse/QPIDJMS-2
 Project: Qpid JMS
  Issue Type: Task
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell


JIRA for testing gitsvn2jira integration.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Created] (QPIDJMS-1) Create a Proton based AMQP 1.0 client implementing JMS 2.0

2013-07-30 Thread Robbie Gemmell (JIRA)

Robbie Gemmell created QPIDJMS-1:


 Summary: Create a Proton based AMQP 1.0 client implementing JMS 2.0
 Key: QPIDJMS-1
 URL: https://issues.apache.org/jira/browse/QPIDJMS-1
 Project: Qpid JMS
  Issue Type: Bug
Reporter: Robbie Gemmell


Create a Proton based AMQP 1.0 client implementing JMS 2.0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

43 matches

Mail list logo