[jira] [Created] (QPID-5418) qpidd loading both linear and legacy store succeeds without a warning/error

Ernest Allen created QPID-5418: -- Summary: qpidd loading both linear and legacy store succeeds without a warning/error Key: QPID-5418 URL: https://issues.apache.org/jira/browse/QPID-5418 Project: Qpid

[jira] [Commented] (QPID-5380) Dispatch - Simplify use of non-system instances

[ https://issues.apache.org/jira/browse/QPID-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845649#comment-13845649 ] ASF subversion and git services commented on QPID-5380: --- Commit 15502

[jira] [Updated] (QPID-5417) ClassCastException when using amqp-1-0-jms-0.24 client

[ https://issues.apache.org/jira/browse/QPID-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Romahn updated QPID-5417: Summary: ClassCastException when using amqp-1-0-jms-0.24 client (was: lassCastException when using

[jira] [Commented] (QPID-5417) lassCastException when using amqp-1-0-jms-0.24 client

[ https://issues.apache.org/jira/browse/QPID-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845620#comment-13845620 ] Ulrich Romahn commented on QPID-5417: - I have create a public Github repo with the demo

[jira] [Created] (QPID-5417) lassCastException when using amqp-1-0-jms-0.24 client

Ulrich Romahn created QPID-5417: --- Summary: lassCastException when using amqp-1-0-jms-0.24 client Key: QPID-5417 URL: https://issues.apache.org/jira/browse/QPID-5417 Project: Qpid Issue Type: Bu

[jira] [Commented] (QPIDJMS-9) implement the JMS Message types and support for mapping them to/from AMQP messages

[ https://issues.apache.org/jira/browse/QPIDJMS-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845601#comment-13845601 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 15502

[jira] [Commented] (QPIDJMS-9) implement the JMS Message types and support for mapping them to/from AMQP messages

[ https://issues.apache.org/jira/browse/QPIDJMS-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845602#comment-13845602 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 15502

Re: Java Broker - adding support for multi-node HA clusters

On 12/11/2013 07:45 AM, Keith W wrote: We wish to let you know we are currently extending the high availability features provided by the Java Broker. Qpid Release 0.18 added simplistic support for Java Broker clusters formed of two nodes together with a basic JMX management layer allowing the cl

[jira] [Commented] (QPID-5416) [AMQP 1.0] sending a qmfv2 getTimestampConfig request over 1.0 causes broker crash

[ https://issues.apache.org/jira/browse/QPID-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845541#comment-13845541 ] ASF subversion and git services commented on QPID-5416: --- Commit 15501

[jira] [Commented] (QPIDJMS-9) implement the JMS Message types and support for mapping them to/from AMQP messages

[ https://issues.apache.org/jira/browse/QPIDJMS-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845399#comment-13845399 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 15501

Java Broker - adding support for multi-node HA clusters

We wish to let you know we are currently extending the high availability features provided by the Java Broker. Qpid Release 0.18 added simplistic support for Java Broker clusters formed of two nodes together with a basic JMX management layer allowing the cluster to be controlled. This piece of wo

[jira] [Updated] (QPID-5264) Can't change maxprefetch limit with JMS AMQP 1.0

[ https://issues.apache.org/jira/browse/QPID-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-5264: -- Fix Version/s: (was: 0.25) > Can't change maxprefetch limit with JMS AMQP 1.0 >

[jira] [Resolved] (QPID-5224) [Java 0-x Client] connection is abruptly closed when creating consumers against RabbitMQ

[ https://issues.apache.org/jira/browse/QPID-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved QPID-5224. --- Resolution: Fixed > [Java 0-x Client] connection is abruptly closed when creating consumers > against

[jira] [Updated] (QPID-5266) [Java Broker] the client product is not logged in the connection open message

[ https://issues.apache.org/jira/browse/QPID-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-5266: -- Status: Ready To Review (was: In Progress) > [Java Broker] the client product is not logged in the conn

[jira] [Resolved] (QPID-5266) [Java Broker] the client product is not logged in the connection open message

[ https://issues.apache.org/jira/browse/QPID-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved QPID-5266. --- Resolution: Fixed > [Java Broker] the client product is not logged in the connection open message > --

[jira] [Resolved] (QPID-5265) [Java Broker] the client version is only logged for 0-8/9/9-1 connections if a clientid is also set

[ https://issues.apache.org/jira/browse/QPID-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved QPID-5265. --- Resolution: Fixed > [Java Broker] the client version is only logged for 0-8/9/9-1 connections if > a

[jira] [Resolved] (QPID-5297) [Java Broker] make the 1.0 protocol plugin use a single ProtocolEngineCreator

[ https://issues.apache.org/jira/browse/QPID-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved QPID-5297. --- Resolution: Fixed > [Java Broker] make the 1.0 protocol plugin use a single ProtocolEngineCreator > --

[jira] [Updated] (QPID-4709) [AMQP 1.0] failover for broker initiated links

[ https://issues.apache.org/jira/browse/QPID-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-4709: - Fix Version/s: (was: 0.25) Future > [AMQP 1.0] failover for broker initiated links

[jira] [Resolved] (QPID-5170) [AMQP 1.0] outgoing deliveries that are settled without an explicit disposition are not dequeued

[ https://issues.apache.org/jira/browse/QPID-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-5170. -- Resolution: Fixed > [AMQP 1.0] outgoing deliveries that are settled without an explicit > disposition a

[jira] [Updated] (QPID-5179) [AMQP 1.0] add support for default- and supported- outcomes

[ https://issues.apache.org/jira/browse/QPID-5179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-5179: - Fix Version/s: (was: 0.25) Future > [AMQP 1.0] add support for default- and support

[jira] [Updated] (QPID-4710) [AMQP 1.0] Support for transactions

[ https://issues.apache.org/jira/browse/QPID-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-4710: - Fix Version/s: (was: 0.25) 0.27 > [AMQP 1.0] Support for transactions > ---

[jira] [Updated] (QPID-4648) C++ client library Send() timeout

[ https://issues.apache.org/jira/browse/QPID-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-4648: - Fix Version/s: (was: 0.25) Future > C++ client library Send() timeout > ---

[jira] [Resolved] (QPID-5277) Add ability create, delete and list objects of arbitrary types

[ https://issues.apache.org/jira/browse/QPID-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-5277. -- Resolution: Fixed > Add ability create, delete and list objects of arbitrary types > ---

[jira] [Updated] (QPID-5255) 0.26 release tasks

[ https://issues.apache.org/jira/browse/QPID-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-5255: -- Fix Version/s: 0.26 > 0.26 release tasks > -- > > Key: QPID-5255 >

[jira] [Closed] (QPID-5329) QMFv2 tests fail when qmf console code is unavailable

[ https://issues.apache.org/jira/browse/QPID-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-5329. - Resolution: Invalid This problem only surfaces when you have a system-installed qmf console. If the cons

[jira] [Updated] (QPID-5047) Release.sh is written to bash, not sh, and has an incorrect shebang

[ https://issues.apache.org/jira/browse/QPID-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-5047: -- Fix Version/s: (was: 0.25) 0.27 > Release.sh is written to bash, not sh, and has

[jira] [Updated] (QPID-4585) JIRA Clean up for a number of commponents

[ https://issues.apache.org/jira/browse/QPID-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4585: -- Fix Version/s: (was: 0.25) 0.27 > JIRA Clean up for a number of commponents > ---

[jira] [Commented] (QPID-5311) Website improvements for the 0.26 timeframe

[ https://issues.apache.org/jira/browse/QPID-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845266#comment-13845266 ] ASF subversion and git services commented on QPID-5311: --- Commit 15500