[jira] [Resolved] (QPID-4245) [Java Broker] add a LogActor for the HTTP management interface

[ https://issues.apache.org/jira/browse/QPID-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4245. -- Resolution: Fixed Resolving, did with Phil. > [Java Broker] add a LogActor for

[jira] [Created] (QPID-4306) race condition during concurrent use of an AMQDestination may lead to NPE

Robbie Gemmell created QPID-4306: Summary: race condition during concurrent use of an AMQDestination may lead to NPE Key: QPID-4306 URL: https://issues.apache.org/jira/browse/QPID-4306 Project: Qpid

[jira] [Created] (QPID-4307) [Java Broker] prevent moving/copying messages back onto queues they already exist on

Robbie Gemmell created QPID-4307: Summary: [Java Broker] prevent moving/copying messages back onto queues they already exist on Key: QPID-4307 URL: https://issues.apache.org/jira/browse/QPID-4307 Proj

[jira] [Created] (QPID-4308) ACL v2 spec does not allow permissioning of publication to the default exchange

Robbie Gemmell created QPID-4308: Summary: ACL v2 spec does not allow permissioning of publication to the default exchange Key: QPID-4308 URL: https://issues.apache.org/jira/browse/QPID-4308 Project:

[jira] [Created] (QPID-4309) [Java Broker] ACL permissions for moving/copying/deleting messages via HTTP mangement interface should not use the JMX 'method' permissions

Robbie Gemmell created QPID-4309: Summary: [Java Broker] ACL permissions for moving/copying/deleting messages via HTTP mangement interface should not use the JMX 'method' permissions Key: QPID-4309 URL: https://i

[jira] [Updated] (QPID-4250) [Java client] producer creation using BindingURLs on 0-8/0-9/0-9-1 connections does not respect setting qpid.declare_exchanges=false

[ https://issues.apache.org/jira/browse/QPID-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4250: - Component/s: Java Client > [Java client] producer creation using BindingURLs on 0-8/0-9/0-9-1

[jira] [Resolved] (QPID-4250) [Java client] producer creation using BindingURLs on 0-8/0-9/0-9-1 connections does not respect setting qpid.declare_exchanges=false

[ https://issues.apache.org/jira/browse/QPID-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4250. -- Resolution: Fixed > [Java client] producer creation using BindingURLs on 0-8/0-9/0-9-1 > co

[jira] [Updated] (QPID-4277) [Java client] 0-10 client path cant declare durable/auto-delete exchanges when using 'Address' based destinations

[ https://issues.apache.org/jira/browse/QPID-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4277: - Component/s: Java Client > [Java client] 0-10 client path cant declare durable/auto-delete exc

[jira] [Created] (QPID-4312) [Java client] [0-8/0-9/0-9-1] add option for performing verification of queue existence during creation of a MessageProducer for a Queue destination on a generic Session

Robbie Gemmell created QPID-4312: Summary: [Java client] [0-8/0-9/0-9-1] add option for performing verification of queue existence during creation of a MessageProducer for a Queue destination on a generic Session Key: QPID-4312

[jira] [Resolved] (QPID-3228) Qpid broker JMX API allows creation of queues with queue name length greater than 255, owner name length greather than 255, routine key length greather than 255, exchange

[ https://issues.apache.org/jira/browse/QPID-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-3228. -- Resolution: Won't Fix > Qpid broker JMX API allows creation of queues with queue name length

[jira] [Closed] (QPID-3424) DerbyMessageStoreLoggingTest tests fail with derby profile

[ https://issues.apache.org/jira/browse/QPID-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed QPID-3424. Resolution: Fixed Test no longer exists. > DerbyMessageStoreLoggingTest tests fail

[jira] [Resolved] (QPID-3997) [Java Broker] Allow assignment of AuthenticationManager on a per-port basis

[ https://issues.apache.org/jira/browse/QPID-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-3997. -- Resolution: Fixed Fix Version/s: 0.18 > [Java Broker] Allow assignment of Authenticat

[jira] [Updated] (QPID-4242) Remove Incomplete QMF1 implementation from Java Broker

[ https://issues.apache.org/jira/browse/QPID-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4242: - Fix Version/s: 0.19 > Remove Incomplete QMF1 implementation from Java Broker > ---

[jira] [Resolved] (QPID-4056) HAClusterManagementTest.testRemoveNodeFromGroup fails occasionally on Apache CI

[ https://issues.apache.org/jira/browse/QPID-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4056. -- Resolution: Fixed Fix Version/s: 0.19 Looks good to me. > HAClusterManag

[jira] [Closed] (QPID-1657) Allows amqp.properties file to be found in the CLASSPATH

[ https://issues.apache.org/jira/browse/QPID-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed QPID-1657. Resolution: Won't Fix > Allows amqp.properties file to be found in the CLASSPATH > -

[jira] [Resolved] (QPID-2343) Provide a consistent naming convention for JMS client properties

[ https://issues.apache.org/jira/browse/QPID-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-2343. -- Resolution: Implemented Fix Version/s: (was: Future) Resolving, this has been open fo

[jira] [Resolved] (QPID-2743) [Java Client] Deadlock observed when broker spontaneously closes connection

[ https://issues.apache.org/jira/browse/QPID-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-2743. -- Resolution: Cannot Reproduce > [Java Client] Deadlock observed when broker spontaneously clo

[jira] [Resolved] (QPID-2776) refactor AMQMessageDelegate(0_8 / 0_10) to rationalise duplicated message property functionality

[ https://issues.apache.org/jira/browse/QPID-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-2776. -- Resolution: Won't Fix > refactor AMQMessageDelegate(0_8 / 0_10) to rationalise duplicated me

[jira] [Resolved] (QPID-3134) Exceptions thrown during synchronous operations should be caught and wrapped appropriately

[ https://issues.apache.org/jira/browse/QPID-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-3134. -- Resolution: Fixed > Exceptions thrown during synchronous operations should be caught and wra

[jira] [Closed] (QPID-3234) Exception handling logic is incorrect in AMQConnection.java

[ https://issues.apache.org/jira/browse/QPID-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed QPID-3234. Resolution: Later > Exception handling logic is incorrect in AMQConnection.java > --

[jira] [Resolved] (QPID-3303) JMS client can't handle messages of type amqp/list, as sent by QMFv2

[ https://issues.apache.org/jira/browse/QPID-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-3303. -- Resolution: Duplicate Resolving, this has been duplicated by another JIRA that has a patch and

[jira] [Resolved] (QPID-4288) PID and Platform info should be cached and reused for subsequent connections

[ https://issues.apache.org/jira/browse/QPID-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4288. -- Resolution: Fixed Assignee: (was: Rajith Attapattu) Completing the create - commit - c

[jira] [Updated] (QPID-3741) Fixed the test Rake target: it now calls the Rspec tests

[ https://issues.apache.org/jira/browse/QPID-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3741: - Component/s: (was: Ruby Test Suite) > Fixed the test Rake target: it now calls the Rspec t

[jira] [Updated] (QPID-4291) Renamed the Ruby gemfile to "qpid_messaging"

[ https://issues.apache.org/jira/browse/QPID-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4291: - Component/s: (was: Ruby Test Suite) > Renamed the Ruby gemfile to "qpid_messaging" > -

[jira] [Updated] (QPID-3741) Fixed the test Rake target: it now calls the Rspec tests

[ https://issues.apache.org/jira/browse/QPID-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3741: - Component/s: Ruby Client > Fixed the test Rake target: it now calls the Rspec tests >

[jira] [Updated] (QPID-924) Ruby test.rb use of '0.0.0.0' for localhost doesn't work under cygwin

[ https://issues.apache.org/jira/browse/QPID-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-924: Labels: old_ruby_test_suite_component (was: ) > Ruby test.rb use of '0.0.0.0' for localhost does

[jira] [Updated] (QPID-3791) Provides Cucumber-based integration tests.

[ https://issues.apache.org/jira/browse/QPID-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3791: - Labels: old_ruby_test_suite_component (was: ) > Provides Cucumber-based integration tests. >

[jira] [Updated] (QPID-832) Merge M2.1 and trunk

[ https://issues.apache.org/jira/browse/QPID-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-832: Labels: old_ruby_test_suite_component (was: old_maven_build_system) > Merge M2.1 and trunk > ---

[jira] [Updated] (QPID-1601) Parameterize the amqp url used in qmf tests

[ https://issues.apache.org/jira/browse/QPID-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-1601: - Labels: old_ruby_test_suite_component (was: ) > Parameterize the amqp url used in qmf tests >

[jira] [Updated] (QPID-3976) Added support to the Ruby Rakefile to locate the cqpid.so file.r

[ https://issues.apache.org/jira/browse/QPID-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3976: - Labels: old_ruby_test_suite_component (was: ) > Added support to the Ruby Rakefile to locate

[jira] [Updated] (QPID-3361) Provides integration tests for the Ruby APIs

[ https://issues.apache.org/jira/browse/QPID-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3361: - Labels: old_ruby_test_suite_component (was: amqp_compliance) > Provides integration tests for

[jira] [Updated] (QPID-3962) Added licensing to the Cucumber feature test step definitions.r

[ https://issues.apache.org/jira/browse/QPID-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3962: - Labels: old_ruby_test_suite_component (was: ) > Added licensing to the Cucumber feature test

[jira] [Updated] (QPID-3995) Cleans up queues created during Cucumber feature tests

[ https://issues.apache.org/jira/browse/QPID-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3995: - Labels: old_ruby_test_suite_component (was: ) > Cleans up queues created during Cucumber feat

[jira] [Resolved] (QPID-2725) Large quantities of documentation are duplicated

[ https://issues.apache.org/jira/browse/QPID-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-2725. -- Resolution: Fixed The duplication is no longer present, resolving. > Large quan

[jira] [Resolved] (QPID-3722) Improve DocBook HTML presentation

[ https://issues.apache.org/jira/browse/QPID-3722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-3722. -- Resolution: Fixed Resolving, work was done on making the presentation better (content ongoing).

[jira] [Resolved] (QPID-4284) Remove system test dependencies on development and localhost virtual hosts

[ https://issues.apache.org/jira/browse/QPID-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4284. -- Resolution: Fixed Looks good to me. > Remove system test dependencies on develo

[jira] [Updated] (QPID-4291) Renamed the Ruby gemfile to "qpid_messaging"

[ https://issues.apache.org/jira/browse/QPID-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4291: - Fix Version/s: (was: 0.18) 0.19 > Renamed the Ruby gemfile to "qpid_mes

[jira] [Commented] (QPID-4291) Renamed the Ruby gemfile to "qpid_messaging"

[ https://issues.apache.org/jira/browse/QPID-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458237#comment-13458237 ] Robbie Gemmell commented on QPID-4291: -- Bumped fix-for to 0.19 since 0.18 already went

[jira] [Resolved] (QPID-1354) buildCreator recurses directorys looking for patches.

[ https://issues.apache.org/jira/browse/QPID-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-1354. -- Resolution: Won't Fix > buildCreator recurses directorys looking for patches. >

[jira] [Resolved] (QPID-1429) buildCreator uses fixed location of binarires.

[ https://issues.apache.org/jira/browse/QPID-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-1429. -- Resolution: Won't Fix > buildCreator uses fixed location of binarires. > --

[jira] [Resolved] (QPID-3489) The Exchange plugin examples do not work and are not tested

[ https://issues.apache.org/jira/browse/QPID-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-3489. -- Resolution: Won't Fix These 'examples' were removed a while ago precisely because they are not u

[jira] [Resolved] (QPID-3149) Set up Hudson Continuous Integration

[ https://issues.apache.org/jira/browse/QPID-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-3149. -- Resolution: Fixed Resolving as this has now been running for 18 months. Future changes can get

[jira] [Created] (QPID-4333) [Java broker] remove the Slow Consumer Detection plugin

Robbie Gemmell created QPID-4333: Summary: [Java broker] remove the Slow Consumer Detection plugin Key: QPID-4333 URL: https://issues.apache.org/jira/browse/QPID-4333 Project: Qpid Issue Type

[jira] [Created] (QPID-4334) [Java broker] move the Firewall functionality into the ACL plugin

Robbie Gemmell created QPID-4334: Summary: [Java broker] move the Firewall functionality into the ACL plugin Key: QPID-4334 URL: https://issues.apache.org/jira/browse/QPID-4334 Project: Qpid

[jira] [Created] (QPID-4335) [java broker] replace current plugin system with a simplified system

Robbie Gemmell created QPID-4335: Summary: [java broker] replace current plugin system with a simplified system Key: QPID-4335 URL: https://issues.apache.org/jira/browse/QPID-4335 Project: Qpid

[jira] [Updated] (QPID-4314) [Java Distributed Tests] Add performance tests measuring the impact of selectors on consumer performance

[ https://issues.apache.org/jira/browse/QPID-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4314: - Assignee: Alex Rudyy (was: Robbie Gemmell) Status: Open (was: Ready To Review) Hi Alex, K

[jira] [Resolved] (QPID-4310) [Java Distributed Tests] Display performance test results in messages per second

[ https://issues.apache.org/jira/browse/QPID-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4310. -- Resolution: Fixed Patch applied with some minor changes (resolving conflict with changes made s

[jira] [Resolved] (QPID-4321) Perf tests should not try to Message.acknowledge a producing session

[ https://issues.apache.org/jira/browse/QPID-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4321. -- Resolution: Fixed Looks good to me. > Perf tests should not try to Message.ackn

[jira] [Assigned] (QPID-4333) [Java broker] remove the Slow Consumer Detection plugin

[ https://issues.apache.org/jira/browse/QPID-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-4333: Assignee: Robbie Gemmell > [Java broker] remove the Slow Consumer Detection plugin > ---

[jira] [Updated] (QPID-4333) [Java broker] remove the Slow Consumer Detection plugin

[ https://issues.apache.org/jira/browse/QPID-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4333: - Status: Ready To Review (was: In Progress) > [Java broker] remove the Slow Consumer Detection

[jira] [Resolved] (QPID-4303) FailoverTest sometimes fails on slower CI boxes.

[ https://issues.apache.org/jira/browse/QPID-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4303. -- Resolution: Fixed Changes look good to me. > FailoverTest sometimes fails on sl

[jira] [Assigned] (QPID-4333) [Java broker] remove the Slow Consumer Detection plugin

[ https://issues.apache.org/jira/browse/QPID-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-4333: Assignee: Keith Wall (was: Robbie Gemmell) Hi Keith, could you review this change please?

[jira] [Commented] (QPID-4311) [Java Distributed Tests] Publishing client publishes messages infinitely if start delay interval exceeds the maximum duration

[ https://issues.apache.org/jira/browse/QPID-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460576#comment-13460576 ] Robbie Gemmell commented on QPID-4311: -- I noticed an issue to do with the producer fai

[jira] [Commented] (QPID-4340) Cannot create a durable exchange with addressing

[ https://issues.apache.org/jira/browse/QPID-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460738#comment-13460738 ] Robbie Gemmell commented on QPID-4340: -- >From recent JIRA cleanup and having raised on

[jira] [Created] (QPID-4341) ensure the Topic perftests actually use Topic destinations

Robbie Gemmell created QPID-4341: Summary: ensure the Topic perftests actually use Topic destinations Key: QPID-4341 URL: https://issues.apache.org/jira/browse/QPID-4341 Project: Qpid Issue T

[jira] [Assigned] (QPID-4352) Java client logs key_store_password/trust_store_password from connection url at debug

[ https://issues.apache.org/jira/browse/QPID-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-4352: Assignee: Keith Wall (was: Robbie Gemmell) Hi Keith, I noticed that the connection factory

[jira] [Created] (QPID-4359) [Java Broker] an IOException is logged when closing a connection which is SSL

Robbie Gemmell created QPID-4359: Summary: [Java Broker] an IOException is logged when closing a connection which is SSL Key: QPID-4359 URL: https://issues.apache.org/jira/browse/QPID-4359 Project: Qp

[jira] [Updated] (QPID-4359) [Java Broker] an IOException is logged when closing a connection which is SSL

[ https://issues.apache.org/jira/browse/QPID-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4359: - Description: When closing a connection which is using SSL, an IOException is logged by the broker

[jira] [Assigned] (QPID-4359) [Java Broker] an IOException is logged when closing a connection which is SSL

[ https://issues.apache.org/jira/browse/QPID-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-4359: Assignee: Robbie Gemmell > [Java Broker] an IOException is logged when closing a connect

[jira] [Commented] (QPID-4359) [Java Broker] an IOException is logged when closing a connection which is SSL

[ https://issues.apache.org/jira/browse/QPID-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470194#comment-13470194 ] Robbie Gemmell commented on QPID-4359: -- This seems to be because whilst the client is

[jira] [Updated] (QPID-4359) [Java Broker] an IOException is logged when closing a connection which is using SSL

[ https://issues.apache.org/jira/browse/QPID-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4359: - Summary: [Java Broker] an IOException is logged when closing a connection which is using SSL (was

[jira] [Resolved] (QPID-4364) broken links

[ https://issues.apache.org/jira/browse/QPID-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4364. -- Resolution: Fixed Assignee: Robbie Gemmell Fixed, though in the former case I went for the

[jira] [Updated] (QPID-4335) [java broker] replace current plugin system with a simplified system

[ https://issues.apache.org/jira/browse/QPID-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4335: - Status: Ready To Review (was: In Progress) > [java broker] replace current plugin system with

[jira] [Assigned] (QPID-4353) Reorganise Java system tests so they will work with de-OSGI-fied plugins

[ https://issues.apache.org/jira/browse/QPID-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-4353: Assignee: Robbie Gemmell > Reorganise Java system tests so they will work with de-OSGI-f

[jira] [Resolved] (QPID-4353) Reorganise Java system tests so they will work with de-OSGI-fied plugins

[ https://issues.apache.org/jira/browse/QPID-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4353. -- Resolution: Fixed Fix Version/s: 0.19 Patch (on linked JIRA) applied. >

[jira] [Resolved] (QPID-4335) [java broker] replace current plugin system with a simplified system

[ https://issues.apache.org/jira/browse/QPID-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4335. -- Resolution: Fixed Patch applied. > [java broker] replace current plugin system

[jira] [Resolved] (QPID-4359) [Java Broker] an IOException is logged when closing a connection which is using SSL

[ https://issues.apache.org/jira/browse/QPID-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4359. -- Resolution: Fixed Resolving. > [Java Broker] an IOException is logged when clos

[jira] [Commented] (QPID-4389) Qpid topic exchange does not resend message when subsciber come back online

[ https://issues.apache.org/jira/browse/QPID-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483546#comment-13483546 ] Robbie Gemmell commented on QPID-4389: -- Hi Andrew, The issue is actually client side

[jira] [Updated] (QPID-4344) FailoverTest.testP2PFailover 0-9 - failover not begun by client

[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4344: - Status: Ready To Review (was: In Progress) > FailoverTest.testP2PFailover 0-9 - failover not

[jira] [Reopened] (QPID-4289) [Java Client 0-8/0-9.x] Failover functionality sometimes does not restore the connection

[ https://issues.apache.org/jira/browse/QPID-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reopened QPID-4289: -- Reopening due to issues discussed on QPID-4344 which resulted from the changes sin this JIRA.

[jira] [Updated] (QPID-4365) [AMQP 1-0 JMS Client] Support setting the client-id after the JMS connection has been created.

[ https://issues.apache.org/jira/browse/QPID-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4365: - Summary: [AMQP 1-0 JMS Client] Support setting the client-id after the JMS connection has been cre

[jira] [Updated] (QPID-4381) [AMQP 1-0 JMS Client] Add heartbeating the the JMS AMQP 1.0 client

[ https://issues.apache.org/jira/browse/QPID-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4381: - Summary: [AMQP 1-0 JMS Client] Add heartbeating the the JMS AMQP 1.0 client (was: [AMQP 1.0 JMS]

[jira] [Updated] (QPID-4383) [AMQP 1-0 JMS Client] Fix connection string to allow for URL encoded username/password

[ https://issues.apache.org/jira/browse/QPID-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4383: - Summary: [AMQP 1-0 JMS Client] Fix connection string to allow for URL encoded username/password (

[jira] [Updated] (QPID-4395) [AMQP 1-0 JMS Client] Client ACk in onMessage not working

[ https://issues.apache.org/jira/browse/QPID-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4395: - Summary: [AMQP 1-0 JMS Client] Client ACk in onMessage not working (was: [JMS AMQP 1.0 Client] Cl

[jira] [Updated] (QPID-4395) [AMQP 1-0 JMS Client] Client Ack in onMessage not working

[ https://issues.apache.org/jira/browse/QPID-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4395: - Summary: [AMQP 1-0 JMS Client] Client Ack in onMessage not working (was: [AMQP 1-0 JMS Client] Cl

[jira] [Updated] (QPID-4396) [AMQP 1-0 Java Client] Move examples into sub-module and thus remove dependency on commons-cli

[ https://issues.apache.org/jira/browse/QPID-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4396: - Summary: [AMQP 1-0 Java Client] Move examples into sub-module and thus remove dependency on common

[jira] [Updated] (QPID-4408) [AMQP 1-0 JMS Client] Potential NullPointerException on connection close

[ https://issues.apache.org/jira/browse/QPID-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4408: - Summary: [AMQP 1-0 JMS Client] Potential NullPointerException on connection close (was: Potential

[jira] [Updated] (QPID-4409) [AMQP 1-0 JMS Client] QueueConnection createDurableConnectionConsumer() should throw IllegalStateException

[ https://issues.apache.org/jira/browse/QPID-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4409: - Summary: [AMQP 1-0 JMS Client] QueueConnection createDurableConnectionConsumer() should throw Ille

[jira] [Updated] (QPID-4412) [AMQP 1-0 Java Common] ReceivingLinkEndpoint.isDrained result is invalid

[ https://issues.apache.org/jira/browse/QPID-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4412: - Summary: [AMQP 1-0 Java Common] ReceivingLinkEndpoint.isDrained result is invalid (was: QPID Java

[jira] [Updated] (QPID-4411) [AMQP 1-0 JMS Client] QueueBrowser should defer getting messages until getEnumeration() is called.

[ https://issues.apache.org/jira/browse/QPID-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4411: - Summary: [AMQP 1-0 JMS Client] QueueBrowser should defer getting messages until getEnumeration() i

[jira] [Commented] (QPID-4289) [Java Client 0-8/0-9.x] Failover functionality sometimes does not restore the connection

[ https://issues.apache.org/jira/browse/QPID-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490036#comment-13490036 ] Robbie Gemmell commented on QPID-4289: -- I have applied a patch from Phil Harvey (found

[jira] [Updated] (QPID-4289) [Java Client 0-8/0-9.x] Failover functionality sometimes does not restore the connection

[ https://issues.apache.org/jira/browse/QPID-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4289: - Status: Ready To Review (was: In Progress) > [Java Client 0-8/0-9.x] Failover functionality s

[jira] [Assigned] (QPID-4289) [Java Client 0-8/0-9.x] Failover functionality sometimes does not restore the connection

[ https://issues.apache.org/jira/browse/QPID-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-4289: Assignee: Philip Harvey (was: Robbie Gemmell) Phil, could you review the change please?

[jira] [Commented] (QPID-4344) FailoverTest.testP2PFailover 0-9 - failover not begun by client

[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490038#comment-13490038 ] Robbie Gemmell commented on QPID-4344: -- I have applied the patch, but with some furthe

[jira] [Updated] (QPID-4344) FailoverTest.testP2PFailover 0-9 - failover not begun by client

[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4344: - Status: Open (was: Ready To Review) > FailoverTest.testP2PFailover 0-9 - failover not begun b

[jira] [Resolved] (QPID-4344) FailoverTest.testP2PFailover 0-9 - failover not begun by client

[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4344. -- Resolution: Duplicate > FailoverTest.testP2PFailover 0-9 - failover not begun by client > --

[jira] [Comment Edited] (QPID-4344) FailoverTest.testP2PFailover 0-9 - failover not begun by client

[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490038#comment-13490038 ] Robbie Gemmell edited comment on QPID-4344 at 11/3/12 3:33 PM: --

[jira] [Created] (QPID-4419) [Java Broker] incorrect handling of missing sasl mechanism during 0-10 connection establishment

Robbie Gemmell created QPID-4419: Summary: [Java Broker] incorrect handling of missing sasl mechanism during 0-10 connection establishment Key: QPID-4419 URL: https://issues.apache.org/jira/browse/QPID-4419

[jira] [Updated] (QPID-4419) [Java Broker] incorrect handling of missing sasl mechanism during 0-10 connection establishment

[ https://issues.apache.org/jira/browse/QPID-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4419: - Description: A user recently asked for assistance (see mail thread: http://mail-archives.apache.o

[jira] [Assigned] (QPID-4419) [Java Broker] incorrect handling of missing sasl mechanism during 0-10 connection establishment

[ https://issues.apache.org/jira/browse/QPID-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-4419: Assignee: Robbie Gemmell > [Java Broker] incorrect handling of missing sasl mechanism du

[jira] [Updated] (QPID-4419) [Java Broker] incorrect handling of missing sasl mechanism during 0-10 connection establishment

[ https://issues.apache.org/jira/browse/QPID-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4419: - Status: Ready To Review (was: In Progress) > [Java Broker] incorrect handling of missing sasl

[jira] [Assigned] (QPID-4419) [Java Broker] incorrect handling of missing sasl mechanism during 0-10 connection establishment

[ https://issues.apache.org/jira/browse/QPID-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-4419: Assignee: Rob Godfrey (was: Robbie Gemmell) Rob, Could you review this change please? Than

[jira] [Comment Edited] (QPID-4419) [Java Broker] incorrect handling of missing sasl mechanism during 0-10 connection establishment

[ https://issues.apache.org/jira/browse/QPID-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490134#comment-13490134 ] Robbie Gemmell edited comment on QPID-4419 at 11/4/12 2:17 AM: --

[jira] [Created] (QPID-4420) [Java broker] add documentation for SSL and Authentication Providers to the docbook

Robbie Gemmell created QPID-4420: Summary: [Java broker] add documentation for SSL and Authentication Providers to the docbook Key: QPID-4420 URL: https://issues.apache.org/jira/browse/QPID-4420 Proj

[jira] [Created] (QPID-4431) deploy snapshot maven artefacts to repository.apache.org from CI

Robbie Gemmell created QPID-4431: Summary: deploy snapshot maven artefacts to repository.apache.org from CI Key: QPID-4431 URL: https://issues.apache.org/jira/browse/QPID-4431 Project: Qpid

[jira] [Assigned] (QPID-4431) deploy snapshot maven artefacts to repository.apache.org from CI

[ https://issues.apache.org/jira/browse/QPID-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-4431: Assignee: Robbie Gemmell > deploy snapshot maven artefacts to repository.apache.org from

[jira] [Resolved] (QPID-4431) deploy snapshot maven artefacts to repository.apache.org from CI

[ https://issues.apache.org/jira/browse/QPID-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4431. -- Resolution: Fixed https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Artefact-Release/ i

[jira] [Comment Edited] (QPID-4431) deploy snapshot maven artefacts to repository.apache.org from CI

[ https://issues.apache.org/jira/browse/QPID-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494955#comment-13494955 ] Robbie Gemmell edited comment on QPID-4431 at 11/11/12 8:17 PM: -

[jira] [Created] (QPID-4441) [Java broker] queue declare arguments are lost during v6 schema update for the optional bdbstore

Robbie Gemmell created QPID-4441: Summary: [Java broker] queue declare arguments are lost during v6 schema update for the optional bdbstore Key: QPID-4441 URL: https://issues.apache.org/jira/browse/QPID-4441

[jira] [Commented] (QPID-4441) [Java broker] queue declare arguments are lost during v6 schema update for the optional bdbstore

[ https://issues.apache.org/jira/browse/QPID-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499865#comment-13499865 ] Robbie Gemmell commented on QPID-4441: -- Committed a fix for the underlying FieldTable#

<    5   6   7   8   9   10   11   12   13   14   >