[jira] [Created] (PROTON-1266) Reactor API does not allow to set maxFrameSize
Michael Haeusler created PROTON-1266: Summary: Reactor API does not allow to set maxFrameSize Key: PROTON-1266 URL: https://issues.apache.org/jira/browse/PROTON-1266 Project: Qpid Proton Issue Type: Improvement Components: proton-j Affects Versions: 0.12.2 Reporter: Michael Haeusler There is currently no option to set the maxFrameSize of the Transport instance when using the Reactor API. In the server case the whole setup happens in the private AcceptorReadable class. In client case there is one option to subclass IOHandler and override the onConnectionLocalOpen(Event event) method, so that the max frame size can be set. However this requires that the onConnectionLocalOpen method of the parent class is never called which results in duplicate code and may diverge from the parent code when updating to a later proton-j version. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1265) Testing with python 3 is broken
[ https://issues.apache.org/jira/browse/PROTON-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-1265. - Resolution: Fixed Fix Version/s: 0.14.0 > Testing with python 3 is broken > --- > > Key: PROTON-1265 > URL: https://issues.apache.org/jira/browse/PROTON-1265 > Project: Qpid Proton > Issue Type: Bug > Components: build >Affects Versions: 0.12.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.14.0 > > > In various specific circumstances (not always) ctest fails if python 3 is > being used. > For example it fails on windows; it fails if you specify > PYTHON_EXECUTABLE=/usr/bin/python3 specifically for cmake. > Some of this is due to python 2 specific code that has snuck into the test > code, and some is due to calling subsidiary python scripts using the wrong > python interpreter. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1265) Testing with python 3 is broken
[ https://issues.apache.org/jira/browse/PROTON-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386689#comment-15386689 ] ASF subversion and git services commented on PROTON-1265: - Commit 7ea2ee12afb983a8c3a9b7fedd2eb974d763b1c8 in qpid-proton's branch refs/heads/master from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=7ea2ee1 ] PROTON-1265: Fix some problems using python 3 with proton-c > Testing with python 3 is broken > --- > > Key: PROTON-1265 > URL: https://issues.apache.org/jira/browse/PROTON-1265 > Project: Qpid Proton > Issue Type: Bug > Components: build >Affects Versions: 0.12.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > > In various specific circumstances (not always) ctest fails if python 3 is > being used. > For example it fails on windows; it fails if you specify > PYTHON_EXECUTABLE=/usr/bin/python3 specifically for cmake. > Some of this is due to python 2 specific code that has snuck into the test > code, and some is due to calling subsidiary python scripts using the wrong > python interpreter. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-1265) Testing with python 3 is broken
[ https://issues.apache.org/jira/browse/PROTON-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-1265: --- Assignee: Andrew Stitcher > Testing with python 3 is broken > --- > > Key: PROTON-1265 > URL: https://issues.apache.org/jira/browse/PROTON-1265 > Project: Qpid Proton > Issue Type: Bug > Components: build >Affects Versions: 0.12.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > > In various specific circumstances (not always) ctest fails if python 3 is > being used. > For example it fails on windows; it fails if you specify > PYTHON_EXECUTABLE=/usr/bin/python3 specifically for cmake. > Some of this is due to python 2 specific code that has snuck into the test > code, and some is due to calling subsidiary python scripts using the wrong > python interpreter. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1265) Testing with python 3 is broken
Andrew Stitcher created PROTON-1265: --- Summary: Testing with python 3 is broken Key: PROTON-1265 URL: https://issues.apache.org/jira/browse/PROTON-1265 Project: Qpid Proton Issue Type: Bug Components: build Affects Versions: 0.12.0 Reporter: Andrew Stitcher In various specific circumstances (not always) ctest fails if python 3 is being used. For example it fails on windows; it fails if you specify PYTHON_EXECUTABLE=/usr/bin/python3 specifically for cmake. Some of this is due to python 2 specific code that has snuck into the test code, and some is due to calling subsidiary python scripts using the wrong python interpreter. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1264) on_receiver_open event after close
[ https://issues.apache.org/jira/browse/PROTON-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386678#comment-15386678 ] Andrew Stitcher commented on PROTON-1264: - I'm not sure there is a bug here. The proton code has sent a close and so has closed half of the connection (client->server), but the other half is still open. So receiving incoming frames is still valid even if _we_ can do nothing with them, until the server send us a close. Given that in general you can#t know whether you expect to send or receive an attach frame first I'm not sure if the behaviour is actually wrong (as opposed to being inscrutable) > on_receiver_open event after close > -- > > Key: PROTON-1264 > URL: https://issues.apache.org/jira/browse/PROTON-1264 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: 0.14.0 >Reporter: Cliff Jansen >Assignee: Cliff Jansen >Priority: Minor > Attachments: slow_attach > > > If the peer is slow to respond with its attach frame from a receiver open and > the initiator gives up and closes the receiver, the eventual attach frame > from the peer will generate an on_receiver_open() event. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (DISPATCH-450) Class and phase should not be part of the address returned in management responses
[
https://issues.apache.org/jira/browse/DISPATCH-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-450:
--
Assignee: Ganesh Murthy
> Class and phase should not be part of the address returned in management
> responses
> --
>
> Key: DISPATCH-450
> URL: https://issues.apache.org/jira/browse/DISPATCH-450
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 0.6.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>
> The address string returned as a response for some management queries
> contains a class and phase as part of the address string. For example, when
> you issue a qdstat -l command, the following entities are returned
> {noformat}
> Entity(name=709ed0b8-bb43-4a17-a814-27d5de452123-$management, identity=15,
> type=org.apache.qpid.dispatch.router.link, linkType=endpoint,
> deliveryCount=1, unsettledCount=0, capacity=250, operStatus=up, linkDir=in,
> connectionId=4, peer=None, owningAddr=M0$management, undeliveredCount=0,
> linkName=709ed0b8-bb43-4a17-a814-27d5de452123-$management,
> adminStatus=enabled)
> Entity(name=709ed0b8-bb43-4a17-a814-27d5de452123-82833595-97ff-41be-94fb-424a0d48999d,
> identity=16, type=org.apache.qpid.dispatch.router.link, linkType=endpoint,
> deliveryCount=0, unsettledCount=0, capacity=250, operStatus=up, linkDir=out,
> connectionId=4, peer=None, owningAddr=Ltemp.y5YXZL3NYEH6sxt,
> undeliveredCount=0,
> linkName=709ed0b8-bb43-4a17-a814-27d5de452123-82833595-97ff-41be-94fb-424a0d48999d,
> adminStatus=enabled)
> {noformat}
> Observe above that owningAddr contains M0 and L (class and phase
> respectively). The class and the phase must be separate fields and not part
> of the owningAddr.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-450) Class and phase should not be part of the address returned in management responses
Ganesh Murthy created DISPATCH-450:
--
Summary: Class and phase should not be part of the address
returned in management responses
Key: DISPATCH-450
URL: https://issues.apache.org/jira/browse/DISPATCH-450
Project: Qpid Dispatch
Issue Type: Bug
Components: Container
Affects Versions: 0.6.0
Reporter: Ganesh Murthy
The address string returned as a response for some management queries contains
a class and phase as part of the address string. For example, when you issue a
qdstat -l command, the following entities are returned
{noformat}
Entity(name=709ed0b8-bb43-4a17-a814-27d5de452123-$management, identity=15,
type=org.apache.qpid.dispatch.router.link, linkType=endpoint, deliveryCount=1,
unsettledCount=0, capacity=250, operStatus=up, linkDir=in, connectionId=4,
peer=None, owningAddr=M0$management, undeliveredCount=0,
linkName=709ed0b8-bb43-4a17-a814-27d5de452123-$management, adminStatus=enabled)
Entity(name=709ed0b8-bb43-4a17-a814-27d5de452123-82833595-97ff-41be-94fb-424a0d48999d,
identity=16, type=org.apache.qpid.dispatch.router.link, linkType=endpoint,
deliveryCount=0, unsettledCount=0, capacity=250, operStatus=up, linkDir=out,
connectionId=4, peer=None, owningAddr=Ltemp.y5YXZL3NYEH6sxt,
undeliveredCount=0,
linkName=709ed0b8-bb43-4a17-a814-27d5de452123-82833595-97ff-41be-94fb-424a0d48999d,
adminStatus=enabled)
{noformat}
Observe above that owningAddr contains M0 and L (class and phase respectively).
The class and the phase must be separate fields and not part of the owningAddr.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1264) on_receiver_open event after close
[ https://issues.apache.org/jira/browse/PROTON-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen updated PROTON-1264: - Attachment: slow_attach A Service Bus example trace. Note that it is normal for the responding attach to be delayed indefinitely since the attach frame filter content is populated from the next available message whenever it eventually arrives. > on_receiver_open event after close > -- > > Key: PROTON-1264 > URL: https://issues.apache.org/jira/browse/PROTON-1264 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: 0.14.0 >Reporter: Cliff Jansen >Assignee: Cliff Jansen >Priority: Minor > Attachments: slow_attach > > > If the peer is slow to respond with its attach frame from a receiver open and > the initiator gives up and closes the receiver, the eventual attach frame > from the peer will generate an on_receiver_open() event. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1264) on_receiver_open event after close
Cliff Jansen created PROTON-1264: Summary: on_receiver_open event after close Key: PROTON-1264 URL: https://issues.apache.org/jira/browse/PROTON-1264 Project: Qpid Proton Issue Type: Bug Components: cpp-binding Affects Versions: 0.14.0 Reporter: Cliff Jansen Assignee: Cliff Jansen Priority: Minor If the peer is slow to respond with its attach frame from a receiver open and the initiator gives up and closes the receiver, the eventual attach frame from the peer will generate an on_receiver_open() event. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1263) c++ add proton::to_string for value and scalar types
[ https://issues.apache.org/jira/browse/PROTON-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1263: Fix Version/s: (was: 0.13.1) (was: 0.13.0) 0.14.0 > c++ add proton::to_string for value and scalar types > > > Key: PROTON-1263 > URL: https://issues.apache.org/jira/browse/PROTON-1263 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: 0.12.2 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Minor > Fix For: 0.14.0 > > > Add proton::to_string overloads for proton::value, proton::scalar and > proton::url. These return a std::string with the same representation given by > ostream operator>>. > Similar to std::to_string() for the built-in integral types. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1263) c++ add proton::to_string for value and scalar types
[ https://issues.apache.org/jira/browse/PROTON-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1263: Fix Version/s: 0.13.1 > c++ add proton::to_string for value and scalar types > > > Key: PROTON-1263 > URL: https://issues.apache.org/jira/browse/PROTON-1263 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: 0.12.2 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Minor > Fix For: 0.14.0 > > > Add proton::to_string overloads for proton::value, proton::scalar and > proton::url. These return a std::string with the same representation given by > ostream operator>>. > Similar to std::to_string() for the built-in integral types. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1263) c++ add proton::to_string for value and scalar types
[ https://issues.apache.org/jira/browse/PROTON-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1263. - Resolution: Fixed > c++ add proton::to_string for value and scalar types > > > Key: PROTON-1263 > URL: https://issues.apache.org/jira/browse/PROTON-1263 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: 0.12.2 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Minor > Fix For: 0.13.0 > > > Add proton::to_string overloads for proton::value, proton::scalar and > proton::url. These return a std::string with the same representation given by > ostream operator>>. > Similar to std::to_string() for the built-in integral types. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1263) c++ add proton::to_string for value and scalar types
[ https://issues.apache.org/jira/browse/PROTON-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386251#comment-15386251 ] ASF subversion and git services commented on PROTON-1263: - Commit f62369d9219b45ecf12d2cf8a2a2424ce54cb75e in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=f62369d ] PROTON-1263: c++ add proton::to_string for value and scalar types Provides ostream<< representation as a string, with std::boolalpha so boolean prints as true/false. Also added for proton::url, since conversion to/from string is common. Cleaned up value op<< to use the scalar op<< for scalar values. > c++ add proton::to_string for value and scalar types > > > Key: PROTON-1263 > URL: https://issues.apache.org/jira/browse/PROTON-1263 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: 0.12.2 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Minor > Fix For: 0.13.0 > > > Add proton::to_string overloads for proton::value, proton::scalar and > proton::url. These return a std::string with the same representation given by > ostream operator>>. > Similar to std::to_string() for the built-in integral types. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1263) c++ add proton::to_string for value and scalar types
[ https://issues.apache.org/jira/browse/PROTON-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386217#comment-15386217 ] ASF subversion and git services commented on PROTON-1263: - Commit 9528a77bbb08249d6f6edd0cae5c1745a9a200eb in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=9528a77 ] PROTON-1263: c++ add proton::to_string for value and scalar types Also added for proton::url, since conversion to/from string is common. Cleaned up value op<< to use the scalar op<< for scalar values. > c++ add proton::to_string for value and scalar types > > > Key: PROTON-1263 > URL: https://issues.apache.org/jira/browse/PROTON-1263 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: 0.12.2 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Minor > Fix For: 0.13.0 > > > Add proton::to_string overloads for proton::value, proton::scalar and > proton::url. These return a std::string with the same representation given by > ostream operator>>. > Similar to std::to_string() for the built-in integral types. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-7276) [Java Broker] Message delay UI improvements
[
https://issues.apache.org/jira/browse/QPID-7276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack reassigned QPID-7276:
--
Assignee: Lorenz Quack
> [Java Broker] Message delay UI improvements
> ---
>
> Key: QPID-7276
> URL: https://issues.apache.org/jira/browse/QPID-7276
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
>Reporter: Keith Wall
>Assignee: Lorenz Quack
> Fix For: qpid-java-6.1
>
> Attachments:
> 0001-QPID-7276-Java-Broker-WMC-WIP-Add-UI-for-message-del.patch
>
>
> QPID-7255 introduced support of message delays. To make the feature more
> useful/usable, the following additions are identified:
> # Extend the Queue UI to allow {{holdOnPublishEnabled}} to be enabled when
> creating or updating a queue.
> # Reveal through the UI when a Queue Entry is held.
> # Make the Message content UI treat {{NotValidBefore}} as a date/time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7276) [Java Broker] Message delay UI improvements
[
https://issues.apache.org/jira/browse/QPID-7276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack updated QPID-7276:
---
Attachment: 0001-QPID-7276-Java-Broker-WMC-WIP-Add-UI-for-message-del.patch
Attached patch is WIP.
* adds a checkbox to add/edit queue to toggle holdOnPublishEnabled
* adds notValidBefore to MessageInfo and expose through messageView dialogue
missing is:
* exposing the held state
* adding the notValidBefore date to the grid (do we want this?)
> [Java Broker] Message delay UI improvements
> ---
>
> Key: QPID-7276
> URL: https://issues.apache.org/jira/browse/QPID-7276
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
>Reporter: Keith Wall
> Fix For: qpid-java-6.1
>
> Attachments:
> 0001-QPID-7276-Java-Broker-WMC-WIP-Add-UI-for-message-del.patch
>
>
> QPID-7255 introduced support of message delays. To make the feature more
> useful/usable, the following additions are identified:
> # Extend the Queue UI to allow {{holdOnPublishEnabled}} to be enabled when
> creating or updating a queue.
> # Reveal through the UI when a Queue Entry is held.
> # Make the Message content UI treat {{NotValidBefore}} as a date/time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7248) Extend the UI to allow queries to be saved, retrieved and re-run
[ https://issues.apache.org/jira/browse/QPID-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386058#comment-15386058 ] Keith Wall commented on QPID-7248: -- r1753475 - I am uncomfortable with the idea of the programatically changing focus to generate events. This feels like a hack. > Extend the UI to allow queries to be saved, retrieved and re-run > > > Key: QPID-7248 > URL: https://issues.apache.org/jira/browse/QPID-7248 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall > Fix For: qpid-java-6.1 > > Attachments: > 0001-QPID-7248-Java-Broker-Preferences-show-preferences-b.patch, > extend-query-ui-to-allow-queries-to-be-saved.tar.gz, > query-browser-patches.tar.gz > > > Extend the UI to allow the user to save a query so that it is available for > use later on. The user should be able to see a list of saved queries, pick > one and rerun it or change it. The user should be able to delete queries too. > The user should also be able to see queries that are visible to him. He > should be able to select these queries and execute them. > * When defining a query, the UI should offer a 'save as' button allowing the > query to be named, visibility to be chosen, and saved. > * If the query has been saved already, the name should be filled in already. > * Saved queries and queries that are visible to the user will appear to the > user as a list (expandable/collapsible widget) > * From the list the user will be able to delete queries that belong to him. > * Also from the list, the user will be able to recall queries (either queries > that belong to him or ones that are visible). The query will be recalled in > the advanced > view, even if the query is representable in standard view. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7356) Change default configuration provided by initial-config.json to model version 6.1
[
https://issues.apache.org/jira/browse/QPID-7356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack updated QPID-7356:
---
Attachment: 0001-QPID-7356-Java-Broker-bump-model-version-in-initial-.patch
> Change default configuration provided by initial-config.json to model version
> 6.1
> -
>
> Key: QPID-7356
> URL: https://issues.apache.org/jira/browse/QPID-7356
> Project: Qpid
> Issue Type: Task
> Components: Java Broker
>Reporter: Keith Wall
>Assignee: Lorenz Quack
> Fix For: qpid-java-6.1
>
> Attachments:
> 0001-QPID-7356-Java-Broker-bump-model-version-in-initial-.patch
>
>
> {{initial-config.json}} stores the default configuration used for a new Java
> Broker instance. It is currently at model version 6.0. Change the
> configuration to 6.1.
> Also change its systest counterpart {{config-systest.json}} too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-7356) Change default configuration provided by initial-config.json to model version 6.1
[
https://issues.apache.org/jira/browse/QPID-7356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack reassigned QPID-7356:
--
Assignee: Lorenz Quack
> Change default configuration provided by initial-config.json to model version
> 6.1
> -
>
> Key: QPID-7356
> URL: https://issues.apache.org/jira/browse/QPID-7356
> Project: Qpid
> Issue Type: Task
> Components: Java Broker
>Reporter: Keith Wall
>Assignee: Lorenz Quack
> Fix For: qpid-java-6.1
>
> Attachments:
> 0001-QPID-7356-Java-Broker-bump-model-version-in-initial-.patch
>
>
> {{initial-config.json}} stores the default configuration used for a new Java
> Broker instance. It is currently at model version 6.0. Change the
> configuration to 6.1.
> Also change its systest counterpart {{config-systest.json}} too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-7337) [Java Broker] Preference Store JDBC/Derby backend
[ https://issues.apache.org/jira/browse/QPID-7337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack resolved QPID-7337. Resolution: Fixed > [Java Broker] Preference Store JDBC/Derby backend > - > > Key: QPID-7337 > URL: https://issues.apache.org/jira/browse/QPID-7337 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Reporter: Lorenz Quack > Fix For: qpid-java-6.1 > > > Implement JDBC/Derby backend to the PreferenceStore > see also QPID-7330 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7347) [Java Broker, WMC] Opening a BDBHA Replica VirtualHost tab results in a 404 error
[
https://issues.apache.org/jira/browse/QPID-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack updated QPID-7347:
---
Attachment: 0001-QPID-7347-Java-Broker-WMC-Add-noop-show.js-for-BDBHA.patch
> [Java Broker, WMC] Opening a BDBHA Replica VirtualHost tab results in a 404
> error
> -
>
> Key: QPID-7347
> URL: https://issues.apache.org/jira/browse/QPID-7347
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0, qpid-java-6.0.4
>Reporter: Lorenz Quack
>Assignee: Lorenz Quack
>Priority: Minor
> Fix For: qpid-java-6.1
>
> Attachments:
> 0001-QPID-7347-Java-Broker-WMC-Add-noop-show.js-for-BDBHA.patch
>
>
> When opening the VirtualHost tab of a BDBHA Replica node I see a 404 error in
> the JavaScript console:
> {code}GET
> http://localhost:8080/js/qpid/management/virtualhost/bdb_ha_replica/show.js{code}
> followed by a rather unhelpful script error:
> {code}
> Error: scriptErrordojo.js:15:20424
> Stack trace:
> _f@http://localhost:8080/dojo/dojo/dojo.js:15:436
> req.injectUrl/_10c<@http://localhost:8080/dojo/dojo/dojo.js:15:18391
> dojo.js:15
> req.signal/<()dojo.js:15
> _9()dojo.js:15
> req.signal()dojo.js:15
> req.injectUrl/_10c<()dojo.js:15
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1263) c++ add proton::to_string for value and scalar types
Alan Conway created PROTON-1263: --- Summary: c++ add proton::to_string for value and scalar types Key: PROTON-1263 URL: https://issues.apache.org/jira/browse/PROTON-1263 Project: Qpid Proton Issue Type: Improvement Components: cpp-binding Affects Versions: 0.12.2 Reporter: Alan Conway Assignee: Alan Conway Priority: Minor Fix For: 0.13.0 Add proton::to_string overloads for proton::value, proton::scalar and proton::url. These return a std::string with the same representation given by ostream operator>>. Similar to std::to_string() for the built-in integral types. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-7347) [Java Broker, WMC] Opening a BDBHA Replica VirtualHost tab results in a 404 error
[
https://issues.apache.org/jira/browse/QPID-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack reassigned QPID-7347:
--
Assignee: Lorenz Quack
> [Java Broker, WMC] Opening a BDBHA Replica VirtualHost tab results in a 404
> error
> -
>
> Key: QPID-7347
> URL: https://issues.apache.org/jira/browse/QPID-7347
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0, qpid-java-6.0.4
>Reporter: Lorenz Quack
>Assignee: Lorenz Quack
>Priority: Minor
> Fix For: qpid-java-6.1
>
>
> When opening the VirtualHost tab of a BDBHA Replica node I see a 404 error in
> the JavaScript console:
> {code}GET
> http://localhost:8080/js/qpid/management/virtualhost/bdb_ha_replica/show.js{code}
> followed by a rather unhelpful script error:
> {code}
> Error: scriptErrordojo.js:15:20424
> Stack trace:
> _f@http://localhost:8080/dojo/dojo/dojo.js:15:436
> req.injectUrl/_10c<@http://localhost:8080/dojo/dojo/dojo.js:15:18391
> dojo.js:15
> req.signal/<()dojo.js:15
> _9()dojo.js:15
> req.signal()dojo.js:15
> req.injectUrl/_10c<()dojo.js:15
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-7238) [Java Broker, WMC] Share data from structure service amongst UI elements
[ https://issues.apache.org/jira/browse/QPID-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7238. -- Resolution: Fixed > [Java Broker, WMC] Share data from structure service amongst UI elements > > > Key: QPID-7238 > URL: https://issues.apache.org/jira/browse/QPID-7238 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Lorenz Quack >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > > Currently the TreeView in the WMC polls the structure service every 5 > seconds. Other UI components (e.g. QueryBuilder) also occasionally need this > information. > We should share the information instead of making multiple requests. > One possible way is to store this information in management. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-7327) [Java Broker] Deleting Redirector VirtualHost results in IllegalStateException
[
https://issues.apache.org/jira/browse/QPID-7327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack resolved QPID-7327.
Resolution: Fixed
> [Java Broker] Deleting Redirector VirtualHost results in IllegalStateException
> --
>
> Key: QPID-7327
> URL: https://issues.apache.org/jira/browse/QPID-7327
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0.3, qpid-java-6.1
>Reporter: Lorenz Quack
>Assignee: Lorenz Quack
>Priority: Minor
> Fix For: qpid-java-6.1
>
>
> When deleting a Redirector VirtualHost through the WMC you get a 500
> response. The broker logs show the following error:
> {code}
> 2016-06-28 12:14:25,234 ERROR [HttpManagement-httpanon-108]
> (o.a.q.s.m.p.f.ExceptionHandlingFilter) - Unexpected exception in servlet
> '/api/latest/virtualhost/drgtde/drgtde':
> java.lang.IllegalStateException: The virtual host state of UNAVAILABLE does
> not permit this operation.
> at
> org.apache.qpid.server.virtualhostnode.RedirectingVirtualHostImpl.throwUnsupportedForRedirector(RedirectingVirtualHostImpl.java:509)
> ~[classes/:na]
> at
> org.apache.qpid.server.virtualhostnode.RedirectingVirtualHostImpl.validateChange(RedirectingVirtualHostImpl.java:132)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1539)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1508)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:567)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:560)
> ~[classes/:na]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:270)
> ~[classes/:na]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:342)
> ~[classes/:na]
> at java.security.AccessController.doPrivileged(Native Method)
> ~[na:1.8.0_91]
> at javax.security.auth.Subject.doAs(Subject.java:360) ~[na:1.8.0_91]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:335)
> ~[classes/:na]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> ~[na:1.8.0_91]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> ~[na:1.8.0_91]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ~[na:1.8.0_91]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7238) [Java Broker, WMC] Share data from structure service amongst UI elements
[ https://issues.apache.org/jira/browse/QPID-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385938#comment-15385938 ] ASF subversion and git services commented on QPID-7238: --- Commit 1753520 from [~k-wall] in branch 'java/trunk' [ https://svn.apache.org/r1753520 ] QPID-7238: Correct typo in variable name > [Java Broker, WMC] Share data from structure service amongst UI elements > > > Key: QPID-7238 > URL: https://issues.apache.org/jira/browse/QPID-7238 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Lorenz Quack >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > > Currently the TreeView in the WMC polls the structure service every 5 > seconds. Other UI components (e.g. QueryBuilder) also occasionally need this > information. > We should share the information instead of making multiple requests. > One possible way is to store this information in management. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7358) [Java Broker] forbid the same state transition to be defined more than once
Lorenz Quack created QPID-7358:
--
Summary: [Java Broker] forbid the same state transition to be
defined more than once
Key: QPID-7358
URL: https://issues.apache.org/jira/browse/QPID-7358
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: qpid-java-6.0, qpid-java-6.1, qpid-java-6.0.5
Reporter: Lorenz Quack
Currently if we define a state transition more than once, only one will be used
and the others will be silently discarded. For example on
{{AbstractVirtualHost}} the state transition {{ERRORED -> ACTIVE}} is defined
twice:
{code}@StateTransition(currentState = {State.UNINITIALIZED, State.ERRORED},
desiredState = State.ACTIVE)
private ListenableFuture onActivate()
{...}
@StateTransition( currentState = { State.STOPPED, State.ERRORED }, desiredState
= State.ACTIVE )
private ListenableFuture onRestart()
{...}{code}
The relevant code that does the discarding is
{{ConfiguredObjectTypeRegistry#addStateTransitions}} and
{{ConfiguredObjectTypeRegistry#addStateTransition}}.
I would argue that this should be a compilation error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-447) Modify cmake to optionally Install stand-alone and hawtio console
[ https://issues.apache.org/jira/browse/DISPATCH-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385898#comment-15385898 ] ASF subversion and git services commented on DISPATCH-447: -- Commit b34136d63201e4853728ab3e5052838c597bd658 in qpid-dispatch's branch refs/heads/master from [~eallen] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=b34136d ] DISPATCH-447 Adding README.txt to stand-alone install > Modify cmake to optionally Install stand-alone and hawtio console > - > > Key: DISPATCH-447 > URL: https://issues.apache.org/jira/browse/DISPATCH-447 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Console >Affects Versions: 0.6.0 >Reporter: Ernest Allen >Assignee: Ernest Allen > Fix For: 0.7.0 > > > Allow the console to be installed to prefix>/share/qpid-dispatch/console > Stand-alone version is put under a stand-alone directory and the hawtio war > file is put inder a hawtio directory. > Add a readme file to the stand-alone version. > Add a custom make target for building the hawtio version. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7247) Implement preferences model and REST API
[ https://issues.apache.org/jira/browse/QPID-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385893#comment-15385893 ] Keith Wall commented on QPID-7247: -- Alex - your changes seemed reasonable. I made a couple of smaller changes, which i think makes things easier to understand. > Implement preferences model and REST API > > > Key: QPID-7247 > URL: https://issues.apache.org/jira/browse/QPID-7247 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > > Implement the preferences model and the REST API described by: > https://cwiki.apache.org/confluence/display/qpid/Preference+Store > After this work it will be possible to add/update/remove preference from the > REST API, but there will be no persistence. At this stage all preferences > will be available to all users. There will be no security in preferences > layer. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7247) Implement preferences model and REST API
[ https://issues.apache.org/jira/browse/QPID-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7247: - Assignee: Alex Rudyy (was: Keith Wall) > Implement preferences model and REST API > > > Key: QPID-7247 > URL: https://issues.apache.org/jira/browse/QPID-7247 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Alex Rudyy > Fix For: qpid-java-6.1 > > > Implement the preferences model and the REST API described by: > https://cwiki.apache.org/confluence/display/qpid/Preference+Store > After this work it will be possible to add/update/remove preference from the > REST API, but there will be no persistence. At this stage all preferences > will be available to all users. There will be no security in preferences > layer. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7247) Implement preferences model and REST API
[ https://issues.apache.org/jira/browse/QPID-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385888#comment-15385888 ] ASF subversion and git services commented on QPID-7247: --- Commit 1753518 from [~k-wall] in branch 'java/trunk' [ https://svn.apache.org/r1753518 ] QPID-7247: Refactor preference validations to make checks more cohesive Also improved the unit tests. > Implement preferences model and REST API > > > Key: QPID-7247 > URL: https://issues.apache.org/jira/browse/QPID-7247 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > > Implement the preferences model and the REST API described by: > https://cwiki.apache.org/confluence/display/qpid/Preference+Store > After this work it will be possible to add/update/remove preference from the > REST API, but there will be no persistence. At this stage all preferences > will be available to all users. There will be no security in preferences > layer. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7278) [Java Broker] broker crashes when creating a JDBC VirtualHost with invalid JDBC Url
[
https://issues.apache.org/jira/browse/QPID-7278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack updated QPID-7278:
---
Attachment: 0001-QPID-7278-Java-Broker-validate-VirtualHost-message-s.patch
validate VH message store in onValidate
> [Java Broker] broker crashes when creating a JDBC VirtualHost with invalid
> JDBC Url
> ---
>
> Key: QPID-7278
> URL: https://issues.apache.org/jira/browse/QPID-7278
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Reporter: Lorenz Quack
>Assignee: Lorenz Quack
> Fix For: qpid-java-6.1
>
> Attachments:
> 0001-QPID-7278-Java-Broker-validate-VirtualHost-message-s.patch
>
>
> trying to create a JDBC VirtualHost with an invalid JDBC Url like
> "jdbc://foo:bar" causes the broker to shutdown due to an uncaught
> StoreException:
> {code}
> org.apache.qpid.server.store.StoreException: Failed to create message store
> tables
> at
> org.apache.qpid.server.store.AbstractJDBCMessageStore.createOrOpenMessageStoreDatabase(AbstractJDBCMessageStore.java:311)
> ~[classes/:na]
> at
> org.apache.qpid.server.store.jdbc.GenericAbstractJDBCMessageStore.openMessageStore(GenericAbstractJDBCMessageStore.java:48)
> ~[classes/:na]
> at
> org.apache.qpid.server.virtualhost.AbstractVirtualHost.onActivate(AbstractVirtualHost.java:1877)
> ~[classes/:na]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0_91]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:1.8.0_91]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0_91]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_91]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1309)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1288)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:909)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:903)
> ~[classes/:na]
> at com.google.common.util.concurrent.Futures$6.run(Futures.java:1319)
> ~[guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:457)
> ~[guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156)
> ~[guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.ExecutionList.add(ExecutionList.java:101)
> ~[guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.AbstractFuture.addListener(AbstractFuture.java:170)
> ~[guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.Futures.addCallback(Futures.java:1322)
> ~[guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.Futures.addCallback(Futures.java:1258)
> ~[guava-18.0.jar:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.doAttainState(AbstractConfiguredObject.java:902)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.access$300(AbstractConfiguredObject.java:81)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$1.execute(AbstractConfiguredObject.java:514)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$1.execute(AbstractConfiguredObject.java:501)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:562)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:555)
> ~[classes/:na]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:270)
> ~[classes/:na]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:342)
> ~[classes/:na]
> at java.security.AccessController.doPrivileged(Native Method)
> ~[na:1.8.0_91]
> at javax.security.auth.Subject.doAs(Subject.java:360) ~[na:1.8.0_91]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:335)
> ~[classes/:na]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> ~[na:1.8.0_91]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> ~[na:1.8.0_91]
> at
> java.ut
[jira] [Assigned] (QPID-7278) [Java Broker] broker crashes when creating a JDBC VirtualHost with invalid JDBC Url
[
https://issues.apache.org/jira/browse/QPID-7278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack reassigned QPID-7278:
--
Assignee: Lorenz Quack
> [Java Broker] broker crashes when creating a JDBC VirtualHost with invalid
> JDBC Url
> ---
>
> Key: QPID-7278
> URL: https://issues.apache.org/jira/browse/QPID-7278
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Reporter: Lorenz Quack
>Assignee: Lorenz Quack
> Fix For: qpid-java-6.1
>
>
> trying to create a JDBC VirtualHost with an invalid JDBC Url like
> "jdbc://foo:bar" causes the broker to shutdown due to an uncaught
> StoreException:
> {code}
> org.apache.qpid.server.store.StoreException: Failed to create message store
> tables
> at
> org.apache.qpid.server.store.AbstractJDBCMessageStore.createOrOpenMessageStoreDatabase(AbstractJDBCMessageStore.java:311)
> ~[classes/:na]
> at
> org.apache.qpid.server.store.jdbc.GenericAbstractJDBCMessageStore.openMessageStore(GenericAbstractJDBCMessageStore.java:48)
> ~[classes/:na]
> at
> org.apache.qpid.server.virtualhost.AbstractVirtualHost.onActivate(AbstractVirtualHost.java:1877)
> ~[classes/:na]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0_91]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:1.8.0_91]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0_91]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_91]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1309)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1288)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:909)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:903)
> ~[classes/:na]
> at com.google.common.util.concurrent.Futures$6.run(Futures.java:1319)
> ~[guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:457)
> ~[guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156)
> ~[guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.ExecutionList.add(ExecutionList.java:101)
> ~[guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.AbstractFuture.addListener(AbstractFuture.java:170)
> ~[guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.Futures.addCallback(Futures.java:1322)
> ~[guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.Futures.addCallback(Futures.java:1258)
> ~[guava-18.0.jar:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.doAttainState(AbstractConfiguredObject.java:902)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.access$300(AbstractConfiguredObject.java:81)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$1.execute(AbstractConfiguredObject.java:514)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$1.execute(AbstractConfiguredObject.java:501)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:562)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:555)
> ~[classes/:na]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:270)
> ~[classes/:na]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:342)
> ~[classes/:na]
> at java.security.AccessController.doPrivileged(Native Method)
> ~[na:1.8.0_91]
> at javax.security.auth.Subject.doAs(Subject.java:360) ~[na:1.8.0_91]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:335)
> ~[classes/:na]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> ~[na:1.8.0_91]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> ~[na:1.8.0_91]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ~[na:1.8.0_91]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
> Caused by: java.sql.S
[jira] [Commented] (PROTON-1255) connection_engine support for built-in proton SSL/SASL
[ https://issues.apache.org/jira/browse/PROTON-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385789#comment-15385789 ] Alan Conway commented on PROTON-1255: - Important note: for external SSL the user will need to set the host and username on the connection object, that should be made clear in docs/examples. For proton-internal SSL, make sure the engine picks up host/user from the internal SSL objects. > connection_engine support for built-in proton SSL/SASL > -- > > Key: PROTON-1255 > URL: https://issues.apache.org/jira/browse/PROTON-1255 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding, go-binding, proton-c >Affects Versions: 0.12.2 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Critical > Fix For: 0.15.0 > > > Make sure proton's built-in SSL and SASL work fully with the connection > engine for all bindings that have one (C, C++, Go) > The connection_engine also allows a secure connection to be established > externally. Check that we have sufficient hooks to pass external security > principal info to the handler via connection and transport properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7248) Extend the UI to allow queries to be saved, retrieved and re-run
[ https://issues.apache.org/jira/browse/QPID-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385621#comment-15385621 ] ASF subversion and git services commented on QPID-7248: --- Commit 1753476 from oru...@apache.org in branch 'java/trunk' [ https://svn.apache.org/r1753476 ] QPID-7248: Emit change event from query widget only when query is changed > Extend the UI to allow queries to be saved, retrieved and re-run > > > Key: QPID-7248 > URL: https://issues.apache.org/jira/browse/QPID-7248 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall > Fix For: qpid-java-6.1 > > Attachments: > 0001-QPID-7248-Java-Broker-Preferences-show-preferences-b.patch, > extend-query-ui-to-allow-queries-to-be-saved.tar.gz, > query-browser-patches.tar.gz > > > Extend the UI to allow the user to save a query so that it is available for > use later on. The user should be able to see a list of saved queries, pick > one and rerun it or change it. The user should be able to delete queries too. > The user should also be able to see queries that are visible to him. He > should be able to select these queries and execute them. > * When defining a query, the UI should offer a 'save as' button allowing the > query to be named, visibility to be chosen, and saved. > * If the query has been saved already, the name should be filled in already. > * Saved queries and queries that are visible to the user will appear to the > user as a list (expandable/collapsible widget) > * From the list the user will be able to delete queries that belong to him. > * Also from the list, the user will be able to recall queries (either queries > that belong to him or ones that are visible). The query will be recalled in > the advanced > view, even if the query is representable in standard view. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7247) Implement preferences model and REST API
[ https://issues.apache.org/jira/browse/QPID-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385619#comment-15385619 ] ASF subversion and git services commented on QPID-7247: --- Commit 1753474 from oru...@apache.org in branch 'java/trunk' [ https://svn.apache.org/r1753474 ] QPID-7247: Fix evluation whether query is own user query or shared one > Implement preferences model and REST API > > > Key: QPID-7247 > URL: https://issues.apache.org/jira/browse/QPID-7247 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > > Implement the preferences model and the REST API described by: > https://cwiki.apache.org/confluence/display/qpid/Preference+Store > After this work it will be possible to add/update/remove preference from the > REST API, but there will be no persistence. At this stage all preferences > will be available to all users. There will be no security in preferences > layer. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7248) Extend the UI to allow queries to be saved, retrieved and re-run
[ https://issues.apache.org/jira/browse/QPID-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385622#comment-15385622 ] ASF subversion and git services commented on QPID-7248: --- Commit 1753477 from oru...@apache.org in branch 'java/trunk' [ https://svn.apache.org/r1753477 ] QPID-7248: Shorten query tab titles > Extend the UI to allow queries to be saved, retrieved and re-run > > > Key: QPID-7248 > URL: https://issues.apache.org/jira/browse/QPID-7248 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall > Fix For: qpid-java-6.1 > > Attachments: > 0001-QPID-7248-Java-Broker-Preferences-show-preferences-b.patch, > extend-query-ui-to-allow-queries-to-be-saved.tar.gz, > query-browser-patches.tar.gz > > > Extend the UI to allow the user to save a query so that it is available for > use later on. The user should be able to see a list of saved queries, pick > one and rerun it or change it. The user should be able to delete queries too. > The user should also be able to see queries that are visible to him. He > should be able to select these queries and execute them. > * When defining a query, the UI should offer a 'save as' button allowing the > query to be named, visibility to be chosen, and saved. > * If the query has been saved already, the name should be filled in already. > * Saved queries and queries that are visible to the user will appear to the > user as a list (expandable/collapsible widget) > * From the list the user will be able to delete queries that belong to him. > * Also from the list, the user will be able to recall queries (either queries > that belong to him or ones that are visible). The query will be recalled in > the advanced > view, even if the query is representable in standard view. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7248) Extend the UI to allow queries to be saved, retrieved and re-run
[ https://issues.apache.org/jira/browse/QPID-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385620#comment-15385620 ] ASF subversion and git services commented on QPID-7248: --- Commit 1753475 from oru...@apache.org in branch 'java/trunk' [ https://svn.apache.org/r1753475 ] QPID-7248: Restore an ability to search query by pressing 'enter' key in advanced mode controls > Extend the UI to allow queries to be saved, retrieved and re-run > > > Key: QPID-7248 > URL: https://issues.apache.org/jira/browse/QPID-7248 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall > Fix For: qpid-java-6.1 > > Attachments: > 0001-QPID-7248-Java-Broker-Preferences-show-preferences-b.patch, > extend-query-ui-to-allow-queries-to-be-saved.tar.gz, > query-browser-patches.tar.gz > > > Extend the UI to allow the user to save a query so that it is available for > use later on. The user should be able to see a list of saved queries, pick > one and rerun it or change it. The user should be able to delete queries too. > The user should also be able to see queries that are visible to him. He > should be able to select these queries and execute them. > * When defining a query, the UI should offer a 'save as' button allowing the > query to be named, visibility to be chosen, and saved. > * If the query has been saved already, the name should be filled in already. > * Saved queries and queries that are visible to the user will appear to the > user as a list (expandable/collapsible widget) > * From the list the user will be able to delete queries that belong to him. > * Also from the list, the user will be able to recall queries (either queries > that belong to him or ones that are visible). The query will be recalled in > the advanced > view, even if the query is representable in standard view. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1261) Qpid-Proton 0.12.2 unable to open link with Azure when using connection_engine
[ https://issues.apache.org/jira/browse/PROTON-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385563#comment-15385563 ] Tobias Duckworth commented on PROTON-1261: -- This problem appears to have been caused by the hostname not being set in a connection_engine build. The simple workaround (until the problem is fixed inside the qpid-proton library) is simply to call connection().host() from within the on_start callback. > Qpid-Proton 0.12.2 unable to open link with Azure when using connection_engine > -- > > Key: PROTON-1261 > URL: https://issues.apache.org/jira/browse/PROTON-1261 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: 0.12.2 > Environment: Linux >Reporter: Tobias Duckworth >Assignee: Cliff Jansen > Attachments: AzureWithQpidProton_FAILonOpenSender.pcapng, > AzureWithQpidProton_SUCCESS.pcapng > > > Since proton's built in SSL does not work when running as a connection_engine > I used libcurl to achieve an SSL connection. > I have tested this against a local broker and am able to connect, open > sessions, senders and receivers fine. > However, on connecting to a Microsoft Azure IoTHub I find that whilst I am > able to connect and open a session, when attempting to open a sender or > receiver the remote (Azure) end immediately closes it again. > The problem does not occur with a reactor/messenger build of the same > program, which uses proton's built in SSL support. However I don't think that > the use of internal or external SSL is the cause of the problem. (It's tricky > to prove this as I haven't found a way to do the io_reads and io_writes with > a reactor build, which is why I'm using connection_engine/socket_engine in > the first place - However, I did hack around in connection_options.cpp and > convinced ssl_init to get called and found that the connection_engine build > fails in the same way when using built in SSL). > I'll try to attach wireshark traces from both sample programs to this bug. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7355) qpid-cpp-client holding open file descriptors to dead tcp sockets after connection is closed
[
https://issues.apache.org/jira/browse/QPID-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385559#comment-15385559
]
Gordon Sim commented on QPID-7355:
--
I can't reproduce this, even using the exact same package. Probably need more
detail on a reproducer to make any further progress.
> qpid-cpp-client holding open file descriptors to dead tcp sockets after
> connection is closed
>
>
> Key: QPID-7355
> URL: https://issues.apache.org/jira/browse/QPID-7355
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
>Affects Versions: qpid-cpp-0.34
>Reporter: Chester Knapp
>Assignee: Gordon Sim
>
> We use the qpid-cpp-client-0.34-6.el7.x86_64 driver in one of our
> applications.
> I'm noticing a lot of open files (to dead TCP sockets) that are being held
> open and it appears that they are qpid related (this project don't open any
> TCP connections other than what the qpid client handles).
> Is there perhaps something I need to do on the underlying
> qpid::messaging::Connection other than call close() in order for the file
> descriptor to be closed?
> Here's some representative output from lsof:
> {code}
> #lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | head -n 1
> COMMANDPID TIDUSER FD TYPE DEVICE SIZE/OFF
> NODE NAME
> cloudisti 6387 6404root 55u sock0,6 0t0
> 66423 protocol: TCP
> {code}
> {code}
> # lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | wc -l
> 192
> {code}
> For what its worth, we don't see this issue in another of our applications,
> which uses a driver built from the qpid-cpp-0.34-rc branch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
