Hi all, Rob and I spent some hours last week going through the backlog of Jiras assigned against components java client, java common, and java broker on a late spring clean exercise. You'll have no doubt been deluged by JIRA update mails over the weekend, sorry about that.
Many jiras that were in fact resolved have now been marked as such, duplicates identified, fix versions set etc. Jiras related to the amqp-1-0-client-jms client have been moved from the java client component to a new JMS AMQP 1.0 Client component to differentiate the two. We were uncertain about the status of the following jiras. All of these are Open against the java-client component. Some of these seem to have work against them, some have patches, some are very old. Some might be duplicates. Could everyone with an interest in the java client, please take a look through the list and make any appropriate updates? Kind regards, Keith. QPID-2559 When a subscription is created, message credits should only be set if the dispatcher is not null. QPID-2604 Incorrect logic for handling message credits in BasicMessageConsumer_0_10 could result in the client receiving more messages than it needs. QPID-2976 deletion policy in new addressing options doesn't work QPID-3018 Better support for filtering in messaging API QPID-3207 AMQSession.java close() does not close the consumers with the correct arguments QPID-3259 Deadlock on Java client side while closing session when topic operation is unauthorised QPID-3272 Allow JMS messages originated from another vendor to be sent through Qpid with the Message ID intact. QPID-3289 Session exceptions should only be notified via the exception listener, if it cannot be thrown directly to the application. QPID-3388 Implement producer capacity to leverage producer flow control implemented by the C++ broker QPID-3462 Failover is not transparent when using CLIENT_ACK mode QPID-3494 Defining non-exclusive and/or auto-delete queues in JMS API is not possible with addresses based on links QPID-3538 ADDR address format not supported for topic. and queue. entries in JNDI properties QPID-3557 Using a Destination retrieved from JNDI property file, a MessageConsumer on a queue with a selector does not actually consume QPID-3602 Fix Consumer message credit issues in 0-10 code path QPID-4357 If an exception is received while the client is blocked on sync, the client should return immediately rather than timing out. QPID-4906 If Session close() or closed() method is invoked while inside onMessage(), they should be excuted after onMessage() has completed. QPID-4922 If Consumer close() method is invoked while inside onMessage(), it should be excuted after onMessage() has completed. QPID-5204 qpid.subject is an invalid JMS property identifier QPID-5345 JMS 0-10 client doesn't recognise exclusive option in link scoped x-declare or x-subscribe QPID-5868 Java client ignores exceptions when waiting on sync --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org