[jira] [Commented] (QPID-5532) [C++ broker] Add debug log when timeouting DTX transaction
[ https://issues.apache.org/jira/browse/QPID-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888553#comment-13888553 ] ASF subversion and git services commented on QPID-5532: --- Commit 1563403 from [~pmoravec] in branch 'qpid/trunk' [ https://svn.apache.org/r1563403 ] QPID-5532: [C++ broker] Add debug log when timeouting DTX transaction > [C++ broker] Add debug log when timeouting DTX transaction > -- > > Key: QPID-5532 > URL: https://issues.apache.org/jira/browse/QPID-5532 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.24 >Reporter: Pavel Moravec >Assignee: Pavel Moravec >Priority: Trivial > Labels: easyfix, patch > Fix For: 0.27 > > > Any timeout-ed DTX transaction shall be logged. Especially once QPID-5531 is > implemented, as then every DTX will have some default timeout. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5504) [Java Broker] Allow other routing/storage node types than Queues and Exchanges
[ https://issues.apache.org/jira/browse/QPID-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888633#comment-13888633 ] ASF subversion and git services commented on QPID-5504: --- Commit 1563431 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1563431 ] QPID-5504 : Moving routing to Exchange from session classes > [Java Broker] Allow other routing/storage node types than Queues and Exchanges > -- > > Key: QPID-5504 > URL: https://issues.apache.org/jira/browse/QPID-5504 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5121) Store module does not raise exception when attempting to enqueue a message bigger than the journal size
[
https://issues.apache.org/jira/browse/QPID-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888924#comment-13888924
]
ASF subversion and git services commented on QPID-5121:
---
Commit 1563613 from [~pmoravec] in branch 'qpid/trunk'
[ https://svn.apache.org/r1563613 ]
QPID-5121: Store module does not raise exception when attempting to enqueue a
message bigger than the journal size
> Store module does not raise exception when attempting to enqueue a message
> bigger than the journal size
> ---
>
> Key: QPID-5121
> URL: https://issues.apache.org/jira/browse/QPID-5121
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
>Affects Versions: 0.22
>Reporter: Pavel Moravec
> Attachments: QPID-5121.patch
>
>
> Description of problem:
> Whenever store module tries to write to a journal a message bigger than the
> journal capacity is, it a) does not store the message (so far so good), but
> b) it does _not_ raise an error (!!!). So the broker thinks the message was
> enqueued.
> That is a big gotcha, as the durable message is kept in memory only.
> Version-Release number of selected component (if applicable):
> 0.22
> How reproducible:
> 100%
> Steps to Reproduce:
> rm -rf /var/lib/qpidd/* /var/lib/qpidd/.* 2> /dev/null
> service qpidd restart
> # create a durable queue with tiny journal and send there one huge message
> qpid-send -a "DurableQueue4; {create:always, node:{durable:true, x-declare:{
> arguments:{'qpid.flow_stop_count':0, 'qpid.max_count':0, 'qpid.file_count':4,
> 'qpid.file_size':8, 'qpid.flow_resume_count':0, 'qpid.flow_stop_size':0,
> 'qpid.flow_resume_size':0, 'qpid.max_size':0 " -m 1
> --content-size=1 --durable=yes
> # check in stats the queue has the message enqueued
> qpid-stat -q
> Queues
> queue dur autoDel excl msg msgIn
> msgOut bytes bytesIn bytesOut cons bind
>
> =
> 7e553cc6-89d4-46b2-93fd-5ad7cf1f72a9:0.0 YY0 0
> 0 0 00 1 2
> DurableQueue4 Y 1 1
> 0 100m 100m 0 0 1
> # restart the broker and check queue stats
> service qpidd restart
> qpid-stat -q
> Queues
> queue dur autoDel excl msg msgIn
> msgOut bytes bytesIn bytesOut cons bind
>
> =
> DurableQueue4 Y 0 0
> 0 0 00 0 1
> cd53-5b98-4101-ad35-de71e038cd61:0.0 YY0 0
> 0 0 00 1 2
> # ouch, where the _durable_ message went to???
> Actual results:
> 1) generic reproducer for regular durable queue:
> - qpid-send/broker/store has not returned an error (THIS is the wrong)
> - after the broker restart, the queue has no message (this should be ok but
> not after no error raised)
> Expected results:
> qpid-send should fail due to "Enqueue capacity threshold" error (and no
> message should be kept in the broker later on).
> Additional info:
> - Optional/variant scenarios: send first some tiny message to the journal and
> then the huge one.
> - Trivial patch to be added
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5519) ACL property/properties for paged queues
[ https://issues.apache.org/jira/browse/QPID-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888940#comment-13888940 ] ASF subversion and git services commented on QPID-5519: --- Commit 1563628 from [~pmoravec] in branch 'qpid/trunk' [ https://svn.apache.org/r1563628 ] QPID-5519: ACL property/properties for paged queues > ACL property/properties for paged queues > > > Key: QPID-5519 > URL: https://issues.apache.org/jira/browse/QPID-5519 > Project: Qpid > Issue Type: Improvement > Components: C++ Broker >Affects Versions: 0.24 >Reporter: Pavel Moravec >Assignee: Pavel Moravec >Priority: Minor > Labels: improvement, patch > Attachments: QPID-5519.patch > > > Description of problem: > QPID-4339 adds paged queue but there is no corresponding ACL rule/property > limiting users in creating paged queues. As from system management point of > view, a paged queue (being backed up by a physical file) is very similar to a > durable queue. > Therefore ACL should have property "paging=true" / "paging=false" in create > queue rule. Additionally, it has some (limited) sense to have limits for > max_pages_loaded and page_factor attributes. Those limits: > - could limit memory usage (if the property would compare > max_pages_loaded*page_factor) > - could limit maximal message size to be successfully enqueued (page_factor) > - though I dont see a big value of such ACL limit; please provide a business > justification if there is > - could _indirectly_ limit maximal size of the underlying file (that upper > limit is page_factor*value_of_(/proc/sys/vm/max_map_count) ) - as > max_map_count is usually high, it is less usefull > Version-Release number of selected component (if applicable): > any (incl. qpid 0.26) > How reproducible: > 100% > Steps to Reproduce: > any user can run: > qpid-config add queue my-paged-queue --argument qpid.paging=True --argument > qpid.max_pages_loaded=1 --argument qpid.page_factor=1 > Actual results: > Any user can create paged queue of arbitrary parameters (paged queue related). > Expected results: > ACL parameters could prevent so. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5504) [Java Broker] Allow other routing/storage node types than Queues and Exchanges
[ https://issues.apache.org/jira/browse/QPID-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889160#comment-13889160 ] ASF subversion and git services commented on QPID-5504: --- Commit 1563755 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1563755 ] QPID-5504 : Adding missing class > [Java Broker] Allow other routing/storage node types than Queues and Exchanges > -- > > Key: QPID-5504 > URL: https://issues.apache.org/jira/browse/QPID-5504 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5534) [C++ broker] Headers exchange can route a message to one queue multiple times
[ https://issues.apache.org/jira/browse/QPID-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889444#comment-13889444 ] ASF subversion and git services commented on QPID-5534: --- Commit 1563863 from [~pmoravec] in branch 'qpid/trunk' [ https://svn.apache.org/r1563863 ] QPID-5534: [C++ broker] Headers exchange can route a message to one queue multiple times > [C++ broker] Headers exchange can route a message to one queue multiple times > - > > Key: QPID-5534 > URL: https://issues.apache.org/jira/browse/QPID-5534 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.24 >Reporter: Pavel Moravec >Assignee: Pavel Moravec >Priority: Minor > Fix For: 0.27 > > > If a message sent to a headers exchange matches two bindings to one queue, it > is enqueued to that queue twice. > Further, if the queue and the message are durable, journal raises error: > JERR_MAP_DUPLICATE: Attempted to insert record into map using duplicate key. > Reproducer: > qpid-config add queue MyQueue --durable > qpid-config bind amq.match MyQueue SomeKey any property1=value1 > qpid-config bind amq.match MyQueue OtherKey all property2=value2 > qpid-send -a "amq.match" -m 1 -P property1=value1 -P property2=value2 > --durable=true -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5519) ACL property/properties for paged queues
[ https://issues.apache.org/jira/browse/QPID-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889448#comment-13889448 ] ASF subversion and git services commented on QPID-5519: --- Commit 1563866 from [~pmoravec] in branch 'qpid/trunk' [ https://svn.apache.org/r1563866 ] QPID-5519: ACL property/properties for paged queues - fixed typo, added tests and documentation > ACL property/properties for paged queues > > > Key: QPID-5519 > URL: https://issues.apache.org/jira/browse/QPID-5519 > Project: Qpid > Issue Type: Improvement > Components: C++ Broker >Affects Versions: 0.24 >Reporter: Pavel Moravec >Assignee: Pavel Moravec >Priority: Minor > Labels: improvement, patch > Fix For: 0.27 > > Attachments: QPID-5519.patch > > > Description of problem: > QPID-4339 adds paged queue but there is no corresponding ACL rule/property > limiting users in creating paged queues. As from system management point of > view, a paged queue (being backed up by a physical file) is very similar to a > durable queue. > Therefore ACL should have property "paging=true" / "paging=false" in create > queue rule. Additionally, it has some (limited) sense to have limits for > max_pages_loaded and page_factor attributes. Those limits: > - could limit memory usage (if the property would compare > max_pages_loaded*page_factor) > - could limit maximal message size to be successfully enqueued (page_factor) > - though I dont see a big value of such ACL limit; please provide a business > justification if there is > - could _indirectly_ limit maximal size of the underlying file (that upper > limit is page_factor*value_of_(/proc/sys/vm/max_map_count) ) - as > max_map_count is usually high, it is less usefull > Version-Release number of selected component (if applicable): > any (incl. qpid 0.26) > How reproducible: > 100% > Steps to Reproduce: > any user can run: > qpid-config add queue my-paged-queue --argument qpid.paging=True --argument > qpid.max_pages_loaded=1 --argument qpid.page_factor=1 > Actual results: > Any user can create paged queue of arbitrary parameters (paged queue related). > Expected results: > ACL parameters could prevent so. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13889519#comment-13889519 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1563934 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1563934 ] QPIDJMS-9: tidy up message tests to remove their direct use/knowledge of the test message classes > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-11) add configuration for RAT to check licence headers
[ https://issues.apache.org/jira/browse/QPIDJMS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889521#comment-13889521 ] ASF subversion and git services commented on QPIDJMS-11: Commit 1563935 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1563935 ] QPIDJMS-11: configure RAT plugin + report, fix files it identified as missing the licence header > add configuration for RAT to check licence headers > -- > > Key: QPIDJMS-11 > URL: https://issues.apache.org/jira/browse/QPIDJMS-11 > Project: Qpid JMS > Issue Type: Improvement >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > add configuration for RAT to check licence headers -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13889522#comment-13889522 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1563936 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1563936 ] QPIDJMS-9: use new UnsignedLong.valueOf(BigInteger) method since added to Proton. > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13889638#comment-13889638 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1563983 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1563983 ] QPIDJMS-9: set JMSMessageID when sending. Initial work on correlation-id handling. > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5528) HA Clean up error messages around queue deletion
[
https://issues.apache.org/jira/browse/QPID-5528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889781#comment-13889781
]
ASF subversion and git services commented on QPID-5528:
---
Commit 1564010 from [~aconway] in branch 'qpid/trunk'
[ https://svn.apache.org/r1564010 ]
QPID-5528: HA Clean up error messages around rolled-back transactions.
A simple transaction test on a 3 node cluster generates a lot of errors and
rollback messages in the broker logs even though the test code never rolls back
a
transaction. E.g.
qpid-cluster-benchmark -b 20.0.20.200 -n1 -m 1000 -q3 -s2 -r2 --send-arg=--tx
--send-arg=10 --receive-arg=--tx --receive-arg=10
The errors are caused by queues being deleted while backup brokers are using
them. This happens a lot in the transaction test because a transactional session
must create a new transaction when the previous one closes. When the session
closes the open transaction is rolled back automatically. Thus there is almost
always an empty transaction that is created then immediately rolled back at the
end of the session. Backup brokers may still be in the process of subscribing to
the transaction's replication queue at this point, causing (harmlesss) errors.
This commit takes the following steps to clean up the unwanted error and
rollback messages:
HA TX messages cleaned up:
- Remove log messages about rolling back/destroying empty transactions.
- Remove misleading "backup disconnected" message for cancelled transactions.
- Remove spurious warning about ignored unreplicated dequeues.
- Include TxReplicator destroy in QueueReplicator mutex, idempotence check
before destroy.
Allow HA to suppress/modify broker exception logging:
- Move broker exception logging into ErrorListener
- Every SessionHandler has DefaultErrorListener that does the same logging as
before.
- Added SessionHandlerObserver to allow plugins to change the error listener.
- HA plugin set ErrorListeners to log harmless exceptions as HA debug messages.
Unrelated cleanup:
- Broker now logs "incoming execution exceptions" as debug messages rather than
ignoring.
- Exception prefixes: don't add the prefix if already present.
The exception test above should now pass without errors or rollback messages in
the logs.
> HA Clean up error messages around queue deletion
>
>
> Key: QPID-5528
> URL: https://issues.apache.org/jira/browse/QPID-5528
> Project: Qpid
> Issue Type: Bug
> Components: C++ Clustering
>Affects Versions: 0.26
>Reporter: Alan Conway
>Assignee: Alan Conway
>
> See also https://bugzilla.redhat.com/show_bug.cgi?id=1024528
> Running the following simple transaction test:
> {noformat}
> qpid-cluster-benchmark -b 20.0.20.200 -n1 -m 1000 -q3 -s2 -r2 $AMQP10
> --send-arg=--tx --send-arg=10 --receive-arg=--tx --receive-arg=10
> {noformat}
> Generates a lot of errors and rollback messages in the broker logs.
> It should complete cleanly.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5528) HA Clean up error messages around queue deletion
[
https://issues.apache.org/jira/browse/QPID-5528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890028#comment-13890028
]
ASF subversion and git services commented on QPID-5528:
---
Commit 1564120 from [~aconway] in branch 'qpid/trunk'
[ https://svn.apache.org/r1564120 ]
QPID-5528: HA add missing QPID_BROKER_EXTERN declarations.
Missing from previous commit
r1564010 | QPID-5528: HA Clean up error messages around rolled-back
transactions.
> HA Clean up error messages around queue deletion
>
>
> Key: QPID-5528
> URL: https://issues.apache.org/jira/browse/QPID-5528
> Project: Qpid
> Issue Type: Bug
> Components: C++ Clustering
>Affects Versions: 0.26
>Reporter: Alan Conway
>Assignee: Alan Conway
>
> See also https://bugzilla.redhat.com/show_bug.cgi?id=1024528
> Running the following simple transaction test:
> {noformat}
> qpid-cluster-benchmark -b 20.0.20.200 -n1 -m 1000 -q3 -s2 -r2 $AMQP10
> --send-arg=--tx --send-arg=10 --receive-arg=--tx --receive-arg=10
> {noformat}
> Generates a lot of errors and rollback messages in the broker logs.
> It should complete cleanly.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5409) [Java Broker] Add support for multi-node HA cluster into BDB JE HA message store
[ https://issues.apache.org/jira/browse/QPID-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890547#comment-13890547 ] ASF subversion and git services commented on QPID-5409: --- Commit 1564250 from [~k-wall] in branch 'qpid/branches/java-broker-bdb-ha' [ https://svn.apache.org/r1564250 ] QPID-5409: Refactor BDB HA system tests to use management REST interfaces instead of JMX. Add new system tests for setting priority, quorum override and role > [Java Broker] Add support for multi-node HA cluster into BDB JE HA message > store > > > Key: QPID-5409 > URL: https://issues.apache.org/jira/browse/QPID-5409 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Alex Rudyy > Fix For: 0.27 > > > The Java Qpid Broker currently supports only 2-nodes HA cluster with BDB JE > message store. This JIRA aims to extend the current HA functionality and add > support for multi-node HA cluster into BDB JE message store. > Here is the list of high-level requirements for the HA multi-node support: > # Only persistent messages are to be replicated. Transient messages will be > lost on failover. > # System must support clusters formed of an arbitrary number of nodes > # System must continue to support clusters formed of two nodes. Existing > public interfaces (notably JMX and existing virtualhost.xml format) must be > retained (though may be deprecated) to allow existing users a convenient > upgrade path. > # System must allow a user to completely configure a new node via the > web-management interface. > # System must allow a user to monitor the nodes of the cluster in order to > ascertain its health and perform day to day operations for via the > web-management interface. > ## expose statistics to allow the health of the cluster to be established > (exact details to be determined: could be low level like DbPing or something > more abstract) > # System must be amenable to monitoring by third-party tools. The Broker > should emit clear operational log messages as it transitions between states. > These messages will be targeted at the end-user. > # System must permit a mode of operation whereby the user (or other external > agent) determines which virtual host becomes active following a store > failover. In this mode of operation, following a failure, the store nodes in > the cluster will elect a new master and the replica node will still sync-up > with the new master node, but the system will not automatically mark the > virtual host corresponding to the master as active. The user will then > transfer the master to the desired location and make the virtualhost as > active, allowing business traffic to recommence. > # System must permit a mode of operation whereby the election of a store node > as master also causes the corresponding virtual host to become active. > # System must allow a user to influence a node's electability. These > features will allow a customer whose cluster spans primary/DR sites to keep > the active virtual hosts on the primary site in normal situations by > favouring failover within the primary site.Specifically, this will allow: > ## making a node unelectable - the node, even though it remains part of the > cluster, will never be elected as master) > ## making a node more likely to be elected master than other nodes - that > is, if two or more nodes have an equally up to date set of transactions, the > node with the highest priority will be elected master > ## node electability settings must survive restart, > ## node electability settings must be alterable at run-time. > # System must allow a user to alter quorum. This feature is required in > extraordinary situations where the system is required to continue to operate > despite the loss of sufficient nodes to mean there is no longer simple > majority. > # System must allow the user to move the active virtual host from one node to > another. This feature will help a user to restore a system to its BAU state > following an extraordinary situation. > # System must provide a user with a read-only view Queue when the underlying > store is in a replica state. This must provide at least queue name and queue > depth. This feature will allow a user to be able to see that replication is > indeed functioning. > # System must allow all HA operations to be allowed/denied according to rules > in the ACL. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5504) [Java Broker] Allow other routing/storage node types than Queues and Exchanges
[ https://issues.apache.org/jira/browse/QPID-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890592#comment-13890592 ] ASF subversion and git services commented on QPID-5504: --- Commit 1564258 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1564258 ] QPID-5504 : fix bug in DistributedTransaction when enqueuing a single message - brought to light by earlier refactoring > [Java Broker] Allow other routing/storage node types than Queues and Exchanges > -- > > Key: QPID-5504 > URL: https://issues.apache.org/jira/browse/QPID-5504 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5504) [Java Broker] Allow other routing/storage node types than Queues and Exchanges
[ https://issues.apache.org/jira/browse/QPID-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890596#comment-13890596 ] ASF subversion and git services commented on QPID-5504: --- Commit 1564259 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1564259 ] QPID-5504 : remove unused inner classes > [Java Broker] Allow other routing/storage node types than Queues and Exchanges > -- > > Key: QPID-5504 > URL: https://issues.apache.org/jira/browse/QPID-5504 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13890694#comment-13890694 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1564300 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1564300 ] QPIDJMS-9: add integration tests for recieving messages with correlation-id, and basic string test for sending. Add/reword javadoc and split unit tests to be more clearer and more specific. > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13890881#comment-13890881 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1564390 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1564390 ] QPIDJMS-9: initial work on decoding JMSMessageIDs on incoming messages then used as JMSCorrelationID values on outgoing messages, enabling type retention for the transmitted AMQP correlation-id value > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5539) Provide Windows SslCredential class
[ https://issues.apache.org/jira/browse/QPID-5539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891642#comment-13891642 ] ASF subversion and git services commented on QPID-5539: --- Commit 1564611 from cliffjan...@apache.org in branch 'qpid/trunk' [ https://svn.apache.org/r1564611 ] QPID-5539: Separate credential processing for re-use in AMQP1.0 SSL transport. > Provide Windows SslCredential class > --- > > Key: QPID-5539 > URL: https://issues.apache.org/jira/browse/QPID-5539 > Project: Qpid > Issue Type: Improvement > Components: C++ Client >Affects Versions: 0.27 > Environment: Windows >Reporter: Cliff Jansen >Assignee: Cliff Jansen > Fix For: 0.27 > > > The logic in SslConnector.cpp for finding certificates and transforming them > into credential structures (required by Windows SChannel) needs to be reused > in the AMQP1.0 transport code. Separate it out to a separate class. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5540) Windows connection close error: SCHANNEL_SHUTDOWN called twice
[ https://issues.apache.org/jira/browse/QPID-5540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891863#comment-13891863 ] ASF subversion and git services commented on QPID-5540: --- Commit 1564644 from cliffjan...@apache.org in branch 'qpid/trunk' [ https://svn.apache.org/r1564644 ] QPID-5540: use mutex to ensure single SCHANNEL_SHUTDOWN > Windows connection close error: SCHANNEL_SHUTDOWN called twice > -- > > Key: QPID-5540 > URL: https://issues.apache.org/jira/browse/QPID-5540 > Project: Qpid > Issue Type: Bug > Components: C++ Client >Affects Versions: 0.27 > Environment: Windows c++ >Reporter: Cliff Jansen >Assignee: Cliff Jansen > > SslAsynchIO::queueWriteClose can be called by both user and IO threads > causing two SCHANNEL_SHUTDOWN actions in separate threads and a spurious > error from SChannel. A mutex can prevent the second shutdown. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5531) [C++ broker] Set timeout for every DTX transaction
[ https://issues.apache.org/jira/browse/QPID-5531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891962#comment-13891962 ] ASF subversion and git services commented on QPID-5531: --- Commit 1564694 from [~pmoravec] in branch 'qpid/trunk' [ https://svn.apache.org/r1564694 ] QPID-5531: [C++ broker] Set timeout for every DTX transaction > [C++ broker] Set timeout for every DTX transaction > -- > > Key: QPID-5531 > URL: https://issues.apache.org/jira/browse/QPID-5531 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.24 >Reporter: Pavel Moravec >Assignee: Pavel Moravec >Priority: Minor > Labels: patch > Fix For: 0.27 > > Attachments: QPID-5531.patch, qpid-txtest_modified.patch > > > Description of problem: > If an external Transaction Manager (TM) prepares a DTX transaction but > forgets, due to any reason, to commit or abort it, tpl journal has an > orphaned enqueue record forever (that in legacystore causes enqueue capacity > threshold exception after a while, preventing _any_ transaction to > commit/abort). > To prevent such orphaned XID entries in tpl, every incoming DTX transaction > should have a default timeout set (while dtx.set-timeout AMQP 0-10 primitive > changes it). > The timeout should be broker-wide parameter configurable via > --dtx-default-timeout option. > Version-Release number of selected component (if applicable): > any (incl upstream 0.26) > How reproducible: > 100% > Steps to Reproduce: > 1. Mimic an external TM that prepares a DTX but never commits or aborts it - > use e.g. _modified_ qpid-txtest (patch attached): > qpid-txtest --queues=1 --total-messages=1 --dtx=1 --dtx-commit=no > 2. /usr/libexec/qpid/store_chk /var/lib/qpidd/rhm/tpl -b tpl > Actual results: > tpl journal keeps the unfinished transaction forever > Expected results: > sleeping for dtx-default-timeout, the transaction should be gone -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5541) HA incorrect options for expected-backups in qpid-ha tool.
[ https://issues.apache.org/jira/browse/QPID-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892208#comment-13892208 ] ASF subversion and git services commented on QPID-5541: --- Commit 1564797 from [~aconway] in branch 'qpid/trunk' [ https://svn.apache.org/r1564797 ] QPID-5541: HA incorrect options for expected-backups in qpid-ha tool Remove invalid --backup option from qpid-ha set and query commands. > HA incorrect options for expected-backups in qpid-ha tool. > -- > > Key: QPID-5541 > URL: https://issues.apache.org/jira/browse/QPID-5541 > Project: Qpid > Issue Type: Bug > Components: Python Tools >Affects Versions: 0.26 >Reporter: Alan Conway >Assignee: Alan Conway > > The qpid-ha tool offers options to set and query the "expected backup count" > on a HA broker. There is no such count, these options are part of some idea > that was never finished and should be removed. > See also: https://bugzilla.redhat.com/show_bug.cgi?id=1061754 -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5362) Linearstore: No store tools exist for examining the journals
[ https://issues.apache.org/jira/browse/QPID-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892233#comment-13892233 ] ASF subversion and git services commented on QPID-5362: --- Commit 1564808 from [~kpvdr] in branch 'qpid/trunk' [ https://svn.apache.org/r1564808 ] QPID-5362: Bugfixes and enhancements for qpid_qls_analyze > Linearstore: No store tools exist for examining the journals > > > Key: QPID-5362 > URL: https://issues.apache.org/jira/browse/QPID-5362 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Minor > Labels: linearstore > > There are no tools which can off-line (ie when the broker is not running) > examine the linearstore journal files and empty file pools. It would be > useful to be able to: > 1. Manage the state of the empty file pool(s), and to add/remove different > partitions and pools containing different file sizes; > 2. Examine any journal files present and view the still-enqueued messages > that may be present; > 3. Examine the transaction prepared list journal and determine which > transactions (if any) are incomplete or in an inconsistent state. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5409) [Java Broker] Add support for multi-node HA cluster into BDB JE HA message store
[ https://issues.apache.org/jira/browse/QPID-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892239#comment-13892239 ] ASF subversion and git services commented on QPID-5409: --- Commit 1564813 from [~k-wall] in branch 'qpid/branches/java-broker-bdb-ha' [ https://svn.apache.org/r1564813 ] QPID-5409: Add functionality into RemoteReplicationNode to change role attribute from REPLICA to MASTER > [Java Broker] Add support for multi-node HA cluster into BDB JE HA message > store > > > Key: QPID-5409 > URL: https://issues.apache.org/jira/browse/QPID-5409 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Alex Rudyy > Fix For: 0.27 > > > The Java Qpid Broker currently supports only 2-nodes HA cluster with BDB JE > message store. This JIRA aims to extend the current HA functionality and add > support for multi-node HA cluster into BDB JE message store. > Here is the list of high-level requirements for the HA multi-node support: > # Only persistent messages are to be replicated. Transient messages will be > lost on failover. > # System must support clusters formed of an arbitrary number of nodes > # System must continue to support clusters formed of two nodes. Existing > public interfaces (notably JMX and existing virtualhost.xml format) must be > retained (though may be deprecated) to allow existing users a convenient > upgrade path. > # System must allow a user to completely configure a new node via the > web-management interface. > # System must allow a user to monitor the nodes of the cluster in order to > ascertain its health and perform day to day operations for via the > web-management interface. > ## expose statistics to allow the health of the cluster to be established > (exact details to be determined: could be low level like DbPing or something > more abstract) > # System must be amenable to monitoring by third-party tools. The Broker > should emit clear operational log messages as it transitions between states. > These messages will be targeted at the end-user. > # System must permit a mode of operation whereby the user (or other external > agent) determines which virtual host becomes active following a store > failover. In this mode of operation, following a failure, the store nodes in > the cluster will elect a new master and the replica node will still sync-up > with the new master node, but the system will not automatically mark the > virtual host corresponding to the master as active. The user will then > transfer the master to the desired location and make the virtualhost as > active, allowing business traffic to recommence. > # System must permit a mode of operation whereby the election of a store node > as master also causes the corresponding virtual host to become active. > # System must allow a user to influence a node's electability. These > features will allow a customer whose cluster spans primary/DR sites to keep > the active virtual hosts on the primary site in normal situations by > favouring failover within the primary site.Specifically, this will allow: > ## making a node unelectable - the node, even though it remains part of the > cluster, will never be elected as master) > ## making a node more likely to be elected master than other nodes - that > is, if two or more nodes have an equally up to date set of transactions, the > node with the highest priority will be elected master > ## node electability settings must survive restart, > ## node electability settings must be alterable at run-time. > # System must allow a user to alter quorum. This feature is required in > extraordinary situations where the system is required to continue to operate > despite the loss of sufficient nodes to mean there is no longer simple > majority. > # System must allow the user to move the active virtual host from one node to > another. This feature will help a user to restore a system to its BAU state > following an extraordinary situation. > # System must provide a user with a read-only view Queue when the underlying > store is in a replica state. This must provide at least queue name and queue > depth. This feature will allow a user to be able to see that replication is > indeed functioning. > # System must allow all HA operations to be allowed/denied according to rules > in the ACL. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5409) [Java Broker] Add support for multi-node HA cluster into BDB JE HA message store
[ https://issues.apache.org/jira/browse/QPID-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892240#comment-13892240 ] ASF subversion and git services commented on QPID-5409: --- Commit 1564814 from [~k-wall] in branch 'qpid/branches/java-broker-bdb-ha' [ https://svn.apache.org/r1564814 ] QPID-5409: Add functionality to delete remote node > [Java Broker] Add support for multi-node HA cluster into BDB JE HA message > store > > > Key: QPID-5409 > URL: https://issues.apache.org/jira/browse/QPID-5409 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Alex Rudyy > Fix For: 0.27 > > > The Java Qpid Broker currently supports only 2-nodes HA cluster with BDB JE > message store. This JIRA aims to extend the current HA functionality and add > support for multi-node HA cluster into BDB JE message store. > Here is the list of high-level requirements for the HA multi-node support: > # Only persistent messages are to be replicated. Transient messages will be > lost on failover. > # System must support clusters formed of an arbitrary number of nodes > # System must continue to support clusters formed of two nodes. Existing > public interfaces (notably JMX and existing virtualhost.xml format) must be > retained (though may be deprecated) to allow existing users a convenient > upgrade path. > # System must allow a user to completely configure a new node via the > web-management interface. > # System must allow a user to monitor the nodes of the cluster in order to > ascertain its health and perform day to day operations for via the > web-management interface. > ## expose statistics to allow the health of the cluster to be established > (exact details to be determined: could be low level like DbPing or something > more abstract) > # System must be amenable to monitoring by third-party tools. The Broker > should emit clear operational log messages as it transitions between states. > These messages will be targeted at the end-user. > # System must permit a mode of operation whereby the user (or other external > agent) determines which virtual host becomes active following a store > failover. In this mode of operation, following a failure, the store nodes in > the cluster will elect a new master and the replica node will still sync-up > with the new master node, but the system will not automatically mark the > virtual host corresponding to the master as active. The user will then > transfer the master to the desired location and make the virtualhost as > active, allowing business traffic to recommence. > # System must permit a mode of operation whereby the election of a store node > as master also causes the corresponding virtual host to become active. > # System must allow a user to influence a node's electability. These > features will allow a customer whose cluster spans primary/DR sites to keep > the active virtual hosts on the primary site in normal situations by > favouring failover within the primary site.Specifically, this will allow: > ## making a node unelectable - the node, even though it remains part of the > cluster, will never be elected as master) > ## making a node more likely to be elected master than other nodes - that > is, if two or more nodes have an equally up to date set of transactions, the > node with the highest priority will be elected master > ## node electability settings must survive restart, > ## node electability settings must be alterable at run-time. > # System must allow a user to alter quorum. This feature is required in > extraordinary situations where the system is required to continue to operate > despite the loss of sufficient nodes to mean there is no longer simple > majority. > # System must allow the user to move the active virtual host from one node to > another. This feature will help a user to restore a system to its BAU state > following an extraordinary situation. > # System must provide a user with a read-only view Queue when the underlying > store is in a replica state. This must provide at least queue name and queue > depth. This feature will allow a user to be able to see that replication is > indeed functioning. > # System must allow all HA operations to be allowed/denied according to rules > in the ACL. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5409) [Java Broker] Add support for multi-node HA cluster into BDB JE HA message store
[ https://issues.apache.org/jira/browse/QPID-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892241#comment-13892241 ] ASF subversion and git services commented on QPID-5409: --- Commit 1564815 from [~k-wall] in branch 'qpid/branches/java-broker-bdb-ha' [ https://svn.apache.org/r1564815 ] QPID-5409: Refactor RemoteReplicationNode to delegate je calls to ReplicatedEnvironmentFacade > [Java Broker] Add support for multi-node HA cluster into BDB JE HA message > store > > > Key: QPID-5409 > URL: https://issues.apache.org/jira/browse/QPID-5409 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Alex Rudyy > Fix For: 0.27 > > > The Java Qpid Broker currently supports only 2-nodes HA cluster with BDB JE > message store. This JIRA aims to extend the current HA functionality and add > support for multi-node HA cluster into BDB JE message store. > Here is the list of high-level requirements for the HA multi-node support: > # Only persistent messages are to be replicated. Transient messages will be > lost on failover. > # System must support clusters formed of an arbitrary number of nodes > # System must continue to support clusters formed of two nodes. Existing > public interfaces (notably JMX and existing virtualhost.xml format) must be > retained (though may be deprecated) to allow existing users a convenient > upgrade path. > # System must allow a user to completely configure a new node via the > web-management interface. > # System must allow a user to monitor the nodes of the cluster in order to > ascertain its health and perform day to day operations for via the > web-management interface. > ## expose statistics to allow the health of the cluster to be established > (exact details to be determined: could be low level like DbPing or something > more abstract) > # System must be amenable to monitoring by third-party tools. The Broker > should emit clear operational log messages as it transitions between states. > These messages will be targeted at the end-user. > # System must permit a mode of operation whereby the user (or other external > agent) determines which virtual host becomes active following a store > failover. In this mode of operation, following a failure, the store nodes in > the cluster will elect a new master and the replica node will still sync-up > with the new master node, but the system will not automatically mark the > virtual host corresponding to the master as active. The user will then > transfer the master to the desired location and make the virtualhost as > active, allowing business traffic to recommence. > # System must permit a mode of operation whereby the election of a store node > as master also causes the corresponding virtual host to become active. > # System must allow a user to influence a node's electability. These > features will allow a customer whose cluster spans primary/DR sites to keep > the active virtual hosts on the primary site in normal situations by > favouring failover within the primary site.Specifically, this will allow: > ## making a node unelectable - the node, even though it remains part of the > cluster, will never be elected as master) > ## making a node more likely to be elected master than other nodes - that > is, if two or more nodes have an equally up to date set of transactions, the > node with the highest priority will be elected master > ## node electability settings must survive restart, > ## node electability settings must be alterable at run-time. > # System must allow a user to alter quorum. This feature is required in > extraordinary situations where the system is required to continue to operate > despite the loss of sufficient nodes to mean there is no longer simple > majority. > # System must allow the user to move the active virtual host from one node to > another. This feature will help a user to restore a system to its BAU state > following an extraordinary situation. > # System must provide a user with a read-only view Queue when the underlying > store is in a replica state. This must provide at least queue name and queue > depth. This feature will allow a user to be able to see that replication is > indeed functioning. > # System must allow all HA operations to be allowed/denied according to rules > in the ACL. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5480) [linearstore] Recovery of store failure with "JERR_MAP_NOTFOUND: Key not found in map." error message
[
https://issues.apache.org/jira/browse/QPID-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892418#comment-13892418
]
ASF subversion and git services commented on QPID-5480:
---
Commit 1564877 from [~kpvdr] in branch 'qpid/trunk'
[ https://svn.apache.org/r1564877 ]
QPID-5480: Recovery of store failure with "JERR_MAP_NOTFOUND: Key not found in
map." error message. Fixed numerous recovery issues, particularly the handling
of files at the end of the file list during recovery when the last file is not
used or incompletely written.
> [linearstore] Recovery of store failure with "JERR_MAP_NOTFOUND: Key not
> found in map." error message
> -
>
> Key: QPID-5480
> URL: https://issues.apache.org/jira/browse/QPID-5480
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
> Attachments: QPID-5480.tar.gz
>
>
> While running a qpid-txtest soak test, a store was encountered which could
> not be recovered. The broker stopped with the following error message:
> {color:blue}{{\[Broker\] critical Unexpected error: Error commitjexception
> 0x0b01 wmgr::dequeue() threw JERR_MAP_NOTFOUND: Key not found in map.
> (rid=0x3e4f0)
> (/home/kpvdr/RedHat/qpid/cpp/src/qpid/linearstore/TxnCtxt.cpp:55)}}{color}
> The store in question is attached. An additional similar error message is
> seen during store shutdown.
> To reproduce:
> 1. Expand the store into a store directory. Note that the store directory is
> the one that contains the *{{qls}}* directory in the attached archive, and is
> supplied to the broker using the *{{--store-dir}}* parameter.
> 2. Start the broker so as to recover the store in the store directory:
> {color:blue}{{./qpidd --load-module linearstore.so -m no --auth no
> --default-flow-stop-threshold 0 --default-flow-resume-threshold 0
> --default-queue-limit 0 --store-dir --log-enable info+
> --truncate no}}{color}
> The store does not recover, and the broker exits with the above error message.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5361) Linearstore: No tests for linearstore functionality currently exist
[ https://issues.apache.org/jira/browse/QPID-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892468#comment-13892468 ] ASF subversion and git services commented on QPID-5361: --- Commit 1564893 from [~kpvdr] in branch 'qpid/trunk' [ https://svn.apache.org/r1564893 ] QPID-5361: Added a bash script which allows for transactional soak testing. > Linearstore: No tests for linearstore functionality currently exist > --- > > Key: QPID-5361 > URL: https://issues.apache.org/jira/browse/QPID-5361 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Reporter: Kim van der Riet >Assignee: Kim van der Riet > Labels: linearstore > > The linearstore currently has no tests. The following test categories are > needed: > 1. Generic client/server persistence tests which check for persistence from a > client point of view and should work for any store; > 2. Linearstore specific broker-side tests which check for specific responses > in the broker and on disk (eg, checking for file creation, Empty File Pool > file movement, etc.) > 3. Linearstore class/module tests > These should work in the current cmake/python frameworks if possible. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5048) [Java] Implement a Maven 3 build system
[ https://issues.apache.org/jira/browse/QPID-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893430#comment-13893430 ] ASF subversion and git services commented on QPID-5048: --- Commit 1565303 from [~gemmellr] in branch 'qpid/trunk' [ https://svn.apache.org/r1565303 ] QPID-5048: Maven POM refactoring - names, descriptions, dependencies & versions Patch supplied by Andrew MacBean > [Java] Implement a Maven 3 build system > > > Key: QPID-5048 > URL: https://issues.apache.org/jira/browse/QPID-5048 > Project: Qpid > Issue Type: Task > Components: Build Tools >Reporter: Rob Godfrey >Assignee: Robbie Gemmell > Attachments: > 0001-QPID-5048-Maven-POM-refactoring-names-descriptions-d.patch, > 0001-QPID-5048-Moved-slf4j-deps-to-test-utils-to-workarou.patch, > 0002-QPID-5048-Logging-dependency-and-configuration-tidy-.patch, > 0003-QPID-5048-logging-and-build-output-cleanup.patch > > > Implement a Maven build system which generates the same artefacts as the > current ant based build. > See: https://cwiki.apache.org/confluence/display/qpid/Java+Build+System -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5409) [Java Broker] Add support for multi-node HA cluster into BDB JE HA message store
[ https://issues.apache.org/jira/browse/QPID-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893439#comment-13893439 ] ASF subversion and git services commented on QPID-5409: --- Commit 1565308 from [~k-wall] in branch 'qpid/branches/java-broker-bdb-ha' [ https://svn.apache.org/r1565308 ] QPID-5409: Refactor BDB HA MBean to delegate the operations to the underlying node configured object. Unregister BDB HA MBean on virtual host deletion or replication node removal > [Java Broker] Add support for multi-node HA cluster into BDB JE HA message > store > > > Key: QPID-5409 > URL: https://issues.apache.org/jira/browse/QPID-5409 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Alex Rudyy > Fix For: 0.27 > > > The Java Qpid Broker currently supports only 2-nodes HA cluster with BDB JE > message store. This JIRA aims to extend the current HA functionality and add > support for multi-node HA cluster into BDB JE message store. > Here is the list of high-level requirements for the HA multi-node support: > # Only persistent messages are to be replicated. Transient messages will be > lost on failover. > # System must support clusters formed of an arbitrary number of nodes > # System must continue to support clusters formed of two nodes. Existing > public interfaces (notably JMX and existing virtualhost.xml format) must be > retained (though may be deprecated) to allow existing users a convenient > upgrade path. > # System must allow a user to completely configure a new node via the > web-management interface. > # System must allow a user to monitor the nodes of the cluster in order to > ascertain its health and perform day to day operations for via the > web-management interface. > ## expose statistics to allow the health of the cluster to be established > (exact details to be determined: could be low level like DbPing or something > more abstract) > # System must be amenable to monitoring by third-party tools. The Broker > should emit clear operational log messages as it transitions between states. > These messages will be targeted at the end-user. > # System must permit a mode of operation whereby the user (or other external > agent) determines which virtual host becomes active following a store > failover. In this mode of operation, following a failure, the store nodes in > the cluster will elect a new master and the replica node will still sync-up > with the new master node, but the system will not automatically mark the > virtual host corresponding to the master as active. The user will then > transfer the master to the desired location and make the virtualhost as > active, allowing business traffic to recommence. > # System must permit a mode of operation whereby the election of a store node > as master also causes the corresponding virtual host to become active. > # System must allow a user to influence a node's electability. These > features will allow a customer whose cluster spans primary/DR sites to keep > the active virtual hosts on the primary site in normal situations by > favouring failover within the primary site.Specifically, this will allow: > ## making a node unelectable - the node, even though it remains part of the > cluster, will never be elected as master) > ## making a node more likely to be elected master than other nodes - that > is, if two or more nodes have an equally up to date set of transactions, the > node with the highest priority will be elected master > ## node electability settings must survive restart, > ## node electability settings must be alterable at run-time. > # System must allow a user to alter quorum. This feature is required in > extraordinary situations where the system is required to continue to operate > despite the loss of sufficient nodes to mean there is no longer simple > majority. > # System must allow the user to move the active virtual host from one node to > another. This feature will help a user to restore a system to its BAU state > following an extraordinary situation. > # System must provide a user with a read-only view Queue when the underlying > store is in a replica state. This must provide at least queue name and queue > depth. This feature will allow a user to be able to see that replication is > indeed functioning. > # System must allow all HA operations to be allowed/denied according to rules > in the ACL. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5544) HA memory leak in backup broker after shutdown.
[ https://issues.apache.org/jira/browse/QPID-5544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893523#comment-13893523 ] ASF subversion and git services commented on QPID-5544: --- Commit 1565340 from [~aconway] in branch 'qpid/trunk' [ https://svn.apache.org/r1565340 ] QPID-5544: HA memory leak in backup broker after shutdown. The memory leaks were due to shared_ptr cycles between the QueueReplicator, Bridge and Link objects. This patch breaks the cycles using weak_ptrs in the appropriate places. > HA memory leak in backup broker after shutdown. > --- > > Key: QPID-5544 > URL: https://issues.apache.org/jira/browse/QPID-5544 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Affects Versions: 0.26 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.27 > > > Valgrind shows memory leaks in backup broker after taking these steps: > 1. Start primary broker > 2. Create a queue > 3. Start backup broker with valgrind > 4. Wait to see "Joining established cluster" message from backup > 5. Shut down backup broker > Valgrind will reprort memory leaks. > For more detail see: https://bugzilla.redhat.com/show_bug.cgi?id=1004411 -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5409) [Java Broker] Add support for multi-node HA cluster into BDB JE HA message store
[ https://issues.apache.org/jira/browse/QPID-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893565#comment-13893565 ] ASF subversion and git services commented on QPID-5409: --- Commit 1565370 from [~k-wall] in branch 'qpid/branches/java-broker-bdb-ha' [ https://svn.apache.org/r1565370 ] QPID-5409: Environment thread is now used to perform set designated primary/set electable group override/set node prioriy > [Java Broker] Add support for multi-node HA cluster into BDB JE HA message > store > > > Key: QPID-5409 > URL: https://issues.apache.org/jira/browse/QPID-5409 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Alex Rudyy > Fix For: 0.27 > > > The Java Qpid Broker currently supports only 2-nodes HA cluster with BDB JE > message store. This JIRA aims to extend the current HA functionality and add > support for multi-node HA cluster into BDB JE message store. > Here is the list of high-level requirements for the HA multi-node support: > # Only persistent messages are to be replicated. Transient messages will be > lost on failover. > # System must support clusters formed of an arbitrary number of nodes > # System must continue to support clusters formed of two nodes. Existing > public interfaces (notably JMX and existing virtualhost.xml format) must be > retained (though may be deprecated) to allow existing users a convenient > upgrade path. > # System must allow a user to completely configure a new node via the > web-management interface. > # System must allow a user to monitor the nodes of the cluster in order to > ascertain its health and perform day to day operations for via the > web-management interface. > ## expose statistics to allow the health of the cluster to be established > (exact details to be determined: could be low level like DbPing or something > more abstract) > # System must be amenable to monitoring by third-party tools. The Broker > should emit clear operational log messages as it transitions between states. > These messages will be targeted at the end-user. > # System must permit a mode of operation whereby the user (or other external > agent) determines which virtual host becomes active following a store > failover. In this mode of operation, following a failure, the store nodes in > the cluster will elect a new master and the replica node will still sync-up > with the new master node, but the system will not automatically mark the > virtual host corresponding to the master as active. The user will then > transfer the master to the desired location and make the virtualhost as > active, allowing business traffic to recommence. > # System must permit a mode of operation whereby the election of a store node > as master also causes the corresponding virtual host to become active. > # System must allow a user to influence a node's electability. These > features will allow a customer whose cluster spans primary/DR sites to keep > the active virtual hosts on the primary site in normal situations by > favouring failover within the primary site.Specifically, this will allow: > ## making a node unelectable - the node, even though it remains part of the > cluster, will never be elected as master) > ## making a node more likely to be elected master than other nodes - that > is, if two or more nodes have an equally up to date set of transactions, the > node with the highest priority will be elected master > ## node electability settings must survive restart, > ## node electability settings must be alterable at run-time. > # System must allow a user to alter quorum. This feature is required in > extraordinary situations where the system is required to continue to operate > despite the loss of sufficient nodes to mean there is no longer simple > majority. > # System must allow the user to move the active virtual host from one node to > another. This feature will help a user to restore a system to its BAU state > following an extraordinary situation. > # System must provide a user with a read-only view Queue when the underlying > store is in a replica state. This must provide at least queue name and queue > depth. This feature will allow a user to be able to see that replication is > indeed functioning. > # System must allow all HA operations to be allowed/denied according to rules > in the ACL. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5409) [Java Broker] Add support for multi-node HA cluster into BDB JE HA message store
[ https://issues.apache.org/jira/browse/QPID-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893564#comment-13893564 ] ASF subversion and git services commented on QPID-5409: --- Commit 1565369 from [~k-wall] in branch 'qpid/branches/java-broker-bdb-ha' [ https://svn.apache.org/r1565369 ] QPID-5409: Fix LocalReplicationNode#setAttribute, ignore exception thrown by ReplicatedEnvironmentFacade in LocalReplicationNode#getAttribute > [Java Broker] Add support for multi-node HA cluster into BDB JE HA message > store > > > Key: QPID-5409 > URL: https://issues.apache.org/jira/browse/QPID-5409 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Alex Rudyy > Fix For: 0.27 > > > The Java Qpid Broker currently supports only 2-nodes HA cluster with BDB JE > message store. This JIRA aims to extend the current HA functionality and add > support for multi-node HA cluster into BDB JE message store. > Here is the list of high-level requirements for the HA multi-node support: > # Only persistent messages are to be replicated. Transient messages will be > lost on failover. > # System must support clusters formed of an arbitrary number of nodes > # System must continue to support clusters formed of two nodes. Existing > public interfaces (notably JMX and existing virtualhost.xml format) must be > retained (though may be deprecated) to allow existing users a convenient > upgrade path. > # System must allow a user to completely configure a new node via the > web-management interface. > # System must allow a user to monitor the nodes of the cluster in order to > ascertain its health and perform day to day operations for via the > web-management interface. > ## expose statistics to allow the health of the cluster to be established > (exact details to be determined: could be low level like DbPing or something > more abstract) > # System must be amenable to monitoring by third-party tools. The Broker > should emit clear operational log messages as it transitions between states. > These messages will be targeted at the end-user. > # System must permit a mode of operation whereby the user (or other external > agent) determines which virtual host becomes active following a store > failover. In this mode of operation, following a failure, the store nodes in > the cluster will elect a new master and the replica node will still sync-up > with the new master node, but the system will not automatically mark the > virtual host corresponding to the master as active. The user will then > transfer the master to the desired location and make the virtualhost as > active, allowing business traffic to recommence. > # System must permit a mode of operation whereby the election of a store node > as master also causes the corresponding virtual host to become active. > # System must allow a user to influence a node's electability. These > features will allow a customer whose cluster spans primary/DR sites to keep > the active virtual hosts on the primary site in normal situations by > favouring failover within the primary site.Specifically, this will allow: > ## making a node unelectable - the node, even though it remains part of the > cluster, will never be elected as master) > ## making a node more likely to be elected master than other nodes - that > is, if two or more nodes have an equally up to date set of transactions, the > node with the highest priority will be elected master > ## node electability settings must survive restart, > ## node electability settings must be alterable at run-time. > # System must allow a user to alter quorum. This feature is required in > extraordinary situations where the system is required to continue to operate > despite the loss of sufficient nodes to mean there is no longer simple > majority. > # System must allow the user to move the active virtual host from one node to > another. This feature will help a user to restore a system to its BAU state > following an extraordinary situation. > # System must provide a user with a read-only view Queue when the underlying > store is in a replica state. This must provide at least queue name and queue > depth. This feature will allow a user to be able to see that replication is > indeed functioning. > # System must allow all HA operations to be allowed/denied according to rules > in the ACL. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5524) Missing ssl-cert-name connection argument processing in AMQP 1.0. cpp client
[ https://issues.apache.org/jira/browse/QPID-5524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893597#comment-13893597 ] ASF subversion and git services commented on QPID-5524: --- Commit 1565376 from cliffjan...@apache.org in branch 'qpid/trunk' [ https://svn.apache.org/r1565376 ] QPID-5524: ssl-cert-name connection argument processing in AMQP 1.0. cpp client > Missing ssl-cert-name connection argument processing in AMQP 1.0. cpp client > > > Key: QPID-5524 > URL: https://issues.apache.org/jira/browse/QPID-5524 > Project: Qpid > Issue Type: Bug > Components: C++ Client >Affects Versions: 0.26 > Environment: Posix SSL processing >Reporter: Cliff Jansen >Assignee: Cliff Jansen > Fix For: 0.27 > > > The ssl-cert-name connection option should work, including overriding the > value set in the QPID_SSL_CERT_NAME environment variable for AMQP 1.0 > connections. This would match the AMQP 0-10 behavior. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-24) Add ssl option to system_tests_two_routers.py test
[ https://issues.apache.org/jira/browse/DISPATCH-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893655#comment-13893655 ] ASF subversion and git services commented on DISPATCH-24: - Commit 1565393 from [~tedross] in branch 'dispatch/trunk' [ https://svn.apache.org/r1565393 ] DISPATCH-24 - Added tests with SSL interconnect Applied a patch submitted by Irina Boverman > Add ssl option to system_tests_two_routers.py test > -- > > Key: DISPATCH-24 > URL: https://issues.apache.org/jira/browse/DISPATCH-24 > Project: Qpid Dispatch > Issue Type: Test >Affects Versions: 0.1 >Reporter: Irina Boverman >Assignee: Ted Ross >Priority: Minor > Fix For: 0.2 > > Attachments: patch-DISPATCH-24.txt > > > Add an option to configure SSL authentication for this test. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-25) Man page updates for 0.2
[ https://issues.apache.org/jira/browse/DISPATCH-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893904#comment-13893904 ] ASF subversion and git services commented on DISPATCH-25: - Commit 1565463 from [~tedross] in branch 'dispatch/trunk' [ https://svn.apache.org/r1565463 ] DISPATCH-25 - Updated the man page for the configuration file. > Man page updates for 0.2 > > > Key: DISPATCH-25 > URL: https://issues.apache.org/jira/browse/DISPATCH-25 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Documentation >Affects Versions: 0.1 >Reporter: Ted Ross > Fix For: 0.2 > > > This issue tracks updates to the man pages for Dispatch. > There are updates to the configuration file that will need to be reflected in > the man page. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-25) Man page updates for 0.2
[ https://issues.apache.org/jira/browse/DISPATCH-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893920#comment-13893920 ] ASF subversion and git services commented on DISPATCH-25: - Commit 1565467 from [~tedross] in branch 'dispatch/trunk' [ https://svn.apache.org/r1565467 ] DISPATCH-25 - Fixed a bug found when writing the man pages :) > Man page updates for 0.2 > > > Key: DISPATCH-25 > URL: https://issues.apache.org/jira/browse/DISPATCH-25 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Documentation >Affects Versions: 0.1 >Reporter: Ted Ross > Fix For: 0.2 > > > This issue tracks updates to the man pages for Dispatch. > There are updates to the configuration file that will need to be reflected in > the man page. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5499) Ruby/Perl bindings fail to compile with -Werror=format-security
[ https://issues.apache.org/jira/browse/QPID-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894529#comment-13894529 ] ASF subversion and git services commented on QPID-5499: --- Commit 1565651 from [~mcpierce] in branch 'qpid/trunk' [ https://svn.apache.org/r1565651 ] QPID-5499: Fix Ruby/Perl bindings when built with -Werror=format-security Changed the swig descriptors so that they use a constant format string. > Ruby/Perl bindings fail to compile with -Werror=format-security > --- > > Key: QPID-5499 > URL: https://issues.apache.org/jira/browse/QPID-5499 > Project: Qpid > Issue Type: Bug > Components: Perl Client, Ruby Client >Affects Versions: 0.24 >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce > Fix For: 0.27 > > > With Fedora 21 the option -Werror=format-security has been enabled. As a > result, the code generated by Swig for the Ruby bindings fail to compile. The > culprit code is in ruby.i: > rb_raise(merror, mex.what()); > Which is using a method from the printf family but is not using a static > format string. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-27) Intermittent test failures on RHEL platforms
[
https://issues.apache.org/jira/browse/DISPATCH-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894605#comment-13894605
]
ASF subversion and git services commented on DISPATCH-27:
-
Commit 1565670 from [~tedross] in branch 'dispatch/trunk'
[ https://svn.apache.org/r1565670 ]
DISPATCH-27 - Make the wait-for-stable process more thorough
> Intermittent test failures on RHEL platforms
>
>
> Key: DISPATCH-27
> URL: https://issues.apache.org/jira/browse/DISPATCH-27
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 0.1
>Reporter: Ted Ross
>
> =
> ERROR: test_09_management (__main__.RouterTest)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/workspace/qpid-dispatch-trunk/label/master/install/lib/qpid-dispatch/tests/system_tests_two_routers.py",
> line 556, in test_09_management
> M.recv()
> File "/usr/lib64/python2.6/site-packages/proton.py", line 534, in recv
> self._check(pn_messenger_recv(self._mng, n))
> File "/usr/lib64/python2.6/site-packages/proton.py", line 267, in _check
> raise exc("[%s]: %s" % (err,
> pn_error_text(pn_messenger_error(self._mng
> Timeout: [-7]: None
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5547) [Java Broker] When handling rejects in 0-8/9/9-1 treat queues with no max delivery set as having infinite max delivery, rather than max delivery of 1
[ https://issues.apache.org/jira/browse/QPID-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894660#comment-13894660 ] ASF subversion and git services commented on QPID-5547: --- Commit 1565701 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1565701 ] QPID-5547 : [Java Broker] When handling rejects in 0-8/9/9-1 treat queues with no max delivery set as having infinite max delivery, rather than max delivery of 1 > [Java Broker] When handling rejects in 0-8/9/9-1 treat queues with no max > delivery set as having infinite max delivery, rather than max delivery of 1 > - > > Key: QPID-5547 > URL: https://issues.apache.org/jira/browse/QPID-5547 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > > BasicRejectHandler assumes that when handling a reject, if a queue does not > have a max delivery value set, then it does not want to redeliver. From a > user point of view this is counter intuitive - the messages should be > requeued and not DLQd -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13894712#comment-13894712 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1565719 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1565719 ] QPIDJMS-9: fix constants and method names relating to the ulong id conversion > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13894709#comment-13894709 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1565718 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1565718 ] QPIDJMS-9: consolidate the correlationId and messageId setters/getters, tweak id conversion for ulong > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5504) [Java Broker] Allow other routing/storage node types than Queues and Exchanges
[ https://issues.apache.org/jira/browse/QPID-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894723#comment-13894723 ] ASF subversion and git services commented on QPID-5504: --- Commit 1565726 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1565726 ] QPID-5504 : Refactoring to allow for nodes other than queues to be subscribed from, and nodes other than exchanges to be sent to (merged from separate branch) > [Java Broker] Allow other routing/storage node types than Queues and Exchanges > -- > > Key: QPID-5504 > URL: https://issues.apache.org/jira/browse/QPID-5504 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-27) Intermittent test failures on RHEL platforms
[
https://issues.apache.org/jira/browse/DISPATCH-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894929#comment-13894929
]
ASF subversion and git services commented on DISPATCH-27:
-
Commit 1565773 from [~tedross] in branch 'dispatch/trunk'
[ https://svn.apache.org/r1565773 ]
DISPATCH-27 - Trivial label change
> Intermittent test failures on RHEL platforms
>
>
> Key: DISPATCH-27
> URL: https://issues.apache.org/jira/browse/DISPATCH-27
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 0.1
>Reporter: Ted Ross
>
> =
> ERROR: test_09_management (__main__.RouterTest)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/workspace/qpid-dispatch-trunk/label/master/install/lib/qpid-dispatch/tests/system_tests_two_routers.py",
> line 556, in test_09_management
> M.recv()
> File "/usr/lib64/python2.6/site-packages/proton.py", line 534, in recv
> self._check(pn_messenger_recv(self._mng, n))
> File "/usr/lib64/python2.6/site-packages/proton.py", line 267, in _check
> raise exc("[%s]: %s" % (err,
> pn_error_text(pn_messenger_error(self._mng
> Timeout: [-7]: None
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-27) Intermittent test failures on RHEL platforms
[
https://issues.apache.org/jira/browse/DISPATCH-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894921#comment-13894921
]
ASF subversion and git services commented on DISPATCH-27:
-
Commit 1565769 from [~tedross] in branch 'dispatch/trunk'
[ https://svn.apache.org/r1565769 ]
DISPATCH-27 - Updates to the system test framework
> Intermittent test failures on RHEL platforms
>
>
> Key: DISPATCH-27
> URL: https://issues.apache.org/jira/browse/DISPATCH-27
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 0.1
>Reporter: Ted Ross
>
> =
> ERROR: test_09_management (__main__.RouterTest)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/workspace/qpid-dispatch-trunk/label/master/install/lib/qpid-dispatch/tests/system_tests_two_routers.py",
> line 556, in test_09_management
> M.recv()
> File "/usr/lib64/python2.6/site-packages/proton.py", line 534, in recv
> self._check(pn_messenger_recv(self._mng, n))
> File "/usr/lib64/python2.6/site-packages/proton.py", line 267, in _check
> raise exc("[%s]: %s" % (err,
> pn_error_text(pn_messenger_error(self._mng
> Timeout: [-7]: None
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-28) Increase the length of the random portion of temporary addresses.
[ https://issues.apache.org/jira/browse/DISPATCH-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894999#comment-13894999 ] ASF subversion and git services commented on DISPATCH-28: - Commit 1565798 from [~tedross] in branch 'dispatch/trunk' [ https://svn.apache.org/r1565798 ] DISPATCH-28 - Increased the size of the random portion of temporary addresses. > Increase the length of the random portion of temporary addresses. > - > > Key: DISPATCH-28 > URL: https://issues.apache.org/jira/browse/DISPATCH-28 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Affects Versions: 0.1 >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Minor > Fix For: 0.2 > > > The random portion of temporary addresses is based on 32 bits of random > value. Increase it to use 60 bits (10 base-64 symbols). -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5548) C++ Messaging API does not specify the connection Connection URL format
[
https://issues.apache.org/jira/browse/QPID-5548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13895044#comment-13895044
]
ASF subversion and git services commented on QPID-5548:
---
Commit 1565819 from c...@apache.org in branch 'qpid/trunk'
[ https://svn.apache.org/r1565819 ]
QPID-5548: C++ Messaging API does not specify the connection Connection URL
format
Add Connection section and Connection URLs subsection.
Demote Connection Options to be a subsection of Connection.
> C++ Messaging API does not specify the connection Connection URL format
> ---
>
> Key: QPID-5548
> URL: https://issues.apache.org/jira/browse/QPID-5548
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client, Documentation
>Affects Versions: 0.27
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>
> The Programming In Apache Qpid documentation never discusses the format of
> the Connection URL string, the only required argument for constructing a
> Messaging Connection. The URL is specified by AMPQ 0.10:
> {noformat}
> amqp_url = "amqp:" prot_addr_list
> prot_addr_list = [prot_addr ","]* prot_addr
> prot_addr = tcp_prot_addr | tls_prot_addr
> tcp_prot_addr = tcp_id tcp_addr
> tcp_id = "tcp:" | ""
> tcp_addr = [host [":" port] ]
> host = http://www.ietf.org/rfc/rfc3986.txt>
> port = number
> {noformat}
> The C++ Messaging connection string is not the same as the JMS Connection
> http://qpid.apache.org/releases/qpid-0.24/programming/book/QpidJNDI.html#section-jms-connection-url
> This issue tracks adding a few lines to the documentation describing the
> connection format.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5504) [Java Broker] Allow other routing/storage node types than Queues and Exchanges
[ https://issues.apache.org/jira/browse/QPID-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896122#comment-13896122 ] ASF subversion and git services commented on QPID-5504: --- Commit 1566479 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1566479 ] QPID-5504 : Fix bug in routeToAlternate which left queue entries in database if there were no alternates to route to > [Java Broker] Allow other routing/storage node types than Queues and Exchanges > -- > > Key: QPID-5504 > URL: https://issues.apache.org/jira/browse/QPID-5504 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.27 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-12) add configuration for jacoco to check coverage
[ https://issues.apache.org/jira/browse/QPIDJMS-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896152#comment-13896152 ] ASF subversion and git services commented on QPIDJMS-12: Commit 1566488 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1566488 ] QPIDJMS-12: add configuration for jacoco to check coverage > add configuration for jacoco to check coverage > -- > > Key: QPIDJMS-12 > URL: https://issues.apache.org/jira/browse/QPIDJMS-12 > Project: Qpid JMS > Issue Type: Improvement >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > add configuration for jacoco to check coverage -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5504) [Java Broker] Allow other routing/storage node types than Queues and Exchanges
[ https://issues.apache.org/jira/browse/QPID-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896333#comment-13896333 ] ASF subversion and git services commented on QPID-5504: --- Commit 1566531 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1566531 ] QPID-5504 : fixed implementation of 0-8 GET when using NoAck > [Java Broker] Allow other routing/storage node types than Queues and Exchanges > -- > > Key: QPID-5504 > URL: https://issues.apache.org/jira/browse/QPID-5504 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.27 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5504) [Java Broker] Allow other routing/storage node types than Queues and Exchanges
[ https://issues.apache.org/jira/browse/QPID-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896342#comment-13896342 ] ASF subversion and git services commented on QPID-5504: --- Commit 1566535 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1566535 ] QPID-5504 : Re-enable the use of no-local on consumers to queues in 0-8 protocol > [Java Broker] Allow other routing/storage node types than Queues and Exchanges > -- > > Key: QPID-5504 > URL: https://issues.apache.org/jira/browse/QPID-5504 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.27 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5504) [Java Broker] Allow other routing/storage node types than Queues and Exchanges
[ https://issues.apache.org/jira/browse/QPID-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896357#comment-13896357 ] ASF subversion and git services commented on QPID-5504: --- Commit 1566543 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1566543 ] QPID-5504 : allow for case where consumer target is closed before consumer is attached > [Java Broker] Allow other routing/storage node types than Queues and Exchanges > -- > > Key: QPID-5504 > URL: https://issues.apache.org/jira/browse/QPID-5504 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.27 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5531) [C++ broker] Set timeout for every DTX transaction
[ https://issues.apache.org/jira/browse/QPID-5531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896394#comment-13896394 ] ASF subversion and git services commented on QPID-5531: --- Commit 1566579 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1566579 ] QPID-5531 : Adding an exclude to the Java Python test ignore list for the test which was changed without the feature also being changed in the Java Broker > [C++ broker] Set timeout for every DTX transaction > -- > > Key: QPID-5531 > URL: https://issues.apache.org/jira/browse/QPID-5531 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.24 >Reporter: Pavel Moravec >Assignee: Pavel Moravec >Priority: Minor > Labels: patch > Fix For: 0.27 > > Attachments: QPID-5531.patch, qpid-txtest_modified.patch > > > Description of problem: > If an external Transaction Manager (TM) prepares a DTX transaction but > forgets, due to any reason, to commit or abort it, tpl journal has an > orphaned enqueue record forever (that in legacystore causes enqueue capacity > threshold exception after a while, preventing _any_ transaction to > commit/abort). > To prevent such orphaned XID entries in tpl, every incoming DTX transaction > should have a default timeout set (while dtx.set-timeout AMQP 0-10 primitive > changes it). > The timeout should be broker-wide parameter configurable via > --dtx-default-timeout option. > Version-Release number of selected component (if applicable): > any (incl upstream 0.26) > How reproducible: > 100% > Steps to Reproduce: > 1. Mimic an external TM that prepares a DTX but never commits or aborts it - > use e.g. _modified_ qpid-txtest (patch attached): > qpid-txtest --queues=1 --total-messages=1 --dtx=1 --dtx-commit=no > 2. /usr/libexec/qpid/store_chk /var/lib/qpidd/rhm/tpl -b tpl > Actual results: > tpl journal keeps the unfinished transaction forever > Expected results: > sleeping for dtx-default-timeout, the transaction should be gone -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13896477#comment-13896477 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1566611 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1566611 ] QPIDJMS-9: work on binary message-id/correlation-id handling, etc > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5504) [Java Broker] Allow other routing/storage node types than Queues and Exchanges
[ https://issues.apache.org/jira/browse/QPID-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897704#comment-13897704 ] ASF subversion and git services commented on QPID-5504: --- Commit 1567026 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1567026 ] QPID-5504 : refactring of queues, and introduce management node and amqp-management module > [Java Broker] Allow other routing/storage node types than Queues and Exchanges > -- > > Key: QPID-5504 > URL: https://issues.apache.org/jira/browse/QPID-5504 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.27 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5504) [Java Broker] Allow other routing/storage node types than Queues and Exchanges
[ https://issues.apache.org/jira/browse/QPID-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897761#comment-13897761 ] ASF subversion and git services commented on QPID-5504: --- Commit 1567063 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1567063 ] QPID-5504 : fix for different interpretation of generics in 1.6 > [Java Broker] Allow other routing/storage node types than Queues and Exchanges > -- > > Key: QPID-5504 > URL: https://issues.apache.org/jira/browse/QPID-5504 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.27 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5504) [Java Broker] Allow other routing/storage node types than Queues and Exchanges
[ https://issues.apache.org/jira/browse/QPID-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897785#comment-13897785 ] ASF subversion and git services commented on QPID-5504: --- Commit 1567077 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1567077 ] QPID-5504 : another fix for generics, this time working differently between OpenJDK 1.6u27 and Oracle JDK 6u45 > [Java Broker] Allow other routing/storage node types than Queues and Exchanges > -- > > Key: QPID-5504 > URL: https://issues.apache.org/jira/browse/QPID-5504 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.27 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5546) Perl bindings use encode/decode instead of getContentObject/setContentObject
[ https://issues.apache.org/jira/browse/QPID-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897907#comment-13897907 ] ASF subversion and git services commented on QPID-5546: --- Commit 1567173 from [~mcpierce] in branch 'qpid/trunk' [ https://svn.apache.org/r1567173 ] QPID-5546: Expose the get_content_object method in Perl. Updated the spout and drain examples to use this rather than encode/decode to retrieve the content of a message. > Perl bindings use encode/decode instead of getContentObject/setContentObject > > > Key: QPID-5546 > URL: https://issues.apache.org/jira/browse/QPID-5546 > Project: Qpid > Issue Type: Bug > Components: Perl Client >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce > > perl qpid client receiving AMQP 1.0 map/list message causes what(): > illegal-argument: Not enough data for list, expected 3506438144 bytes but > only 254 available > (/builddir/build/BUILD/qpid-0.22/cpp/src/qpid/framing/List.cpp:59) > This defect is similar to bug 1021974. In c++ Vienna client is recommended to > use msg.getContenObject() instead of decode(). Current perl client still uses > decode() (Message.pm) which causes problems. > I propose to fix Message.pm to use getContentObject()/setContentObject() > instead of encode()/decode() in msg->get_content()/set_content(). > Perl's Message implementation do not have > getContentObject()/setContentObject() methods which differentiate from c++ > and I also propose to review whether to add those as aliases to > get_content/set_content(). -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13898079#comment-13898079 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1567240 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1567240 ] QPIDJMS-9: remove stale comments > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13898479#comment-13898479 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1567451 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1567451 ] QPIDJMS-9: implement get/setJMSCorrelationIDAsBytes > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5409) [Java Broker] Add support for multi-node HA cluster into BDB JE HA message store
[ https://issues.apache.org/jira/browse/QPID-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898947#comment-13898947 ] ASF subversion and git services commented on QPID-5409: --- Commit 1567576 from oru...@apache.org in branch 'qpid/branches/java-broker-bdb-ha' [ https://svn.apache.org/r1567576 ] QPID-5409: Save virtual host state in the virtual host configuration store. Restore VH state from the store. > [Java Broker] Add support for multi-node HA cluster into BDB JE HA message > store > > > Key: QPID-5409 > URL: https://issues.apache.org/jira/browse/QPID-5409 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Alex Rudyy > Fix For: 0.27 > > > The Java Qpid Broker currently supports only 2-nodes HA cluster with BDB JE > message store. This JIRA aims to extend the current HA functionality and add > support for multi-node HA cluster into BDB JE message store. > Here is the list of high-level requirements for the HA multi-node support: > # Only persistent messages are to be replicated. Transient messages will be > lost on failover. > # System must support clusters formed of an arbitrary number of nodes > # System must continue to support clusters formed of two nodes. Existing > public interfaces (notably JMX and existing virtualhost.xml format) must be > retained (though may be deprecated) to allow existing users a convenient > upgrade path. > # System must allow a user to completely configure a new node via the > web-management interface. > # System must allow a user to monitor the nodes of the cluster in order to > ascertain its health and perform day to day operations for via the > web-management interface. > ## expose statistics to allow the health of the cluster to be established > (exact details to be determined: could be low level like DbPing or something > more abstract) > # System must be amenable to monitoring by third-party tools. The Broker > should emit clear operational log messages as it transitions between states. > These messages will be targeted at the end-user. > # System must permit a mode of operation whereby the user (or other external > agent) determines which virtual host becomes active following a store > failover. In this mode of operation, following a failure, the store nodes in > the cluster will elect a new master and the replica node will still sync-up > with the new master node, but the system will not automatically mark the > virtual host corresponding to the master as active. The user will then > transfer the master to the desired location and make the virtualhost as > active, allowing business traffic to recommence. > # System must permit a mode of operation whereby the election of a store node > as master also causes the corresponding virtual host to become active. > # System must allow a user to influence a node's electability. These > features will allow a customer whose cluster spans primary/DR sites to keep > the active virtual hosts on the primary site in normal situations by > favouring failover within the primary site.Specifically, this will allow: > ## making a node unelectable - the node, even though it remains part of the > cluster, will never be elected as master) > ## making a node more likely to be elected master than other nodes - that > is, if two or more nodes have an equally up to date set of transactions, the > node with the highest priority will be elected master > ## node electability settings must survive restart, > ## node electability settings must be alterable at run-time. > # System must allow a user to alter quorum. This feature is required in > extraordinary situations where the system is required to continue to operate > despite the loss of sufficient nodes to mean there is no longer simple > majority. > # System must allow the user to move the active virtual host from one node to > another. This feature will help a user to restore a system to its BAU state > following an extraordinary situation. > # System must provide a user with a read-only view Queue when the underlying > store is in a replica state. This must provide at least queue name and queue > depth. This feature will allow a user to be able to see that replication is > indeed functioning. > # System must allow all HA operations to be allowed/denied according to rules > in the ACL. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13899173#comment-13899173 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1567642 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1567642 ] QPIDJMS-9: update exception behaviour for setJMSCorrelationID, tweak javadoc on helper class to more closely cover its usage > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13899205#comment-13899205 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1567657 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1567657 ] QPIDJMS-9: implement get/setJMSType methods > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13899287#comment-13899287 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1567685 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1567685 ] QPIDJMS-9: implement read-only mode for properties of received messages > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13899286#comment-13899286 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1567682 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1567682 ] QPIDJMS-9: add some missing testing around handling of missing properties > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13900257#comment-13900257 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1567898 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1567898 ] QPIDJMS-9: implement validation that property names meet the identifier requirements > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5409) [Java Broker] Add support for multi-node HA cluster into BDB JE HA message store
[ https://issues.apache.org/jira/browse/QPID-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900381#comment-13900381 ] ASF subversion and git services commented on QPID-5409: --- Commit 1567942 from oru...@apache.org in branch 'qpid/branches/java-broker-bdb-ha' [ https://svn.apache.org/r1567942 ] QPID-5409: Add basic state management on local replication node and add ability to set the node state > [Java Broker] Add support for multi-node HA cluster into BDB JE HA message > store > > > Key: QPID-5409 > URL: https://issues.apache.org/jira/browse/QPID-5409 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Alex Rudyy > Fix For: 0.27 > > > The Java Qpid Broker currently supports only 2-nodes HA cluster with BDB JE > message store. This JIRA aims to extend the current HA functionality and add > support for multi-node HA cluster into BDB JE message store. > Here is the list of high-level requirements for the HA multi-node support: > # Only persistent messages are to be replicated. Transient messages will be > lost on failover. > # System must support clusters formed of an arbitrary number of nodes > # System must continue to support clusters formed of two nodes. Existing > public interfaces (notably JMX and existing virtualhost.xml format) must be > retained (though may be deprecated) to allow existing users a convenient > upgrade path. > # System must allow a user to completely configure a new node via the > web-management interface. > # System must allow a user to monitor the nodes of the cluster in order to > ascertain its health and perform day to day operations for via the > web-management interface. > ## expose statistics to allow the health of the cluster to be established > (exact details to be determined: could be low level like DbPing or something > more abstract) > # System must be amenable to monitoring by third-party tools. The Broker > should emit clear operational log messages as it transitions between states. > These messages will be targeted at the end-user. > # System must permit a mode of operation whereby the user (or other external > agent) determines which virtual host becomes active following a store > failover. In this mode of operation, following a failure, the store nodes in > the cluster will elect a new master and the replica node will still sync-up > with the new master node, but the system will not automatically mark the > virtual host corresponding to the master as active. The user will then > transfer the master to the desired location and make the virtualhost as > active, allowing business traffic to recommence. > # System must permit a mode of operation whereby the election of a store node > as master also causes the corresponding virtual host to become active. > # System must allow a user to influence a node's electability. These > features will allow a customer whose cluster spans primary/DR sites to keep > the active virtual hosts on the primary site in normal situations by > favouring failover within the primary site.Specifically, this will allow: > ## making a node unelectable - the node, even though it remains part of the > cluster, will never be elected as master) > ## making a node more likely to be elected master than other nodes - that > is, if two or more nodes have an equally up to date set of transactions, the > node with the highest priority will be elected master > ## node electability settings must survive restart, > ## node electability settings must be alterable at run-time. > # System must allow a user to alter quorum. This feature is required in > extraordinary situations where the system is required to continue to operate > despite the loss of sufficient nodes to mean there is no longer simple > majority. > # System must allow the user to move the active virtual host from one node to > another. This feature will help a user to restore a system to its BAU state > following an extraordinary situation. > # System must provide a user with a read-only view Queue when the underlying > store is in a replica state. This must provide at least queue name and queue > depth. This feature will allow a user to be able to see that replication is > indeed functioning. > # System must allow all HA operations to be allowed/denied according to rules > in the ACL. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5551) [Java Broker] Improve use of exceptions throughout the broker
[ https://issues.apache.org/jira/browse/QPID-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900474#comment-13900474 ] ASF subversion and git services commented on QPID-5551: --- Commit 1567971 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1567971 ] QPID-5551 : Remove redundant throws AMQException clauses > [Java Broker] Improve use of exceptions throughout the broker > - > > Key: QPID-5551 > URL: https://issues.apache.org/jira/browse/QPID-5551 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey >Priority: Minor > > Currently lots of methods throw AMQException which was original intended to > represent connection and channel closure reasons. > Now these are actually only generated from the 0-8 protocol plugin, however > the same base class is used for security exceptions (AMQSecurityException) > and also for errors encountered in the store (via AMQInternalException). > Where there is no obvious way to deal with an exception it is either being > directly rethrown, or wrapped in a runtime exception or similar. > We should remove cases of methods throwing AMQException when there is no path > through which they can actually throw that exception. We should then change > the use of exceptions in the broker to differentiate between those which we > expect to handle in some way (like security exceptions) versus those which > will only be handled in a coarse manner (exceptions that can only result in > the closure of a connection, or even of the entire virtual host or broker). > For the latter two cases I propose we introduce new RuntimeException classes > for ConnectionScopedRuntimeException, VirtualHostScopedRuntimeException and > BrokerScopedRuntimeException. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13900562#comment-13900562 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1567989 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1567989 ] QPIDJMS-9: work on support for JMSXUserID > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5551) [Java Broker] Improve use of exceptions throughout the broker
[ https://issues.apache.org/jira/browse/QPID-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900646#comment-13900646 ] ASF subversion and git services commented on QPID-5551: --- Commit 1568015 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1568015 ] QPID-5551 : replace AMQSecurityException with QpidSecurityException in the broker > [Java Broker] Improve use of exceptions throughout the broker > - > > Key: QPID-5551 > URL: https://issues.apache.org/jira/browse/QPID-5551 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey >Priority: Minor > > Currently lots of methods throw AMQException which was original intended to > represent connection and channel closure reasons. > Now these are actually only generated from the 0-8 protocol plugin, however > the same base class is used for security exceptions (AMQSecurityException) > and also for errors encountered in the store (via AMQInternalException). > Where there is no obvious way to deal with an exception it is either being > directly rethrown, or wrapped in a runtime exception or similar. > We should remove cases of methods throwing AMQException when there is no path > through which they can actually throw that exception. We should then change > the use of exceptions in the broker to differentiate between those which we > expect to handle in some way (like security exceptions) versus those which > will only be handled in a coarse manner (exceptions that can only result in > the closure of a connection, or even of the entire virtual host or broker). > For the latter two cases I propose we introduce new RuntimeException classes > for ConnectionScopedRuntimeException, VirtualHostScopedRuntimeException and > BrokerScopedRuntimeException. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5551) [Java Broker] Improve use of exceptions throughout the broker
[ https://issues.apache.org/jira/browse/QPID-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901304#comment-13901304 ] ASF subversion and git services commented on QPID-5551: --- Commit 1568235 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1568235 ] QPID-5551 : Remove uses of AMQException, add ServerScopedRuntimeException and ConnectionScopedRuntimeException > [Java Broker] Improve use of exceptions throughout the broker > - > > Key: QPID-5551 > URL: https://issues.apache.org/jira/browse/QPID-5551 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey >Priority: Minor > > Currently lots of methods throw AMQException which was original intended to > represent connection and channel closure reasons. > Now these are actually only generated from the 0-8 protocol plugin, however > the same base class is used for security exceptions (AMQSecurityException) > and also for errors encountered in the store (via AMQInternalException). > Where there is no obvious way to deal with an exception it is either being > directly rethrown, or wrapped in a runtime exception or similar. > We should remove cases of methods throwing AMQException when there is no path > through which they can actually throw that exception. We should then change > the use of exceptions in the broker to differentiate between those which we > expect to handle in some way (like security exceptions) versus those which > will only be handled in a coarse manner (exceptions that can only result in > the closure of a connection, or even of the entire virtual host or broker). > For the latter two cases I propose we introduce new RuntimeException classes > for ConnectionScopedRuntimeException, VirtualHostScopedRuntimeException and > BrokerScopedRuntimeException. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5551) [Java Broker] Improve use of exceptions throughout the broker
[ https://issues.apache.org/jira/browse/QPID-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901359#comment-13901359 ] ASF subversion and git services commented on QPID-5551: --- Commit 1568252 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1568252 ] QPID-5551 : Change AMQStoreException to StoreException which inherits from ServerScopedRuntimeException > [Java Broker] Improve use of exceptions throughout the broker > - > > Key: QPID-5551 > URL: https://issues.apache.org/jira/browse/QPID-5551 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey >Priority: Minor > > Currently lots of methods throw AMQException which was original intended to > represent connection and channel closure reasons. > Now these are actually only generated from the 0-8 protocol plugin, however > the same base class is used for security exceptions (AMQSecurityException) > and also for errors encountered in the store (via AMQInternalException). > Where there is no obvious way to deal with an exception it is either being > directly rethrown, or wrapped in a runtime exception or similar. > We should remove cases of methods throwing AMQException when there is no path > through which they can actually throw that exception. We should then change > the use of exceptions in the broker to differentiate between those which we > expect to handle in some way (like security exceptions) versus those which > will only be handled in a coarse manner (exceptions that can only result in > the closure of a connection, or even of the entire virtual host or broker). > For the latter two cases I propose we introduce new RuntimeException classes > for ConnectionScopedRuntimeException, VirtualHostScopedRuntimeException and > BrokerScopedRuntimeException. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13901688#comment-13901688 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1568389 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1568389 ] QPIDJMS-9: add some additional tests for JMSXUserID, consolidate MFE creation into utility methods > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5552) Client abrupt stop causes QPID Server crash
[ https://issues.apache.org/jira/browse/QPID-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901771#comment-13901771 ] ASF subversion and git services commented on QPID-5552: --- Commit 1568452 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1568452 ] QPID-5552 : [Java Broker] Propertly handle transport exceptions encountered in methods invoked in AMQP 1.0 from the IOReceiver thread > Client abrupt stop causes QPID Server crash > --- > > Key: QPID-5552 > URL: https://issues.apache.org/jira/browse/QPID-5552 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.24 > Environment: RHEL >Reporter: Chris Kapp > Labels: epic, fail > > Re-create: > With the Proton client, create a moderate load of reads and writes. Stop the > client abruptly without any cleanup. > Result: > QPID Server shuts down. The frequency of re-creating seems to be about 80%. > Expected Result: > No messaging client should be able to cause the Message Broker to crash. > The Server output is: > java.net.SocketException: Broken pipe > at java.net.SocketOutputStream.socketWrite0(Native Method) > at java.net.SocketOutputStream.socketWrite(Unknown Source) > at java.net.SocketOutputStream.write(Unknown Source) > at > org.apache.qpid.transport.network.io.IoSender.run(IoSender.java:313) > at java.lang.Thread.run(Unknown Source) > 2014-02-14 09:45:05,469 ERROR [IoSender - /10.109.60.180:52514] (io.IoSender) > - error in write thread > java.net.SocketException: Broken pipe > at java.net.SocketOutputStream.socketWrite0(Native Method) > at java.net.SocketOutputStream.socketWrite(Unknown Source) > at java.net.SocketOutputStream.write(Unknown Source) > at > org.apache.qpid.transport.network.io.IoSender.run(IoSender.java:313) > at java.lang.Thread.run(Unknown Source) > 2014-02-14 09:50:08,657 ERROR [IoSender - /10.109.60.180:53546] (io.IoSender) > - error in write thread > java.net.SocketException: Connection reset > at java.net.SocketOutputStream.socketWrite(Unknown Source) > at java.net.SocketOutputStream.write(Unknown Source) > at > org.apache.qpid.transport.network.io.IoSender.run(IoSender.java:313) > at java.lang.Thread.run(Unknown Source) > 2014-02-14 09:50:08,658 ERROR [IoReceiver - /10.109.60.180:53546] > (thread.LoggingUncaughtExceptionHandler) - Uncaught exception in thread > "IoReceiver - /10.109.60.180:53546" > org.apache.qpid.transport.SenderClosedException: sender is closed > at > org.apache.qpid.transport.network.io.IoSender.send(IoSender.java:114) > at > org.apache.qpid.transport.network.io.IoSender.send(IoSender.java:40) > at > org.apache.qpid.server.protocol.v1_0.ProtocolEngine_1_0_0_SASL.send(ProtocolEngine_1_0_0_SASL.java:424) > at > org.apache.qpid.server.protocol.v1_0.ProtocolEngine_1_0_0_SASL.send(ProtocolEngine_1_0_0_SASL.java:385) > at > org.apache.qpid.amqp_1_0.transport.ConnectionEndpoint.send(ConnectionEndpoint.java:598) > at > org.apache.qpid.amqp_1_0.transport.ConnectionEndpoint.send(ConnectionEndpoint.java:561) > at > org.apache.qpid.amqp_1_0.transport.SessionEndpoint.send(SessionEndpoint.java:254) > at > org.apache.qpid.amqp_1_0.transport.SessionEndpoint.sendDetach(SessionEndpoint.java:725) > at > org.apache.qpid.amqp_1_0.transport.LinkEndpoint.detach(LinkEndpoint.java:405) > at > org.apache.qpid.amqp_1_0.transport.LinkEndpoint.detach(LinkEndpoint.java:364) > at > org.apache.qpid.server.protocol.v1_0.Subscription_1_0.close(Subscription_1_0.java:188) > at > org.apache.qpid.server.queue.SimpleAMQQueue.unregisterSubscription(SimpleAMQQueue.java:487) > at > org.apache.qpid.server.protocol.v1_0.SendingLink_1_0.remoteDetached(SendingLink_1_0.java:394) > at > org.apache.qpid.amqp_1_0.transport.LinkEndpoint.remoteDetached(LinkEndpoint.java:171) > at > org.apache.qpid.amqp_1_0.transport.SessionEndpoint.detach(SessionEndpoint.java:290) > at > org.apache.qpid.amqp_1_0.transport.SessionEndpoint.detachLinks(SessionEndpoint.java:192) > at > org.apache.qpid.amqp_1_0.transport.SessionEndpoint.end(SessionEndpoint.java:165) > at > org.apache.qpid.amqp_1_0.transport.SessionEndpoint.end(SessionEndpoint.java:152) > at > org.apache.qpid.amqp_1_0.transport.ConnectionEndpoint.inputClosed(ConnectionEndpoint.java:387) > at > org.apache.qpid.server.protocol.v1_0.ProtocolEngine_1_0_0_SASL.closed(ProtocolEngine_1_0_0_SASL.java:364) > at > org.apache.qpid.server.protocol.MultiVersionProtocolEngine.closed(MultiVersionProtocolEngine.java:115) > at > org.ap
[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=13902567#comment-13902567 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1568703 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1568703 ] QPIDJMS-9: work on support for JMSXGroupID > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13902566#comment-13902566 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1568702 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1568702 ] QPIDJMS-9: move responsibility for implementing clearBody() to the concrete message classes > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13902877#comment-13902877 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1568858 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1568858 ] QPIDJMS-9: initial work on implementing JMSXGroupSeq > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5409) [Java Broker] Add support for multi-node HA cluster into BDB JE HA message store
[ https://issues.apache.org/jira/browse/QPID-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903110#comment-13903110 ] ASF subversion and git services commented on QPID-5409: --- Commit 1568923 from oru...@apache.org in branch 'qpid/branches/java-broker-bdb-ha' [ https://svn.apache.org/r1568923 ] QPID-5409: Add UI for editing node attributes > [Java Broker] Add support for multi-node HA cluster into BDB JE HA message > store > > > Key: QPID-5409 > URL: https://issues.apache.org/jira/browse/QPID-5409 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Alex Rudyy > Fix For: 0.27 > > > The Java Qpid Broker currently supports only 2-nodes HA cluster with BDB JE > message store. This JIRA aims to extend the current HA functionality and add > support for multi-node HA cluster into BDB JE message store. > Here is the list of high-level requirements for the HA multi-node support: > # Only persistent messages are to be replicated. Transient messages will be > lost on failover. > # System must support clusters formed of an arbitrary number of nodes > # System must continue to support clusters formed of two nodes. Existing > public interfaces (notably JMX and existing virtualhost.xml format) must be > retained (though may be deprecated) to allow existing users a convenient > upgrade path. > # System must allow a user to completely configure a new node via the > web-management interface. > # System must allow a user to monitor the nodes of the cluster in order to > ascertain its health and perform day to day operations for via the > web-management interface. > ## expose statistics to allow the health of the cluster to be established > (exact details to be determined: could be low level like DbPing or something > more abstract) > # System must be amenable to monitoring by third-party tools. The Broker > should emit clear operational log messages as it transitions between states. > These messages will be targeted at the end-user. > # System must permit a mode of operation whereby the user (or other external > agent) determines which virtual host becomes active following a store > failover. In this mode of operation, following a failure, the store nodes in > the cluster will elect a new master and the replica node will still sync-up > with the new master node, but the system will not automatically mark the > virtual host corresponding to the master as active. The user will then > transfer the master to the desired location and make the virtualhost as > active, allowing business traffic to recommence. > # System must permit a mode of operation whereby the election of a store node > as master also causes the corresponding virtual host to become active. > # System must allow a user to influence a node's electability. These > features will allow a customer whose cluster spans primary/DR sites to keep > the active virtual hosts on the primary site in normal situations by > favouring failover within the primary site.Specifically, this will allow: > ## making a node unelectable - the node, even though it remains part of the > cluster, will never be elected as master) > ## making a node more likely to be elected master than other nodes - that > is, if two or more nodes have an equally up to date set of transactions, the > node with the highest priority will be elected master > ## node electability settings must survive restart, > ## node electability settings must be alterable at run-time. > # System must allow a user to alter quorum. This feature is required in > extraordinary situations where the system is required to continue to operate > despite the loss of sufficient nodes to mean there is no longer simple > majority. > # System must allow the user to move the active virtual host from one node to > another. This feature will help a user to restore a system to its BAU state > following an extraordinary situation. > # System must provide a user with a read-only view Queue when the underlying > store is in a replica state. This must provide at least queue name and queue > depth. This feature will allow a user to be able to see that replication is > indeed functioning. > # System must allow all HA operations to be allowed/denied according to rules > in the ACL. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5555) [Java Broker] Modify Queue implementation of lifetime / exclusivity policies
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903497#comment-13903497 ] ASF subversion and git services commented on QPID-: --- Commit 1569109 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1569109 ] QPID- : [Java Broker] Modify implementation of Queues to provide better notions of exclusivity and lifetime > [Java Broker] Modify Queue implementation of lifetime / exclusivity policies > > > Key: QPID- > URL: https://issues.apache.org/jira/browse/QPID- > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.27 > > > AMQP 0-8/9/9-1 and AMQP 0-10 both have notions of "autodelete" and > "exclusive" for Queues. However while they use the same names, they are in > fact subtly different. The Java Broker Queue implementation should better > abstract these notions into the lifetime and exclusivity policies. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5558) [Java Broker] Update implementation of draft AMQP Management to conform with WD06
[ https://issues.apache.org/jira/browse/QPID-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903518#comment-13903518 ] ASF subversion and git services commented on QPID-5558: --- Commit 1569115 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1569115 ] QPID-5558 : [Java Broker] update management node to follow definitions in working draft 06 > [Java Broker] Update implementation of draft AMQP Management to conform with > WD06 > - > > Key: QPID-5558 > URL: https://issues.apache.org/jira/browse/QPID-5558 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.27 > > > Working Draft 6 of the AMQP Management specification [1] introduces changes > to some operations to keep them within the bounds of what is allowed for > message application-properties as defined in the core specification. > [1] > https://www.oasis-open.org/committees/document.php?document_id=52237&wg_abbrev=amqp -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5556) Update qpid.pm and qpid_messaging.pm to export the proper package
[ https://issues.apache.org/jira/browse/QPID-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903537#comment-13903537 ] ASF subversion and git services commented on QPID-5556: --- Commit 1569117 from [~mcpierce] in branch 'qpid/trunk' [ https://svn.apache.org/r1569117 ] QPID-5556: Provide the right Perl packages in top-level modules. > Update qpid.pm and qpid_messaging.pm to export the proper package > - > > Key: QPID-5556 > URL: https://issues.apache.org/jira/browse/QPID-5556 > Project: Qpid > Issue Type: Bug > Components: Perl Client >Affects Versions: 0.24 >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce > Fix For: 0.27 > > > Neither module is currently defining the appropriate package. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5559) [Java Broker] Remove unused methods from the AMQQueue interface and implementations
[ https://issues.apache.org/jira/browse/QPID-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903548#comment-13903548 ] ASF subversion and git services commented on QPID-5559: --- Commit 1569119 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1569119 ] QPID-5559 : [Java Broker] remove unused methods from AMQQueue interface > [Java Broker] Remove unused methods from the AMQQueue interface and > implementations > > > Key: QPID-5559 > URL: https://issues.apache.org/jira/browse/QPID-5559 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.27 > > > (set)deleteOnNoConsumers() is now no longer needed as this is covered by > lifetime policies > deleteMessageFromTop() is only used in tests and only to clear the queue (so > use clearQueue() instead) -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4000) [Java 1.0] Implement message translation between AMQP 1.0 and other AMQP message types
[ https://issues.apache.org/jira/browse/QPID-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903633#comment-13903633 ] ASF subversion and git services commented on QPID-4000: --- Commit 1569151 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1569151 ] QPID-4000 : [Java Broker] add initial conversions from AMQP 1.0 messages to 0-8 and 0-10 > [Java 1.0] Implement message translation between AMQP 1.0 and other AMQP > message types > -- > > Key: QPID-4000 > URL: https://issues.apache.org/jira/browse/QPID-4000 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: Future > > > Allow automatic conversion between AMQP 1.0 messages and 0-8,0-9,0-10 > messages within the broker -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5555) [Java Broker] Modify Queue implementation of lifetime / exclusivity policies
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903899#comment-13903899 ] ASF subversion and git services commented on QPID-: --- Commit 1569245 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1569245 ] QPID- : Fix queue exclusivity issues > [Java Broker] Modify Queue implementation of lifetime / exclusivity policies > > > Key: QPID- > URL: https://issues.apache.org/jira/browse/QPID- > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Robbie Gemmell > Fix For: 0.27 > > > AMQP 0-8/9/9-1 and AMQP 0-10 both have notions of "autodelete" and > "exclusive" for Queues. However while they use the same names, they are in > fact subtly different. The Java Broker Queue implementation should better > abstract these notions into the lifetime and exclusivity policies. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5555) [Java Broker] Modify Queue implementation of lifetime / exclusivity policies
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904589#comment-13904589 ] ASF subversion and git services commented on QPID-: --- Commit 1569525 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1569525 ] QPID- : fix breakage in the broker QMF plugin caused by rework to broker internals > [Java Broker] Modify Queue implementation of lifetime / exclusivity policies > > > Key: QPID- > URL: https://issues.apache.org/jira/browse/QPID- > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Robbie Gemmell > Fix For: 0.27 > > > AMQP 0-8/9/9-1 and AMQP 0-10 both have notions of "autodelete" and > "exclusive" for Queues. However while they use the same names, they are in > fact subtly different. The Java Broker Queue implementation should better > abstract these notions into the lifetime and exclusivity policies. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13904622#comment-13904622 ] ASF subversion and git services commented on QPID-5311: --- Commit 1569530 from [~justi9] [ https://svn.apache.org/r1569530 ] QPID-5311: Improvements for mobile devices, page load times, and navigation Mailing list discussion: http://qpid.2158936.n2.nabble.com/Qpid-website-update-td7603954.html This update also adds Qpid 0.26 and fixes broken links from the transition to the svnpubsub release distribution method. > Website improvements for the 0.26 timeframe > --- > > Key: QPID-5311 > URL: https://issues.apache.org/jira/browse/QPID-5311 > Project: Qpid > Issue Type: Task > Components: Website >Affects Versions: 0.24 >Reporter: Justin Ross >Assignee: Justin Ross > Fix For: 0.26 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13904653#comment-13904653 ] ASF subversion and git services commented on QPID-5311: --- Commit 1569536 from [~justi9] [ https://svn.apache.org/r1569536 ] QPID-5311: Temporarily disable caching to force browsers to refresh; remove webmaster id file that breaks render > Website improvements for the 0.26 timeframe > --- > > Key: QPID-5311 > URL: https://issues.apache.org/jira/browse/QPID-5311 > Project: Qpid > Issue Type: Task > Components: Website >Affects Versions: 0.24 >Reporter: Justin Ross >Assignee: Justin Ross > Fix For: 0.26 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5562) [Java Broker] Make all ACL assertions throw AccessControlException on failure
[ https://issues.apache.org/jira/browse/QPID-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904761#comment-13904761 ] ASF subversion and git services commented on QPID-5562: --- Commit 1569552 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1569552 ] QPID-5562 : [Java Broker] make all failed ACL checks throw AccessControlException > [Java Broker] Make all ACL assertions throw AccessControlException on failure > - > > Key: QPID-5562 > URL: https://issues.apache.org/jira/browse/QPID-5562 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.27 > > > Remove the QpidSecurityException and instead have the SecurityManager throw > AccessControlException -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13904813#comment-13904813 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1569560 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1569560 ] QPIDJMS-9: some small cleanup, add some additional tests > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[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=13904815#comment-13904815 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1569562 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1569562 ] QPIDJMS-9: ensure to clear up fields for JMSXUserID, JMSXGroupID, JMSXGroupSeq when clearing properties > implement the JMS Message types and support for mapping them to/from AMQP > messages > -- > > Key: QPIDJMS-9 > URL: https://issues.apache.org/jira/browse/QPIDJMS-9 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > > implement the JMS message types and support for mapping them to/from AMQP > messages -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5563) [Java Broker] [AMQP 1.0] Use hostname field in open to select virtualhost
[ https://issues.apache.org/jira/browse/QPID-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904817#comment-13904817 ] ASF subversion and git services commented on QPID-5563: --- Commit 1569563 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1569563 ] QPID-5563 : [Java Broker] [AMQP 1.0] Use the hostname field in the open frame to select the virtual host > [Java Broker] [AMQP 1.0] Use hostname field in open to select virtualhost > - > > Key: QPID-5563 > URL: https://issues.apache.org/jira/browse/QPID-5563 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.27 > > > Currently only the default virtual host can be accessed using an AMQP 1.0 > connection. Allow the selection of a different virtualhost using the > "hostname" supplied in the open frame. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5255) 0.26 release tasks
[ https://issues.apache.org/jira/browse/QPID-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905059#comment-13905059 ] ASF subversion and git services commented on QPID-5255: --- Commit 1569618 from [~justi9] [ https://svn.apache.org/r1569618 ] QPID-5255: Tag the 0.26 release > 0.26 release tasks > -- > > Key: QPID-5255 > URL: https://issues.apache.org/jira/browse/QPID-5255 > Project: Qpid > Issue Type: Task > Components: Packaging, Website >Affects Versions: 0.25 >Reporter: Justin Ross >Assignee: Justin Ross > Fix For: 0.26 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5255) 0.26 release tasks
[ https://issues.apache.org/jira/browse/QPID-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905323#comment-13905323 ] ASF subversion and git services commented on QPID-5255: --- Commit 1569696 from [~justi9] [ https://svn.apache.org/r1569696 ] QPID-5255: Add Qpid 0.26 to the project metadata; update the mailing list link > 0.26 release tasks > -- > > Key: QPID-5255 > URL: https://issues.apache.org/jira/browse/QPID-5255 > Project: Qpid > Issue Type: Task > Components: Packaging, Website >Affects Versions: 0.25 >Reporter: Justin Ross >Assignee: Justin Ross > Fix For: 0.26 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5409) [Java Broker] Add support for multi-node HA cluster into BDB JE HA message store
[ https://issues.apache.org/jira/browse/QPID-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905648#comment-13905648 ] ASF subversion and git services commented on QPID-5409: --- Commit 1569814 from oru...@apache.org in branch 'qpid/branches/java-broker-bdb-ha' [ https://svn.apache.org/r1569814 ] QPID-5409: Restart the former master environment on MASTER transfer > [Java Broker] Add support for multi-node HA cluster into BDB JE HA message > store > > > Key: QPID-5409 > URL: https://issues.apache.org/jira/browse/QPID-5409 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Alex Rudyy > Fix For: 0.27 > > > The Java Qpid Broker currently supports only 2-nodes HA cluster with BDB JE > message store. This JIRA aims to extend the current HA functionality and add > support for multi-node HA cluster into BDB JE message store. > Here is the list of high-level requirements for the HA multi-node support: > # Only persistent messages are to be replicated. Transient messages will be > lost on failover. > # System must support clusters formed of an arbitrary number of nodes > # System must continue to support clusters formed of two nodes. Existing > public interfaces (notably JMX and existing virtualhost.xml format) must be > retained (though may be deprecated) to allow existing users a convenient > upgrade path. > # System must allow a user to completely configure a new node via the > web-management interface. > # System must allow a user to monitor the nodes of the cluster in order to > ascertain its health and perform day to day operations for via the > web-management interface. > ## expose statistics to allow the health of the cluster to be established > (exact details to be determined: could be low level like DbPing or something > more abstract) > # System must be amenable to monitoring by third-party tools. The Broker > should emit clear operational log messages as it transitions between states. > These messages will be targeted at the end-user. > # System must permit a mode of operation whereby the user (or other external > agent) determines which virtual host becomes active following a store > failover. In this mode of operation, following a failure, the store nodes in > the cluster will elect a new master and the replica node will still sync-up > with the new master node, but the system will not automatically mark the > virtual host corresponding to the master as active. The user will then > transfer the master to the desired location and make the virtualhost as > active, allowing business traffic to recommence. > # System must permit a mode of operation whereby the election of a store node > as master also causes the corresponding virtual host to become active. > # System must allow a user to influence a node's electability. These > features will allow a customer whose cluster spans primary/DR sites to keep > the active virtual hosts on the primary site in normal situations by > favouring failover within the primary site.Specifically, this will allow: > ## making a node unelectable - the node, even though it remains part of the > cluster, will never be elected as master) > ## making a node more likely to be elected master than other nodes - that > is, if two or more nodes have an equally up to date set of transactions, the > node with the highest priority will be elected master > ## node electability settings must survive restart, > ## node electability settings must be alterable at run-time. > # System must allow a user to alter quorum. This feature is required in > extraordinary situations where the system is required to continue to operate > despite the loss of sufficient nodes to mean there is no longer simple > majority. > # System must allow the user to move the active virtual host from one node to > another. This feature will help a user to restore a system to its BAU state > following an extraordinary situation. > # System must provide a user with a read-only view Queue when the underlying > store is in a replica state. This must provide at least queue name and queue > depth. This feature will allow a user to be able to see that replication is > indeed functioning. > # System must allow all HA operations to be allowed/denied according to rules > in the ACL. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5409) [Java Broker] Add support for multi-node HA cluster into BDB JE HA message store
[ https://issues.apache.org/jira/browse/QPID-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905647#comment-13905647 ] ASF subversion and git services commented on QPID-5409: --- Commit 1569813 from oru...@apache.org in branch 'qpid/branches/java-broker-bdb-ha' [ https://svn.apache.org/r1569813 ] QPID-5409: Fix failing unit test LocalReplicationNodeWithReplicatedEnvironmentFacadeTest#testSetRole > [Java Broker] Add support for multi-node HA cluster into BDB JE HA message > store > > > Key: QPID-5409 > URL: https://issues.apache.org/jira/browse/QPID-5409 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Alex Rudyy > Fix For: 0.27 > > > The Java Qpid Broker currently supports only 2-nodes HA cluster with BDB JE > message store. This JIRA aims to extend the current HA functionality and add > support for multi-node HA cluster into BDB JE message store. > Here is the list of high-level requirements for the HA multi-node support: > # Only persistent messages are to be replicated. Transient messages will be > lost on failover. > # System must support clusters formed of an arbitrary number of nodes > # System must continue to support clusters formed of two nodes. Existing > public interfaces (notably JMX and existing virtualhost.xml format) must be > retained (though may be deprecated) to allow existing users a convenient > upgrade path. > # System must allow a user to completely configure a new node via the > web-management interface. > # System must allow a user to monitor the nodes of the cluster in order to > ascertain its health and perform day to day operations for via the > web-management interface. > ## expose statistics to allow the health of the cluster to be established > (exact details to be determined: could be low level like DbPing or something > more abstract) > # System must be amenable to monitoring by third-party tools. The Broker > should emit clear operational log messages as it transitions between states. > These messages will be targeted at the end-user. > # System must permit a mode of operation whereby the user (or other external > agent) determines which virtual host becomes active following a store > failover. In this mode of operation, following a failure, the store nodes in > the cluster will elect a new master and the replica node will still sync-up > with the new master node, but the system will not automatically mark the > virtual host corresponding to the master as active. The user will then > transfer the master to the desired location and make the virtualhost as > active, allowing business traffic to recommence. > # System must permit a mode of operation whereby the election of a store node > as master also causes the corresponding virtual host to become active. > # System must allow a user to influence a node's electability. These > features will allow a customer whose cluster spans primary/DR sites to keep > the active virtual hosts on the primary site in normal situations by > favouring failover within the primary site.Specifically, this will allow: > ## making a node unelectable - the node, even though it remains part of the > cluster, will never be elected as master) > ## making a node more likely to be elected master than other nodes - that > is, if two or more nodes have an equally up to date set of transactions, the > node with the highest priority will be elected master > ## node electability settings must survive restart, > ## node electability settings must be alterable at run-time. > # System must allow a user to alter quorum. This feature is required in > extraordinary situations where the system is required to continue to operate > despite the loss of sufficient nodes to mean there is no longer simple > majority. > # System must allow the user to move the active virtual host from one node to > another. This feature will help a user to restore a system to its BAU state > following an extraordinary situation. > # System must provide a user with a read-only view Queue when the underlying > store is in a replica state. This must provide at least queue name and queue > depth. This feature will allow a user to be able to see that replication is > indeed functioning. > # System must allow all HA operations to be allowed/denied according to rules > in the ACL. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5566) [JMS AMQP 1.0] DestinationImpl implements both Queue and Topic, which confuses some other JMS implementations
[ https://issues.apache.org/jira/browse/QPID-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906055#comment-13906055 ] ASF subversion and git services commented on QPID-5566: --- Commit 1569914 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1569914 ] QPID-5566 : DestinationImpl should implement neither Queue nor Topic > [JMS AMQP 1.0] DestinationImpl implements both Queue and Topic, which > confuses some other JMS implementations > - > > Key: QPID-5566 > URL: https://issues.apache.org/jira/browse/QPID-5566 > Project: Qpid > Issue Type: Improvement >Reporter: Rob Godfrey >Assignee: Rob Godfrey > > DestinationImpl implements both Queue and Topic, it should implement neither > - only Destination. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5549) Windows SSL client support for AMQP 1.0
[ https://issues.apache.org/jira/browse/QPID-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906060#comment-13906060 ] ASF subversion and git services commented on QPID-5549: --- Commit 1569916 from cliffjan...@apache.org in branch 'qpid/trunk' [ https://svn.apache.org/r1569916 ] QPID-5549: windows ssl over AMQP 1.0 > Windows SSL client support for AMQP 1.0 > --- > > Key: QPID-5549 > URL: https://issues.apache.org/jira/browse/QPID-5549 > Project: Qpid > Issue Type: Improvement > Components: C++ Client >Affects Versions: 0.27 > Environment: Windows >Reporter: Cliff Jansen >Assignee: Cliff Jansen > > Add an SslTransport implementation for Windows. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5567) [Java Broker] Remove SecurityManager "CurrentSubject" thread local, and always use the subject from the current AccessControlContext
[ https://issues.apache.org/jira/browse/QPID-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906139#comment-13906139 ] ASF subversion and git services commented on QPID-5567: --- Commit 1569934 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1569934 ] QPID-5567 : Always Use AccessControllerContext to find the current context Subject > [Java Broker] Remove SecurityManager "CurrentSubject" thread local, and > always use the subject from the current AccessControlContext > > > Key: QPID-5567 > URL: https://issues.apache.org/jira/browse/QPID-5567 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > > Rather than invent our own security context, we should use the one Java > provides. > Moreover since we perform security checks based on the Connection and Session > of the user, we should add these as "Principals" of the current subject. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5570) [JMS AMQP 1.0 Client] Client incorrectly acknowledges pre-fetched messages with CLIENT_ACK
[ https://issues.apache.org/jira/browse/QPID-5570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907077#comment-13907077 ] ASF subversion and git services commented on QPID-5570: --- Commit 1570233 from [~godfrer] in branch 'qpid/trunk' [ https://svn.apache.org/r1570233 ] QPID-5570 : Client incorrectly acknowledges prefetched messages with client-ack > [JMS AMQP 1.0 Client] Client incorrectly acknowledges pre-fetched messages > with CLIENT_ACK > -- > > Key: QPID-5570 > URL: https://issues.apache.org/jira/browse/QPID-5570 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: 0.26 >Reporter: Rob Godfrey >Assignee: Rob Godfrey >Priority: Blocker > Fix For: 0.27 > > > See > http://stackoverflow.com/questions/21679926/servicebus-over-amqp-looses-redelivered-messages/21864141?noredirect=1#21864141 > and > http://qpid.2158936.n2.nabble.com/Java-JMS-acknowledge-and-prefetech-td7604576.html -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5568) HA C++ qpid::messaging AMQP 1.0 client failover logging is not clear.
[ https://issues.apache.org/jira/browse/QPID-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907074#comment-13907074 ] ASF subversion and git services commented on QPID-5568: --- Commit 1570231 from [~aconway] in branch 'qpid/trunk' [ https://svn.apache.org/r1570231 ] QPID-5568: HA C++ qpid::messaging AMQP 1.0 client failover logging is not clear The qpid::messaging AMQP 1.0 protocol logging did not give clear information about reconnection during failover. This patch simplifies the reconnect logic by collapsing all known addresses from broker URL and reconnect URLs into a single URL with no duplicates. It rationalizes the info and notice logging as follows: # Initial connection with multiple addresses, info logs show the # full URL, each attempt to connect and the finally connected address. [Messaging] info Starting connection to amqp:tcp:20.0.10.33:5672,tcp:20.0.10.34:5672,tcp:20.0.10.35:5672 [Messaging] info Connecting to tcp:20.0.10.33:5672 [Messaging] info Failed to connect to tcp:20.0.10.33:5672 [Messaging] info Connecting to tcp:20.0.10.34:5672 [Messaging] info Failed to connect to tcp:20.0.10.34:5672 [Messaging] info Connecting to tcp:20.0.10.35:5672 [Messaging] info Connected to tcp:20.0.10.35:5672 # Re-connection due to a failure. notice logs for the start of reconnection (with full URL) # and eventual sucess (with individual address). info logs for individual connection attempts. [Messaging] notice Auto-reconnecting to amqp:tcp:20.0.10.33:5672,tcp:20.0.10.34:5672,tcp:20.0.10.35:5672 [Messaging] info Connecting to tcp:20.0.10.33:5672 [Messaging] info Failed to connect to tcp:20.0.10.33:5672 [Messaging] info Connected to tcp:20.0.10.33:5672 [Messaging] notice Auto-reconnected to amqp:tcp:20.0.10.33:5672 The idea here is that there are no logs by default (info is not on by default) for "normal" behavior, but failover does get a (short) notice log by default. By turning on info logs you can follow the detailed blow-by-blow of failover without getting drowned in the detail of debug logs. Note that final failure to connect is signalled to the application via an exception. There was not previously any log message for that and I didn't add one. Additional changes: updated qpid-ping test client to use the messaging library. > HA C++ qpid::messaging AMQP 1.0 client failover logging is not clear. > - > > Key: QPID-5568 > URL: https://issues.apache.org/jira/browse/QPID-5568 > Project: Qpid > Issue Type: Bug > Components: C++ Client >Affects Versions: 0.27 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.27 > > > The qpid::messaging AMQP 1.0 protocol logging does give clear information > about reconnection during failover. It does not log all reconnect attempts. > see also > https://bugzilla.redhat.com/show_bug.cgi?id=1050856 > https://reviews.apache.org/r/17856/ -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
