[jira] [Commented] (DISPATCH-1207) [tools] Scraper does not handle session recreation over same connection
[ https://issues.apache.org/jira/browse/DISPATCH-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707919#comment-16707919 ] ASF subversion and git services commented on DISPATCH-1207: --- Commit db87d5d3e7191b17af0804f741f8817e2eddb529 in qpid-dispatch's branch refs/heads/master from [~chug] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=db87d5d ] DISPATCH-1207: create multiple sessions with same ID over single connection > [tools] Scraper does not handle session recreation over same connection > --- > > Key: DISPATCH-1207 > URL: https://issues.apache.org/jira/browse/DISPATCH-1207 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Tools >Affects Versions: 1.5.0 >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > > The creating a session with a pair of begins and then ending it with a pair > of ends does not retire the session. Instead the next pair of begins with the > same session id reuses the same session. Then dispositions and settlement > reports become confused. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1207) [tools] Scraper does not handle session recreation over same connection
Chuck Rolke created DISPATCH-1207: - Summary: [tools] Scraper does not handle session recreation over same connection Key: DISPATCH-1207 URL: https://issues.apache.org/jira/browse/DISPATCH-1207 Project: Qpid Dispatch Issue Type: Improvement Components: Tools Affects Versions: 1.5.0 Reporter: Chuck Rolke Assignee: Chuck Rolke The creating a session with a pair of begins and then ending it with a pair of ends does not retire the session. Instead the next pair of begins with the same session id reuses the same session. Then dispositions and settlement reports become confused. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1205) Allow signed int values >= 0 be parsed as unsigned int
[ https://issues.apache.org/jira/browse/DISPATCH-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved DISPATCH-1205. -- Resolution: Fixed > Allow signed int values >= 0 be parsed as unsigned int > -- > > Key: DISPATCH-1205 > URL: https://issues.apache.org/jira/browse/DISPATCH-1205 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Affects Versions: 1.4.1 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.5.0 > > > The parse module should allow parsing positive signed integer as unsigned > integer. > Also the parse module should allow parsing unsigned integers as signed if the > unsigned value can be expressed as a positive signed number of the proper > width. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1194) Asynchronous address lookup on attach for Edge to determine if there are link-route destinations
[ https://issues.apache.org/jira/browse/DISPATCH-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707808#comment-16707808 ] ASF GitHub Bot commented on DISPATCH-1194: -- GitHub user kgiusti opened a pull request: https://github.com/apache/qpid-dispatch/pull/423 DISPATCH-1194: Link Route address lookup for edge router You can merge this pull request into a Git repository by running: $ git pull https://github.com/kgiusti/dispatch DISPATCH-1194 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/423.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 #423 commit 82293c46a3944000b2fbbb473ecd2e555eda6d69 Author: Kenneth Giusti Date: 2018-11-28T14:30:09Z DISPATCH-1194: Link Route address lookup for edge router > Asynchronous address lookup on attach for Edge to determine if there are > link-route destinations > > > Key: DISPATCH-1194 > URL: https://issues.apache.org/jira/browse/DISPATCH-1194 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Major > Fix For: 1.5.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #423: DISPATCH-1194: Link Route address lookup fo...
GitHub user kgiusti opened a pull request: https://github.com/apache/qpid-dispatch/pull/423 DISPATCH-1194: Link Route address lookup for edge router You can merge this pull request into a Git repository by running: $ git pull https://github.com/kgiusti/dispatch DISPATCH-1194 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/423.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 #423 commit 82293c46a3944000b2fbbb473ecd2e555eda6d69 Author: Kenneth Giusti Date: 2018-11-28T14:30:09Z DISPATCH-1194: Link Route address lookup for edge router --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1205) Allow signed int values >= 0 be parsed as unsigned int
[ https://issues.apache.org/jira/browse/DISPATCH-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707804#comment-16707804 ] ASF GitHub Bot commented on DISPATCH-1205: -- Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/422 > Allow signed int values >= 0 be parsed as unsigned int > -- > > Key: DISPATCH-1205 > URL: https://issues.apache.org/jira/browse/DISPATCH-1205 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Affects Versions: 1.4.1 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.5.0 > > > The parse module should allow parsing positive signed integer as unsigned > integer. > Also the parse module should allow parsing unsigned integers as signed if the > unsigned value can be expressed as a positive signed number of the proper > width. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1205) Allow signed int values >= 0 be parsed as unsigned int
[ https://issues.apache.org/jira/browse/DISPATCH-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707803#comment-16707803 ] ASF subversion and git services commented on DISPATCH-1205: --- Commit 93c89a75825a57a5749d262f4b5be26301f70c82 in qpid-dispatch's branch refs/heads/master from Kenneth Giusti [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=93c89a7 ] DISPATCH-1205: accept valid integer sign coversions when parsing This closes #422 > Allow signed int values >= 0 be parsed as unsigned int > -- > > Key: DISPATCH-1205 > URL: https://issues.apache.org/jira/browse/DISPATCH-1205 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Affects Versions: 1.4.1 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.5.0 > > > The parse module should allow parsing positive signed integer as unsigned > integer. > Also the parse module should allow parsing unsigned integers as signed if the > unsigned value can be expressed as a positive signed number of the proper > width. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #422: DISPATCH-1205: accept valid integer sign co...
Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/422 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1205) Allow signed int values >= 0 be parsed as unsigned int
[ https://issues.apache.org/jira/browse/DISPATCH-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707781#comment-16707781 ] ASF GitHub Bot commented on DISPATCH-1205: -- Github user codecov-io commented on the issue: https://github.com/apache/qpid-dispatch/pull/422 # [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/422?src=pr&el=h1) Report > :exclamation: No coverage uploaded for pull request base (`master@663a997`). [Click here to learn what that means](https://docs.codecov.io/docs/error-reference#section-missing-base-commit). > The diff coverage is `100%`. [](https://codecov.io/gh/apache/qpid-dispatch/pull/422?src=pr&el=tree) ```diff @@Coverage Diff@@ ## master #422 +/- ## = Coverage ? 87.88% = Files ? 82 Lines ?17933 Branches ?0 = Hits ?15760 Misses? 2173 Partials ?0 ``` | [Impacted Files](https://codecov.io/gh/apache/qpid-dispatch/pull/422?src=pr&el=tree) | Coverage Δ | | |---|---|---| | [src/parse.c](https://codecov.io/gh/apache/qpid-dispatch/pull/422/diff?src=pr&el=tree#diff-c3JjL3BhcnNlLmM=) | `88.01% <100%> (ø)` | | | [tests/parse\_test.c](https://codecov.io/gh/apache/qpid-dispatch/pull/422/diff?src=pr&el=tree#diff-dGVzdHMvcGFyc2VfdGVzdC5j) | `70.04% <100%> (ø)` | | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/422?src=pr&el=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/422?src=pr&el=footer). Last update [663a997...d789bb2](https://codecov.io/gh/apache/qpid-dispatch/pull/422?src=pr&el=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). > Allow signed int values >= 0 be parsed as unsigned int > -- > > Key: DISPATCH-1205 > URL: https://issues.apache.org/jira/browse/DISPATCH-1205 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Affects Versions: 1.4.1 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.5.0 > > > The parse module should allow parsing positive signed integer as unsigned > integer. > Also the parse module should allow parsing unsigned integers as signed if the > unsigned value can be expressed as a positive signed number of the proper > width. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch issue #422: DISPATCH-1205: accept valid integer sign coversion...
Github user codecov-io commented on the issue: https://github.com/apache/qpid-dispatch/pull/422 # [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/422?src=pr&el=h1) Report > :exclamation: No coverage uploaded for pull request base (`master@663a997`). [Click here to learn what that means](https://docs.codecov.io/docs/error-reference#section-missing-base-commit). > The diff coverage is `100%`. [](https://codecov.io/gh/apache/qpid-dispatch/pull/422?src=pr&el=tree) ```diff @@Coverage Diff@@ ## master #422 +/- ## = Coverage ? 87.88% = Files ? 82 Lines ?17933 Branches ?0 = Hits ?15760 Misses? 2173 Partials ?0 ``` | [Impacted Files](https://codecov.io/gh/apache/qpid-dispatch/pull/422?src=pr&el=tree) | Coverage Π| | |---|---|---| | [src/parse.c](https://codecov.io/gh/apache/qpid-dispatch/pull/422/diff?src=pr&el=tree#diff-c3JjL3BhcnNlLmM=) | `88.01% <100%> (ø)` | | | [tests/parse\_test.c](https://codecov.io/gh/apache/qpid-dispatch/pull/422/diff?src=pr&el=tree#diff-dGVzdHMvcGFyc2VfdGVzdC5j) | `70.04% <100%> (ø)` | | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/422?src=pr&el=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Π= absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/422?src=pr&el=footer). Last update [663a997...d789bb2](https://codecov.io/gh/apache/qpid-dispatch/pull/422?src=pr&el=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1121) qd_parse_as_(u)int() fails to detect over/underflow of 32bit integers
[ https://issues.apache.org/jira/browse/DISPATCH-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707737#comment-16707737 ] ASF subversion and git services commented on DISPATCH-1121: --- Commit 663a997c3abc8e03c3cfeeea46116745309c99f8 in qpid-dispatch's branch refs/heads/master from [~chug] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=663a997 ] DISPATCH-1121: Exclude same files in new directory > qd_parse_as_(u)int() fails to detect over/underflow of 32bit integers > - > > Key: DISPATCH-1121 > URL: https://issues.apache.org/jira/browse/DISPATCH-1121 > Project: Qpid Dispatch > Issue Type: Bug > Components: Management Agent >Affects Versions: 1.3.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Minor > Fix For: 1.4.0 > > > Attempting to parse a number that is out of range for a 32bit value will not > set the parse error flag. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1202) [tools] Scraper README is stale
[ https://issues.apache.org/jira/browse/DISPATCH-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke resolved DISPATCH-1202. --- Resolution: Fixed Fix Version/s: 1.5.0 > [tools] Scraper README is stale > --- > > Key: DISPATCH-1202 > URL: https://issues.apache.org/jira/browse/DISPATCH-1202 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Tools >Affects Versions: 1.5.0 >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > Fix For: 1.5.0 > > > The README does not reflect recent changes: > * The files have moved > * A --split function was added -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1205) Allow signed int values >= 0 be parsed as unsigned int
[ https://issues.apache.org/jira/browse/DISPATCH-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707667#comment-16707667 ] ASF GitHub Bot commented on DISPATCH-1205: -- GitHub user kgiusti opened a pull request: https://github.com/apache/qpid-dispatch/pull/422 DISPATCH-1205: accept valid integer sign coversions when parsing You can merge this pull request into a Git repository by running: $ git pull https://github.com/kgiusti/dispatch DISPATCH-1205 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/422.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 #422 commit ac157282881fade8f3491227d7de3d71625deac4 Author: Kenneth Giusti Date: 2018-12-03T18:57:00Z DISPATCH-1205: accept valid integer sign coversions when parsing > Allow signed int values >= 0 be parsed as unsigned int > -- > > Key: DISPATCH-1205 > URL: https://issues.apache.org/jira/browse/DISPATCH-1205 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Affects Versions: 1.4.1 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.5.0 > > > The parse module should allow parsing positive signed integer as unsigned > integer. > Also the parse module should allow parsing unsigned integers as signed if the > unsigned value can be expressed as a positive signed number of the proper > width. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #422: DISPATCH-1205: accept valid integer sign co...
GitHub user kgiusti opened a pull request: https://github.com/apache/qpid-dispatch/pull/422 DISPATCH-1205: accept valid integer sign coversions when parsing You can merge this pull request into a Git repository by running: $ git pull https://github.com/kgiusti/dispatch DISPATCH-1205 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/422.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 #422 commit ac157282881fade8f3491227d7de3d71625deac4 Author: Kenneth Giusti Date: 2018-12-03T18:57:00Z DISPATCH-1205: accept valid integer sign coversions when parsing --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1204) Add console tests for edge router
[ https://issues.apache.org/jira/browse/DISPATCH-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707644#comment-16707644 ] ASF subversion and git services commented on DISPATCH-1204: --- Commit db6ed6b15cc3c2a658cb37ab8f2122a8cb806db5 in qpid-dispatch's branch refs/heads/master from [~eallen] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=db6ed6b ] DISPATCH-1204 Added console tests for edge routers > Add console tests for edge router > - > > Key: DISPATCH-1204 > URL: https://issues.apache.org/jira/browse/DISPATCH-1204 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Tests >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > > Add console tests that ensure edge routers are identified and handled > correctly. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1205) Allow signed int values >= 0 be parsed as unsigned int
Ken Giusti created DISPATCH-1205: Summary: Allow signed int values >= 0 be parsed as unsigned int Key: DISPATCH-1205 URL: https://issues.apache.org/jira/browse/DISPATCH-1205 Project: Qpid Dispatch Issue Type: Improvement Components: Router Node Affects Versions: 1.4.1 Reporter: Ken Giusti Assignee: Ken Giusti Fix For: 1.5.0 The parse module should allow parsing positive signed integer as unsigned integer. Also the parse module should allow parsing unsigned integers as signed if the unsigned value can be expressed as a positive signed number of the proper width. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1206) Consolidate similar HTML templates into an angularjs directive
Ernest Allen created DISPATCH-1206: -- Summary: Consolidate similar HTML templates into an angularjs directive Key: DISPATCH-1206 URL: https://issues.apache.org/jira/browse/DISPATCH-1206 Project: Qpid Dispatch Issue Type: Improvement Components: Console Reporter: Ernest Allen Assignee: Ernest Allen There are multiple templates used to display the detail popups on the topology page. These templates all follow a similar pattern and only differ by which scope variables are used. These templates can be consolidated into a single angularjs directive. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1204) Add console tests for edge router
Ernest Allen created DISPATCH-1204: -- Summary: Add console tests for edge router Key: DISPATCH-1204 URL: https://issues.apache.org/jira/browse/DISPATCH-1204 Project: Qpid Dispatch Issue Type: Improvement Components: Tests Reporter: Ernest Allen Assignee: Ernest Allen Add console tests that ensure edge routers are identified and handled correctly. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton pull request #170: PROTON-1959 [cpp] Binary compatible reconnect
GitHub user alanconway opened a pull request: https://github.com/apache/qpid-proton/pull/170 PROTON-1959 [cpp] Binary compatible reconnect The previous commit f53c7683d7e90363 added virtual functions to messaging_handler which is a binary incompatible change. Modify & update doc to work with existing messaging_handler functions. Use existing pn_connection_open() and pn_transport_error() events instead of creating new ones. You can merge this pull request into a Git repository by running: $ git pull https://github.com/alanconway/qpid-proton cpp-reconnect-backward-compat Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/170.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 #170 commit 302c7da439cbffdc7e85959a43421838418d0cc7 Author: Alan Conway Date: 2018-11-30T19:07:58Z PROTON-1959 [cpp] Binary compatible reconnect The previous commit f53c7683d7e90363 added virtual functions to messaging_handler which is a binary incompatible change. Modify & update doc to work with existing messaging_handler functions. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1959) [c,cpp] API additions to simplify reconnect
[ https://issues.apache.org/jira/browse/PROTON-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707549#comment-16707549 ] ASF GitHub Bot commented on PROTON-1959: GitHub user alanconway opened a pull request: https://github.com/apache/qpid-proton/pull/170 PROTON-1959 [cpp] Binary compatible reconnect The previous commit f53c7683d7e90363 added virtual functions to messaging_handler which is a binary incompatible change. Modify & update doc to work with existing messaging_handler functions. Use existing pn_connection_open() and pn_transport_error() events instead of creating new ones. You can merge this pull request into a Git repository by running: $ git pull https://github.com/alanconway/qpid-proton cpp-reconnect-backward-compat Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/170.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 #170 commit 302c7da439cbffdc7e85959a43421838418d0cc7 Author: Alan Conway Date: 2018-11-30T19:07:58Z PROTON-1959 [cpp] Binary compatible reconnect The previous commit f53c7683d7e90363 added virtual functions to messaging_handler which is a binary incompatible change. Modify & update doc to work with existing messaging_handler functions. > [c,cpp] API additions to simplify reconnect > --- > > Key: PROTON-1959 > URL: https://issues.apache.org/jira/browse/PROTON-1959 > Project: Qpid Proton > Issue Type: Improvement >Affects Versions: proton-c-0.26.0 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Major > Fix For: proton-c-0.27.0 > > > Add some minor API extensions to make it easier to tell if a connection is > reconnecting, and to set up one-time events that only happen on the initial > connect. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6948) [Broker-J] Introduce REST API compatibility layer
[ https://issues.apache.org/jira/browse/QPID-6948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-6948: - Summary: [Broker-J] Introduce REST API compatibility layer (was: Introduce REST API compatibility layer) > [Broker-J] Introduce REST API compatibility layer > - > > Key: QPID-6948 > URL: https://issues.apache.org/jira/browse/QPID-6948 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Keith Wall >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > Make the REST API backwardly compatibility with model as used by 0.32. > In general the compatibility layer should: > For GET: > * attributes that are removed should be simulated (e.g. defaultVirtualHost) > * new attributes/new types don't need to be hidden > For POST/PUT: > * on creation, new mandatory attributes should be given sensible defaults > * removed operations should be supported perhaps by rewriting the request in > terms of new operations. > When the model changes structurally, the compatibility layer should present > the old model. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7694) [Broker-J] Add 0-8..0-10 wire queue declare argument for holds on publish
[ https://issues.apache.org/jira/browse/QPID-7694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7694: - Summary: [Broker-J] Add 0-8..0-10 wire queue declare argument for holds on publish (was: Add 0-8..0-10 wire queue declare argument for holds on publish) > [Broker-J] Add 0-8..0-10 wire queue declare argument for holds on publish > - > > Key: QPID-7694 > URL: https://issues.apache.org/jira/browse/QPID-7694 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Keith Wall >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > From an ADDR address, I ought to be able to specify that the queue is > declared with holdOnPublishEnabled enabled.Currently > Queue#holdOnPublishEnabled is not mapped to a wire argument, so this is not > possible, -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1202) [tools] Scraper README is stale
[ https://issues.apache.org/jira/browse/DISPATCH-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707468#comment-16707468 ] ASF subversion and git services commented on DISPATCH-1202: --- Commit f6a0ecf025c9e314d3b87a9d6ace79e2ff8f5e80 in qpid-dispatch's branch refs/heads/master from [~chug] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=f6a0ecf ] DISPATCH-1202: Update scraper README > [tools] Scraper README is stale > --- > > Key: DISPATCH-1202 > URL: https://issues.apache.org/jira/browse/DISPATCH-1202 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Tools >Affects Versions: 1.5.0 >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > > The README does not reflect recent changes: > * The files have moved > * A --split function was added -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8261) [Broker-J] Change broker model version to 7.1
[ https://issues.apache.org/jira/browse/QPID-8261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8261: - Status: Reviewable (was: In Progress) > [Broker-J] Change broker model version to 7.1 > - > > Key: QPID-8261 > URL: https://issues.apache.org/jira/browse/QPID-8261 > Project: Qpid > Issue Type: Task > Components: Broker-J >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > The model version needs to be changed to 7.1 for broker 7.1.0 release -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-8261) [Broker-J] Change broker model version to 7.1
[ https://issues.apache.org/jira/browse/QPID-8261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-8261: Assignee: Alex Rudyy > [Broker-J] Change broker model version to 7.1 > - > > Key: QPID-8261 > URL: https://issues.apache.org/jira/browse/QPID-8261 > Project: Qpid > Issue Type: Task > Components: Broker-J >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > The model version needs to be changed to 7.1 for broker 7.1.0 release -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8261) [Broker-J] Change broker model version to 7.1
[ https://issues.apache.org/jira/browse/QPID-8261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707437#comment-16707437 ] ASF subversion and git services commented on QPID-8261: --- Commit 40691ecb9409c91fedf6ab561e4fde671f5dd565 in qpid-broker-j's branch refs/heads/master from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=40691ec ] QPID-8261: [Broker-J] Change broker model version to 7.1 > [Broker-J] Change broker model version to 7.1 > - > > Key: QPID-8261 > URL: https://issues.apache.org/jira/browse/QPID-8261 > Project: Qpid > Issue Type: Task > Components: Broker-J >Reporter: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > The model version needs to be changed to 7.1 for broker 7.1.0 release -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1195) Continually update detail info on conole topology page
[ https://issues.apache.org/jira/browse/DISPATCH-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707404#comment-16707404 ] ASF subversion and git services commented on DISPATCH-1195: --- Commit 55b7ae55e4f4c2f89f25a928fdd0e98049372f5e in qpid-dispatch's branch refs/heads/master from [~eallen] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=55b7ae5 ] DISPATCH-1195 Periodically update popup detail on topology page > Continually update detail info on conole topology page > -- > > Key: DISPATCH-1195 > URL: https://issues.apache.org/jira/browse/DISPATCH-1195 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > > When you click on clients (single or groups) on the topology page, a popup > appears that shows connection info in the case of clients, or edge router > info in the case of edge routers. > This info is a snapshot taken at the time the client is clicked. The info > should be updated periodically while the popup is still visible. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1203) Console tests are skipped
Ernest Allen created DISPATCH-1203: -- Summary: Console tests are skipped Key: DISPATCH-1203 URL: https://issues.apache.org/jira/browse/DISPATCH-1203 Project: Qpid Dispatch Issue Type: Bug Components: Tests Reporter: Ernest Allen Assignee: Ernest Allen Running 'make test' will run the console test only if the console/stand-alone directory does not contain a node_modules/ directory. Otherwise, the test will not be run, but will be reported as 'passed'. Since running 'make test' will create the node_modules directory, the test will only be run the first time. Subsequent runs of 'make test' will report that the console test succeeds, but in fact, the actual test was not run. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1203) Console tests are skipped
[ https://issues.apache.org/jira/browse/DISPATCH-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707382#comment-16707382 ] ASF subversion and git services commented on DISPATCH-1203: --- Commit 3adde8e5dbe62a0b293584a0b210979c897a97c6 in qpid-dispatch's branch refs/heads/master from [~eallen] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=3adde8e ] DISPATCH-1203 Ensure console test runs each time > Console tests are skipped > - > > Key: DISPATCH-1203 > URL: https://issues.apache.org/jira/browse/DISPATCH-1203 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > > Running 'make test' will run the console test only if the console/stand-alone > directory does not contain a node_modules/ directory. Otherwise, the test > will not be run, but will be reported as 'passed'. > Since running 'make test' will create the node_modules directory, the test > will only be run the first time. Subsequent runs of 'make test' will report > that the console test succeeds, but in fact, the actual test was not run. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (PROTON-1959) [c,cpp] API additions to simplify reconnect
[ https://issues.apache.org/jira/browse/PROTON-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway reopened PROTON-1959: - This fix is binary incompatible with 0.26, it introduces new virtual functions on messaging_handler, which is subclassed in user code and called by the library. Replace with a compatible fix for 0.27 and schedule incompatible changes for a future binary release. > [c,cpp] API additions to simplify reconnect > --- > > Key: PROTON-1959 > URL: https://issues.apache.org/jira/browse/PROTON-1959 > Project: Qpid Proton > Issue Type: Improvement >Affects Versions: proton-c-0.26.0 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Major > Fix For: proton-c-0.27.0 > > > Add some minor API extensions to make it easier to tell if a connection is > reconnecting, and to set up one-time events that only happen on the initial > connect. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8139) [Broker-J] [AMQP1-0] [JMSBINDMAP] JMS selectors using JMSMessageID or JMSCorrelationID expressed using the AMQP type encoded form values fail to select target message
[
https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707157#comment-16707157
]
Alex Rudyy commented on QPID-8139:
--
The issue is descoped from version 7.1.0
> [Broker-J] [AMQP1-0] [JMSBINDMAP] JMS selectors using JMSMessageID or
> JMSCorrelationID expressed using the AMQP type encoded form values fail to
> select target message
> ---
>
> Key: QPID-8139
> URL: https://issues.apache.org/jira/browse/QPID-8139
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.2, qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: Future
>
> Attachments:
> 0001-QPID-8139-Broker-J-AMQP-1.0-Make-sure-that-selector-.patch
>
>
> When using the Qpid JMS AMQP 1.0 Client with Broker-J, if the consumer
> specifies a JMS message selectors including a {{JMSMessageID}} or
> {{JMSCorrelationID}} predicate, the selector can fail to find the target
> message in some circumstances. This occurs when the message producer is
> configured to use one of the following {{jms.messageIDPolicy.messageIDType}}
> modes: {{UUID}}. {{UUID_STRING}}, {{PREFIXED_UUID_STRING}}. In the default
> mode, {{BUILTIN}} the problem does not manifest.
> The issue is the Broker-J JMS selector implementation does not understand the
> AMQP type encoded forms specified by 3.2.1.1 of the Advanced Message Queuing
> Protocol (AMQP) JMS Mapping Version 1.0 [WD9].
> The problem also manifests when the Broker's message conversion feature is in
> use. For instance, a message produced by a AMQP 0-10 producer cannot be
> selected by an consumer using a Qpid JMS Client 1.0 using a {{JMSMessageID}}
> or {{JMSCorrelationID}} predicate. This was originally highlighted by the
> following user list post:
> http://qpid.2158936.n2.nabble.com/JMSMessageID-differences-in-JMS-0-30-0-and-JMS-AMQP-0-x-6-3-0-clients-td7674019.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8139) [Broker-J] [AMQP1-0] [JMSBINDMAP] JMS selectors using JMSMessageID or JMSCorrelationID expressed using the AMQP type encoded form values fail to select target message
[
https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8139:
-
Fix Version/s: (was: qpid-java-broker-7.1.0)
Future
> [Broker-J] [AMQP1-0] [JMSBINDMAP] JMS selectors using JMSMessageID or
> JMSCorrelationID expressed using the AMQP type encoded form values fail to
> select target message
> ---
>
> Key: QPID-8139
> URL: https://issues.apache.org/jira/browse/QPID-8139
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.2, qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: Future
>
> Attachments:
> 0001-QPID-8139-Broker-J-AMQP-1.0-Make-sure-that-selector-.patch
>
>
> When using the Qpid JMS AMQP 1.0 Client with Broker-J, if the consumer
> specifies a JMS message selectors including a {{JMSMessageID}} or
> {{JMSCorrelationID}} predicate, the selector can fail to find the target
> message in some circumstances. This occurs when the message producer is
> configured to use one of the following {{jms.messageIDPolicy.messageIDType}}
> modes: {{UUID}}. {{UUID_STRING}}, {{PREFIXED_UUID_STRING}}. In the default
> mode, {{BUILTIN}} the problem does not manifest.
> The issue is the Broker-J JMS selector implementation does not understand the
> AMQP type encoded forms specified by 3.2.1.1 of the Advanced Message Queuing
> Protocol (AMQP) JMS Mapping Version 1.0 [WD9].
> The problem also manifests when the Broker's message conversion feature is in
> use. For instance, a message produced by a AMQP 0-10 producer cannot be
> selected by an consumer using a Qpid JMS Client 1.0 using a {{JMSMessageID}}
> or {{JMSCorrelationID}} predicate. This was originally highlighted by the
> following user list post:
> http://qpid.2158936.n2.nabble.com/JMSMessageID-differences-in-JMS-0-30-0-and-JMS-AMQP-0-x-6-3-0-clients-td7674019.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-8262) [Broker-J] Release Qpid Broker-J 7.1.0
Alex Rudyy created QPID-8262: Summary: [Broker-J] Release Qpid Broker-J 7.1.0 Key: QPID-8262 URL: https://issues.apache.org/jira/browse/QPID-8262 Project: Qpid Issue Type: Task Components: Broker-J Reporter: Alex Rudyy Fix For: qpid-java-broker-7.1.0 Release Qpid Broker-J following instructions provided at [https://cwiki.apache.org/confluence/display/qpid/Releasing+Qpid+Broker-J] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-8261) [Broker-J] Change broker model version to 7.1
Alex Rudyy created QPID-8261: Summary: [Broker-J] Change broker model version to 7.1 Key: QPID-8261 URL: https://issues.apache.org/jira/browse/QPID-8261 Project: Qpid Issue Type: Task Components: Broker-J Reporter: Alex Rudyy Fix For: qpid-java-broker-7.1.0 The model version needs to be changed to 7.1 for broker 7.1.0 release -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7138) [Java Broker] Broker should detect duplicate IDs in configured objects
[ https://issues.apache.org/jira/browse/QPID-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707005#comment-16707005 ] Alex Rudyy commented on QPID-7138: -- The work is descoped from 7.1.0 > [Java Broker] Broker should detect duplicate IDs in configured objects > -- > > Key: QPID-7138 > URL: https://issues.apache.org/jira/browse/QPID-7138 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: 0.28, 0.30, 0.32, qpid-java-6.0, qpid-java-6.0.1 >Reporter: Alex Rudyy >Priority: Minor > Fix For: Future > > > Currently UUID uniqueness is enforced only amongst immediate siblings. This > means that, say, a virtual host with queue with UUID A would reject a second > queue with the same UUID A. Currently if a second virtual host had a queue > with same UUID A, this would be allowed. This presents a problem for clients > (including the Web Management Console) that expect UUID to be universally > unique. > Change ACO so that object UUID are universally so.The validatation would > need to be applied as new objects are created, as the Broker starts up and as > Virtualhosts are recovered. This latter may or may not be at start-up time. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7141) [Java Broker] Make sure all data in the ApiDocs are correctly escaped/encoded
[ https://issues.apache.org/jira/browse/QPID-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706997#comment-16706997 ] Alex Rudyy commented on QPID-7141: -- Descoped from 7.1.0 > [Java Broker] Make sure all data in the ApiDocs are correctly escaped/encoded > - > > Key: QPID-7141 > URL: https://issues.apache.org/jira/browse/QPID-7141 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Reporter: Lorenz Quack >Priority: Minor > Fix For: Future > > > The content of the /apidocs html page is derived from the broker which is not > aware of html semantics. > We have to make sure the strings coming from the broker are correctly encoded > before putting them in the HTML DOM. > OWASP has some information about correct escaping/encoding for different > scenarios: > https://www.owasp.org/index.php/XSS_%28Cross_Site_Scripting%29_Prevention_Cheat_Sheet -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7138) [Java Broker] Broker should detect duplicate IDs in configured objects
[ https://issues.apache.org/jira/browse/QPID-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7138: - Fix Version/s: (was: qpid-java-broker-7.1.0) Future > [Java Broker] Broker should detect duplicate IDs in configured objects > -- > > Key: QPID-7138 > URL: https://issues.apache.org/jira/browse/QPID-7138 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: 0.28, 0.30, 0.32, qpid-java-6.0, qpid-java-6.0.1 >Reporter: Alex Rudyy >Priority: Minor > Fix For: Future > > > Currently UUID uniqueness is enforced only amongst immediate siblings. This > means that, say, a virtual host with queue with UUID A would reject a second > queue with the same UUID A. Currently if a second virtual host had a queue > with same UUID A, this would be allowed. This presents a problem for clients > (including the Web Management Console) that expect UUID to be universally > unique. > Change ACO so that object UUID are universally so.The validatation would > need to be applied as new objects are created, as the Broker starts up and as > Virtualhosts are recovered. This latter may or may not be at start-up time. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8011) [Broker-J][WMC] Auto-refresh functionality is broken for grids of type EnhancedGrid when pagination plugin and Observable/Memory store are used
[ https://issues.apache.org/jira/browse/QPID-8011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8011: - Fix Version/s: (was: qpid-java-broker-7.1.0) Future > [Broker-J][WMC] Auto-refresh functionality is broken for grids of type > EnhancedGrid when pagination plugin and Observable/Memory store are used > --- > > Key: QPID-8011 > URL: https://issues.apache.org/jira/browse/QPID-8011 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-6.1.4, qpid-java-broker-7.0.0 >Reporter: Alex Rudyy >Priority: Trivial > Fix For: Future > > > All EnhancedGrid grids with pagination and Observable/Memory store do not > update the rows properly. The following issues are seen: > * pagination is not updated after number of rows reaches page size. Total > number of items is displayed incorrectly (equals to page size) and the links > to next pages are not displayed. The pagination can be updated by > increasing/reducing page number. > * After navigation to next page, on grid update the updated items from the > previous page can be displayed unexpectedly on currently displayed page. The > displayed total number of items is increased by number of updated rows. > Sorting on navigation back and forward can temporary restore the page but > after grid update the updated items from previous pages can reappear again > The following grids are affected: > * Ports grid on Broker tab (Virtual host grids invokes explicitly _refresh() > on update which works around the issues ) > * Log Files grid on FileLogger tab > * Groups grid for group managing group providers (FileGroupProvider, > ManagedGroupProvider) > * Group Memebers grid on Group tab > * Certificates grid on ManagedCertificateStore > * Users grid on user managing auth providers > * -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8011) [Broker-J][WMC] Auto-refresh functionality is broken for grids of type EnhancedGrid when pagination plugin and Observable/Memory store are used
[ https://issues.apache.org/jira/browse/QPID-8011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707000#comment-16707000 ] Alex Rudyy commented on QPID-8011: -- The work is descoped from 7.1.0. It makes more seance to replace EnchancedGrid and DataGrid with new dgrid type and address auto-refresh issue as part of refactoring > [Broker-J][WMC] Auto-refresh functionality is broken for grids of type > EnhancedGrid when pagination plugin and Observable/Memory store are used > --- > > Key: QPID-8011 > URL: https://issues.apache.org/jira/browse/QPID-8011 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-6.1.4, qpid-java-broker-7.0.0 >Reporter: Alex Rudyy >Priority: Trivial > Fix For: Future > > > All EnhancedGrid grids with pagination and Observable/Memory store do not > update the rows properly. The following issues are seen: > * pagination is not updated after number of rows reaches page size. Total > number of items is displayed incorrectly (equals to page size) and the links > to next pages are not displayed. The pagination can be updated by > increasing/reducing page number. > * After navigation to next page, on grid update the updated items from the > previous page can be displayed unexpectedly on currently displayed page. The > displayed total number of items is increased by number of updated rows. > Sorting on navigation back and forward can temporary restore the page but > after grid update the updated items from previous pages can reappear again > The following grids are affected: > * Ports grid on Broker tab (Virtual host grids invokes explicitly _refresh() > on update which works around the issues ) > * Log Files grid on FileLogger tab > * Groups grid for group managing group providers (FileGroupProvider, > ManagedGroupProvider) > * Group Memebers grid on Group tab > * Certificates grid on ManagedCertificateStore > * Users grid on user managing auth providers > * -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7141) [Java Broker] Make sure all data in the ApiDocs are correctly escaped/encoded
[ https://issues.apache.org/jira/browse/QPID-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7141: - Fix Version/s: (was: qpid-java-broker-7.1.0) Future > [Java Broker] Make sure all data in the ApiDocs are correctly escaped/encoded > - > > Key: QPID-7141 > URL: https://issues.apache.org/jira/browse/QPID-7141 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Reporter: Lorenz Quack >Priority: Minor > Fix For: Future > > > The content of the /apidocs html page is derived from the broker which is not > aware of html semantics. > We have to make sure the strings coming from the broker are correctly encoded > before putting them in the HTML DOM. > OWASP has some information about correct escaping/encoding for different > scenarios: > https://www.owasp.org/index.php/XSS_%28Cross_Site_Scripting%29_Prevention_Cheat_Sheet -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8156) [Broker-J] Heap memory is leaked on deletion of virtual host node
[
https://issues.apache.org/jira/browse/QPID-8156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy closed QPID-8156.
Resolution: Fixed
Fix Version/s: qpid-java-broker-7.1.0
The defect is fixed as part of changes for QPID-8157. See [
https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=d33550b ]
> [Broker-J] Heap memory is leaked on deletion of virtual host node
> -
>
> Key: QPID-8156
> URL: https://issues.apache.org/jira/browse/QPID-8156
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.3, qpid-java-broker-7.1.0
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0
>
>
> {{SystemNodeRegistry}} of deleted {{VirtualHost}} is still referenced after
> virtual host node deletion. It prevents VHN/VH garbage collection. The
> reference to registry is hold by
> {{TrustStoreMessageSourceCreator$TrustStoreChangeListener}} which is
> registered on broker as part of invocation
> {{TrustStoreMessageSourceCreator#register}}.
> The user impact is minimalistic as it is not expected that virtual host nodes
> are often created and deleted in production environment.
> Broker restart should resolve the issue.
> Steps to reproduce:
> # create BDB HA virtual host node
> # delete BDB HA virtual host node
> # collect heap dump and check references to deleted virtual host node
> {noformat}
> select * from
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImplWithAccessChecking
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
