[jira] [Commented] (QPID-8345) [Broker-J][AMQP 1.0] Consumed messages are left in acquired state on a queue when receiver’s desired snd-settle-mode is set to settled and transactions are not used for

[ https://issues.apache.org/jira/browse/QPID-8345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890266#comment-16890266 ] Rob Godfrey commented on QPID-8345: --- [~robbie] yes - to be fair, when sending settled the sender has

[jira] [Comment Edited] (QPID-8345) [Broker-J][AMQP 1.0] Consumed messages are left in acquired state on a queue when receiver’s desired snd-settle-mode is set to settled and sender sends pre-settled

[ https://issues.apache.org/jira/browse/QPID-8345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890215#comment-16890215 ] Rob Godfrey edited comment on QPID-8345 at 7/22/19 2:36 PM: [~robbie] actually

[jira] [Commented] (QPID-8345) [Broker-J][AMQP 1.0] Consumed messages are left in acquired state on a queue when receiver’s desired snd-settle-mode is set to settled and sender sends pre-settled messa

[ https://issues.apache.org/jira/browse/QPID-8345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890215#comment-16890215 ] Rob Godfrey commented on QPID-8345: --- [~robbie] actually I think that [~orudyy] is correct here

[jira] [Commented] (QPID-3616) Java Broker misinterprets message.flow infinite credit value (0xFFFFFFFF)

[ https://issues.apache.org/jira/browse/QPID-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16881407#comment-16881407 ] Rob Godfrey commented on QPID-3616: --- I believe this was fixed in QPID-8225 (there was a recent change

[jira] [Resolved] (QPID-3616) Java Broker misinterprets message.flow infinite credit value (0xFFFFFFFF)

[ https://issues.apache.org/jira/browse/QPID-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved QPID-3616. --- Resolution: Fixed > Java Broker misinterprets message.flow infinite credit value (0xF

[jira] [Updated] (QPID-8318) [Broker-J] [AMQP 0-8/9/9-1] Queue.Purge does not return deleted count

[ https://issues.apache.org/jira/browse/QPID-8318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8318: -- Status: Reviewable (was: In Progress) > [Broker-J] [AMQP 0-8/9/9-1] Queue.Purge does not ret

[jira] [Created] (QPID-8318) [Broker-J] [AMQP 0-8/9/9-1] Queue.Purge does not return deleted count

Rob Godfrey created QPID-8318: - Summary: [Broker-J] [AMQP 0-8/9/9-1] Queue.Purge does not return deleted count Key: QPID-8318 URL: https://issues.apache.org/jira/browse/QPID-8318 Project: Qpid

[jira] [Moved] (QPIDJMS-452) Receiving a large message with a jms polling consumer with timeout of 1 sec can hang when the timeout is reached while message is in transfer.

[ https://issues.apache.org/jira/browse/QPIDJMS-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey moved QPID-8295 to QPIDJMS-452: --- Affects Version/s: (was: Future) Component/s: (was: Java

[jira] [Commented] (QPID-8286) [Broker-J] Add operation into priority queue to change message priority

[ https://issues.apache.org/jira/browse/QPID-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793661#comment-16793661 ] Rob Godfrey commented on QPID-8286: --- [~orudyy] is the expectation here that this update to priority

Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org

On Mon, 10 Dec 2018 at 17:10, Robbie Gemmell wrote: > Hi Folks, > > Per the below mail sent by the ASF Infrastructure team (to dev@), our Git > repositories will be migrated from the original/old git-wip-us service on > to > the newer gitbox.apache.org service by February 7th. > > This is

[jira] [Updated] (QPID-8260) [Broker-J] Add support for provided preferences store into Derby and JDBC system configs

[ https://issues.apache.org/jira/browse/QPID-8260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8260: -- Summary: [Broker-J] Add support for provided preferences store into Derby and JDBC system configs

[jira] [Commented] (QPID-8257) Sybase message store not supporting empty messages

[ https://issues.apache.org/jira/browse/QPID-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676633#comment-16676633 ] Rob Godfrey commented on QPID-8257: --- [~alex.rufous] but that is a choice at a higher level of the code

[jira] [Comment Edited] (QPID-8257) Sybase message store not supporting empty messages

[ https://issues.apache.org/jira/browse/QPID-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676614#comment-16676614 ] Rob Godfrey edited comment on QPID-8257 at 11/6/18 11:13 AM: - [~overmeulen

[jira] [Commented] (QPID-8257) Sybase message store not supporting empty messages

[ https://issues.apache.org/jira/browse/QPID-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676614#comment-16676614 ] Rob Godfrey commented on QPID-8257: --- [~overmeulen] The thing is that the column shouldn't need

[jira] [Commented] (QPID-8257) Sybase message store not supporting empty messages

[ https://issues.apache.org/jira/browse/QPID-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676599#comment-16676599 ] Rob Godfrey commented on QPID-8257: --- [~alex.rufous] IIRC (and this was *years* ago) there were (API

[jira] [Commented] (QPID-8257) Sybase message store not supporting empty messages

[ https://issues.apache.org/jira/browse/QPID-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676596#comment-16676596 ] Rob Godfrey commented on QPID-8257: --- Looking at this a bit more, would the simplest change of replacing

[jira] [Commented] (QPID-8257) Sybase message store not supporting empty messages

[ https://issues.apache.org/jira/browse/QPID-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676588#comment-16676588 ] Rob Godfrey commented on QPID-8257: --- Alex, Olivier - I guess the probable cause might be that Sybase

[jira] [Assigned] (QPID-8242) [Broker-J] JDBC store should remove message content/metadata asynchronously

[ https://issues.apache.org/jira/browse/QPID-8242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned QPID-8242: - Assignee: Alex Rudyy (was: Rob Godfrey) > [Broker-J] JDBC store should remove message cont

[jira] [Updated] (QPID-8242) [Broker-J] JDBC store should remove message content/metadata asynchronously

[ https://issues.apache.org/jira/browse/QPID-8242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8242: -- Status: Reviewable (was: In Progress) > [Broker-J] JDBC store should remove message content/metad

[jira] [Assigned] (QPID-8242) [Broker-J] JDBC store should remove message content/metadata asynchronously

[ https://issues.apache.org/jira/browse/QPID-8242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned QPID-8242: - Assignee: Rob Godfrey > [Broker-J] JDBC store should remove message content/metad

[jira] [Commented] (QPID-8245) [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand

[ https://issues.apache.org/jira/browse/QPID-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16633855#comment-16633855 ] Rob Godfrey commented on QPID-8245: --- [~alex.rufous] Ah - I forgot about that flow to disk feature

[jira] [Comment Edited] (QPID-8245) [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand

[ https://issues.apache.org/jira/browse/QPID-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16633750#comment-16633750 ] Rob Godfrey edited comment on QPID-8245 at 10/1/18 9:18 AM: [~alex.rufous] Yes

[jira] [Commented] (QPID-8245) [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand

[ https://issues.apache.org/jira/browse/QPID-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16633750#comment-16633750 ] Rob Godfrey commented on QPID-8245: --- [~alex.rufous] Yes - that was my intent, I just also imagined

[jira] [Commented] (QPID-8245) [Broker-J] [AMQP 0-8..0-91] Decode FiledTable fields on demand

[ https://issues.apache.org/jira/browse/QPID-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627756#comment-16627756 ] Rob Godfrey commented on QPID-8245: --- [~alex.rufous] My assumption is that it will be quicker to "

[jira] [Commented] (QPID-8245) [Broker-J] [AMQP 0-8..0-91] Decode FiledTable fields on demand

[ https://issues.apache.org/jira/browse/QPID-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627470#comment-16627470 ] Rob Godfrey commented on QPID-8245: --- [~alex.rufous] So the majority of the patches aren't that different

[jira] [Updated] (QPID-8242) [Broker-J] JDBC store should remove message content/metadata asynchronously

[ https://issues.apache.org/jira/browse/QPID-8242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8242: -- Attachment: (was: QPID-8242.patch) > [Broker-J] JDBC store should remove message content/metad

[jira] [Updated] (QPID-8242) [Broker-J] JDBC store should remove message content/metadata asynchronously

[ https://issues.apache.org/jira/browse/QPID-8242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8242: -- Attachment: QPID-8242.patch > [Broker-J] JDBC store should remove message content/metad

[jira] [Commented] (QPID-8245) [Broker-J] [AMQP 0-8..0-91] Decode FiledTable fields on demand

[ https://issues.apache.org/jira/browse/QPID-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627149#comment-16627149 ] Rob Godfrey commented on QPID-8245: --- So I started playing around with this before I went on vacation. I

[jira] [Updated] (QPID-8242) [Broker-J] JDBC store should remove message content/metadata asynchronously

[ https://issues.apache.org/jira/browse/QPID-8242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8242: -- Attachment: QPID-8242.patch > [Broker-J] JDBC store should remove message content/metad

[jira] [Updated] (QPID-8242) [Broker-J] JDBC store should remove message content/metadata asynchronously

[ https://issues.apache.org/jira/browse/QPID-8242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8242: -- Attachment: (was: QPID-8242.patch) > [Broker-J] JDBC store should remove message content/metad

[jira] [Updated] (QPID-8242) [Broker-J] JDBC store should remove message content/metadata asynchronously

[ https://issues.apache.org/jira/browse/QPID-8242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8242: -- Attachment: QPID-8242.patch > [Broker-J] JDBC store should remove message content/metad

[jira] [Updated] (QPID-8242) [Broker-J] JDBC store should remove message content/metadata asynchronously

[ https://issues.apache.org/jira/browse/QPID-8242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8242: -- Summary: [Broker-J] JDBC store should remove message content/metadata asynchronously (was: [Broker-J

[jira] [Created] (QPID-8242) [Broker-J] JDBC store should remove message content/metadata asynchronousle

Rob Godfrey created QPID-8242: - Summary: [Broker-J] JDBC store should remove message content/metadata asynchronousle Key: QPID-8242 URL: https://issues.apache.org/jira/browse/QPID-8242 Project: Qpid

[jira] [Assigned] (QPID-8241) [Broker-J] Remove use of javax.xml.bind.DatatypeConverter

[ https://issues.apache.org/jira/browse/QPID-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned QPID-8241: - Assignee: Rob Godfrey > [Broker-J] Remove use of javax.xml.bind.DatatypeConver

[jira] [Updated] (QPID-8241) [Broker-J] Remove use of javax.xml.bind.DatatypeConverter

[ https://issues.apache.org/jira/browse/QPID-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8241: -- Status: Reviewable (was: In Progress) > [Broker-J] Remove use of javax.xml.bind.DatatypeConver

[jira] [Commented] (QPID-8241) [Broker-J] Remove use of javax.xml.bind.DatatypeConverter

[ https://issues.apache.org/jira/browse/QPID-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619166#comment-16619166 ] Rob Godfrey commented on QPID-8241: --- Note there are a couple of tests that verify a Date/Time

[jira] [Updated] (QPID-8241) [Broker-J] Remove use of javax.xml.bind.DatatypeConverter

[ https://issues.apache.org/jira/browse/QPID-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8241: -- Issue Type: Improvement (was: Bug) > [Broker-J] Remove use of javax.xml.bind.DatatypeConver

[jira] [Updated] (QPID-8241) [Broker-J] Remove use of javax.xml.bind.DatatypeConverter

[ https://issues.apache.org/jira/browse/QPID-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8241: -- Description: As per [this comment|https://issues.apache.org/jira/browse/QPID-7885?focusedCommentId

[jira] [Created] (QPID-8241) [Broker-J] Remove use of javax.xml.bind.DatatypeConverter

Rob Godfrey created QPID-8241: - Summary: [Broker-J] Remove use of javax.xml.bind.DatatypeConverter Key: QPID-8241 URL: https://issues.apache.org/jira/browse/QPID-8241 Project: Qpid Issue Type

[jira] [Commented] (QPID-7885) [Java Broker] Support Java 9

[ https://issues.apache.org/jira/browse/QPID-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614763#comment-16614763 ] Rob Godfrey commented on QPID-7885: --- For this particular issue I wonder if it might not be better

[jira] [Commented] (QPID-8238) [Broker-J] Improve performance of asynchronous publishing of transient messages into topic exchange having queues bound using non-overlapping selectors

[ https://issues.apache.org/jira/browse/QPID-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16601990#comment-16601990 ] Rob Godfrey commented on QPID-8238: --- [~alex.rufous] that's interesting. I'll maybe play with my patch

[jira] [Commented] (QPID-8238) [Broker-J] Improve performance of asynchronous publishing of transient messages into topic exchange having queues bound using non-overlapping selectors

[ https://issues.apache.org/jira/browse/QPID-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16601936#comment-16601936 ] Rob Godfrey commented on QPID-8238: --- [~alex.rufous] Did you test the performance after your patch? I

[jira] [Commented] (QPID-8238) [Broker-J] Improve performance of asynchronous publishing of transient messages into topic exchange having queues bound using non-overlapping selectors

[ https://issues.apache.org/jira/browse/QPID-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598564#comment-16598564 ] Rob Godfrey commented on QPID-8238: --- In terms of the AMQShortString -> String conversions - wo

[jira] [Commented] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593394#comment-16593394 ] Rob Godfrey commented on PROTON-1917: - So - I cleaned and rebuilt the broker at the end of last week

[jira] [Commented] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590741#comment-16590741 ] Rob Godfrey commented on PROTON-1917: - Hmmm... that's a different error - it's reporting you

[jira] [Updated] (QPID-8233) [Broker-J][AMQP 1.0] Failure on connecting to a virtual host which is not yet active should use connection-forced error

[ https://issues.apache.org/jira/browse/QPID-8233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8233: -- Attachment: apache-qpid-broker-j-7.0.3-bin.zip > [Broker-J][AMQP 1.0] Failure on connect

[jira] [Updated] (QPID-8233) [Broker-J][AMQP 1.0] Failure on connecting to a virtual host which is not yet active should use connection-forced error

[ https://issues.apache.org/jira/browse/QPID-8233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8233: -- Attachment: (was: apache-qpid-broker-j-7.0.3-bin.zip) > [Broker-J][AMQP 1.0] Failure on connect

[jira] [Commented] (QPID-8234) [Broker-J] Return amqp error "amqp:connection:forced" on opening connections to non-existing or not-active virtual hosts

[ https://issues.apache.org/jira/browse/QPID-8234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590059#comment-16590059 ] Rob Godfrey commented on QPID-8234: --- I think this duplicates QPID-8233 :) > [Broker-J] Return a

[jira] [Created] (QPID-8235) [Broker-J] Broker should delay opening/closing connections to virtual hosts which are still activating

Rob Godfrey created QPID-8235: - Summary: [Broker-J] Broker should delay opening/closing connections to virtual hosts which are still activating Key: QPID-8235 URL: https://issues.apache.org/jira/browse/QPID-8235

[jira] [Commented] (QPID-8233) [Broker-J][AMQP 1.0] Failure on connecting to a virtual host which is not yet active should use connection-forced error

[ https://issues.apache.org/jira/browse/QPID-8233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590049#comment-16590049 ] Rob Godfrey commented on QPID-8233: --- Attached are a patch and a full build of Broker-J 7.0.3

[jira] [Updated] (QPID-8233) [Broker-J][AMQP 1.0] Failure on connecting to a virtual host which is not yet active should use connection-forced error

[ https://issues.apache.org/jira/browse/QPID-8233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8233: -- Attachment: apache-qpid-broker-j-7.0.3-bin.zip > [Broker-J][AMQP 1.0] Failure on connect

[jira] [Updated] (QPID-8233) [Broker-J][AMQP 1.0] Failure on connecting to a virtual host which is not yet active should use connection-forced error

[ https://issues.apache.org/jira/browse/QPID-8233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8233: -- Attachment: QPID-8233.diff > [Broker-J][AMQP 1.0] Failure on connecting to a virtual host wh

[jira] [Commented] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590045#comment-16590045 ] Rob Godfrey commented on PROTON-1917: - I have created QPID-8233 for the Broker-J change, and I

[jira] [Created] (QPID-8233) [Broker-J][AMQP 1.0] Failure on connecting to a virtual host which is not yet active should use connection-forced error

Rob Godfrey created QPID-8233: - Summary: [Broker-J][AMQP 1.0] Failure on connecting to a virtual host which is not yet active should use connection-forced error Key: QPID-8233 URL: https://issues.apache.org/jira

[jira] [Commented] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590026#comment-16590026 ] Rob Godfrey commented on PROTON-1917: - [~jeremy.aouad] Which version of Broker-J are you using? I

[jira] [Commented] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16589996#comment-16589996 ] Rob Godfrey commented on PROTON-1917: - [~gemmellr] Do you know how the JMS client will behave

[jira] [Comment Edited] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16589977#comment-16589977 ] Rob Godfrey edited comment on PROTON-1917 at 8/23/18 9:48 AM: -- I'm still

[jira] [Commented] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16589977#comment-16589977 ] Rob Godfrey commented on PROTON-1917: - I'm still not totally convinced that this is really Proton's

[jira] [Updated] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-1917: Summary: [proton-c] the c++ proton consumer with retry should continue to retry if virtual host

[jira] [Comment Edited] (PROTON-1917) [proton-c] When qpid broker is killed and started, the c++ proton consumer (with retry) is randomly exiting with an error

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16589937#comment-16589937 ] Rob Godfrey edited comment on PROTON-1917 at 8/23/18 9:09 AM: -- >F

[jira] [Resolved] (PROTON-1917) [proton-c] When qpid broker is killed and started, the c++ proton consumer (with retry) is randomly exiting with an error

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-1917. - Resolution: Not A Problem > [proton-c] When qpid broker is killed and started, the c++ pro

[jira] [Reopened] (PROTON-1917) [proton-c] When qpid broker is killed and started, the c++ proton consumer (with retry) is randomly exiting with an error

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reopened PROTON-1917: - > [proton-c] When qpid broker is killed and started, the c++ proton consumer > (with

[jira] [Commented] (PROTON-1917) [proton-c] When qpid broker is killed and started, the c++ proton consumer (with retry) is randomly exiting with an error

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16589937#comment-16589937 ] Rob Godfrey commented on PROTON-1917: - This is not really a proton issue. From the error message

[jira] [Commented] (QPID-8227) [Broker-J] Replace qpidbrokerversion.properties with jar metadata

[ https://issues.apache.org/jira/browse/QPID-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16573425#comment-16573425 ] Rob Godfrey commented on QPID-8227: --- Under what situations would the fallback-version.txt be used? Just

[jira] [Updated] (QPID-8225) [Broker-J][AMQP 0-10] stops delivering queue/consumer messages after 4 GB data transfer

[ https://issues.apache.org/jira/browse/QPID-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8225: -- Attachment: qpid-broker-plugins-amqp-0-10-protocol-7.0.6.jar > [Broker-J][AMQP 0-10] stops deliver

[jira] [Updated] (QPID-8225) [Broker-J][AMQP 0-10] stops delivering queue/consumer messages after 4 GB data transfer

[ https://issues.apache.org/jira/browse/QPID-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8225: -- Issue Type: Bug (was: Task) > [Broker-J][AMQP 0-10] stops delivering queue/consumer messages afte

[jira] [Updated] (QPID-8225) [Broker-J][AMQP 0-10] stops delivering queue/consumer messages after 4 GB data transfer

[ https://issues.apache.org/jira/browse/QPID-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8225: -- Priority: Critical (was: Minor) > [Broker-J][AMQP 0-10] stops delivering queue/consumer messages af

[jira] [Updated] (QPID-8225) [Broker-J][AMQP 0-10] stops delivering queue/consumer messages after 4 GB data transfer

[ https://issues.apache.org/jira/browse/QPID-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8225: -- Summary: [Broker-J][AMQP 0-10] stops delivering queue/consumer messages after 4 GB data transfer

[jira] [Commented] (QPIDJMS-402) Massive performance degradation in 0.34.0

[ https://issues.apache.org/jira/browse/QPIDJMS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543700#comment-16543700 ] Rob Godfrey commented on QPIDJMS-402: - [~gemmellr] so I've now tried two more Mac laptops. On my

[jira] [Commented] (QPIDJMS-402) Massive performance degradation in 0.34.0

[ https://issues.apache.org/jira/browse/QPIDJMS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543213#comment-16543213 ] Rob Godfrey commented on QPIDJMS-402: - Testing on my machines, the machine/operating system

[jira] [Commented] (QPID-7153) Allow expired messages to be sent to DLQ

[ https://issues.apache.org/jira/browse/QPID-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533852#comment-16533852 ] Rob Godfrey commented on QPID-7153: --- {noformat}- q -> !((q instanceof AbstractQueue) && ((Ab

[jira] [Commented] (QPID-7153) Allow expired messages to be sent to DLQ

[ https://issues.apache.org/jira/browse/QPID-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483766#comment-16483766 ] Rob Godfrey commented on QPID-7153: --- Good point on the MAX_VALUE calculation.  I did consider a third

[jira] [Created] (QPID-8193) [Broker-J] Updating maximum / minimum TTL on a queue does not affect messages already in the queue (until restart)

Rob Godfrey created QPID-8193: - Summary: [Broker-J] Updating maximum / minimum TTL on a queue does not affect messages already in the queue (until restart) Key: QPID-8193 URL: https://issues.apache.org/jira/browse

[jira] [Commented] (QPID-7153) Allow expired messages to be sent to DLQ

[ https://issues.apache.org/jira/browse/QPID-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478856#comment-16478856 ] Rob Godfrey commented on QPID-7153: --- Updated after getting round to actually testing :) Fix the case

[jira] [Updated] (QPID-7153) Allow expired messages to be sent to DLQ

[ https://issues.apache.org/jira/browse/QPID-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-7153: -- Attachment: QPID-7153v2.diff > Allow expired messages to be sent to

[jira] [Updated] (QPID-7153) Allow expired messages to be sent to DLQ

[ https://issues.apache.org/jira/browse/QPID-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-7153: -- Attachment: (was: QPID-7153.diff) > Allow expired messages to be sent to

[jira] [Commented] (QPID-7153) Allow expired messages to be sent to DLQ

[ https://issues.apache.org/jira/browse/QPID-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477245#comment-16477245 ] Rob Godfrey commented on QPID-7153: --- Attached an untested patch which might provide a way forward

[jira] [Updated] (QPID-7153) Allow expired messages to be sent to DLQ

[ https://issues.apache.org/jira/browse/QPID-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-7153: -- Attachment: QPID-7153.diff > Allow expired messages to be sent to

[jira] [Commented] (QPID-8178) [Broker-J] [Websocket] Support authentication from bearer token carried by authentication header

[ https://issues.apache.org/jira/browse/QPID-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16460690#comment-16460690 ] Rob Godfrey commented on QPID-8178: --- For this case, what would you expect the agreed SASL mechanism

[jira] [Comment Edited] (QPIDJMS-373) Support for OAuth flow and setting of "Authorization" Header for WS upgrade request

[ https://issues.apache.org/jira/browse/QPIDJMS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426828#comment-16426828 ] Rob Godfrey edited comment on QPIDJMS-373 at 4/5/18 12:27 PM: -- [~gemmellr

[jira] [Commented] (QPIDJMS-373) Support for OAuth flow and setting of "Authorization" Header for WS upgrade request

[ https://issues.apache.org/jira/browse/QPIDJMS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426828#comment-16426828 ] Rob Godfrey commented on QPIDJMS-373: - [~gemmellr] Registering a callback would be a nice general

[jira] [Commented] (QPIDJMS-373) Support for OAuth flow and setting of "Authorization" Header for WS upgrade request

[ https://issues.apache.org/jira/browse/QPIDJMS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425990#comment-16425990 ] Rob Godfrey commented on QPIDJMS-373: - Is there an advantage to doing this as a new transport rather

[jira] [Comment Edited] (QPIDJMS-373) Support for OAuth flow and setting of "Authorization" Header for WS upgrade request

[ https://issues.apache.org/jira/browse/QPIDJMS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425990#comment-16425990 ] Rob Godfrey edited comment on QPIDJMS-373 at 4/4/18 6:36 PM

[jira] [Commented] (QPID-8152) [Broker-J][BDB] Virtual host start-up fails with IOException: User limit of inotify instances reached or too many open files

[ https://issues.apache.org/jira/browse/QPID-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424222#comment-16424222 ] Rob Godfrey commented on QPID-8152: --- I agree with [~k-wall] it would seem better to document than to turn

[jira] [Updated] (QPID-8150) [Broker-J] Prevent test failures due to slow initialisation of hostname resolution in HostnameAliasImpl

[ https://issues.apache.org/jira/browse/QPID-8150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8150: -- Fix Version/s: qpid-java-broker-7.1.0 > [Broker-J] Prevent test failures due to slow initialisat

[jira] [Assigned] (QPID-8150) [Broker-J] Prevent test failures due to slow initialisation of hostname resolution in HostnameAliasImpl

[ https://issues.apache.org/jira/browse/QPID-8150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned QPID-8150: - Assignee: Rob Godfrey > [Broker-J] Prevent test failures due to slow initialisation of hostn

[jira] [Updated] (QPID-8150) [Broker-J] Prevent test failures due to slow initialisation of hostname resolution in HostnameAliasImpl

[ https://issues.apache.org/jira/browse/QPID-8150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8150: -- Status: Reviewable (was: In Progress) > [Broker-J] Prevent test failures due to slow initialisat

[jira] [Created] (QPID-8150) [Broker-J] Prevent test failures due to slow initialisation of hostname resolution in HostnameAliasImpl

Rob Godfrey created QPID-8150: - Summary: [Broker-J] Prevent test failures due to slow initialisation of hostname resolution in HostnameAliasImpl Key: QPID-8150 URL: https://issues.apache.org/jira/browse/QPID-8150

[jira] [Updated] (QPID-8143) [Broker-J] Properly validate @ManagedAttributeValueTypes, and allow for factory methods

[ https://issues.apache.org/jira/browse/QPID-8143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8143: -- Status: Reviewable (was: In Progress) > [Broker-J] Properly validate @ManagedAttributeValueTy

[jira] [Assigned] (QPID-8143) [Broker-J] Properly validate @ManagedAttributeValueTypes, and allow for factory methods

[ https://issues.apache.org/jira/browse/QPID-8143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned QPID-8143: - Assignee: Keith Wall (was: Rob Godfrey) > [Broker-J] Properly valid

[jira] [Assigned] (QPID-8143) [Broker-J] Properly validate @ManagedAttributeValueTypes, and allow for factory methods

[ https://issues.apache.org/jira/browse/QPID-8143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned QPID-8143: - Assignee: Rob Godfrey > [Broker-J] Properly validate @ManagedAttributeValueTypes, and al

[jira] [Created] (QPID-8143) [Broker-J] Properly validate @ManagedAttributeValueTypes, and allow for factory methods

Rob Godfrey created QPID-8143: - Summary: [Broker-J] Properly validate @ManagedAttributeValueTypes, and allow for factory methods Key: QPID-8143 URL: https://issues.apache.org/jira/browse/QPID-8143

[jira] [Commented] (QPIDJMS-371) String representation of JMSMessageID values generated with message ID policy of type 'UUID' cannot be used in selector expressions

[ https://issues.apache.org/jira/browse/QPIDJMS-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411731#comment-16411731 ] Rob Godfrey commented on QPIDJMS-371: - [~alex.rufous] the JMS client is working as designed

[jira] [Commented] (QPID-8139) [Broker-J] Selector containing JMSMessageID expressions might not find the message when expression JMSMessageID value starts with 'ID:' prefix but the real message id do

[ https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411729#comment-16411729 ] Rob Godfrey commented on QPID-8139: --- [~alex.rufous]: the draft JMS AMQP mapping specifies how

[jira] [Commented] (QPID-7567) [Java Broker] Select appropriate certificate for TLS based on SNIServerName

[ https://issues.apache.org/jira/browse/QPID-7567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411174#comment-16411174 ] Rob Godfrey commented on QPID-7567: --- Yeah - I basically decided that if you have multiple valid

[jira] [Created] (QPIDJMS-367) Add support for XOAUTH2 Sasl Autentication

Rob Godfrey created QPIDJMS-367: --- Summary: Add support for XOAUTH2 Sasl Autentication Key: QPIDJMS-367 URL: https://issues.apache.org/jira/browse/QPIDJMS-367 Project: Qpid JMS Issue Type

[jira] [Commented] (QPID-8122) [Broker-J] Create JDBC backed virtualhost node fails on MariaDB when database charset is utf8mb4

[ https://issues.apache.org/jira/browse/QPID-8122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16395092#comment-16395092 ] Rob Godfrey commented on QPID-8122: --- This table seems like it was designed with the notion of children

[jira] [Commented] (QPID-8122) [Broker-J] Create JDBC backed virtualhost node fails on MariaDB when database charset is utf8mb4

[ https://issues.apache.org/jira/browse/QPID-8122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393041#comment-16393041 ] Rob Godfrey commented on QPID-8122: --- Does MariaDB/MySQL have a binary type?  Another alternative would

[jira] [Commented] (QPID-8114) [Broker-J] Attempting to use an unknown filter type incorrectly causes connection closure with a decode error

[ https://issues.apache.org/jira/browse/QPID-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381738#comment-16381738 ] Rob Godfrey commented on QPID-8114: --- Attached a patch which I think would address this particular

[jira] [Updated] (QPID-8114) [Broker-J] Attempting to use an unknown filter type incorrectly causes connection closure with a decode error

[ https://issues.apache.org/jira/browse/QPID-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8114: -- Attachment: QPID-8114___[Broker-J

  1   2   3   4   5   6   7   8   9   10   >