[jira] [Commented] (QPID-6701) [Regression btw 0.30 - 0.32] If address doesn't resolve an exception is not thrown

[ https://issues.apache.org/jira/browse/QPID-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14706717#comment-14706717 ] Rajith Attapattu commented on QPID-6701: Couple of points, 1. Assert was to verify

[jira] [Commented] (QPID-6701) [Regression btw 0.30 - 0.32] If address doesn't resolve an exception is not thrown

[ https://issues.apache.org/jira/browse/QPID-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14705746#comment-14705746 ] Rajith Attapattu commented on QPID-6701: QPID-6040 (rev 1620659) changed the

[jira] [Created] (QPID-6701) [Regression btw 0.30 - 0.32] If address doesn't resolve an exception is not thrown

Rajith Attapattu created QPID-6701: -- Summary: [Regression btw 0.30 - 0.32] If address doesn't resolve an exception is not thrown Key: QPID-6701 URL: https://issues.apache.org/jira/browse/QPID-6701

[jira] [Updated] (QPID-5870) Closing a topic consumer should delete its exclusive auto-delete queue

[ https://issues.apache.org/jira/browse/QPID-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-5870: --- Attachment: QPID-5870.part2.patch I added a check to ensure that the subscription queue is

[jira] [Commented] (QPID-5870) Closing a topic consumer should delete its exclusive auto-delete queue

[ https://issues.apache.org/jira/browse/QPID-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14055304#comment-14055304 ] Rajith Attapattu commented on QPID-5870: but I wonder what happens around e.g.

[jira] [Commented] (QPID-5868) Java client ignores exceptions when waiting on sync

[ https://issues.apache.org/jira/browse/QPID-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052509#comment-14052509 ] Rajith Attapattu commented on QPID-5868: As for the session being closed, once the

[jira] [Commented] (QPID-5868) Java client ignores exceptions when waiting on sync

[ https://issues.apache.org/jira/browse/QPID-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052508#comment-14052508 ] Rajith Attapattu commented on QPID-5868: Apologies for not putting enough info in

[jira] [Commented] (QPID-5870) Closing a topic consumer should delete its exclusive auto-delete queue

[ https://issues.apache.org/jira/browse/QPID-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052523#comment-14052523 ] Rajith Attapattu commented on QPID-5870: Again I apologize for not providing enough

[jira] [Commented] (QPID-5868) Java client ignores exceptions when waiting on sync

[ https://issues.apache.org/jira/browse/QPID-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052722#comment-14052722 ] Rajith Attapattu commented on QPID-5868: I verified that both the transport session

[jira] [Created] (QPID-5868) Java client ignores exceptions when waiting on sync

Rajith Attapattu created QPID-5868: -- Summary: Java client ignores exceptions when waiting on sync Key: QPID-5868 URL: https://issues.apache.org/jira/browse/QPID-5868 Project: Qpid Issue

[jira] [Updated] (QPID-5868) Java client ignores exceptions when waiting on sync

[ https://issues.apache.org/jira/browse/QPID-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-5868: --- Attachment: QPID-5868.patch This patch suggests a potential fix for the issue. Java client

[jira] [Created] (QPID-5869) Specifying an ACL file will cause a core dumps when management is sisabled

Rajith Attapattu created QPID-5869: -- Summary: Specifying an ACL file will cause a core dumps when management is sisabled Key: QPID-5869 URL: https://issues.apache.org/jira/browse/QPID-5869 Project:

[jira] [Updated] (QPID-5869) Specifying an invalid ACL file will cause a core dumps when management is sisabled

[ https://issues.apache.org/jira/browse/QPID-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-5869: --- Summary: Specifying an invalid ACL file will cause a core dumps when management is sisabled

[jira] [Resolved] (QPID-5869) Specifying an invalid ACL file will cause a core dumps when management is disabled

[ https://issues.apache.org/jira/browse/QPID-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-5869. Resolution: Fixed Assignee: Rajith Attapattu Added a fix on trunk at r1607488. There

[jira] [Updated] (QPID-5870) Closing a topic consumer should delete its exclusive auto-delete queue

[ https://issues.apache.org/jira/browse/QPID-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-5870: --- Attachment: QPID-5870.patch The subscription queue is now deleted when the consumer is

[jira] [Updated] (DISPATCH-16) Improve logging for dispatch

[ https://issues.apache.org/jira/browse/DISPATCH-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated DISPATCH-16: - Attachment: patch_1_schema_change.diff

[jira] [Updated] (DISPATCH-16) Improve logging for dispatch

[ https://issues.apache.org/jira/browse/DISPATCH-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated DISPATCH-16: - Attachment: patch_5_remove_set_mask_method.diff Improve logging for dispatch

[jira] [Updated] (QPID-5491) Improve logging for dispatch

[ https://issues.apache.org/jira/browse/QPID-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-5491: --- Attachment: (was: log_patch.2) Improve logging for dispatch

[jira] [Updated] (QPID-5491) Improve logging for dispatch

[ https://issues.apache.org/jira/browse/QPID-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-5491: --- Attachment: log_patch.3 Reworked the patch to work on top of Ted's changes. Improve logging

[jira] [Updated] (QPID-5491) Improve logging for dispatch

[ https://issues.apache.org/jira/browse/QPID-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-5491: --- Attachment: log_patch.2 The patch contains the following changes. 1. Each module registers

[jira] [Commented] (QPID-5491) Improve logging for dispatch

[ https://issues.apache.org/jira/browse/QPID-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13874837#comment-13874837 ] Rajith Attapattu commented on QPID-5491: Sample configuration. logging {

[jira] [Comment Edited] (QPID-5491) Improve logging for dispatch

[ https://issues.apache.org/jira/browse/QPID-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13874837#comment-13874837 ] Rajith Attapattu edited comment on QPID-5491 at 1/17/14 2:52 PM:

[jira] [Commented] (QPID-5204) qpid.subject is an invalid JMS property identifier

[ https://issues.apache.org/jira/browse/QPID-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13785382#comment-13785382 ] Rajith Attapattu commented on QPID-5204: QPID-3838 prefixes vendor specific

[jira] [Resolved] (QPID-3838) [JMS] Vendor specific properties should be prefixed with JMS_

[ https://issues.apache.org/jira/browse/QPID-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-3838. Resolution: Fixed A fix has been made on trunk and also ported to 0.24

[jira] [Updated] (QPID-4922) If Consumer close() method is invoked while inside onMessage(), it should be excuted after onMessage() has completed.

[ https://issues.apache.org/jira/browse/QPID-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4922: --- Attachment: QPID-4922.patch Marks that close has been called and then executes it after the

[jira] [Updated] (QPID-4922) If Consumer close() method is invoked while inside onMessage(), it should be excuted after onMessage() has completed.

[ https://issues.apache.org/jira/browse/QPID-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4922: --- Attachment: (was: QPID-4922.patch) If Consumer close() method is invoked while

[jira] [Updated] (QPID-4922) If Consumer close() method is invoked while inside onMessage(), it should be excuted after onMessage() has completed.

[ https://issues.apache.org/jira/browse/QPID-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4922: --- Attachment: QPID-4922.patch If Consumer close() method is invoked while inside

[jira] [Updated] (QPID-4357) If an exception is received while the client is blocked on sync, the client should return immediately rather than timing out.

[ https://issues.apache.org/jira/browse/QPID-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4357: --- Fix Version/s: (was: 0.21) Future If an exception is received

[jira] [Commented] (QPID-4574) [JMS] Deadlock involving _failoverMutex and _messageDeliveryLock

[ https://issues.apache.org/jira/browse/QPID-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681283#comment-13681283 ] Rajith Attapattu commented on QPID-4574: Currently the following solution is being

[jira] [Updated] (QPID-4574) [JMS] Deadlock involving _failoverMutex and _messageDeliveryLock

[ https://issues.apache.org/jira/browse/QPID-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4574: --- Fix Version/s: (was: 0.21) Future [JMS] Deadlock involving

[jira] [Resolved] (QPID-4608) JMS client authorization failure throws JMSException instead of JMSSecurityException

[ https://issues.apache.org/jira/browse/QPID-4608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-4608. Resolution: Fixed The relevant commits are

[jira] [Closed] (QPID-3769) NPE in client AMQDestination.equals()

[ https://issues.apache.org/jira/browse/QPID-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu closed QPID-3769. -- Resolution: Fixed Committed to both trunk and 0.22 branch. NPE in client

[jira] [Resolved] (QPID-4540) The subscription queue should only be deleted by the consumer.

[ https://issues.apache.org/jira/browse/QPID-4540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-4540. Resolution: Fixed A fix was committed at http://svn.apache.org/viewvc?rev=1434492view=rev

[jira] [Resolved] (QPID-4497) [Java client] Exclusive property for the subscription queue cannot be overridden using the address string

[ https://issues.apache.org/jira/browse/QPID-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-4497. Resolution: Fixed [Java client] Exclusive property for the subscription queue cannot

[jira] [Updated] (QPID-4906) If Session close() or closed() method is invoked while inside onMessage(), they should be excuted after onMessage() has completed.

[ https://issues.apache.org/jira/browse/QPID-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4906: --- Attachment: QPID-4906.patch If close() or closed() is called while the dispatcher thread is

[jira] [Created] (QPID-4906) If Session close() or closed() method is invoked while inside onMessage(), they should be excuted after onMessage() has completed.

Rajith Attapattu created QPID-4906: -- Summary: If Session close() or closed() method is invoked while inside onMessage(), they should be excuted after onMessage() has completed. Key: QPID-4906 URL:

[jira] [Resolved] (QPID-4873) Optimizations in Java client to reduce queue memory footprint

[ https://issues.apache.org/jira/browse/QPID-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-4873. Resolution: Fixed Committed the patch from Helen with modifications to accommodate the

[jira] [Commented] (QPID-4873) Optimizations in Java client to reduce queue memory footprint

[ https://issues.apache.org/jira/browse/QPID-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13664379#comment-13664379 ] Rajith Attapattu commented on QPID-4873: I'm happy with optimization #2 and #3. A

[jira] [Commented] (QPID-4873) Optimizations in Java client to reduce queue memory footprint

[ https://issues.apache.org/jira/browse/QPID-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13664487#comment-13664487 ] Rajith Attapattu commented on QPID-4873: +1 Seems a good solution! Rajith

[jira] [Commented] (QPID-4873) Optimizations in Java client to reduce queue memory footprint

[ https://issues.apache.org/jira/browse/QPID-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13664819#comment-13664819 ] Rajith Attapattu commented on QPID-4873: Hi Helen, I will take care of it first

[jira] [Created] (QPID-4864) The JMS client shouldn't hold a lock when creating a messge

Rajith Attapattu created QPID-4864: -- Summary: The JMS client shouldn't hold a lock when creating a messge Key: QPID-4864 URL: https://issues.apache.org/jira/browse/QPID-4864 Project: Qpid

[jira] [Resolved] (QPID-4864) The JMS client shouldn't hold a lock when creating a messge

[ https://issues.apache.org/jira/browse/QPID-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-4864. Resolution: Fixed Removed the lock. Fix committed at http://svn.apache.org/r1483877

[jira] [Updated] (QPID-4849) Faulty parsing logic in retrieving CN from an SSL certificate.

[ https://issues.apache.org/jira/browse/QPID-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4849: --- Labels: JMS SSL, (was: ) Faulty parsing logic in retrieving CN from an SSL certificate.

[jira] [Updated] (QPID-4849) Faulty parsing logic in retrieving CN from an SSL certificate.

[ https://issues.apache.org/jira/browse/QPID-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4849: --- Labels: JMS SSL (was: JMS SSL,) Faulty parsing logic in retrieving CN from an SSL

[jira] [Resolved] (QPID-4849) Faulty parsing logic in retrieving CN from an SSL certificate.

[ https://issues.apache.org/jira/browse/QPID-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-4849. Resolution: Fixed Committed a fix at http://svn.apache.org/r1483079

[jira] [Issue Comment Deleted] (QPID-4574) [JMS] Deadlock involving _failoverMutex and _messageDeliveryLock

[ https://issues.apache.org/jira/browse/QPID-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4574: --- Comment: was deleted (was: {code} diff --git

[jira] [Issue Comment Deleted] (QPID-4574) [JMS] Deadlock involving _failoverMutex and _messageDeliveryLock

[ https://issues.apache.org/jira/browse/QPID-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4574: --- Comment: was deleted (was: The change here is that the failoverMutex is acquired before

[jira] [Commented] (QPID-3838) [JMS] Vendor specific properties should be prefixed with JMS_

[ https://issues.apache.org/jira/browse/QPID-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652992#comment-13652992 ] Rajith Attapattu commented on QPID-3838: I have committed the fix described in the

[jira] [Updated] (QPID-3317) JMS client doesn't distinguish between node and link bindings

[ https://issues.apache.org/jira/browse/QPID-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-3317: --- Fix Version/s: 0.20 JMS client doesn't distinguish between node and link bindings

[jira] [Commented] (QPID-4714) AMQConnection close can leak socket connections if exceptions occur earlier in the process

[ https://issues.apache.org/jira/browse/QPID-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645788#comment-13645788 ] Rajith Attapattu commented on QPID-4714: Applied patch to the 0.22 branch. See

[jira] [Resolved] (QPID-4714) AMQConnection close can leak socket connections if exceptions occur earlier in the process

[ https://issues.apache.org/jira/browse/QPID-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-4714. Resolution: Fixed Fix Version/s: (was: Future) 0.22

[jira] [Commented] (QPID-4714) AMQConnection close can leak socket connections if exceptions occur earlier in the process

[ https://issues.apache.org/jira/browse/QPID-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641879#comment-13641879 ] Rajith Attapattu commented on QPID-4714: I have checked in a fix at

[jira] [Commented] (QPID-4714) AMQConnection close is leaking socket connections

[ https://issues.apache.org/jira/browse/QPID-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13639735#comment-13639735 ] Rajith Attapattu commented on QPID-4714: If we move the close connection method

[jira] [Created] (QPID-4714) AMQConnection close is leaking socket connections

Rajith Attapattu created QPID-4714: -- Summary: AMQConnection close is leaking socket connections Key: QPID-4714 URL: https://issues.apache.org/jira/browse/QPID-4714 Project: Qpid Issue Type:

[jira] [Commented] (QPID-3769) NPE in client AMQDestination.equals()

[ https://issues.apache.org/jira/browse/QPID-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618814#comment-13618814 ] Rajith Attapattu commented on QPID-3769: Adjusted the hashcode and equals impl for

[jira] [Updated] (QPID-3769) NPE in client AMQDestination.equals()

[ https://issues.apache.org/jira/browse/QPID-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-3769: --- Fix Version/s: 0.22 NPE in client AMQDestination.equals()

[jira] [Commented] (QPID-3769) NPE in client AMQDestination.equals()

[ https://issues.apache.org/jira/browse/QPID-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618955#comment-13618955 ] Rajith Attapattu commented on QPID-3769: Ported the relevant changes to 0.22

[jira] [Commented] (QPID-3769) NPE in client AMQDestination.equals()

[ https://issues.apache.org/jira/browse/QPID-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13615424#comment-13615424 ] Rajith Attapattu commented on QPID-3769: I was going to request a port, but I

[jira] [Resolved] (QPID-3769) NPE in client AMQDestination.equals()

[ https://issues.apache.org/jira/browse/QPID-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-3769. Resolution: Fixed Fixed the immediate concerns. http://svn.apache.org/r1461324

[jira] [Commented] (QPID-3769) NPE in client AMQDestination.equals()

[ https://issues.apache.org/jira/browse/QPID-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13605172#comment-13605172 ] Rajith Attapattu commented on QPID-3769: I discussed this with Rafi a fair bit

[jira] [Commented] (QPID-3769) NPE in client AMQDestination.equals()

[ https://issues.apache.org/jira/browse/QPID-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13605174#comment-13605174 ] Rajith Attapattu commented on QPID-3769: Alex I will fix the test cases by using

[jira] [Resolved] (QPID-3769) NPE in client AMQDestination.equals()

[ https://issues.apache.org/jira/browse/QPID-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-3769. Resolution: Fixed Assignee: Rajith Attapattu http://svn.apache.org/r1456007

[jira] [Resolved] (QPID-4549) Java client ignores retry parameters for the very first broker

[ https://issues.apache.org/jira/browse/QPID-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-4549. Resolution: Fixed http://svn.apache.org/r1456131 Applied Pavel Moravec's patch.

[jira] [Commented] (QPID-3769) NPE in client AMQDestination.equals()

[ https://issues.apache.org/jira/browse/QPID-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13599289#comment-13599289 ] Rajith Attapattu commented on QPID-3769: There are two options for implementing the

[jira] [Commented] (QPID-3396) Specifying username/password in JMS clients should not be mandatory

[ https://issues.apache.org/jira/browse/QPID-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595928#comment-13595928 ] Rajith Attapattu commented on QPID-3396: Let me look at implementing the same for

[jira] [Commented] (QPID-3396) Specifying username/password in JMS clients should not be mandatory

[ https://issues.apache.org/jira/browse/QPID-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596041#comment-13596041 ] Rajith Attapattu commented on QPID-3396: Alex and Robbie, could you please have a

[jira] [Updated] (QPID-4274) second invocation of createConsumer fails for queue in JNDI properties

[ https://issues.apache.org/jira/browse/QPID-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4274: --- Fix Version/s: 0.21 Assignee: Rajith Attapattu second invocation of

[jira] [Commented] (QPID-4274) second invocation of createConsumer fails for queue in JNDI properties

[ https://issues.apache.org/jira/browse/QPID-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596486#comment-13596486 ] Rajith Attapattu commented on QPID-4274: Applied Pavel's patch but in a different

[jira] [Resolved] (QPID-4274) second invocation of createConsumer fails for queue in JNDI properties

[ https://issues.apache.org/jira/browse/QPID-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-4274. Resolution: Fixed second invocation of createConsumer fails for queue in JNDI

[jira] [Resolved] (QPID-4617) getJMSReplyTo does not return null for when ReplyTo property is empty

[ https://issues.apache.org/jira/browse/QPID-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-4617. Resolution: Fixed getJMSReplyTo does not return null for when ReplyTo property is

[jira] [Commented] (QPID-4617) getJMSReplyTo does not return null for when ReplyTo property is empty

[ https://issues.apache.org/jira/browse/QPID-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13593509#comment-13593509 ] Rajith Attapattu commented on QPID-4617: Robbie, The underlying issue is that when

[jira] [Commented] (QPID-4617) getJMSReplyTo does not return null for when ReplyTo property is empty

[ https://issues.apache.org/jira/browse/QPID-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13593998#comment-13593998 ] Rajith Attapattu commented on QPID-4617: Added a fix to clear the replyTo field if

[jira] [Closed] (QPID-3636) getJMSReplyTo does not return null for null ReplyTo property

[ https://issues.apache.org/jira/browse/QPID-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu closed QPID-3636. -- Resolution: Fixed Pavel's patch as well as a fix for the root cause has been applied at

[jira] [Created] (QPID-4617) getJMSReplyTo does not return null for when ReplyTo property is empty

Rajith Attapattu created QPID-4617: -- Summary: getJMSReplyTo does not return null for when ReplyTo property is empty Key: QPID-4617 URL: https://issues.apache.org/jira/browse/QPID-4617 Project: Qpid

[jira] [Commented] (QPID-4617) getJMSReplyTo does not return null for when ReplyTo property is empty

[ https://issues.apache.org/jira/browse/QPID-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13590990#comment-13590990 ] Rajith Attapattu commented on QPID-4617: Added a fix at rev

[jira] [Commented] (QPID-4608) JMS client authorization failure throws JMSException instead of JMSSecurityException

[ https://issues.apache.org/jira/browse/QPID-4608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13589793#comment-13589793 ] Rajith Attapattu commented on QPID-4608: Alex, I will add code to catch

[jira] [Assigned] (QPID-1381) ACL file reader does not reject file with empty extention lines

[ https://issues.apache.org/jira/browse/QPID-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu reassigned QPID-1381: -- Assignee: Chuck Rolke (was: Rajith Attapattu) Chuck is now the proud owner of this

[jira] [Updated] (QPID-1381) ACL file reader does not reject file with empty extention lines

[ https://issues.apache.org/jira/browse/QPID-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-1381: --- Fix Version/s: Future ACL file reader does not reject file with empty extention lines

[jira] [Commented] (QPID-4608) JMS client authorization failure throws JMSException instead of JMSSecurityException

[ https://issues.apache.org/jira/browse/QPID-4608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13589951#comment-13589951 ] Rajith Attapattu commented on QPID-4608: I have now added code to handle the

[jira] [Created] (QPID-4608) JMS client authorization failure throws JMSException instead of JMSSecurityException

Rajith Attapattu created QPID-4608: -- Summary: JMS client authorization failure throws JMSException instead of JMSSecurityException Key: QPID-4608 URL: https://issues.apache.org/jira/browse/QPID-4608

[jira] [Commented] (QPID-2733) Temp queues created when receiving from an exchange are not deleted.

[ https://issues.apache.org/jira/browse/QPID-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13586121#comment-13586121 ] Rajith Attapattu commented on QPID-2733: The title is slightly misleading. The

[jira] [Created] (QPID-4574) [JMS] Deadlock involving _failoverMutex and _messageDeliveryLock

Rajith Attapattu created QPID-4574: -- Summary: [JMS] Deadlock involving _failoverMutex and _messageDeliveryLock Key: QPID-4574 URL: https://issues.apache.org/jira/browse/QPID-4574 Project: Qpid

[jira] [Commented] (QPID-4574) [JMS] Deadlock involving _failoverMutex and _messageDeliveryLock

[ https://issues.apache.org/jira/browse/QPID-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574608#comment-13574608 ] Rajith Attapattu commented on QPID-4574: The issue here is that the locks are

[jira] [Updated] (QPID-4574) [JMS] Deadlock involving _failoverMutex and _messageDeliveryLock

[ https://issues.apache.org/jira/browse/QPID-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4574: --- Labels: deadlock (was: ) [JMS] Deadlock involving _failoverMutex and

[jira] [Updated] (QPID-4574) [JMS] Deadlock involving _failoverMutex and _messageDeliveryLock

[ https://issues.apache.org/jira/browse/QPID-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4574: --- Attachment: Test_00782235.java Reproducer supplied by Pavel Moravec. Run the reproducer in a

[jira] [Commented] (QPID-4574) [JMS] Deadlock involving _failoverMutex and _messageDeliveryLock

[ https://issues.apache.org/jira/browse/QPID-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574612#comment-13574612 ] Rajith Attapattu commented on QPID-4574: {code} diff --git

[jira] [Commented] (QPID-4574) [JMS] Deadlock involving _failoverMutex and _messageDeliveryLock

[ https://issues.apache.org/jira/browse/QPID-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574613#comment-13574613 ] Rajith Attapattu commented on QPID-4574: The change here is that the failoverMutex

[jira] [Created] (QPID-4566) 0-10 JMS Message Delegate should allow a non UUID String to be set as message-id

Rajith Attapattu created QPID-4566: -- Summary: 0-10 JMS Message Delegate should allow a non UUID String to be set as message-id Key: QPID-4566 URL: https://issues.apache.org/jira/browse/QPID-4566

[jira] [Updated] (QPID-4566) 0-10 JMS Message Delegate should allow a non UUID String to be set as message-id

[ https://issues.apache.org/jira/browse/QPID-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4566: --- Labels: JMS JMS-Compliance (was: ) 0-10 JMS Message Delegate should allow a non UUID

[jira] [Updated] (QPID-4566) 0-10 JMS Message Delegate should allow a non UUID String to be set as message-id

[ https://issues.apache.org/jira/browse/QPID-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4566: --- Fix Version/s: 0.21 Assignee: Rajith Attapattu Affects Version/s: 0.20

[jira] [Resolved] (QPID-4566) 0-10 JMS Message Delegate should allow a non UUID String to be set as message-id

[ https://issues.apache.org/jira/browse/QPID-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-4566. Resolution: Won't Fix Currently there are no compelling reasons to implement this. This use

[jira] [Resolved] (QPID-4541) Messages are replayed after XA commit in a failover scenario

[ https://issues.apache.org/jira/browse/QPID-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-4541. Resolution: Fixed Fix Version/s: 0.21 The following commit fixes this issue.

[jira] [Commented] (QPID-4541) Messages are replayed after XA commit in a failover scenario

[ https://issues.apache.org/jira/browse/QPID-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13561290#comment-13561290 ] Rajith Attapattu commented on QPID-4541: Kieth, I would let Weston to explain the

[jira] [Commented] (QPID-4541) Messages are replayed after XA commit in a failover scenario

[ https://issues.apache.org/jira/browse/QPID-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13557694#comment-13557694 ] Rajith Attapattu commented on QPID-4541: The XA Session is using AUTO_ACK mode

[jira] [Created] (QPID-4540) The subscription queue should only be deleted by the consumer.

Rajith Attapattu created QPID-4540: -- Summary: The subscription queue should only be deleted by the consumer. Key: QPID-4540 URL: https://issues.apache.org/jira/browse/QPID-4540 Project: Qpid

[jira] [Commented] (QPID-4497) [Java client] Exclusive property for the subscription queue cannot be overridden using the address string

[ https://issues.apache.org/jira/browse/QPID-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528131#comment-13528131 ] Rajith Attapattu commented on QPID-4497: The testCustomizingSubscriptionQueue test

[jira] [Commented] (QPID-4496) [Java client] Improve error reporting for invalid addresses

[ https://issues.apache.org/jira/browse/QPID-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528221#comment-13528221 ] Rajith Attapattu commented on QPID-4496: I have fixed the typo and corrected the

[jira] [Commented] (QPID-4497) [Java client] Exclusive property for the subscription queue cannot be overridden using the address string

[ https://issues.apache.org/jira/browse/QPID-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528253#comment-13528253 ] Rajith Attapattu commented on QPID-4497: Perhaps there is a misunderstanding. The

[jira] [Commented] (QPID-3317) JMS client doesn't distinguish between node and link bindings

[ https://issues.apache.org/jira/browse/QPID-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528281#comment-13528281 ] Rajith Attapattu commented on QPID-3317: I did ask Justin offline about this, but

[jira] [Commented] (QPID-4497) [Java client] Exclusive property for the subscription queue cannot be overridden using the address string

[ https://issues.apache.org/jira/browse/QPID-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528300#comment-13528300 ] Rajith Attapattu commented on QPID-4497: As to your original question about a test

  1   2   3   4   5   6   7   >