[jira] [Commented] (DISPATCH-875) Document address and link route wildcards
[ https://issues.apache.org/jira/browse/DISPATCH-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16252566#comment-16252566 ] ASF GitHub Bot commented on DISPATCH-875: - GitHub user bhardesty opened a pull request: https://github.com/apache/qpid-dispatch/pull/218 DISPATCH-875 - Doc new "pattern" attribute (WIP) **Note:** This doc update is under review. Please do not merge. Added some doc describing the new pattern attribute. I updated the following procedures: - Routing Messages Between Clients - Routing Messages Through a Broker Queue - Creating a Link Route It's worth noting that I opted to use "word" instead of "token" to refer to the characters that appear between delimiters. This is less precise technically, but it seems to be the most common usage (i.e. most users would use addresses consisting of words). You can merge this pull request into a Git repository by running: $ git pull https://github.com/bhardesty/qpid-dispatch dispatch-875-address-wildcards-doc Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/218.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 #218 commit 51673d1fa2eb37729b568d3172e89fce86bd227d Author: Ben Hardesty Date: 2017-11-13T22:29:05Z Add doc for new 'pattern' attribute. > Document address and link route wildcards > - > > Key: DISPATCH-875 > URL: https://issues.apache.org/jira/browse/DISPATCH-875 > Project: Qpid Dispatch > Issue Type: Bug > Components: Documentation >Affects Versions: 1.1.0 >Reporter: Ben Hardesty >Assignee: Ben Hardesty > > Update Dispatch Router doc to describe how to define groups of addresses > using the new "pattern" address attribute. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #218: DISPATCH-875 - Doc new "pattern" attribute ...
GitHub user bhardesty opened a pull request: https://github.com/apache/qpid-dispatch/pull/218 DISPATCH-875 - Doc new "pattern" attribute (WIP) **Note:** This doc update is under review. Please do not merge. Added some doc describing the new pattern attribute. I updated the following procedures: - Routing Messages Between Clients - Routing Messages Through a Broker Queue - Creating a Link Route It's worth noting that I opted to use "word" instead of "token" to refer to the characters that appear between delimiters. This is less precise technically, but it seems to be the most common usage (i.e. most users would use addresses consisting of words). You can merge this pull request into a Git repository by running: $ git pull https://github.com/bhardesty/qpid-dispatch dispatch-875-address-wildcards-doc Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/218.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 #218 commit 51673d1fa2eb37729b568d3172e89fce86bd227d Author: Ben Hardesty Date: 2017-11-13T22:29:05Z Add doc for new 'pattern' attribute. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid Broker-J 7.0.0 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid Broker-J 7.0.0. Qpid Broker-J 7.0 brings the following major changes: * Improved AMQP 1.0 support * Support for AMQP JMS Mapping Version 1.0 WD09 * Support for JMS 2.0 shared subscriptions * Improved message conversion for applications using different AMQP protocols * Improved direct memory management The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central: http://qpid.apache.org/maven.html Release notes can be found at: https://qpid.apache.org/releases/qpid-broker-j-7.0.0/release-notes.html Thanks to all involved, Alex - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8035) [Site] Update Qpid web site to replace references to Broker for Java with Broker-J
[ https://issues.apache.org/jira/browse/QPID-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-8035. -- Resolution: Fixed > [Site] Update Qpid web site to replace references to Broker for Java with > Broker-J > -- > > Key: QPID-8035 > URL: https://issues.apache.org/jira/browse/QPID-8035 > Project: Qpid > Issue Type: Bug > Components: Website >Reporter: Alex Rudyy > Fix For: qpid-java-broker-7.0.0 > > > The name "Broker for Java" is used on Qpid web site. We need to replace > references to Broker for Java with Broker-J at least on the pages for v7.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-7755) add release scripts for qpid-broker-j and qpid-jms-amqp-0-x
[ https://issues.apache.org/jira/browse/QPID-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-7755. -- Resolution: Fixed > add release scripts for qpid-broker-j and qpid-jms-amqp-0-x > --- > > Key: QPID-7755 > URL: https://issues.apache.org/jira/browse/QPID-7755 > Project: Qpid > Issue Type: Task > Components: Website >Reporter: Lorenz Quack > Fix For: qpid-java-client-0-x-6.3.0, qpid-java-broker-7.0.0 > > > The qpid-site repository contains scripts for generating release pages. > After separation of java broker and client and the migration from svn to git > we need to create new scripts (or update the old ones). > This needs to happen before/as part of the next release. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch issue #217: NO-JIRA - Change format of README from ReStructure...
Github user jdanekrh commented on the issue: https://github.com/apache/qpid-dispatch/pull/217 AsciiDoc would've been even better. GitHub can render it, and Dispatch documentation either is or soon will be in AsciiDoc. https://gist.github.com/dcode/0cfbf2699a1fe9b46ff04c41721dda74 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch issue #217: NO-JIRA - Change format of README from ReStructure...
Github user enkeys commented on the issue: https://github.com/apache/qpid-dispatch/pull/217 I did not notice than CMakeLists depends on this README. Other changes will be needed. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-869) Multiple brokers in a topology are displayed as a single broker
[ https://issues.apache.org/jira/browse/DISPATCH-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-869. --- Resolution: Fixed Fix Version/s: 1.1.0 > Multiple brokers in a topology are displayed as a single broker > --- > > Key: DISPATCH-869 > URL: https://issues.apache.org/jira/browse/DISPATCH-869 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 1.0.0 >Reporter: Ernest Allen >Assignee: Ernest Allen > Fix For: 1.1.0 > > Attachments: artemii.png, artemis.png > > > When there are multiple Artemis brokers in a topology, they are displayed as > a single broker: > !artemis.png|thumbnail! > The topology diagram should display them separately along with their > connections. > !artemii.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-869) Multiple brokers in a topology are displayed as a single broker
[ https://issues.apache.org/jira/browse/DISPATCH-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16251987#comment-16251987 ] ASF subversion and git services commented on DISPATCH-869: -- Commit c2a935fc8bab6d050e6801de8fad1c3fadfbf3df in qpid-dispatch's branch refs/heads/master from [~eallen] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=c2a935f ] DISPATCH-869 Use connection.container to distinguish unique connections to brokers/clients > Multiple brokers in a topology are displayed as a single broker > --- > > Key: DISPATCH-869 > URL: https://issues.apache.org/jira/browse/DISPATCH-869 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 1.0.0 >Reporter: Ernest Allen >Assignee: Ernest Allen > Attachments: artemii.png, artemis.png > > > When there are multiple Artemis brokers in a topology, they are displayed as > a single broker: > !artemis.png|thumbnail! > The topology diagram should display them separately along with their > connections. > !artemii.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-801) Stand-alone version of the console does not open at all when running offline
[
https://issues.apache.org/jira/browse/DISPATCH-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16251979#comment-16251979
]
ASF subversion and git services commented on DISPATCH-801:
--
Commit 75d9b7e31d166db3a9a61095e1e61f597f9fb023 in qpid-dispatch's branch
refs/heads/master from [~eallen]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=75d9b7e ]
DISPATCH-801 Display correct Create form when switching entities
> Stand-alone version of the console does not open at all when running offline
>
>
> Key: DISPATCH-801
> URL: https://issues.apache.org/jira/browse/DISPATCH-801
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
>Affects Versions: 1.0.0
> Environment: Tested in Internet Explorer 11 on Windows 7 with git tip
> at
> {noformat}
> commit 4dd8764b341cdf9e1d5c06c99697f454d4eaa468
> Author: Ganesh Murthy
> Date: Mon Jul 31 17:09:30 2017 -0400
> DISPATCH-799 - Fixed CMakeLists.txt to set the TEST_RUNNER variable
> correctly
> {noformat}
>Reporter: Jiri Daněk
>Assignee: Ernest Allen
>Priority: Minor
> Fix For: 1.1.0
>
>
> My web browser can only connect to the server running the console and to the
> router; the computer does not have unrestricted network access. With this
> setup, the console does not work.
> In stand-alone version, I am unable to even open the main page of the
> console. I get the following error in browser console
> {noformat}
> HTML1300: Navigation occurred.
> File: stand-alone
> DOM7011: The code on this page disabled back and forward caching. For more
> information, see: http://go.microsoft.com/fwlink/?LinkID=291337
> File: dispatch_hawtio_console
> SCRIPT5009: 'angular' is undefined
> File: angular-patternfly.min.js, Line: 1, Column: 247
> SCRIPT5009: 'angular' is undefined
> File: dispatchPlugin.js, Line: 69, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrOverview.js, Line: 37, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrOverviewLogsController.js, Line: 24, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: navbar.js, Line: 86, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrList.js, Line: 31, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrListChart.js, Line: 24, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrCharts.js, Line: 29, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrSchema.js, Line: 24, Column: 3
> ...
> {noformat}
> In Google Chrome, same thing happens
> {noformat}
> 192.168.99.1/:29 GET https://fonts.googleapis.com/css?family=Open+Sans
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:36 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:38 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap-theme.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:136 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:40 GET
> https://cdnjs.cloudflare.com/ajax/libs/patternfly/3.22.1/css/patternfly.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:41 GET
> https://cdnjs.cloudflare.com/ajax/libs/patternfly/3.22.1/css/patternfly-additions.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:45 GET
> https://cdnjs.cloudflare.com/ajax/libs/jquery.tipsy/1.0.2/jquery.tipsy.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:46 GET
> https://cdnjs.cloudflare.com/ajax/libs/ng-grid/2.0.11/ng-grid.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:105 GET
> https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:110 GET
> https://cdnjs.cloudflare.com/ajax/libs/patternfly/3.22.1/js/patternfly.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:113 GET
> https://ajax.googleapis.com/ajax/libs/angularjs/1.6.2/angular.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:114 GET
> https://ajax.googleapis.com/ajax/libs/angularjs/1.6.2/angular-route.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:36 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:38 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap-theme.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:115 GET
> https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.6.2/angular-resource.min.js
> net::ERR_NAME_NOT_
[jira] [Commented] (DISPATCH-801) Stand-alone version of the console does not open at all when running offline
[
https://issues.apache.org/jira/browse/DISPATCH-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16251977#comment-16251977
]
ASF subversion and git services commented on DISPATCH-801:
--
Commit 72a8dc2b72644c5316933ceda5aff3389a9d092f in qpid-dispatch's branch
refs/heads/master from [~eallen]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=72a8dc2 ]
DISPATCH-801 Allow log messages to wrap on overview dialog
> Stand-alone version of the console does not open at all when running offline
>
>
> Key: DISPATCH-801
> URL: https://issues.apache.org/jira/browse/DISPATCH-801
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
>Affects Versions: 1.0.0
> Environment: Tested in Internet Explorer 11 on Windows 7 with git tip
> at
> {noformat}
> commit 4dd8764b341cdf9e1d5c06c99697f454d4eaa468
> Author: Ganesh Murthy
> Date: Mon Jul 31 17:09:30 2017 -0400
> DISPATCH-799 - Fixed CMakeLists.txt to set the TEST_RUNNER variable
> correctly
> {noformat}
>Reporter: Jiri Daněk
>Assignee: Ernest Allen
>Priority: Minor
> Fix For: 1.1.0
>
>
> My web browser can only connect to the server running the console and to the
> router; the computer does not have unrestricted network access. With this
> setup, the console does not work.
> In stand-alone version, I am unable to even open the main page of the
> console. I get the following error in browser console
> {noformat}
> HTML1300: Navigation occurred.
> File: stand-alone
> DOM7011: The code on this page disabled back and forward caching. For more
> information, see: http://go.microsoft.com/fwlink/?LinkID=291337
> File: dispatch_hawtio_console
> SCRIPT5009: 'angular' is undefined
> File: angular-patternfly.min.js, Line: 1, Column: 247
> SCRIPT5009: 'angular' is undefined
> File: dispatchPlugin.js, Line: 69, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrOverview.js, Line: 37, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrOverviewLogsController.js, Line: 24, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: navbar.js, Line: 86, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrList.js, Line: 31, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrListChart.js, Line: 24, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrCharts.js, Line: 29, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrSchema.js, Line: 24, Column: 3
> ...
> {noformat}
> In Google Chrome, same thing happens
> {noformat}
> 192.168.99.1/:29 GET https://fonts.googleapis.com/css?family=Open+Sans
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:36 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:38 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap-theme.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:136 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:40 GET
> https://cdnjs.cloudflare.com/ajax/libs/patternfly/3.22.1/css/patternfly.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:41 GET
> https://cdnjs.cloudflare.com/ajax/libs/patternfly/3.22.1/css/patternfly-additions.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:45 GET
> https://cdnjs.cloudflare.com/ajax/libs/jquery.tipsy/1.0.2/jquery.tipsy.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:46 GET
> https://cdnjs.cloudflare.com/ajax/libs/ng-grid/2.0.11/ng-grid.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:105 GET
> https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:110 GET
> https://cdnjs.cloudflare.com/ajax/libs/patternfly/3.22.1/js/patternfly.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:113 GET
> https://ajax.googleapis.com/ajax/libs/angularjs/1.6.2/angular.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:114 GET
> https://ajax.googleapis.com/ajax/libs/angularjs/1.6.2/angular-route.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:36 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:38 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap-theme.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:115 GET
> https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.6.2/angular-resource.min.js
> net::ERR_NAME_NOT_RESOLV
[jira] [Commented] (DISPATCH-801) Stand-alone version of the console does not open at all when running offline
[
https://issues.apache.org/jira/browse/DISPATCH-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16251976#comment-16251976
]
ASF subversion and git services commented on DISPATCH-801:
--
Commit 7166fe5450750b92b8a3d31a42713db60e422ea1 in qpid-dispatch's branch
refs/heads/master from [~eallen]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=7166fe5 ]
DISPATCH-801 removing unused geo data
> Stand-alone version of the console does not open at all when running offline
>
>
> Key: DISPATCH-801
> URL: https://issues.apache.org/jira/browse/DISPATCH-801
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
>Affects Versions: 1.0.0
> Environment: Tested in Internet Explorer 11 on Windows 7 with git tip
> at
> {noformat}
> commit 4dd8764b341cdf9e1d5c06c99697f454d4eaa468
> Author: Ganesh Murthy
> Date: Mon Jul 31 17:09:30 2017 -0400
> DISPATCH-799 - Fixed CMakeLists.txt to set the TEST_RUNNER variable
> correctly
> {noformat}
>Reporter: Jiri Daněk
>Assignee: Ernest Allen
>Priority: Minor
> Fix For: 1.1.0
>
>
> My web browser can only connect to the server running the console and to the
> router; the computer does not have unrestricted network access. With this
> setup, the console does not work.
> In stand-alone version, I am unable to even open the main page of the
> console. I get the following error in browser console
> {noformat}
> HTML1300: Navigation occurred.
> File: stand-alone
> DOM7011: The code on this page disabled back and forward caching. For more
> information, see: http://go.microsoft.com/fwlink/?LinkID=291337
> File: dispatch_hawtio_console
> SCRIPT5009: 'angular' is undefined
> File: angular-patternfly.min.js, Line: 1, Column: 247
> SCRIPT5009: 'angular' is undefined
> File: dispatchPlugin.js, Line: 69, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrOverview.js, Line: 37, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrOverviewLogsController.js, Line: 24, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: navbar.js, Line: 86, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrList.js, Line: 31, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrListChart.js, Line: 24, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrCharts.js, Line: 29, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrSchema.js, Line: 24, Column: 3
> ...
> {noformat}
> In Google Chrome, same thing happens
> {noformat}
> 192.168.99.1/:29 GET https://fonts.googleapis.com/css?family=Open+Sans
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:36 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:38 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap-theme.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:136 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:40 GET
> https://cdnjs.cloudflare.com/ajax/libs/patternfly/3.22.1/css/patternfly.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:41 GET
> https://cdnjs.cloudflare.com/ajax/libs/patternfly/3.22.1/css/patternfly-additions.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:45 GET
> https://cdnjs.cloudflare.com/ajax/libs/jquery.tipsy/1.0.2/jquery.tipsy.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:46 GET
> https://cdnjs.cloudflare.com/ajax/libs/ng-grid/2.0.11/ng-grid.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:105 GET
> https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:110 GET
> https://cdnjs.cloudflare.com/ajax/libs/patternfly/3.22.1/js/patternfly.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:113 GET
> https://ajax.googleapis.com/ajax/libs/angularjs/1.6.2/angular.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:114 GET
> https://ajax.googleapis.com/ajax/libs/angularjs/1.6.2/angular-route.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:36 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:38 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap-theme.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:115 GET
> https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.6.2/angular-resource.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:11
[jira] [Commented] (DISPATCH-801) Stand-alone version of the console does not open at all when running offline
[
https://issues.apache.org/jira/browse/DISPATCH-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16251978#comment-16251978
]
ASF subversion and git services commented on DISPATCH-801:
--
Commit be0194750ceddff3847ad23dd119aae7069872b1 in qpid-dispatch's branch
refs/heads/master from [~eallen]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=be01947 ]
DISPATCH-801 Remove test popover text on Router info dialog
> Stand-alone version of the console does not open at all when running offline
>
>
> Key: DISPATCH-801
> URL: https://issues.apache.org/jira/browse/DISPATCH-801
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
>Affects Versions: 1.0.0
> Environment: Tested in Internet Explorer 11 on Windows 7 with git tip
> at
> {noformat}
> commit 4dd8764b341cdf9e1d5c06c99697f454d4eaa468
> Author: Ganesh Murthy
> Date: Mon Jul 31 17:09:30 2017 -0400
> DISPATCH-799 - Fixed CMakeLists.txt to set the TEST_RUNNER variable
> correctly
> {noformat}
>Reporter: Jiri Daněk
>Assignee: Ernest Allen
>Priority: Minor
> Fix For: 1.1.0
>
>
> My web browser can only connect to the server running the console and to the
> router; the computer does not have unrestricted network access. With this
> setup, the console does not work.
> In stand-alone version, I am unable to even open the main page of the
> console. I get the following error in browser console
> {noformat}
> HTML1300: Navigation occurred.
> File: stand-alone
> DOM7011: The code on this page disabled back and forward caching. For more
> information, see: http://go.microsoft.com/fwlink/?LinkID=291337
> File: dispatch_hawtio_console
> SCRIPT5009: 'angular' is undefined
> File: angular-patternfly.min.js, Line: 1, Column: 247
> SCRIPT5009: 'angular' is undefined
> File: dispatchPlugin.js, Line: 69, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrOverview.js, Line: 37, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrOverviewLogsController.js, Line: 24, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: navbar.js, Line: 86, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrList.js, Line: 31, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrListChart.js, Line: 24, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrCharts.js, Line: 29, Column: 3
> SCRIPT5007: Unable to get property 'controller' of undefined or null reference
> File: qdrSchema.js, Line: 24, Column: 3
> ...
> {noformat}
> In Google Chrome, same thing happens
> {noformat}
> 192.168.99.1/:29 GET https://fonts.googleapis.com/css?family=Open+Sans
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:36 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:38 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap-theme.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:136 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:40 GET
> https://cdnjs.cloudflare.com/ajax/libs/patternfly/3.22.1/css/patternfly.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:41 GET
> https://cdnjs.cloudflare.com/ajax/libs/patternfly/3.22.1/css/patternfly-additions.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:45 GET
> https://cdnjs.cloudflare.com/ajax/libs/jquery.tipsy/1.0.2/jquery.tipsy.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:46 GET
> https://cdnjs.cloudflare.com/ajax/libs/ng-grid/2.0.11/ng-grid.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:105 GET
> https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:110 GET
> https://cdnjs.cloudflare.com/ajax/libs/patternfly/3.22.1/js/patternfly.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:113 GET
> https://ajax.googleapis.com/ajax/libs/angularjs/1.6.2/angular.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:114 GET
> https://ajax.googleapis.com/ajax/libs/angularjs/1.6.2/angular-route.min.js
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:36 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:38 GET
> https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap-theme.min.css
> net::ERR_NAME_NOT_RESOLVED
> 192.168.99.1/:115 GET
> https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.6.2/angular-resource.min.js
> net::ERR_NAME_NOT_RESOL
[jira] [Resolved] (DISPATCH-876) config file linkRoute should use connection instead of connector
[ https://issues.apache.org/jira/browse/DISPATCH-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-876. --- Resolution: Fixed Assignee: Ernest Allen Fix Version/s: 1.1.0 > config file linkRoute should use connection instead of connector > - > > Key: DISPATCH-876 > URL: https://issues.apache.org/jira/browse/DISPATCH-876 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Affects Versions: 1.0.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Trivial > Fix For: 1.1.0 > > > The file tests/config-2-broker/A.conf defines several linkRoutes. The router > won't start using this config file because the linRoutes are defining > connector: attributes instead of connection: attributes. > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #217: NO-JIRA - Change format of README from ReSt...
GitHub user enkeys opened a pull request: https://github.com/apache/qpid-dispatch/pull/217 NO-JIRA - Change format of README from ReStructuredText to Markdown - Renamed README to README.md - Added badges for Travis build status and Apache 2.0 license - In READMEÂ moved 'Dependencies' under 'Building and testing' You can merge this pull request into a Git repository by running: $ git pull https://github.com/enkeys/qpid-dispatch readme Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/217.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 #217 commit 1a0929274d953dd01f2da008bd96505d8cd38148 Author: Dominik Lenoch Date: 2017-11-09T09:44:18Z NO-JIRA - Change format of README from ReStructuredText to Markdown Renamed README to README.md Added badges for Travis build status and Apache 2.0 license In READMEÂ moved 'Dependencies' under 'Building and testing' --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-876) config file linkRoute should use connection instead of connector
[ https://issues.apache.org/jira/browse/DISPATCH-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16251958#comment-16251958 ] ASF subversion and git services commented on DISPATCH-876: -- Commit 8856b8cc0d67cd1789b9b1d756283e4d61b1d226 in qpid-dispatch's branch refs/heads/master from [~eallen] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=8856b8c ] DISPATCH-876 Use connection instead of connector in linkRoute section > config file linkRoute should use connection instead of connector > - > > Key: DISPATCH-876 > URL: https://issues.apache.org/jira/browse/DISPATCH-876 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Affects Versions: 1.0.0 >Reporter: Ernest Allen >Priority: Trivial > > The file tests/config-2-broker/A.conf defines several linkRoutes. The router > won't start using this config file because the linRoutes are defining > connector: attributes instead of connection: attributes. > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-876) config file linkRoute should use connection instead of connector
Ernest Allen created DISPATCH-876: - Summary: config file linkRoute should use connection instead of connector Key: DISPATCH-876 URL: https://issues.apache.org/jira/browse/DISPATCH-876 Project: Qpid Dispatch Issue Type: Bug Components: Tests Affects Versions: 1.0.0 Reporter: Ernest Allen Priority: Trivial The file tests/config-2-broker/A.conf defines several linkRoutes. The router won't start using this config file because the linRoutes are defining connector: attributes instead of connection: attributes. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7898) [Java 0-8...0-9-1 Client] Calling getJMSReplyTo on a received message can lead to NullPointerException
[
https://issues.apache.org/jira/browse/QPID-7898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16251757#comment-16251757
]
ASF subversion and git services commented on QPID-7898:
---
Commit ae6d79d38334127039e2d62826d9c441f60f1659 in qpid-jms-amqp-0-x's branch
refs/heads/master from [~k-wall]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms-amqp-0-x.git;h=ae6d79d ]
QPID-7898: [Qpid JMS AMQP 0-x] Prevent possibilities of NPEs when 0-8 path
parses a reply-to address that is not BURL formatted
> [Java 0-8...0-9-1 Client] Calling getJMSReplyTo on a received message can
> lead to NullPointerException
> --
>
> Key: QPID-7898
> URL: https://issues.apache.org/jira/browse/QPID-7898
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Reporter: Lorenz Quack
> Fix For: qpid-java-client-0-x-6.3.0
>
>
> A call to {{Message#getJMSReplyTo()}} can lead to a {{NullPointerException}}.
> {noformat}java.lang.NullPointerException
> at
> org.apache.qpid.client.message.AMQMessageDelegate_0_8.getJMSReplyTo(AMQMessageDelegate_0_8.java:301)
> at
> org.apache.qpid.client.message.AbstractJMSMessage.getJMSReplyTo(AbstractJMSMessage.java:104){noformat}
> The circumstances are
> * a Message received over AMQP 0-8...0-9-1
> * the replyTo set to a non-BURL address not containing a slash ("/")
> * the address must not exist in the
> org.apache.qpid.client.message.AMQMessageDelegate_0_8#_destinationCache
> The code throwing the NPE:
> {code:title=AMQMessageDelegate_0_8#getJMSReplyTo (slightly edited for
> clarity)}public Destination getJMSReplyTo() throws JMSException
> {
> String replyToEncoding =
> getContentHeaderProperties().getReplyToAsString();
> Destination dest;
> try {
> BindingURL binding = new AMQBindingURL(replyToEncoding);
> // something else
> } catch (URISyntaxException e) {
> if (replyToEncoding.startsWith("/")) {
> // something
> } else if (replyToEncoding.contains("/")) {
> // something
> } else if (getAMQSession().isQueueBound(replyToEncoding, null, null))
> {
> // THE ABOVE CALL TO getAMQSession THROWS A NPE!!!
> } else {
> // something
> }
> }
> return dest;
> }{code}
> The root cause seems to be that we are relying on the Message having
> knowledge of the session but we aren't setting the Session on the Message on
> all code paths.
> I encountered this testing message conversion.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-7898) [Java 0-8...0-9-1 Client] Calling getJMSReplyTo on a received message can lead to NullPointerException
[
https://issues.apache.org/jira/browse/QPID-7898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall reassigned QPID-7898:
Assignee: Keith Wall
> [Java 0-8...0-9-1 Client] Calling getJMSReplyTo on a received message can
> lead to NullPointerException
> --
>
> Key: QPID-7898
> URL: https://issues.apache.org/jira/browse/QPID-7898
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Reporter: Lorenz Quack
>Assignee: Keith Wall
> Fix For: qpid-java-client-0-x-6.3.0
>
>
> A call to {{Message#getJMSReplyTo()}} can lead to a {{NullPointerException}}.
> {noformat}java.lang.NullPointerException
> at
> org.apache.qpid.client.message.AMQMessageDelegate_0_8.getJMSReplyTo(AMQMessageDelegate_0_8.java:301)
> at
> org.apache.qpid.client.message.AbstractJMSMessage.getJMSReplyTo(AbstractJMSMessage.java:104){noformat}
> The circumstances are
> * a Message received over AMQP 0-8...0-9-1
> * the replyTo set to a non-BURL address not containing a slash ("/")
> * the address must not exist in the
> org.apache.qpid.client.message.AMQMessageDelegate_0_8#_destinationCache
> The code throwing the NPE:
> {code:title=AMQMessageDelegate_0_8#getJMSReplyTo (slightly edited for
> clarity)}public Destination getJMSReplyTo() throws JMSException
> {
> String replyToEncoding =
> getContentHeaderProperties().getReplyToAsString();
> Destination dest;
> try {
> BindingURL binding = new AMQBindingURL(replyToEncoding);
> // something else
> } catch (URISyntaxException e) {
> if (replyToEncoding.startsWith("/")) {
> // something
> } else if (replyToEncoding.contains("/")) {
> // something
> } else if (getAMQSession().isQueueBound(replyToEncoding, null, null))
> {
> // THE ABOVE CALL TO getAMQSession THROWS A NPE!!!
> } else {
> // something
> }
> }
> return dest;
> }{code}
> The root cause seems to be that we are relying on the Message having
> knowledge of the session but we aren't setting the Session on the Message on
> all code paths.
> I encountered this testing message conversion.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7898) [Java 0-8...0-9-1 Client] Calling getJMSReplyTo on a received message can lead to NullPointerException
[
https://issues.apache.org/jira/browse/QPID-7898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7898:
-
Status: Reviewable (was: In Progress)
> [Java 0-8...0-9-1 Client] Calling getJMSReplyTo on a received message can
> lead to NullPointerException
> --
>
> Key: QPID-7898
> URL: https://issues.apache.org/jira/browse/QPID-7898
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Reporter: Lorenz Quack
>Assignee: Keith Wall
> Fix For: qpid-java-client-0-x-6.3.0
>
>
> A call to {{Message#getJMSReplyTo()}} can lead to a {{NullPointerException}}.
> {noformat}java.lang.NullPointerException
> at
> org.apache.qpid.client.message.AMQMessageDelegate_0_8.getJMSReplyTo(AMQMessageDelegate_0_8.java:301)
> at
> org.apache.qpid.client.message.AbstractJMSMessage.getJMSReplyTo(AbstractJMSMessage.java:104){noformat}
> The circumstances are
> * a Message received over AMQP 0-8...0-9-1
> * the replyTo set to a non-BURL address not containing a slash ("/")
> * the address must not exist in the
> org.apache.qpid.client.message.AMQMessageDelegate_0_8#_destinationCache
> The code throwing the NPE:
> {code:title=AMQMessageDelegate_0_8#getJMSReplyTo (slightly edited for
> clarity)}public Destination getJMSReplyTo() throws JMSException
> {
> String replyToEncoding =
> getContentHeaderProperties().getReplyToAsString();
> Destination dest;
> try {
> BindingURL binding = new AMQBindingURL(replyToEncoding);
> // something else
> } catch (URISyntaxException e) {
> if (replyToEncoding.startsWith("/")) {
> // something
> } else if (replyToEncoding.contains("/")) {
> // something
> } else if (getAMQSession().isQueueBound(replyToEncoding, null, null))
> {
> // THE ABOVE CALL TO getAMQSession THROWS A NPE!!!
> } else {
> // something
> }
> }
> return dest;
> }{code}
> The root cause seems to be that we are relying on the Message having
> knowledge of the session but we aren't setting the Session on the Message on
> all code paths.
> I encountered this testing message conversion.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1660) The gemspec dependency on "json ~> 0" breaks anyone dependning on a recent version of json
[
https://issues.apache.org/jira/browse/PROTON-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16251462#comment-16251462
]
Irina Boverman commented on PROTON-1660:
Updated.
> The gemspec dependency on "json ~> 0" breaks anyone dependning on a recent
> version of json
> --
>
> Key: PROTON-1660
> URL: https://issues.apache.org/jira/browse/PROTON-1660
> Project: Qpid Proton
> Issue Type: Bug
> Components: ruby-binding
>Reporter: Greg Blomquist
>Assignee: Alan Conway
> Fix For: proton-c-0.18.1
>
>
> https://github.com/apache/qpid-proton/blob/0790bb99fabc4a6d7c1c12fb09c0ff76a3594f5a/proton-c/bindings/ruby/qpid_proton.gemspec.in#L31
>
> This line was recently changed in qpid-proton master. It causes any project
> that depends on a recent version of json to break when pulling together
> dependencies. The pessimistic style of version constraint means that
> qpid-proton requires a json version of >= 0.0, but < 1.
> For instance, our project has a dependency on json 2.x. And, we see this
> error when bundling with qpid-proton:
> {code:none}
> Bundler could not find compatible versions for gem "json":
> In Gemfile: manageiq-providers-azure was resolved to 0.1.0,
> which depends on azure-armrest (~> 0.9.1) was resolved to 0.9.1, which
> depends on json (~> 2.0.1)
> qpid_proton (~> 0.18) was resolved to 0.18.0, which depends on json (~> 0)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7898) [Java 0-8...0-9-1 Client] Calling getJMSReplyTo on a received message can lead to NullPointerException
[
https://issues.apache.org/jira/browse/QPID-7898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7898:
-
Description:
A call to {{Message#getJMSReplyTo()}} can lead to a {{NullPointerException}}.
{noformat}java.lang.NullPointerException
at
org.apache.qpid.client.message.AMQMessageDelegate_0_8.getJMSReplyTo(AMQMessageDelegate_0_8.java:301)
at
org.apache.qpid.client.message.AbstractJMSMessage.getJMSReplyTo(AbstractJMSMessage.java:104){noformat}
The circumstances are
* a Message received over AMQP 0-8...0-9-1
* the replyTo set to a non-BURL address not containing a slash ("/")
* the address must not exist in the
org.apache.qpid.client.message.AMQMessageDelegate_0_8#_destinationCache
The code throwing the NPE:
{code:title=AMQMessageDelegate_0_8#getJMSReplyTo (slightly edited for
clarity)}public Destination getJMSReplyTo() throws JMSException
{
String replyToEncoding = getContentHeaderProperties().getReplyToAsString();
Destination dest;
try {
BindingURL binding = new AMQBindingURL(replyToEncoding);
// something else
} catch (URISyntaxException e) {
if (replyToEncoding.startsWith("/")) {
// something
} else if (replyToEncoding.contains("/")) {
// something
} else if (getAMQSession().isQueueBound(replyToEncoding, null, null)) {
// THE ABOVE CALL TO getAMQSession THROWS A NPE!!!
} else {
// something
}
}
return dest;
}{code}
The root cause seems to be that we are relying on the Message having knowledge
of the session but we aren't setting the Session on the Message on all code
paths.
I encountered this testing message conversion.
was:
A call to {{Message#getJMSReplyTo()}} can lead to a {{NullPointerException}}.
{noformat}java.lang.NullPointerException
at
org.apache.qpid.client.message.AMQMessageDelegate_0_8.getJMSReplyTo(AMQMessageDelegate_0_8.java:301)
at
org.apache.qpid.client.message.AbstractJMSMessage.getJMSReplyTo(AbstractJMSMessage.java:104){noformat}
The circumstances are
* a Message received over AMQP 0-8...0-9-1
* the replyTo set to a non-BURL address not containing a slash ("/")
The code throwing the NPE:
{code:title=AMQMessageDelegate_0_8#getJMSReplyTo (slightly edited for
clarity)}public Destination getJMSReplyTo() throws JMSException
{
String replyToEncoding = getContentHeaderProperties().getReplyToAsString();
Destination dest;
try {
BindingURL binding = new AMQBindingURL(replyToEncoding);
// something else
} catch (URISyntaxException e) {
if (replyToEncoding.startsWith("/")) {
// something
} else if (replyToEncoding.contains("/")) {
// something
} else if (getAMQSession().isQueueBound(replyToEncoding, null, null)) {
// THE ABOVE CALL TO getAMQSession THROWS A NPE!!!
} else {
// something
}
}
return dest;
}{code}
The root cause seems to be that we are relying on the Message having knowledge
of the session but we aren't setting the Session on the Message on all code
paths.
I encountered this testing message conversion.
> [Java 0-8...0-9-1 Client] Calling getJMSReplyTo on a received message can
> lead to NullPointerException
> --
>
> Key: QPID-7898
> URL: https://issues.apache.org/jira/browse/QPID-7898
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Reporter: Lorenz Quack
> Fix For: qpid-java-client-0-x-6.3.0
>
>
> A call to {{Message#getJMSReplyTo()}} can lead to a {{NullPointerException}}.
> {noformat}java.lang.NullPointerException
> at
> org.apache.qpid.client.message.AMQMessageDelegate_0_8.getJMSReplyTo(AMQMessageDelegate_0_8.java:301)
> at
> org.apache.qpid.client.message.AbstractJMSMessage.getJMSReplyTo(AbstractJMSMessage.java:104){noformat}
> The circumstances are
> * a Message received over AMQP 0-8...0-9-1
> * the replyTo set to a non-BURL address not containing a slash ("/")
> * the address must not exist in the
> org.apache.qpid.client.message.AMQMessageDelegate_0_8#_destinationCache
> The code throwing the NPE:
> {code:title=AMQMessageDelegate_0_8#getJMSReplyTo (slightly edited for
> clarity)}public Destination getJMSReplyTo() throws JMSException
> {
> String replyToEncoding =
> getContentHeaderProperties().getReplyToAsString();
> Destination dest;
> try {
> BindingURL binding = new AMQBindingURL(replyToEncoding);
> // something else
> } catch (URISyntaxException e) {
> if (replyToEncoding.startsWith("/")) {
> // something
> } else if (replyToEncoding.contains("/")) {
> // something
> } else if (getA
[jira] [Commented] (QPID-7725) Remove direct byte buffer implementation
[ https://issues.apache.org/jira/browse/QPID-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16251175#comment-16251175 ] Keith Wall commented on QPID-7725: -- Changes seemed reasonable to me. Alex and I reviewed 1fdecf3. > Remove direct byte buffer implementation > > > Key: QPID-7725 > URL: https://issues.apache.org/jira/browse/QPID-7725 > Project: Qpid > Issue Type: Improvement > Components: Java Client >Reporter: Keith Wall >Priority: Minor > Fix For: qpid-java-client-0-x-6.3.0 > > > Direct byte buffers were never used on the client, and now the client/broker > are separate, the code is unused. It is unused and could be removed. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-7725) Remove direct byte buffer implementation
[ https://issues.apache.org/jira/browse/QPID-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7725. -- Resolution: Fixed > Remove direct byte buffer implementation > > > Key: QPID-7725 > URL: https://issues.apache.org/jira/browse/QPID-7725 > Project: Qpid > Issue Type: Improvement > Components: Java Client >Reporter: Keith Wall >Priority: Minor > Fix For: qpid-java-client-0-x-6.3.0 > > > Direct byte buffers were never used on the client, and now the client/broker > are separate, the code is unused. It is unused and could be removed. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7725) Remove direct byte buffer implementation
[ https://issues.apache.org/jira/browse/QPID-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16251165#comment-16251165 ] ASF subversion and git services commented on QPID-7725: --- Commit 1fdecf3a80dfadc8d1b5d3ab42334c2154587fb6 in qpid-jms-amqp-0-x's branch refs/heads/master from [~k-wall] [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms-amqp-0-x.git;h=1fdecf3 ] QPID-7725: [Qpid JMS AMQP 0-x] Remove more remnants of direct buffers from 0-10 > Remove direct byte buffer implementation > > > Key: QPID-7725 > URL: https://issues.apache.org/jira/browse/QPID-7725 > Project: Qpid > Issue Type: Improvement > Components: Java Client >Reporter: Keith Wall >Priority: Minor > Fix For: qpid-java-client-0-x-6.3.0 > > > Direct byte buffers were never used on the client, and now the client/broker > are separate, the code is unused. It is unused and could be removed. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6933) Factor out a JMS client neutral messaging test suite from system tests
[ https://issues.apache.org/jira/browse/QPID-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16251168#comment-16251168 ] ASF subversion and git services commented on QPID-6933: --- Commit 35ed69903a961e9dfd1eb4df9f82dff3abe16ab7 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=35ed699 ] [QPID-6933][System Tests] Remove protocol specific tests relying on specific client client classes * Tests are deleted due to changes to client interface ByteBufferSender * Protocol specific tests needs to be implemented to replace deleted system tests > Factor out a JMS client neutral messaging test suite from system tests > -- > > Key: QPID-6933 > URL: https://issues.apache.org/jira/browse/QPID-6933 > Project: Qpid > Issue Type: Improvement > Components: Java Tests >Reporter: Keith Wall > > The existing system testsuite is in a poor state. > * It is poorly structured > * Mixes different types of test. i.e. messaging behaviour with those that > test features of the Java Broker (e.g. REST). > * Many of the tests refer directly to the implementation classes of the Qpid > Client 0-8..0-10 client meaning the tests cannot be run using the new client. > As a first step, we want to factor out a separate messaging system test suite: > * The tests in this suite will be JMS client neutral. > * Written in terms of JNDI/JMS client > * Configurations/Broker observations will be performed via a clean > Broker-neutral facade. For instance > ** a mechanism to cause the queue to be created of a particular type. > ** a mechanism to observe a queue depth. > * The tests will be classified by feature (to be defined) > * The classification system will be used to drive an exclusion feature (to be > defined). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-8035) [Site] Update Qpid web site to replace references to Broker for Java with Broker-J
Alex Rudyy created QPID-8035: Summary: [Site] Update Qpid web site to replace references to Broker for Java with Broker-J Key: QPID-8035 URL: https://issues.apache.org/jira/browse/QPID-8035 Project: Qpid Issue Type: Bug Components: Website Reporter: Alex Rudyy Fix For: qpid-java-broker-7.0.0 The name "Broker for Java" is used on Qpid web site. We need to replace references to Broker for Java with Broker-J at least on the pages for v7.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-7905) [Java Client AMQP 0-x] Connection#start is not thread-safe
[
https://issues.apache.org/jira/browse/QPID-7905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall closed QPID-7905.
Resolution: Won't Fix
Marking Won't Fix. Use newer Qpid JMS Client (AMQ1.0)
https://qpid.apache.org/components/jms/index.html
> [Java Client AMQP 0-x] Connection#start is not thread-safe
> --
>
> Key: QPID-7905
> URL: https://issues.apache.org/jira/browse/QPID-7905
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Reporter: Lorenz Quack
>
> The JMS spec says that Connections may be used from several threads
> concurrently.
> However, our implementation of {{Connection#start}} is currently not
> thread-safe. It iterates over its list of sessions and calls
> {{Session#start}}. The session rightfully (this is specified in the JMS spec
> as well) assumes that it is being called from a single thread.
> An example of the impact of this is that a session can be used (by
> {{Connection#start}}) after it has been closed (via {{Session#close}})
> leading to an Exception due to the broker receiving a frame with an unknown
> {{channelId}}.
> Note: The comment on {{Connection#start}} stating that JMS allows for non
> thread-safe implementations seems to be in error!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7905) [Java Client AMQP 0-x] Connection#start is not thread-safe
[
https://issues.apache.org/jira/browse/QPID-7905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7905:
-
Priority: Major (was: Critical)
> [Java Client AMQP 0-x] Connection#start is not thread-safe
> --
>
> Key: QPID-7905
> URL: https://issues.apache.org/jira/browse/QPID-7905
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Reporter: Lorenz Quack
>
> The JMS spec says that Connections may be used from several threads
> concurrently.
> However, our implementation of {{Connection#start}} is currently not
> thread-safe. It iterates over its list of sessions and calls
> {{Session#start}}. The session rightfully (this is specified in the JMS spec
> as well) assumes that it is being called from a single thread.
> An example of the impact of this is that a session can be used (by
> {{Connection#start}}) after it has been closed (via {{Session#close}})
> leading to an Exception due to the broker receiving a frame with an unknown
> {{channelId}}.
> Note: The comment on {{Connection#start}} stating that JMS allows for non
> thread-safe implementations seems to be in error!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7905) [Java Client AMQP 0-x] Connection#start is not thread-safe
[
https://issues.apache.org/jira/browse/QPID-7905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7905:
-
Fix Version/s: (was: qpid-java-client-0-x-6.3.0)
> [Java Client AMQP 0-x] Connection#start is not thread-safe
> --
>
> Key: QPID-7905
> URL: https://issues.apache.org/jira/browse/QPID-7905
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Reporter: Lorenz Quack
>Priority: Critical
>
> The JMS spec says that Connections may be used from several threads
> concurrently.
> However, our implementation of {{Connection#start}} is currently not
> thread-safe. It iterates over its list of sessions and calls
> {{Session#start}}. The session rightfully (this is specified in the JMS spec
> as well) assumes that it is being called from a single thread.
> An example of the impact of this is that a session can be used (by
> {{Connection#start}}) after it has been closed (via {{Session#close}})
> leading to an Exception due to the broker receiving a frame with an unknown
> {{channelId}}.
> Note: The comment on {{Connection#start}} stating that JMS allows for non
> thread-safe implementations seems to be in error!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
