[jira] [Commented] (PROTON-1249) proton-j: unsafe type initialisations
[ https://issues.apache.org/jira/browse/PROTON-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357914#comment-15357914 ] ASF GitHub Bot commented on PROTON-1249: Github user asfgit closed the pull request at: https://github.com/apache/qpid-proton/pull/76 > proton-j: unsafe type initialisations > - > > Key: PROTON-1249 > URL: https://issues.apache.org/jira/browse/PROTON-1249 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: 0.12.2 >Reporter: Dominic Evans >Assignee: Dominic Evans > Labels: proton-j, security > > In #readValue() for ArrayType, BinaryType, ListType and MapType > decoding, if the 'count' specified is very large then it is likely to > trigger an OutOfMemoryException. As these can come from an external data > source, during the SASL init for example, there is a potential for a > denial of service. The fix is to throw an IllegalArgumentException if > the count value is larger than the amount of data available in the > received bytes. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1249) proton-j: unsafe type initialisations
[ https://issues.apache.org/jira/browse/PROTON-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357913#comment-15357913 ] ASF subversion and git services commented on PROTON-1249: - Commit 0c92828864118517f8d8a23a2801da82852cf36c in qpid-proton's branch refs/heads/master from [~dnwe] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=0c92828 ] PROTON-1249: Safeguard type initialisations. In #readValue() for ArrayType, BinaryType, ListType and MapType decoding, if the 'count' specified is very large then it is likely to trigger an OutOfMemoryException. As these can come from an external data source, during the SASL init for example, there is a potential for a denial of service. The fix is to throw an IllegalArgumentException if the count value is larger than the amount of data available in the received bytes. > proton-j: unsafe type initialisations > - > > Key: PROTON-1249 > URL: https://issues.apache.org/jira/browse/PROTON-1249 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: 0.12.2 >Reporter: Dominic Evans >Assignee: Dominic Evans > Labels: proton-j, security > > In #readValue() for ArrayType, BinaryType, ListType and MapType > decoding, if the 'count' specified is very large then it is likely to > trigger an OutOfMemoryException. As these can come from an external data > source, during the SASL init for example, there is a potential for a > denial of service. The fix is to throw an IllegalArgumentException if > the count value is larger than the amount of data available in the > received bytes. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton pull request #76: PROTON-1249: Safeguard type initialisations.
Github user asfgit closed the pull request at: https://github.com/apache/qpid-proton/pull/76 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-7096) [Java Broker] Add minor release version to REST API version
[ https://issues.apache.org/jira/browse/QPID-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7096. -- Resolution: Fixed Change looks reasonable to me. > [Java Broker] Add minor release version to REST API version > --- > > Key: QPID-7096 > URL: https://issues.apache.org/jira/browse/QPID-7096 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Rob Godfrey > Fix For: qpid-java-6.1 > > > Currently the REST API version uses only the major model version. This > prevents any model changes in minor versions that would require API changes. > This is too restrictive... changing an attribute or modifying operations > should be possible between minor releases. > We should modify the generation of the API to include the minor model number. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7224) Exposed truststores should exclude/include based on virtualhostnode rather than virtualhost
[ https://issues.apache.org/jira/browse/QPID-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357906#comment-15357906 ] Keith Wall commented on QPID-7224: -- Changes look reasonable to me. > Exposed truststores should exclude/include based on virtualhostnode rather > than virtualhost > --- > > Key: QPID-7224 > URL: https://issues.apache.org/jira/browse/QPID-7224 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Keith Wall > Fix For: qpid-java-6.1 > > > Truststores can be exposed as a message sources to clients for the purposes > of public key distribution for end-to-end message encryption. > If a truststore is exposed, by default the truststore is exposed to all > virtualhosts. The user can opt to make this more restrictive by opting to > include or exclude virtualhosts. > The inclusion/exclusion based on virtualhost is problematic in the HA case, > as the virtualhost may be elsewhere in the group. This would prevent the > Truststore from starting (it would go into error). > The Truststore implementations must change to have inclusion/exclusion based > on virtualhostnode. > The configuration upgrader will need to guess that the virtualhostnode name > is the same as the virtualhost. This will work with default configuration in > the non-HA case (where virtualhostnode name = virtualhost name), but will > fail in the HA case. > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-399) Convert documentation to asciidoc format
[ https://issues.apache.org/jira/browse/DISPATCH-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357830#comment-15357830 ] ASF subversion and git services commented on DISPATCH-399: -- Commit 27629e177e52fb2eec0b37e22b30b9e8b8ae0378 in qpid-dispatch's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=27629e1 ] DISPATCH-399: Generate body-only HTML documentation for Qpid site. Also added cmake variable to enable verbose output from doc tools for debugging. > Convert documentation to asciidoc format > > > Key: DISPATCH-399 > URL: https://issues.apache.org/jira/browse/DISPATCH-399 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Documentation >Affects Versions: 0.6.0 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Minor > Fix For: 0.7.0 > > > asciidoc format is becoming more popular for documentation and has several > advantages over RST + sphinx. > - Mature, widely-used DocBook model without painful XML syntax > - Multi-file documents and entity substitution are standard in asciidoc > (Sphinx has non-standard extensions, but not defined by RST) > - simpler, more flexible tools, fewer generation steps. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-439) Connect form cannot be submitted using only keyboard
[ https://issues.apache.org/jira/browse/DISPATCH-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-439: Description: h3. Observed behavior When connecting to the router, after filling Address and Port, the only way to submit the form is to click the Connect button with mouse. Pressing enter while input fields of the form are focused does nothing. Tabbing to the Connect button is difficult, because the Connect button does not have a distinct focused appearance. Same is true for the Autostart checkbox. Pressing enter or space while the button is focused does click it. But there is no visual indication of the fact that the button is focused, as stated already. h3. Expected behavior The connect form is a short form and the risk of accidental submission is small, so I'd expect submitting with enter from anywhere in the form would be enabled. Proper handling of focus is important usability concern. Depending whether or not is accessibility considered important for dispatch-console, this may deserve its own Jira. was: h3. Observed behavior When connecting to the router, after filling Address and Port, the only way to submit the form is to click the Connect button with mouse. Pressing enter while input fields of the form are focused does nothing. Tabbing to the Connect button is difficult, because the Connect button does not have a distinct focused appearance. Same is true for the Autoconnect checkbox. Pressing enter or space while the button is focused does click it. But there is no visual indication of the fact that the button is focused, as stated already. h3. Expected behavior The connect form is a short form and the risk of accidental submission is small, so I'd expect submitting with enter from anywhere in the form would be enabled. Proper handling of focus is important usability concern. Depending whether or not is accessibility considered important for dispatch-console, this may deserve its own Jira. > Connect form cannot be submitted using only keyboard > > > Key: DISPATCH-439 > URL: https://issues.apache.org/jira/browse/DISPATCH-439 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6.1 >Reporter: Jiri Danek > Labels: accessibility > > h3. Observed behavior > When connecting to the router, after filling Address and Port, the only way > to submit the form is to click the Connect button with mouse. > Pressing enter while input fields of the form are focused does nothing. > Tabbing to the Connect button is difficult, because the Connect button does > not have a distinct focused appearance. Same is true for the Autostart > checkbox. > Pressing enter or space while the button is focused does click it. But there > is no visual indication of the fact that the button is focused, as stated > already. > h3. Expected behavior > The connect form is a short form and the risk of accidental submission is > small, so I'd expect submitting with enter from anywhere in the form would be > enabled. > Proper handling of focus is important usability concern. Depending whether or > not is accessibility considered important for dispatch-console, this may > deserve its own Jira. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-440) Use the placeholder HTML attribute to communicate default values in the Connect form
Jiri Danek created DISPATCH-440: --- Summary: Use the placeholder HTML attribute to communicate default values in the Connect form Key: DISPATCH-440 URL: https://issues.apache.org/jira/browse/DISPATCH-440 Project: Qpid Dispatch Issue Type: Improvement Components: Console Affects Versions: 0.6.1 Reporter: Jiri Danek Priority: Minor Attachments: placeholder.png Default values for the Port field can be communicated to the user with the help of the placeholder HTML attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-440) Use the placeholder HTML attribute to communicate default values in the Connect form
[ https://issues.apache.org/jira/browse/DISPATCH-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-440: Description: Default value for the Port field can be communicated to the user with the help of the placeholder HTML attribute. (was: Default values for the Port field can be communicated to the user with the help of the placeholder HTML attribute.) > Use the placeholder HTML attribute to communicate default values in the > Connect form > > > Key: DISPATCH-440 > URL: https://issues.apache.org/jira/browse/DISPATCH-440 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Affects Versions: 0.6.1 >Reporter: Jiri Danek >Priority: Minor > Attachments: placeholder.png > > > Default value for the Port field can be communicated to the user with the > help of the placeholder HTML attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-440) Use the placeholder HTML attribute to communicate default values in the Connect form
[ https://issues.apache.org/jira/browse/DISPATCH-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-440: Attachment: placeholder.png > Use the placeholder HTML attribute to communicate default values in the > Connect form > > > Key: DISPATCH-440 > URL: https://issues.apache.org/jira/browse/DISPATCH-440 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Affects Versions: 0.6.1 >Reporter: Jiri Danek >Priority: Minor > Attachments: placeholder.png > > > Default values for the Port field can be communicated to the user with the > help of the placeholder HTML attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-439) Connect form cannot be submitted using only keyboard
Jiri Danek created DISPATCH-439: --- Summary: Connect form cannot be submitted using only keyboard Key: DISPATCH-439 URL: https://issues.apache.org/jira/browse/DISPATCH-439 Project: Qpid Dispatch Issue Type: Bug Components: Console Affects Versions: 0.6.1 Reporter: Jiri Danek h3. Observed behavior When connecting to the router, after filling Address and Port, the only way to submit the form is to click the Connect button with mouse. Pressing enter while input fields of the form are focused does nothing. Tabbing to the Connect button is difficult, because the Connect button does not have a distinct focused appearance. Same is true for the Autoconnect checkbox. Pressing enter or space while the button is focused does click it. But there is no visual indication of the fact that the button is focused, as stated already. h3. Expected behavior The connect form is a short form and the risk of accidental submission is small, so I'd expect submitting with enter from anywhere in the form would be enabled. Proper handling of focus is important usability concern. Depending whether or not is accessibility considered important for dispatch-console, this may deserve its own Jira. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-399) Convert documentation to asciidoc format
[ https://issues.apache.org/jira/browse/DISPATCH-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357645#comment-15357645 ] ASF subversion and git services commented on DISPATCH-399: -- Commit da6688a53475f80e7ff81adc65484f587efef876 in qpid-dispatch's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=da6688a ] DISPATCH-399: Fix out-dated console docs in asciidoc conversion. The console chapter of the user guide was converted to asciidoc from out-of-date documentaiton, this has been corrected. > Convert documentation to asciidoc format > > > Key: DISPATCH-399 > URL: https://issues.apache.org/jira/browse/DISPATCH-399 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Documentation >Affects Versions: 0.6.0 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Minor > Fix For: 0.7.0 > > > asciidoc format is becoming more popular for documentation and has several > advantages over RST + sphinx. > - Mature, widely-used DocBook model without painful XML syntax > - Multi-file documents and entity substitution are standard in asciidoc > (Sphinx has non-standard extensions, but not defined by RST) > - simpler, more flexible tools, fewer generation steps. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1228) Windows schannel needs default peer_hostname to match OpenSSL
[ https://issues.apache.org/jira/browse/PROTON-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357638#comment-15357638 ] ASF subversion and git services commented on PROTON-1228: - Commit ad532c392816dff3129e03e90e2e07cefe94618c in qpid-proton's branch refs/heads/0.13.x from Clifford Jansen [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=ad532c3 ] PROTON-1233: PROTON-1228: for 0.13.1, make schannel hostname behaviour like openssl > Windows schannel needs default peer_hostname to match OpenSSL > - > > Key: PROTON-1228 > URL: https://issues.apache.org/jira/browse/PROTON-1228 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.13.0, 0.14.0 > Environment: Windows >Reporter: Cliff Jansen >Assignee: Cliff Jansen > Fix For: 0.14.0 > > > The OpenSSL module sets a default peer_hostname from the bound connection. > schannel.c should do the same to behave the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1233) Windows schannel: match OpenSSL and require non-null hostname for PN_SSL_VERIFY_PEER_NAME
[ https://issues.apache.org/jira/browse/PROTON-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357637#comment-15357637 ] ASF subversion and git services commented on PROTON-1233: - Commit ad532c392816dff3129e03e90e2e07cefe94618c in qpid-proton's branch refs/heads/0.13.x from Clifford Jansen [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=ad532c3 ] PROTON-1233: PROTON-1228: for 0.13.1, make schannel hostname behaviour like openssl > Windows schannel: match OpenSSL and require non-null hostname for > PN_SSL_VERIFY_PEER_NAME > - > > Key: PROTON-1233 > URL: https://issues.apache.org/jira/browse/PROTON-1233 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Cliff Jansen >Assignee: Cliff Jansen > Fix For: 0.14.0 > > > A user should not be permitted to omit setting the peer hostname and use > verify peer name at the same time. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: [NOTICE] cease commits to cpp and python subdirs of svn trunk, migrating to git
On 30 June 2016 at 19:12, Andrew Stitcher wrote: > On Wed, 2016-06-29 at 13:18 +0100, Robbie Gemmell wrote: >> Hi folks, >> >> As per previous discussion/votes, the reorganised cpp and python bits >> will be migrating to their own git repositories. The migration is due >> to begin in the next hour or two. >> >> It isn't clear that the svn subdirs will actually be locked at this >> time, so please take note to cease committing to them. If they aren't >> locked (or I guess, even if they are..) we will need to decide what >> approach to take with the old dirs going forward, e.g clear the files >> out and leave a pointer file, eventually remove the dir, etc. > > As we only migrated trunk we need to leave branches unlocked for > possible maintainence. They will be, the notice is only about trunk. > > We should certainly consider just removing the trunk versions with a > little redirection README. > That would be my preference. (resend to include users@ this time) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: [NOTICE] cease commits to cpp and python subdirs of svn trunk, migrating to git
On 30 June 2016 at 19:12, Andrew Stitcher wrote: > On Wed, 2016-06-29 at 13:18 +0100, Robbie Gemmell wrote: >> Hi folks, >> >> As per previous discussion/votes, the reorganised cpp and python bits >> will be migrating to their own git repositories. The migration is due >> to begin in the next hour or two. >> >> It isn't clear that the svn subdirs will actually be locked at this >> time, so please take note to cease committing to them. If they aren't >> locked (or I guess, even if they are..) we will need to decide what >> approach to take with the old dirs going forward, e.g clear the files >> out and leave a pointer file, eventually remove the dir, etc. > > As we only migrated trunk we need to leave branches unlocked for > possible maintainence. They will be, the notice is only about trunk. > > We should certainly consider just removing the trunk versions with a > little redirection README. > That would be my preference. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: [NOTICE] cease commits to cpp and python subdirs of svn trunk, migrating to git
On Wed, 2016-06-29 at 13:18 +0100, Robbie Gemmell wrote: > Hi folks, > > As per previous discussion/votes, the reorganised cpp and python bits > will be migrating to their own git repositories. The migration is due > to begin in the next hour or two. > > It isn't clear that the svn subdirs will actually be locked at this > time, so please take note to cease committing to them. If they aren't > locked (or I guess, even if they are..) we will need to decide what > approach to take with the old dirs going forward, e.g clear the files > out and leave a pointer file, eventually remove the dir, etc. As we only migrated trunk we need to leave branches unlocked for possible maintainence. We should certainly consider just removing the trunk versions with a little redirection README. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1248) There is no way to query the state of deliveries or trackers
[ https://issues.apache.org/jira/browse/PROTON-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-1248: Fix Version/s: (was: 0.14.0) 0.13.1 > There is no way to query the state of deliveries or trackers > > > Key: PROTON-1248 > URL: https://issues.apache.org/jira/browse/PROTON-1248 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: 0.13.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.13.1 > > > proton::transfer which is the parent class of delivery and tracker has a > state() accessor and a state enum but these are protected and so cannot be > used directly by client code using delivery or tracker. > I think this is just a simple oversight and these should actually be public. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1247) Link errors when using proton::delivery::accept(), ...::reject() etc.
[ https://issues.apache.org/jira/browse/PROTON-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-1247: Fix Version/s: (was: 0.14.0) > Link errors when using proton::delivery::accept(), ...::reject() etc. > - > > Key: PROTON-1247 > URL: https://issues.apache.org/jira/browse/PROTON-1247 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: 0.13.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.13.1 > > > proton::transfer::settle(proton::delivery::state) is not an exported symbol, > but is used by inline functions in proton::delivery. This makes the final > link fail for any application that explicitly accepts or rejects etc. > messages. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1247) Link errors when using proton::delivery::accept(), ...::reject() etc.
[ https://issues.apache.org/jira/browse/PROTON-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-1247: Fix Version/s: 0.13.1 > Link errors when using proton::delivery::accept(), ...::reject() etc. > - > > Key: PROTON-1247 > URL: https://issues.apache.org/jira/browse/PROTON-1247 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: 0.13.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.14.0, 0.13.1 > > > proton::transfer::settle(proton::delivery::state) is not an exported symbol, > but is used by inline functions in proton::delivery. This makes the final > link fail for any application that explicitly accepts or rejects etc. > messages. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1233) Windows schannel: match OpenSSL and require non-null hostname for PN_SSL_VERIFY_PEER_NAME
[ https://issues.apache.org/jira/browse/PROTON-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357557#comment-15357557 ] Justin Ross commented on PROTON-1233: - Reviewed by Andrew. Approved for 0.13.1. > Windows schannel: match OpenSSL and require non-null hostname for > PN_SSL_VERIFY_PEER_NAME > - > > Key: PROTON-1233 > URL: https://issues.apache.org/jira/browse/PROTON-1233 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Cliff Jansen >Assignee: Cliff Jansen > Fix For: 0.14.0 > > > A user should not be permitted to omit setting the peer hostname and use > verify peer name at the same time. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1248) There is no way to query the state of deliveries or trackers
[ https://issues.apache.org/jira/browse/PROTON-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357577#comment-15357577 ] ASF subversion and git services commented on PROTON-1248: - Commit fd9d961b642587dd5df63b96088721c7a3226243 in qpid-proton's branch refs/heads/0.13.x from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=fd9d961 ] PROTON-1247: Fix symbol export for transfer, delivery & tracker PROTON-1248: Allow API to query state of delivery and tracker > There is no way to query the state of deliveries or trackers > > > Key: PROTON-1248 > URL: https://issues.apache.org/jira/browse/PROTON-1248 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: 0.13.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.14.0 > > > proton::transfer which is the parent class of delivery and tracker has a > state() accessor and a state enum but these are protected and so cannot be > used directly by client code using delivery or tracker. > I think this is just a simple oversight and these should actually be public. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1247) Link errors when using proton::delivery::accept(), ...::reject() etc.
[ https://issues.apache.org/jira/browse/PROTON-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357576#comment-15357576 ] ASF subversion and git services commented on PROTON-1247: - Commit fd9d961b642587dd5df63b96088721c7a3226243 in qpid-proton's branch refs/heads/0.13.x from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=fd9d961 ] PROTON-1247: Fix symbol export for transfer, delivery & tracker PROTON-1248: Allow API to query state of delivery and tracker > Link errors when using proton::delivery::accept(), ...::reject() etc. > - > > Key: PROTON-1247 > URL: https://issues.apache.org/jira/browse/PROTON-1247 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: 0.13.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.14.0 > > > proton::transfer::settle(proton::delivery::state) is not an exported symbol, > but is used by inline functions in proton::delivery. This makes the final > link fail for any application that explicitly accepts or rejects etc. > messages. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1228) Windows schannel needs default peer_hostname to match OpenSSL
[ https://issues.apache.org/jira/browse/PROTON-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357554#comment-15357554 ] Justin Ross commented on PROTON-1228: - Reviewed by Andrew. Approved for 0.13.1. > Windows schannel needs default peer_hostname to match OpenSSL > - > > Key: PROTON-1228 > URL: https://issues.apache.org/jira/browse/PROTON-1228 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.13.0, 0.14.0 > Environment: Windows >Reporter: Cliff Jansen >Assignee: Cliff Jansen > Fix For: 0.14.0 > > > The OpenSSL module sets a default peer_hostname from the bound connection. > schannel.c should do the same to behave the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1248) There is no way to query the state of deliveries or trackers
[ https://issues.apache.org/jira/browse/PROTON-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357543#comment-15357543 ] Justin Ross commented on PROTON-1248: - Approved for 0.13.1. > There is no way to query the state of deliveries or trackers > > > Key: PROTON-1248 > URL: https://issues.apache.org/jira/browse/PROTON-1248 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: 0.13.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.14.0 > > > proton::transfer which is the parent class of delivery and tracker has a > state() accessor and a state enum but these are protected and so cannot be > used directly by client code using delivery or tracker. > I think this is just a simple oversight and these should actually be public. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1249) proton-j: unsafe type initialisations
[ https://issues.apache.org/jira/browse/PROTON-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357526#comment-15357526 ] ASF GitHub Bot commented on PROTON-1249: Github user gemmellr commented on the issue: https://github.com/apache/qpid-proton/pull/76 Also, 0.13.1 is being cut tomorrow, this should probably go in it. > proton-j: unsafe type initialisations > - > > Key: PROTON-1249 > URL: https://issues.apache.org/jira/browse/PROTON-1249 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: 0.12.2 >Reporter: Dominic Evans >Assignee: Dominic Evans > Labels: proton-j, security > > In #readValue() for ArrayType, BinaryType, ListType and MapType > decoding, if the 'count' specified is very large then it is likely to > trigger an OutOfMemoryException. As these can come from an external data > source, during the SASL init for example, there is a potential for a > denial of service. The fix is to throw an IllegalArgumentException if > the count value is larger than the amount of data available in the > received bytes. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1249) proton-j: unsafe type initialisations
[ https://issues.apache.org/jira/browse/PROTON-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357525#comment-15357525 ] ASF GitHub Bot commented on PROTON-1249: Github user gemmellr commented on the issue: https://github.com/apache/qpid-proton/pull/76 raising the JIRA kind of does that too...if concerned about that, next time private@ :) > proton-j: unsafe type initialisations > - > > Key: PROTON-1249 > URL: https://issues.apache.org/jira/browse/PROTON-1249 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: 0.12.2 >Reporter: Dominic Evans >Assignee: Dominic Evans > Labels: proton-j, security > > In #readValue() for ArrayType, BinaryType, ListType and MapType > decoding, if the 'count' specified is very large then it is likely to > trigger an OutOfMemoryException. As these can come from an external data > source, during the SASL init for example, there is a potential for a > denial of service. The fix is to throw an IllegalArgumentException if > the count value is larger than the amount of data available in the > received bytes. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton issue #76: PROTON-1249: Safeguard type initialisations.
Github user gemmellr commented on the issue: https://github.com/apache/qpid-proton/pull/76 Also, 0.13.1 is being cut tomorrow, this should probably go in it. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton issue #76: PROTON-1249: Safeguard type initialisations.
Github user gemmellr commented on the issue: https://github.com/apache/qpid-proton/pull/76 raising the JIRA kind of does that too...if concerned about that, next time private@ :) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1247) Link errors when using proton::delivery::accept(), ...::reject() etc.
[ https://issues.apache.org/jira/browse/PROTON-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357524#comment-15357524 ] Justin Ross commented on PROTON-1247: - Approved for 0.13.1. > Link errors when using proton::delivery::accept(), ...::reject() etc. > - > > Key: PROTON-1247 > URL: https://issues.apache.org/jira/browse/PROTON-1247 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: 0.13.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.14.0 > > > proton::transfer::settle(proton::delivery::state) is not an exported symbol, > but is used by inline functions in proton::delivery. This makes the final > link fail for any application that explicitly accepts or rejects etc. > messages. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1249) proton-j: unsafe type initialisations
[ https://issues.apache.org/jira/browse/PROTON-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357520#comment-15357520 ] ASF GitHub Bot commented on PROTON-1249: Github user dnwe commented on the issue: https://github.com/apache/qpid-proton/pull/76 Yeah. I wasn't 100% sure about putting unittests in as then it would make the attack obvious ¯\_(ツ)_/¯ > proton-j: unsafe type initialisations > - > > Key: PROTON-1249 > URL: https://issues.apache.org/jira/browse/PROTON-1249 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: 0.12.2 >Reporter: Dominic Evans >Assignee: Dominic Evans > Labels: proton-j, security > > In #readValue() for ArrayType, BinaryType, ListType and MapType > decoding, if the 'count' specified is very large then it is likely to > trigger an OutOfMemoryException. As these can come from an external data > source, during the SASL init for example, there is a potential for a > denial of service. The fix is to throw an IllegalArgumentException if > the count value is larger than the amount of data available in the > received bytes. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton issue #76: PROTON-1249: Safeguard type initialisations.
Github user dnwe commented on the issue: https://github.com/apache/qpid-proton/pull/76 Yeah. I wasn't 100% sure about putting unittests in as then it would make the attack obvious ¯\_(ã)_/¯ --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1249) proton-j: unsafe type initialisations
[ https://issues.apache.org/jira/browse/PROTON-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357515#comment-15357515 ] ASF GitHub Bot commented on PROTON-1249: Github user gemmellr commented on the issue: https://github.com/apache/qpid-proton/pull/76 Changes look reasonable. Some tests might be nice ;) > proton-j: unsafe type initialisations > - > > Key: PROTON-1249 > URL: https://issues.apache.org/jira/browse/PROTON-1249 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: 0.12.2 >Reporter: Dominic Evans >Assignee: Dominic Evans > Labels: proton-j, security > > In #readValue() for ArrayType, BinaryType, ListType and MapType > decoding, if the 'count' specified is very large then it is likely to > trigger an OutOfMemoryException. As these can come from an external data > source, during the SASL init for example, there is a potential for a > denial of service. The fix is to throw an IllegalArgumentException if > the count value is larger than the amount of data available in the > received bytes. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton issue #76: PROTON-1249: Safeguard type initialisations.
Github user gemmellr commented on the issue: https://github.com/apache/qpid-proton/pull/76 Changes look reasonable. Some tests might be nice ;) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7248) Extend the UI to allow queries to be saved, retrieved and re-run
[ https://issues.apache.org/jira/browse/QPID-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7248: - Attachment: query-browser-patches.tar.gz > Extend the UI to allow queries to be saved, retrieved and re-run > > > Key: QPID-7248 > URL: https://issues.apache.org/jira/browse/QPID-7248 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall > Fix For: qpid-java-6.1 > > Attachments: extend-query-ui-to-allow-queries-to-be-saved.tar.gz, > query-browser-patches.tar.gz > > > Extend the UI to allow the user to save a query so that it is available for > use later on. The user should be able to see a list of saved queries, pick > one and rerun it or change it. The user should be able to delete queries too. > The user should also be able to see queries that are visible to him. He > should be able to select these queries and execute them. > * When defining a query, the UI should offer a 'save as' button allowing the > query to be named, visibility to be chosen, and saved. > * If the query has been saved already, the name should be filled in already. > * Saved queries and queries that are visible to the user will appear to the > user as a list (expandable/collapsible widget) > * From the list the user will be able to delete queries that belong to him. > * Also from the list, the user will be able to recall queries (either queries > that belong to him or ones that are visible). The query will be recalled in > the advanced > view, even if the query is representable in standard view. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-438) A policyRuleset cannot be created through the dispatch-plugin
[
https://issues.apache.org/jira/browse/DISPATCH-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek updated DISPATCH-438:
Attachment: policyRuleset.png
> A policyRuleset cannot be created through the dispatch-plugin
> -
>
> Key: DISPATCH-438
> URL: https://issues.apache.org/jira/browse/DISPATCH-438
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
>Affects Versions: 0.6.1
>Reporter: Jiri Danek
> Attachments: policyRuleset.png
>
>
> I use qdrouterd with the standard configuration (+the console section).
> Navigate to Entities tab, open policyRuleset in the tree on the left and
> click on Create.
> Fill in some values, but regardless of what i type to the Application name
> field, after i click the blue Create button, I get a toast with message
> {{Cannot set attribute 'applicationName' in CREATE}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-438) A policyRuleset cannot be created through the dispatch-plugin
Jiri Danek created DISPATCH-438:
---
Summary: A policyRuleset cannot be created through the
dispatch-plugin
Key: DISPATCH-438
URL: https://issues.apache.org/jira/browse/DISPATCH-438
Project: Qpid Dispatch
Issue Type: Bug
Components: Console
Affects Versions: 0.6.1
Reporter: Jiri Danek
I use qdrouterd with the standard configuration (+the console section).
Navigate to Entities tab, open policyRuleset in the tree on the left and click
on Create.
Fill in some values, but regardless of what i type to the Application name
field, after i click the blue Create button, I get a toast with message
{{Cannot set attribute 'applicationName' in CREATE}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-437) Reconcile C and python management agents
Alan Conway created DISPATCH-437: Summary: Reconcile C and python management agents Key: DISPATCH-437 URL: https://issues.apache.org/jira/browse/DISPATCH-437 Project: Qpid Dispatch Issue Type: Bug Components: Management Agent Affects Versions: 0.6.0 Reporter: Alan Conway Assignee: Ted Ross The router now has two management agents, one in C and one in Python. They have overlapping and inconsistent functionality, which creates a difficult user experience. They need to be more closely aligned. Issues noted so far: - python agent "identity" attribute is unique per-agent. C agent "identity" is only unique per type and cannot be used in READ requests (DISPATCH-409) - python agent allows delete by name or identity alone, C agent requires the client specify the type as well (DISPATCH-408) - C agent does not do string conversions for integral attribute types as reqiured by the management spec. The "fix" in qdmanage is incorrect (DISPATCH-411) I recommend that we need: 1. A single code path to validate/convert/insert defaults in incoming requests based on the schema. 2. A clear, documented statement of what "identity" means and whether it is type-scoped or agent-scoped, with a re-implementation of either the C or python entities to comply. We may need to rework the interface between python and C to make it efficient and thread-safe, or refactor some/all of the python functionality as C, but we do need to get rid of the redundancy and inconsistency. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-7047) SaslServlet should invalidate the HTTP session in the event of authentication/authorisation failure
[ https://issues.apache.org/jira/browse/QPID-7047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack resolved QPID-7047. Resolution: Fixed Assignee: Lorenz Quack (was: Alex Rudyy) looks good to me > SaslServlet should invalidate the HTTP session in the event of > authentication/authorisation failure > --- > > Key: QPID-7047 > URL: https://issues.apache.org/jira/browse/QPID-7047 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Lorenz Quack > Fix For: qpid-java-6.1 > > > If SASL authentication over HTTP fails, the HTTP session is currently > retained. This should be changed so that it is automatically invalidated on > these two paths. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-436) Releasing the mouse button outside of the Topology SVG when dragging a node causes the node follow the mouse even if the mouse button is not pressed
Jiri Danek created DISPATCH-436: --- Summary: Releasing the mouse button outside of the Topology SVG when dragging a node causes the node follow the mouse even if the mouse button is not pressed Key: DISPATCH-436 URL: https://issues.apache.org/jira/browse/DISPATCH-436 Project: Qpid Dispatch Issue Type: Bug Components: Console Affects Versions: 0.6.1 Reporter: Jiri Danek Navigate to the Topology page, click a node, drag it to the corner, continue moving the mouse outside of the topology SVG, then release mouse button. Move the mouse inside the SVG without pressing any buttons and watch the node follow the mouse. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-435) Dragging a node to a corner on the topology screen leads to a visual disconnect between the node and its link
[ https://issues.apache.org/jira/browse/DISPATCH-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-435: Attachment: topologyDisconnect.png > Dragging a node to a corner on the topology screen leads to a visual > disconnect between the node and its link > - > > Key: DISPATCH-435 > URL: https://issues.apache.org/jira/browse/DISPATCH-435 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6.1 >Reporter: Jiri Danek > Attachments: topologyDisconnect.png > > > Open the Topology tab and drag a node to the upper left corner. The circular > icon representing the node gets disconnected from the line segment > representing a link between the node and the router. > I believe this is because the node icon sticks to the mouse, but the line > also follows the mouse, not the center of the icon. Because the line can be > brought closer to the edge than the circle, c.f. DISPATCH-318, they stop > touching. > This is a GUI/visualization problem. The actual link on the router is not > affected. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-435) Dragging a node to a corner on the topology screen leads to a visual disconnect between the node and its link
Jiri Danek created DISPATCH-435: --- Summary: Dragging a node to a corner on the topology screen leads to a visual disconnect between the node and its link Key: DISPATCH-435 URL: https://issues.apache.org/jira/browse/DISPATCH-435 Project: Qpid Dispatch Issue Type: Bug Components: Console Affects Versions: 0.6.1 Reporter: Jiri Danek Open the Topology tab and drag a node to the upper left corner. The circular icon representing the node gets disconnected from the line segment representing a link between the node and the router. I believe this is because the node icon sticks to the mouse, but the line also follows the mouse, not the center of the icon. Because the line can be brought closer to the edge than the circle, c.f. DISPATCH-318, they stop touching. This is a GUI/visualization problem. The actual link on the router is not affected. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-434) Remember all entities expanded on overview page
[ https://issues.apache.org/jira/browse/DISPATCH-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-434: Affects Version/s: 0.6.1 Description: This is a natural extension to feature DISPATCH-400 Remember last entity expanded on overview page. Since more than one entity can be expanded, c.f. DISPATCH-426, all expanded entities should be remembered. Component/s: Console Issue Type: Improvement (was: Bug) Summary: Remember all entities expanded on overview page (was: Rem) > Remember all entities expanded on overview page > --- > > Key: DISPATCH-434 > URL: https://issues.apache.org/jira/browse/DISPATCH-434 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Affects Versions: 0.6.1 >Reporter: Jiri Danek > > This is a natural extension to feature DISPATCH-400 Remember last entity > expanded on overview page. Since more than one entity can be expanded, c.f. > DISPATCH-426, all expanded entities should be remembered. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-434) Rem
Jiri Danek created DISPATCH-434: --- Summary: Rem Key: DISPATCH-434 URL: https://issues.apache.org/jira/browse/DISPATCH-434 Project: Qpid Dispatch Issue Type: Bug Reporter: Jiri Danek -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-433) Navigating to console from bookmark displays empty page with just toolbars
[ https://issues.apache.org/jira/browse/DISPATCH-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-433: Affects Version/s: 0.6.1 Component/s: Console > Navigating to console from bookmark displays empty page with just toolbars > -- > > Key: DISPATCH-433 > URL: https://issues.apache.org/jira/browse/DISPATCH-433 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6.1 >Reporter: Jiri Danek > Attachments: overview.png > > > Judging by the description on DISPATCH-275, when navigating to > http://127.0.0.1:8080/hawtio/dispatch_plugin/overview from a bookmark or by > entering the URL directly, I should be redirected to the Connect page. > What actually happens is that I am shown an empty page with just toolbars. > The dialog for connecting to router is not displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-433) Navigating to console from bookmark displays empty page with just toolbars
[ https://issues.apache.org/jira/browse/DISPATCH-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-433: Attachment: overview.png > Navigating to console from bookmark displays empty page with just toolbars > -- > > Key: DISPATCH-433 > URL: https://issues.apache.org/jira/browse/DISPATCH-433 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6.1 >Reporter: Jiri Danek > Attachments: overview.png > > > Judging by the description on DISPATCH-275, when navigating to > http://127.0.0.1:8080/hawtio/dispatch_plugin/overview from a bookmark or by > entering the URL directly, I should be redirected to the Connect page. > What actually happens is that I am shown an empty page with just toolbars. > The dialog for connecting to router is not displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-433) Navigating to console from bookmark displays empty page with just toolbars
Jiri Danek created DISPATCH-433: --- Summary: Navigating to console from bookmark displays empty page with just toolbars Key: DISPATCH-433 URL: https://issues.apache.org/jira/browse/DISPATCH-433 Project: Qpid Dispatch Issue Type: Bug Reporter: Jiri Danek Judging by the description on DISPATCH-275, when navigating to http://127.0.0.1:8080/hawtio/dispatch_plugin/overview from a bookmark or by entering the URL directly, I should be redirected to the Connect page. What actually happens is that I am shown an empty page with just toolbars. The dialog for connecting to router is not displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-432) Qpid Dispatch Router does not close connection to Broker on exit
Jiri Danek created DISPATCH-432:
---
Summary: Qpid Dispatch Router does not close connection to Broker
on exit
Key: DISPATCH-432
URL: https://issues.apache.org/jira/browse/DISPATCH-432
Project: Qpid Dispatch
Issue Type: Bug
Affects Versions: 0.6.0
Reporter: Jiri Danek
I have the following configuration for connecting to broker in my
{{qdrouterd.conf}}
{noformat}
connector {
name: ba
role: route-container
host: 172.28.128.221
port: amqp
sasl-mechanisms: ANONYMOUS
}
address {
prefix: jms.queue
waypoint: yes
}
autoLink {
addr: jms.queue.first
dir: in
connection: ba
}
autoLink {
addr: jms.queue.first
dir: out
connection: ba
}
autoLink {
addr: jms.queue.second
dir: in
connection: ba
}
autoLink {
addr: jms.queue.second
dir: out
connection: ba
}
{noformat}
If I stop dispatch demon with {{sudo service qdrouterd stop}} and then kill
Artemis broker with ^C, broker prints the following
{noformat}
12:18:04,721 INFO [org.apache.activemq.artemis] AMQ241001: HTTP Server started
at http://localhost:8161
12:18:04,722 INFO [org.apache.activemq.artemis] AMQ241002: Artemis Jolokia
REST API available at http://localhost:8161/jolokia
^C12:18:16,881 ERROR [org.apache.activemq.artemis.core.server] AMQ224065:
Failed to remove auto-created queue jms.queue.second:
java.lang.IllegalStateException: Cannot access JMS Server, core server is not
active
at
org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.checkInitialised(JMSServerManagerImpl.java:1416)
[artemis-jms-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.destroyQueue(JMSServerManagerImpl.java:766)
[artemis-jms-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl$JMSQueueDeleter.delete(JMSServerManagerImpl.java:1639)
[artemis-jms-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.core.server.impl.AutoCreatedQueueManagerImpl$1.run(AutoCreatedQueueManagerImpl.java:50)
[artemis-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.utils.ReferenceCounterUtil.decrement(ReferenceCounterUtil.java:55)
[artemis-commons-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.core.server.impl.AutoCreatedQueueManagerImpl.decrement(AutoCreatedQueueManagerImpl.java:78)
[artemis-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.core.server.impl.QueueImpl.removeConsumer(QueueImpl.java:768)
[artemis-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.removeItself(ServerConsumerImpl.java:500)
[artemis-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.close(ServerConsumerImpl.java:446)
[artemis-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.doClose(ServerSessionImpl.java:345)
[artemis-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.core.server.impl.ServerSessionImpl$1.done(ServerSessionImpl.java:1160)
[artemis-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.core.persistence.impl.journal.OperationContextImpl.executeOnCompletion(OperationContextImpl.java:168)
[artemis-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.close(ServerSessionImpl.java:1152)
[artemis-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.freezeConnections(ActiveMQServerImpl.java:926)
[artemis-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:741)
[artemis-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:654)
[artemis-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:547)
[artemis-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.stop(JMSServerManagerImpl.java:407)
[artemis-jms-server-1.2.0.amq-77-redhat-1.jar:1.2.0.amq-77-redhat-1]
at
[jira] [Commented] (QPID-7224) Exposed truststores should exclude/include based on virtualhostnode rather than virtualhost
[ https://issues.apache.org/jira/browse/QPID-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357112#comment-15357112 ] ASF subversion and git services commented on QPID-7224: --- Commit 1750798 from [~lorenz.quack] in branch 'java/trunk' [ https://svn.apache.org/r1750798 ] QPID-7224: [Java Broker] Exposed TrustStores should include/exclude based on VirtualHostNodes rather than VirtualHosts > Exposed truststores should exclude/include based on virtualhostnode rather > than virtualhost > --- > > Key: QPID-7224 > URL: https://issues.apache.org/jira/browse/QPID-7224 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Keith Wall > Fix For: qpid-java-6.1 > > > Truststores can be exposed as a message sources to clients for the purposes > of public key distribution for end-to-end message encryption. > If a truststore is exposed, by default the truststore is exposed to all > virtualhosts. The user can opt to make this more restrictive by opting to > include or exclude virtualhosts. > The inclusion/exclusion based on virtualhost is problematic in the HA case, > as the virtualhost may be elsewhere in the group. This would prevent the > Truststore from starting (it would go into error). > The Truststore implementations must change to have inclusion/exclusion based > on virtualhostnode. > The configuration upgrader will need to guess that the virtualhostnode name > is the same as the virtualhost. This will work with default configuration in > the non-HA case (where virtualhostnode name = virtualhost name), but will > fail in the HA case. > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-431) Do not link to http://127.0.0.1:8080/dispatch-plugin
[ https://issues.apache.org/jira/browse/DISPATCH-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-431: Attachment: dispatch-plugin.png applications.png > Do not link to http://127.0.0.1:8080/dispatch-plugin > > > Key: DISPATCH-431 > URL: https://issues.apache.org/jira/browse/DISPATCH-431 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6.1 >Reporter: Jiri Danek > Attachments: applications.png, dispatch-plugin.png > > > I installed dispatch-plugin to tomcat. Page > http://127.0.0.1:8080/hawtio/tomcat/applications shows URL > http://127.0.0.1:8080/dispatch-plugin. There is nothing on that address > except error page. I'd expect that the page does not link to pages that show > only errors and are otherwise useless. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-431) Do not link to http://127.0.0.1:8080/dispatch-plugin
Jiri Danek created DISPATCH-431: --- Summary: Do not link to http://127.0.0.1:8080/dispatch-plugin Key: DISPATCH-431 URL: https://issues.apache.org/jira/browse/DISPATCH-431 Project: Qpid Dispatch Issue Type: Bug Components: Console Affects Versions: 0.6.1 Reporter: Jiri Danek I installed dispatch-plugin to tomcat. Page http://127.0.0.1:8080/hawtio/tomcat/applications shows URL http://127.0.0.1:8080/dispatch-plugin. There is nothing on that address except error page. I'd expect that the page does not link to pages that show only errors and are otherwise useless. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-430) Cursor snaps way above peeks in a rate chart
[ https://issues.apache.org/jira/browse/DISPATCH-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-430: Attachment: (was: chartPeeks.png) > Cursor snaps way above peeks in a rate chart > > > Key: DISPATCH-430 > URL: https://issues.apache.org/jira/browse/DISPATCH-430 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6.1 >Reporter: Jiri Danek > Attachments: chartPeeks.png > > > Add a chart. Delivery Count on a link is a good variable, because it changes > quickly. Click Configure button on the chart. Change chart type to Rate > chart. On the Duration tab set duration to something short, like 2 minutes. > Apply and close. > Position your mouse cursor under a peek in the chart. The circle that is > supposed to follow the mouse cursor and snap to the curve is placed way above > the peak. > If the chart rolls to the left under the mouse, which happens every time the > chart updates, the position of the snappy circle is not updated to match the > new height of the chart line. until I move my mouse. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-430) Cursor snaps way above peeks in a rate chart
[ https://issues.apache.org/jira/browse/DISPATCH-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-430: Attachment: chartPeeks.png > Cursor snaps way above peeks in a rate chart > > > Key: DISPATCH-430 > URL: https://issues.apache.org/jira/browse/DISPATCH-430 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6.1 >Reporter: Jiri Danek > Attachments: chartPeeks.png > > > Add a chart. Delivery Count on a link is a good variable, because it changes > quickly. Click Configure button on the chart. Change chart type to Rate > chart. On the Duration tab set duration to something short, like 2 minutes. > Apply and close. > Position your mouse cursor under a peek in the chart. The circle that is > supposed to follow the mouse cursor and snap to the curve is placed way above > the peak. > If the chart rolls to the left under the mouse, which happens every time the > chart updates, the position of the snappy circle is not updated to match the > new height of the chart line. until I move my mouse. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-430) Cursor snaps way above peeks in a rate chart
[ https://issues.apache.org/jira/browse/DISPATCH-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-430: Attachment: chartPeeks.png > Cursor snaps way above peeks in a rate chart > > > Key: DISPATCH-430 > URL: https://issues.apache.org/jira/browse/DISPATCH-430 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6.1 >Reporter: Jiri Danek > Attachments: chartPeeks.png > > > Add a chart. Delivery Count on a link is a good variable, because it changes > quickly. Click Configure button on the chart. Change chart type to Rate > chart. On the Duration tab set duration to something short, like 2 minutes. > Apply and close. > Position your mouse cursor under a peek in the chart. The circle that is > supposed to follow the mouse cursor and snap to the curve is placed way above > the peak. > If the chart rolls to the left under the mouse, which happens every time the > chart updates, the position of the snappy circle is not updated to match the > new height of the chart line. until I move my mouse. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-430) Cursor snaps way above peeks in a rate chart
Jiri Danek created DISPATCH-430: --- Summary: Cursor snaps way above peeks in a rate chart Key: DISPATCH-430 URL: https://issues.apache.org/jira/browse/DISPATCH-430 Project: Qpid Dispatch Issue Type: Bug Components: Console Affects Versions: 0.6.1 Reporter: Jiri Danek Add a chart. Delivery Count on a link is a good variable, because it changes quickly. Click Configure button on the chart. Change chart type to Rate chart. On the Duration tab set duration to something short, like 2 minutes. Apply and close. Position your mouse cursor under a peek in the chart. The circle that is supposed to follow the mouse cursor and snap to the curve is placed way above the peak. If the chart rolls to the left under the mouse, which happens every time the chart updates, the position of the snappy circle is not updated to match the new height of the chart line. until I move my mouse. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1249) proton-j: unsafe type initialisations
[ https://issues.apache.org/jira/browse/PROTON-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356975#comment-15356975 ] ASF GitHub Bot commented on PROTON-1249: GitHub user dnwe opened a pull request: https://github.com/apache/qpid-proton/pull/76 PROTON-1249: Safeguard type initialisations. In #readValue() for ArrayType, BinaryType, ListType and MapType decoding, if the 'count' specified is very large then it is likely to trigger an OutOfMemoryException. As these can come from an external data source, during the SASL init for example, there is a potential for a denial of service. The fix is to throw an IllegalArgumentException if the count value is larger than the amount of data available in the received bytes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/dnwe/qpid-proton PROTON-1249 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/76.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #76 commit 0c92828864118517f8d8a23a2801da82852cf36c Author: Dominic Evans Date: 2016-03-18T11:20:23Z PROTON-1249: Safeguard type initialisations. In #readValue() for ArrayType, BinaryType, ListType and MapType decoding, if the 'count' specified is very large then it is likely to trigger an OutOfMemoryException. As these can come from an external data source, during the SASL init for example, there is a potential for a denial of service. The fix is to throw an IllegalArgumentException if the count value is larger than the amount of data available in the received bytes. > proton-j: unsafe type initialisations > - > > Key: PROTON-1249 > URL: https://issues.apache.org/jira/browse/PROTON-1249 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: 0.12.2 >Reporter: Dominic Evans >Assignee: Dominic Evans > Labels: proton-j, security > > In #readValue() for ArrayType, BinaryType, ListType and MapType > decoding, if the 'count' specified is very large then it is likely to > trigger an OutOfMemoryException. As these can come from an external data > source, during the SASL init for example, there is a potential for a > denial of service. The fix is to throw an IllegalArgumentException if > the count value is larger than the amount of data available in the > received bytes. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton pull request #76: PROTON-1249: Safeguard type initialisations.
GitHub user dnwe opened a pull request: https://github.com/apache/qpid-proton/pull/76 PROTON-1249: Safeguard type initialisations. In #readValue() for ArrayType, BinaryType, ListType and MapType decoding, if the 'count' specified is very large then it is likely to trigger an OutOfMemoryException. As these can come from an external data source, during the SASL init for example, there is a potential for a denial of service. The fix is to throw an IllegalArgumentException if the count value is larger than the amount of data available in the received bytes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/dnwe/qpid-proton PROTON-1249 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/76.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #76 commit 0c92828864118517f8d8a23a2801da82852cf36c Author: Dominic Evans Date: 2016-03-18T11:20:23Z PROTON-1249: Safeguard type initialisations. In #readValue() for ArrayType, BinaryType, ListType and MapType decoding, if the 'count' specified is very large then it is likely to trigger an OutOfMemoryException. As these can come from an external data source, during the SASL init for example, there is a potential for a denial of service. The fix is to throw an IllegalArgumentException if the count value is larger than the amount of data available in the received bytes. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1249) proton-j: unsafe type initialisations
Dominic Evans created PROTON-1249: - Summary: proton-j: unsafe type initialisations Key: PROTON-1249 URL: https://issues.apache.org/jira/browse/PROTON-1249 Project: Qpid Proton Issue Type: Bug Components: proton-j Affects Versions: 0.12.2 Reporter: Dominic Evans Assignee: Dominic Evans In #readValue() for ArrayType, BinaryType, ListType and MapType decoding, if the 'count' specified is very large then it is likely to trigger an OutOfMemoryException. As these can come from an external data source, during the SASL init for example, there is a potential for a denial of service. The fix is to throw an IllegalArgumentException if the count value is larger than the amount of data available in the received bytes. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-429) Empty string passed to getElementById()
[
https://issues.apache.org/jira/browse/DISPATCH-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek updated DISPATCH-429:
Attachment: emptystringpassed.png
> Empty string passed to getElementById()
> ---
>
> Key: DISPATCH-429
> URL: https://issues.apache.org/jira/browse/DISPATCH-429
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
>Affects Versions: 0.6.1
>Reporter: Jiri Danek
>Priority: Minor
> Attachments: emptystringpassed.png
>
>
> Clicking at table rows in the console, e.g. the "Router.A" row on the page
> that appears after successful login onto router using default configuration
> (plus a console section, naturally) results in {{Empty string passed to
> getElementById()}} error in the browser JS console (displayed with
> Ctrl+Shift+C in Chromium)
> This error seems to be completely harmless regarding functionality.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-429) Empty string passed to getElementById()
Jiri Danek created DISPATCH-429:
---
Summary: Empty string passed to getElementById()
Key: DISPATCH-429
URL: https://issues.apache.org/jira/browse/DISPATCH-429
Project: Qpid Dispatch
Issue Type: Bug
Components: Console
Affects Versions: 0.6.1
Reporter: Jiri Danek
Priority: Minor
Clicking at table rows in the console, e.g. the "Router.A" row on the page that
appears after successful login onto router using default configuration (plus a
console section, naturally) results in {{Empty string passed to
getElementById()}} error in the browser JS console (displayed with Ctrl+Shift+C
in Chromium)
This error seems to be completely harmless regarding functionality.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-428) Connecting the dispatch-console to wrong port throws JS exception and freezes console
[
https://issues.apache.org/jira/browse/DISPATCH-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek updated DISPATCH-428:
Attachment: port-5.png
> Connecting the dispatch-console to wrong port throws JS exception and freezes
> console
> -
>
> Key: DISPATCH-428
> URL: https://issues.apache.org/jira/browse/DISPATCH-428
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Console
>Affects Versions: 0.6.1
>Reporter: Jiri Danek
> Attachments: port-5.png
>
>
> Connect the console to
> Address: 127.0.0.1
> Port: -5
> After clicking the connect button, the rotating dots appear, a toast with JS
> exception appears and the console stays stuck on the rotating dots.
> {noformat}
> Error: Error: An invalid or illegal string was specified
> Stack trace:
> Error: An invalid or illegal string was specified
> require<[14]http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2
> line 1 > eval:44:764
> require<[1]http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2
> line 1 > eval:3:4056
> require<[1]http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2
> line 1 > eval:3:3637
> require<.rheahttp://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2
> line 1 > eval:87:767
> self.connect@http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2 line 1
> > eval:785:30
> $scope.connect@http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2 line
> 1 > eval:118:9
> G/<@http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2:14:22104
> qd[b]http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2:16:401
> ib/this.$gethttp://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2:14:31528
> ib/this.$gethttp://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2:14:31634
> qd[b]http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2:16:381
> $.event.dispatch@http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2:2:18633
> $.event.add/h@http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2:2:14597
> {noformat}
> I would expect that some input validation is done as I type the values or
> possibly as I click the Connect button.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-428) Connecting the dispatch-console to wrong port throws JS exception and freezes console
Jiri Danek created DISPATCH-428:
---
Summary: Connecting the dispatch-console to wrong port throws JS
exception and freezes console
Key: DISPATCH-428
URL: https://issues.apache.org/jira/browse/DISPATCH-428
Project: Qpid Dispatch
Issue Type: Improvement
Components: Console
Affects Versions: 0.6.1
Reporter: Jiri Danek
Connect the console to
Address: 127.0.0.1
Port: -5
After clicking the connect button, the rotating dots appear, a toast with JS
exception appears and the console stays stuck on the rotating dots.
{noformat}
Error: Error: An invalid or illegal string was specified
Stack trace:
Error: An invalid or illegal string was specified
require<[14]http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2
line 1 > eval:44:764
require<[1]http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2
line 1 > eval:3:4056
require<[1]http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2
line 1 > eval:3:3637
require<.rheahttp://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2
line 1 > eval:87:767
self.connect@http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2 line 1 >
eval:785:30
$scope.connect@http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2 line 1
> eval:118:9
G/<@http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2:14:22104
qd[b]http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2:16:401
ib/this.$gethttp://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2:14:31528
ib/this.$gethttp://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2:14:31634
qd[b]http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2:16:381
$.event.dispatch@http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2:2:18633
$.event.add/h@http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2:2:14597
{noformat}
I would expect that some input validation is done as I type the values or
possibly as I click the Connect button.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-427) Implement expand/collapse all to the Overview and Entities tabs
Jiri Danek created DISPATCH-427: --- Summary: Implement expand/collapse all to the Overview and Entities tabs Key: DISPATCH-427 URL: https://issues.apache.org/jira/browse/DISPATCH-427 Project: Qpid Dispatch Issue Type: Improvement Components: Console Affects Versions: 0.6.1 Reporter: Jiri Danek Attachments: expandCollapseAll.png Hawtio console page http://127.0.0.1:8080/hawtio/jmx/attributes has expand/collapse all buttons on top of the tree view on the left side. Those are the grey arrows above the tree view. I wish to have the same feature in dispatch-plugin pages. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-427) Implement expand/collapse all to the Overview and Entities tabs
[ https://issues.apache.org/jira/browse/DISPATCH-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-427: Attachment: expandCollapseAll.png > Implement expand/collapse all to the Overview and Entities tabs > --- > > Key: DISPATCH-427 > URL: https://issues.apache.org/jira/browse/DISPATCH-427 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Affects Versions: 0.6.1 >Reporter: Jiri Danek > Attachments: expandCollapseAll.png > > > Hawtio console page http://127.0.0.1:8080/hawtio/jmx/attributes has > expand/collapse all buttons on top of the tree view on the left side. Those > are the grey arrows above the tree view. I wish to have the same feature in > dispatch-plugin pages. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6984) [Web Management Console] Allow queries to be saved for later use
[ https://issues.apache.org/jira/browse/QPID-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6984: - Summary: [Web Management Console] Allow queries to be saved for later use (was: [Web Management Console] Allow queries to the saved for later use) > [Web Management Console] Allow queries to be saved for later use > > > Key: QPID-6984 > URL: https://issues.apache.org/jira/browse/QPID-6984 > Project: Qpid > Issue Type: Improvement >Reporter: Keith Wall > Fix For: qpid-java-6.1 > > > After defining a query (QPID-6969) the user should be able to save query so > it may be conveniently re-run at a later time either during the same session, > or future sessions (after logging in again). The user should also have the > ability to recall an existing query for edit, or delete a query. In the long > term queries should be sharable amongst members of a group. > This will require the ability to persist the query to the configuration > store. To support HA properly, a query defined against a virtual host when > the mastership is a node A should be still available to the user when the > mastership flips to another node. This implies that virtual host based > queries should be part of the virtualhost's configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6984) [Web Management Console] Allow queries to be saved for later use
[ https://issues.apache.org/jira/browse/QPID-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6984: - Fix Version/s: qpid-java-6.1 > [Web Management Console] Allow queries to be saved for later use > > > Key: QPID-6984 > URL: https://issues.apache.org/jira/browse/QPID-6984 > Project: Qpid > Issue Type: Improvement >Reporter: Keith Wall > Fix For: qpid-java-6.1 > > > After defining a query (QPID-6969) the user should be able to save query so > it may be conveniently re-run at a later time either during the same session, > or future sessions (after logging in again). The user should also have the > ability to recall an existing query for edit, or delete a query. In the long > term queries should be sharable amongst members of a group. > This will require the ability to persist the query to the configuration > store. To support HA properly, a query defined against a virtual host when > the mastership is a node A should be still available to the user when the > mastership flips to another node. This implies that virtual host based > queries should be part of the virtualhost's configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: [NOTICE] cease commits to cpp and python subdirs of svn trunk, migrating to git
The repositories that exist were created several days ago for testing purposes, as the migration is unusual given the structure of the svn repo. The actual migration has not actually been performed yet (I'm guessing due to the JIRA issues), I'll post a further update when it is. Robbie On 30 June 2016 at 10:38, Oleksandr Rudyy wrote: > Hi, > > It looks like a number of commits is missed in git repo. > > I tried to compile cpp sources from > https://git-wip-us.apache.org/repos/asf/qpid-cpp.git but compilation > failed. > > The compilation errors are similar to the ones reported by Keith > couple days ago. The fixes have been made as part of QPID-7306. > > Here is an extract from build output with compilation failures: > > > [ 57%] Building CXX object > src/CMakeFiles/qpidmessaging.dir/qpid/messaging/FailoverUpdates.cpp.o > > cc1plus: warnings being treated as errors > In file included from > /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/broker/TopicExchange.h:30, > from > /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/AclTopicMatch.h:23, > from > /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/AclData.h:25, > from > /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/AclReader.h:30, > from > /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/Acl.h:25, > from > /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/Acl.cpp:19: > /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/broker/Queue.h:540: > error: ‘qpid::broker::QueueRegistry’ is already a friend of > ‘qpid::broker::Queue’ > [ 57%] Building CXX object > src/CMakeFiles/qpidbroker.dir/qpid/acl/AclConnectionCounter.cpp.o > [ 58%] Building CXX object > src/CMakeFiles/qpidmessaging.dir/qpid/messaging/Logger.cpp.o > > make[2]: *** [src/CMakeFiles/qpidbroker.dir/qpid/acl/Acl.cpp.o] Error 1 > make[2]: *** Waiting for unfinished jobs > Scanning dependencies of target qpid-txtest > [ 59%] Building CXX object > src/tests/CMakeFiles/qpid-txtest.dir/qpid-txtest.cpp.o > Scanning dependencies of target receiver > [ 59%] Building CXX object src/tests/CMakeFiles/receiver.dir/receiver.cpp.o > cc1plus: warnings being treated as errors > In file included from > /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/broker/TopicExchange.h:30, > from > /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/AclTopicMatch.h:23, > from > /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/AclData.h:25, > from > /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/AclConnectionCounter.h:27, > from > /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/AclConnectionCounter.cpp:22: > /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/broker/Queue.h:540: > error: ‘qpid::broker::QueueRegistry’ is already a friend of > ‘qpid::broker::Queue’ > make[2]: *** > [src/CMakeFiles/qpidbroker.dir/qpid/acl/AclConnectionCounter.cpp.o] > Error 1 > make[1]: *** [src/CMakeFiles/qpidbroker.dir/all] Error 2 > make[1]: *** Waiting for unfinished jobs > [ 59%] Building CXX object > src/CMakeFiles/qpidmessaging.dir/qpid/messaging/Message.cpp.o > > [ 59%] Building CXX object > src/CMakeFiles/qpidmessaging.dir/qpid/messaging/Receiver.cpp.o > [ 59%] Building CXX object > src/CMakeFiles/qpidmessaging.dir/qpid/messaging/Session.cpp.o > > [ 59%] Building CXX object > src/CMakeFiles/qpidmessaging.dir/qpid/messaging/Sender.cpp.o > Linking CXX executable receiver > [ 59%] Built target receiver > [ 59%] Building CXX object > src/CMakeFiles/qpidmessaging.dir/qpid/messaging/ConnectionOptions.cpp.o > [ 60%] Building CXX object > src/CMakeFiles/qpidmessaging.dir/qpid/messaging/MessageImpl.cpp.o > > [ 60%] Building CXX object > src/CMakeFiles/qpidmessaging.dir/qpid/messaging/Message_io.cpp.o > [ 60%] Building CXX object > src/CMakeFiles/qpidmessaging.dir/qpid/messaging/ProtocolRegistry.cpp.o > [ 60%] Building CXX object > src/CMakeFiles/qpidmessaging.dir/qpid/messaging/amqp/EncodedMessage.cpp.o > Linking CXX executable qpid-txtest > [ 60%] Built target qpid-txtest > > Linking CXX shared library libqpidmessaging.so > [ 60%] Built target qpidmessaging > make: *** [all] Error 2 > > Kind Regards, > Alex > > > On 29 June 2016 at 13:18, Robbie Gemmell wrote: >> Hi folks, >> >> As per previous discussion/votes, the reorganised cpp and python bits >> will be migrating to their own git repositories. The migration is due >> to begin in the next hour or two. >> >> It isn't clear that the svn subdirs will actually be locked at this >> time, so please take note to cease committing to them. If they aren't >> locked (or I guess, even if they are..) we will need to decide what >> approach to take with the old dirs going forward, e.g clear the files >> out and leave a pointer file, eventually remove the dir, etc. >> >> https://issues.apache.org/jira/browse/INFRA-11794 >> https://issues.apache.org/j
Re: [NOTICE] cease commits to cpp and python subdirs of svn trunk, migrating to git
Hi, It looks like a number of commits is missed in git repo. I tried to compile cpp sources from https://git-wip-us.apache.org/repos/asf/qpid-cpp.git but compilation failed. The compilation errors are similar to the ones reported by Keith couple days ago. The fixes have been made as part of QPID-7306. Here is an extract from build output with compilation failures: [ 57%] Building CXX object src/CMakeFiles/qpidmessaging.dir/qpid/messaging/FailoverUpdates.cpp.o cc1plus: warnings being treated as errors In file included from /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/broker/TopicExchange.h:30, from /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/AclTopicMatch.h:23, from /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/AclData.h:25, from /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/AclReader.h:30, from /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/Acl.h:25, from /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/Acl.cpp:19: /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/broker/Queue.h:540: error: ‘qpid::broker::QueueRegistry’ is already a friend of ‘qpid::broker::Queue’ [ 57%] Building CXX object src/CMakeFiles/qpidbroker.dir/qpid/acl/AclConnectionCounter.cpp.o [ 58%] Building CXX object src/CMakeFiles/qpidmessaging.dir/qpid/messaging/Logger.cpp.o make[2]: *** [src/CMakeFiles/qpidbroker.dir/qpid/acl/Acl.cpp.o] Error 1 make[2]: *** Waiting for unfinished jobs Scanning dependencies of target qpid-txtest [ 59%] Building CXX object src/tests/CMakeFiles/qpid-txtest.dir/qpid-txtest.cpp.o Scanning dependencies of target receiver [ 59%] Building CXX object src/tests/CMakeFiles/receiver.dir/receiver.cpp.o cc1plus: warnings being treated as errors In file included from /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/broker/TopicExchange.h:30, from /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/AclTopicMatch.h:23, from /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/AclData.h:25, from /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/AclConnectionCounter.h:27, from /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/acl/AclConnectionCounter.cpp:22: /apps/qpid/jenkins/workspace/Apache-Qpid-Cpp/src/qpid/broker/Queue.h:540: error: ‘qpid::broker::QueueRegistry’ is already a friend of ‘qpid::broker::Queue’ make[2]: *** [src/CMakeFiles/qpidbroker.dir/qpid/acl/AclConnectionCounter.cpp.o] Error 1 make[1]: *** [src/CMakeFiles/qpidbroker.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs [ 59%] Building CXX object src/CMakeFiles/qpidmessaging.dir/qpid/messaging/Message.cpp.o [ 59%] Building CXX object src/CMakeFiles/qpidmessaging.dir/qpid/messaging/Receiver.cpp.o [ 59%] Building CXX object src/CMakeFiles/qpidmessaging.dir/qpid/messaging/Session.cpp.o [ 59%] Building CXX object src/CMakeFiles/qpidmessaging.dir/qpid/messaging/Sender.cpp.o Linking CXX executable receiver [ 59%] Built target receiver [ 59%] Building CXX object src/CMakeFiles/qpidmessaging.dir/qpid/messaging/ConnectionOptions.cpp.o [ 60%] Building CXX object src/CMakeFiles/qpidmessaging.dir/qpid/messaging/MessageImpl.cpp.o [ 60%] Building CXX object src/CMakeFiles/qpidmessaging.dir/qpid/messaging/Message_io.cpp.o [ 60%] Building CXX object src/CMakeFiles/qpidmessaging.dir/qpid/messaging/ProtocolRegistry.cpp.o [ 60%] Building CXX object src/CMakeFiles/qpidmessaging.dir/qpid/messaging/amqp/EncodedMessage.cpp.o Linking CXX executable qpid-txtest [ 60%] Built target qpid-txtest Linking CXX shared library libqpidmessaging.so [ 60%] Built target qpidmessaging make: *** [all] Error 2 Kind Regards, Alex On 29 June 2016 at 13:18, Robbie Gemmell wrote: > Hi folks, > > As per previous discussion/votes, the reorganised cpp and python bits > will be migrating to their own git repositories. The migration is due > to begin in the next hour or two. > > It isn't clear that the svn subdirs will actually be locked at this > time, so please take note to cease committing to them. If they aren't > locked (or I guess, even if they are..) we will need to decide what > approach to take with the old dirs going forward, e.g clear the files > out and leave a pointer file, eventually remove the dir, etc. > > https://issues.apache.org/jira/browse/INFRA-11794 > https://issues.apache.org/jira/browse/INFRA-11795 > > Robbie > > - > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > For additional commands, e-mail: dev-h...@qpid.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-426) The left tree view in Overview tab allows opening multiple branches at once. Tree view in Entities tab behives like accordeon.
Jiri Danek created DISPATCH-426: --- Summary: The left tree view in Overview tab allows opening multiple branches at once. Tree view in Entities tab behives like accordeon. Key: DISPATCH-426 URL: https://issues.apache.org/jira/browse/DISPATCH-426 Project: Qpid Dispatch Issue Type: Bug Components: Console Reporter: Jiri Danek Navigate to the Overview tab and expand multiple branches. Then navigate to the Entities tab and try to do the same. When opening a second branch in the Entities tab, the first is automatically closed. I'd expect that I can open as many branches in the tree view as I desire. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-425) Tree on the left side gets rerendered when navigating in dispatch-console preferences
[ https://issues.apache.org/jira/browse/DISPATCH-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-425: Attachment: preferencesAndTree.png > Tree on the left side gets rerendered when navigating in dispatch-console > preferences > - > > Key: DISPATCH-425 > URL: https://issues.apache.org/jira/browse/DISPATCH-425 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6.1 >Reporter: Jiri Danek > Attachments: preferencesAndTree.png > > > Go to the Overview tab and expand all branches in the tree view on the left > of the page. > Then click the User button on the top right and select Preferences from the > menu. > Switch between categories in the Preferences dialog, for example, open Core, > then Plugins. > Observe, that the tree view on the left briefly disappears and then > reappears, but all except one branch (the last visited one) are now collapsed. > I'd expect the tree to stay put and not be influenced by navigating around > the Preferences window. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-425) Tree on the left side gets rerendered when navigating in dispatch-console preferences
Jiri Danek created DISPATCH-425: --- Summary: Tree on the left side gets rerendered when navigating in dispatch-console preferences Key: DISPATCH-425 URL: https://issues.apache.org/jira/browse/DISPATCH-425 Project: Qpid Dispatch Issue Type: Bug Components: Console Affects Versions: 0.6.1 Reporter: Jiri Danek Go to the Overview tab and expand all branches in the tree view on the left of the page. Then click the User button on the top right and select Preferences from the menu. Switch between categories in the Preferences dialog, for example, open Core, then Plugins. Observe, that the tree view on the left briefly disappears and then reappears, but all except one branch (the last visited one) are now collapsed. I'd expect the tree to stay put and not be influenced by navigating around the Preferences window. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-424) Sliding animation for opening the logging console is distractingly slow
Jiri Danek created DISPATCH-424: --- Summary: Sliding animation for opening the logging console is distractingly slow Key: DISPATCH-424 URL: https://issues.apache.org/jira/browse/DISPATCH-424 Project: Qpid Dispatch Issue Type: Bug Components: Console Affects Versions: 0.6.1 Reporter: Jiri Danek Click the "Show the logging console" button in the upper right. The console slides out very slowly. I believe having to wait so many hundreds of milliseconds for the console to show is distracting. Suggestions: animate it faster, use snappier easing curve, have it appear at 80% out and animate the last 20% of the trajectory, like Android keyboard does it. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-423) Hovering over the two buttons on the left in the logging console triggers error toasts
[ https://issues.apache.org/jira/browse/DISPATCH-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356692#comment-15356692 ] Jiri Danek commented on DISPATCH-423: - As a sidenote, the buttons mentioned in the issue do not work. Clicking them does nothing. > Hovering over the two buttons on the left in the logging console triggers > error toasts > -- > > Key: DISPATCH-423 > URL: https://issues.apache.org/jira/browse/DISPATCH-423 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6.1 >Reporter: Jiri Danek > Attachments: errorsClickToClearLog.png > > > Open dispatch-console, connect, click the button "Show the logging console" > in the upper right. Hover the mouse over button "Click to clear log" or the > button "copy log to clipboard". Error messages start to appear. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-423) Hovering over the two buttons on the left in the logging console triggers error toasts
[ https://issues.apache.org/jira/browse/DISPATCH-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-423: Attachment: errorsClickToClearLog.png > Hovering over the two buttons on the left in the logging console triggers > error toasts > -- > > Key: DISPATCH-423 > URL: https://issues.apache.org/jira/browse/DISPATCH-423 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6.1 >Reporter: Jiri Danek > Attachments: errorsClickToClearLog.png > > > Open dispatch-console, connect, click the button "Show the logging console" > in the upper right. Hover the mouse over button "Click to clear log" or the > button "copy log to clipboard". Error messages start to appear. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-423) Hovering over the two buttons on the left in the logging console triggers error toasts
Jiri Danek created DISPATCH-423: --- Summary: Hovering over the two buttons on the left in the logging console triggers error toasts Key: DISPATCH-423 URL: https://issues.apache.org/jira/browse/DISPATCH-423 Project: Qpid Dispatch Issue Type: Bug Components: Console Affects Versions: 0.6.1 Reporter: Jiri Danek Open dispatch-console, connect, click the button "Show the logging console" in the upper right. Hover the mouse over button "Click to clear log" or the button "copy log to clipboard". Error messages start to appear. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-422) Internal URLs in toast messages and the logging console should not be hyperlinked and clickable
Jiri Danek created DISPATCH-422:
---
Summary: Internal URLs in toast messages and the logging console
should not be hyperlinked and clickable
Key: DISPATCH-422
URL: https://issues.apache.org/jira/browse/DISPATCH-422
Project: Qpid Dispatch
Issue Type: Bug
Components: Console
Affects Versions: 0.6.1
Reporter: Jiri Danek
Mouse over the button "Click to clear log" to generate some error toasts. These
are logged in the logging console. In both places, in toast and in the console,
the URL is hyperlinked.
{cite}
[Window] TypeError: this.htmlBridge is undefined
(http://127.0.0.1:8080/hawtio/app/app.js?8a388255a8a553f2:61:951)
{cite}
I believe there is no reason why an user would want to click such link. I
clicked it by accident and it brought me out of the dispatch-console and I then
had to reconnect. Therefore, I propose to make the URL unclickable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-420) Deleting an address in the dispatch-console does not work
[
https://issues.apache.org/jira/browse/DISPATCH-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek updated DISPATCH-420:
Attachment: linksInConsoleAndPopups.png
> Deleting an address in the dispatch-console does not work
> -
>
> Key: DISPATCH-420
> URL: https://issues.apache.org/jira/browse/DISPATCH-420
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
>Affects Versions: 0.6.1
>Reporter: Jiri Danek
> Attachments: linksInConsoleAndPopups.png
>
>
> If I use router with default config + console section, connect
> dispatch-console to it and navigate to the Entities tab, select an address,
> click Delete and confirm, a message saying {{No such entity type 'address'}}
> appears in a red toast and address is not deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-421) Toasts messages are not logged in the rolldown "logging console"
Jiri Danek created DISPATCH-421: --- Summary: Toasts messages are not logged in the rolldown "logging console" Key: DISPATCH-421 URL: https://issues.apache.org/jira/browse/DISPATCH-421 Project: Qpid Dispatch Issue Type: Bug Components: Console Affects Versions: 0.6.1 Reporter: Jiri Danek Do something that emits an error or confirmation toast. For example, delete an address as in DISPATCH-418. Then click the icon to open the logging console in the upper right corner. The error message from toast won't be logged in the logging console. I'd expect the toasts to be logged in the logging console. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-418) Deleting an address in the dispatch-console does not work
[
https://issues.apache.org/jira/browse/DISPATCH-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek updated DISPATCH-418:
Attachment: entitiesAddressDelete.png
Deleting e.g. a connector in the console works.
> Deleting an address in the dispatch-console does not work
> -
>
> Key: DISPATCH-418
> URL: https://issues.apache.org/jira/browse/DISPATCH-418
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
>Affects Versions: 0.6.1
>Reporter: Jiri Danek
> Attachments: entitiesAddressDelete.png
>
>
> If I use router with default config + console section, connect
> dispatch-console to it and navigate to the Entities tab, select an address,
> click Delete and confirm, a message saying {{No such entity type 'address'}}
> appears in a red toast and address is not deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (DISPATCH-420) Deleting an address in the dispatch-console does not work
[
https://issues.apache.org/jira/browse/DISPATCH-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek closed DISPATCH-420.
---
Resolution: Duplicate
> Deleting an address in the dispatch-console does not work
> -
>
> Key: DISPATCH-420
> URL: https://issues.apache.org/jira/browse/DISPATCH-420
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
>Affects Versions: 0.6.1
>Reporter: Jiri Danek
>
> If I use router with default config + console section, connect
> dispatch-console to it and navigate to the Entities tab, select an address,
> click Delete and confirm, a message saying {{No such entity type 'address'}}
> appears in a red toast and address is not deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
