[jira] [Assigned] (PROTON-1244) Add user & password connection_options

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher reassigned PROTON-1244:
---

Assignee: Andrew Stitcher  (was: Cliff Jansen)

> Add user & password connection_options
> --
>
> Key: PROTON-1244
> URL: https://issues.apache.org/jira/browse/PROTON-1244
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>
> It would be useful if we could a set connection authentication aside from the 
> textual URL used to specify the connection address.
> I propose that we add
> * connection_options::user(const std::tring&)
> * connection_options::password(const std::string&)



--
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-1238) There is no way to query proton::connection for the url it was created with.

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher reassigned PROTON-1238:
---

Assignee: Andrew Stitcher  (was: Cliff Jansen)

> There is no way to query proton::connection for the url it was created with.
> 
>
> Key: PROTON-1238
> URL: https://issues.apache.org/jira/browse/PROTON-1238
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>
> Although the user could just remember whatever url they used to create a 
> given connection, it is duplicative when the library has the info around.
> Also if it is not provided then the user has to plumb to info to places it is 
> needed inside the event handlers, however the handlers will already get the 
> connection context object anyway so that is unecessary and an extra burden.



--
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-1239) There is no way to query proton::connection for user

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved PROTON-1239.
-
   Resolution: Fixed
Fix Version/s: 0.14.0

> There is no way to query proton::connection for user
> 
>
> Key: PROTON-1239
> URL: https://issues.apache.org/jira/browse/PROTON-1239
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: 0.14.0
>
>
> There is no accessor for the user property of a connection. Either on the 
> client or server side.
> There is a parallel user setter so I tend to think this is an oversight.
> It is not such an issue on the client side (as in theory you could just 
> record the user you set), but on the server side the alternative is to use 
> the sasl object attached to the transport, which is awkward and doesn't cover 
> all the possibilities (SSL client certificates).



--
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-1243) Calling proton::container::stop() from within event handler causes infinite recursion

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher reassigned PROTON-1243:
---

Assignee: Andrew Stitcher  (was: Cliff Jansen)

> Calling proton::container::stop() from within event handler causes infinite 
> recursion
> -
>
> Key: PROTON-1243
> URL: https://issues.apache.org/jira/browse/PROTON-1243
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding, proton-c
>Affects Versions: 0.13.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>
> There is current way to use proton::container::stop() or pn_reactor_stop() 
> from within an event handler without causing infinite recursion.
> Indeed there is even a note inside pn_reactor_stop():
> {noformat}
> ...
> // XXX: should consider removing this from stop to avoid reentrance
> pn_reactor_process(reactor);
> ...
> {noformat}
> So I think there is no way to fix the issue in the current C++ implementation 
> without removing the recursion somehow from the C code. However I don't know 
> if doing this will cause a bug in some other circumstances!



--
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-1256) Proton-c is very lax about allowing amqp and ssl protocol layers

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved PROTON-1256.
-
   Resolution: Fixed
Fix Version/s: 0.14.0

> Proton-c is very lax about allowing amqp and ssl protocol layers
> 
>
> Key: PROTON-1256
> URL: https://issues.apache.org/jira/browse/PROTON-1256
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: 0.13.1
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: 0.14.0
>
>
> The protocol auto detection code which is used when the proton-c transport is 
> in server mode does not verify that the sequence of protocol layers it allows 
> makes sense.
> For instance it would recognise an AMQP_SASL header and process the layer and 
> then allow any other layer to follow that even another AMQP_SASL layer.
> As far as I know there are only a few legal sequences of protocol layers:
> SSL; SASL; AMQP
> SSL; AMQP
> SASL; AMQP
> SASL; AMQP_SSL; AMQP [Not sure if this is legal, seems to be]
> AMQP_SSL; SASL; AMQP
> AMQP_SSL; AMQP
> AMQP
> Any other sequence is non-sensical at best,



--
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-1258) No transport_close event is generated on the listening side of the connection

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved PROTON-1258.
-
   Resolution: Fixed
Fix Version/s: 0.14.0

> No transport_close event is generated on the listening side of the connection
> -
>
> Key: PROTON-1258
> URL: https://issues.apache.org/jira/browse/PROTON-1258
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.13.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: 0.14.0
>
>
> Transport event handling is inconsistent between the listening and connecting 
> sides of an AMQP connection:
> On the client the transport events happen as they should - you always get 
> transport_open an optional transport_error and transport_close.
> On the server you get the transport_open, but no transport_close. However if 
> the connection is interrupted for some reason (say the socket disconnects) 
> then you will transport_error, followed by transport_close.



--
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-1258) No transport_close event is generated on the listening side of the connection

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378222#comment-15378222
 ] 

ASF subversion and git services commented on PROTON-1258:
-

Commit 4a6010110296846e3c77defc0558a45d8792d3b5 in qpid-proton's branch 
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=4a60101 ]

PROTON-1258: Make transport events more consistent on client and server


> No transport_close event is generated on the listening side of the connection
> -
>
> Key: PROTON-1258
> URL: https://issues.apache.org/jira/browse/PROTON-1258
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.13.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>
> Transport event handling is inconsistent between the listening and connecting 
> sides of an AMQP connection:
> On the client the transport events happen as they should - you always get 
> transport_open an optional transport_error and transport_close.
> On the server you get the transport_open, but no transport_close. However if 
> the connection is interrupted for some reason (say the socket disconnects) 
> then you will transport_error, followed by transport_close.



--
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-1256) Proton-c is very lax about allowing amqp and ssl protocol layers

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378220#comment-15378220
 ] 

ASF subversion and git services commented on PROTON-1256:
-

Commit 391685a9e922eb56ee2fd220ee3e904b2e28f5f6 in qpid-proton's branch 
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=391685a ]

PROTON-1256: Track and check auto-detected protocol layers


> Proton-c is very lax about allowing amqp and ssl protocol layers
> 
>
> Key: PROTON-1256
> URL: https://issues.apache.org/jira/browse/PROTON-1256
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: 0.13.1
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>
> The protocol auto detection code which is used when the proton-c transport is 
> in server mode does not verify that the sequence of protocol layers it allows 
> makes sense.
> For instance it would recognise an AMQP_SASL header and process the layer and 
> then allow any other layer to follow that even another AMQP_SASL layer.
> As far as I know there are only a few legal sequences of protocol layers:
> SSL; SASL; AMQP
> SSL; AMQP
> SASL; AMQP
> SASL; AMQP_SSL; AMQP [Not sure if this is legal, seems to be]
> AMQP_SSL; SASL; AMQP
> AMQP_SSL; AMQP
> AMQP
> Any other sequence is non-sensical at best,



--
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-1239) There is no way to query proton::connection for user

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378221#comment-15378221
 ] 

ASF subversion and git services commented on PROTON-1239:
-

Commit 0340eab4977c8a12250b0686c3f008a6da86689e in qpid-proton's branch 
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=0340eab ]

PROTON-1239: Add accessor to connection for authenticated user.
- Also had to fix pn_transport_get_user() to act correctly on a server
  where sasl parameters were set but sasl itself was not required.


> There is no way to query proton::connection for user
> 
>
> Key: PROTON-1239
> URL: https://issues.apache.org/jira/browse/PROTON-1239
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>
> There is no accessor for the user property of a connection. Either on the 
> client or server side.
> There is a parallel user setter so I tend to think this is an oversight.
> It is not such an issue on the client side (as in theory you could just 
> record the user you set), but on the server side the alternative is to use 
> the sasl object attached to the transport, which is awkward and doesn't cover 
> all the possibilities (SSL client certificates).



--
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-1258) No transport_close event is generated on the listening side of the connection

[Andrew Stitcher (JIRA)]

Andrew Stitcher created PROTON-1258:
---

 Summary: No transport_close event is generated on the listening 
side of the connection
 Key: PROTON-1258
 URL: https://issues.apache.org/jira/browse/PROTON-1258
 Project: Qpid Proton
  Issue Type: Bug
  Components: cpp-binding
Affects Versions: 0.13.0
Reporter: Andrew Stitcher
Assignee: Andrew Stitcher


Transport event handling is inconsistent between the listening and connecting 
sides of an AMQP connection:

On the client the transport events happen as they should - you always get 
transport_open an optional transport_error and transport_close.

On the server you get the transport_open, but no transport_close. However if 
the connection is interrupted for some reason (say the socket disconnects) then 
you will transport_error, followed by transport_close.



--
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] [Comment Edited] (QPID-7248) Extend the UI to allow queries to be saved, retrieved and re-run

[Keith Wall (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377894#comment-15377894
 ] 

Keith Wall edited comment on QPID-7248 at 7/14/16 6:09 PM:
---

Alex,

I think I have addressed all the comments except:

# Filter toolbar does not stretch through entire tab width - toolbar looks okay 
to me.  What is the problem?
# Re. the no data message.  I don't think we have precedent for hiding grids.  
The grid looked rather odd empty, so at least the message gives a positive 
confirmation that nothing is amiss.
# I did not mark the query as changed when selected page, limit etc is changed. 
 I do not think this should be persisted.



was (Author: k-wall):
Alex,

I think I have addressed all the comments except:

# Filter toolbar does not stretch through entire tab width - toolbar looks okay 
to me.  What is the problem?
# Re. the no data message.  I don't think we have precedent for hiding grids.  
The grid looked rather odd empty, so at least the message gives a positive 
confirmation that nothing is amiss.


> 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

[Keith Wall (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377894#comment-15377894
 ] 

Keith Wall commented on QPID-7248:
--

Alex,

I think I have addressed all the comments except:

# Filter toolbar does not stretch through entire tab width - toolbar looks okay 
to me.  What is the problem?
# Re. the no data message.  I don't think we have precedent for hiding grids.  
The grid looked rather odd empty, so at least the message gives a positive 
confirmation that nothing is amiss.


> 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-7238) [Java Broker, WMC] Share data from structure service amongst UI elements

[Keith Wall (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall updated QPID-7238:
-
Assignee: Alex Rudyy  (was: Keith Wall)

> [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: Alex Rudyy
> 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] [Updated] (QPID-7238) [Java Broker, WMC] Share data from structure service amongst UI elements

[Keith Wall (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall updated QPID-7238:
-
Status: Reviewable  (was: In Progress)

> [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] [Assigned] (QPID-7238) [Java Broker, WMC] Share data from structure service amongst UI elements

[Keith Wall (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall reassigned QPID-7238:


Assignee: Keith Wall

> [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] [Commented] (QPID-7248) Extend the UI to allow queries to be saved, retrieved and re-run

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377619#comment-15377619
 ] 

ASF subversion and git services commented on QPID-7248:
---

Commit 1752716 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1752716 ]

QPID-7248: [Java Broker] Address review comments from Alex Rudyy 


* Remove remains of the ability to dynamically change scope/category from 
within the widget
* Set the values of textarea's exactly once during widget initialisation 
avoiding spurious change events from advanced select/where/order-by.

> 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-7238) [Java Broker, WMC] Share data from structure service amongst UI elements

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377620#comment-15377620
 ] 

ASF subversion and git services commented on QPID-7238:
---

Commit 1752717 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1752717 ]

QPID-7238: [Java Broker] Web Management Console - share structure data with 
tree view

> [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
> 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] [Commented] (PROTON-1257) c++ cached_map core dump on assignment

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377296#comment-15377296
 ] 

ASF subversion and git services commented on PROTON-1257:
-

Commit f137151490d2242720ce63507f09ed6450120c0b in qpid-proton's branch 
refs/heads/master from Clifford Jansen
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=f137151 ]

PROTON-1257: C++ fix cached_map assignment


> c++ cached_map core dump on assignment
> --
>
> Key: PROTON-1257
> URL: https://issues.apache.org/jira/browse/PROTON-1257
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.14.0
>Reporter: Cliff Jansen
>Assignee: Cliff Jansen
>
> The copy created is deleted but the pn_unique_ptr still points to the 
> released memory.



--
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-1257) c++ cached_map core dump on assignment

[Cliff Jansen (JIRA)]

Cliff Jansen created PROTON-1257:


 Summary: c++ cached_map core dump on assignment
 Key: PROTON-1257
 URL: https://issues.apache.org/jira/browse/PROTON-1257
 Project: Qpid Proton
  Issue Type: Bug
  Components: cpp-binding
Affects Versions: 0.14.0
Reporter: Cliff Jansen
Assignee: Cliff Jansen


The copy created is deleted but the pn_unique_ptr still points to the released 
memory.



--
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] (QPIDJMS-191) Add a WebSocket based transport to the client

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDJMS-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377280#comment-15377280
 ] 

ASF subversion and git services commented on QPIDJMS-191:
-

Commit a083535fd6dffd53c1dd5783f03fcb7dc07f49a1 in qpid-jms's branch 
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=a083535 ]

QPIDJMS-191 Fix CI test failure 

Improve the with error handling to capture issue with SSL handskahe and
context creation.  

> Add a WebSocket based transport to the client
> -
>
> Key: QPIDJMS-191
> URL: https://issues.apache.org/jira/browse/QPIDJMS-191
> Project: Qpid JMS
>  Issue Type: New Feature
>  Components: qpid-jms-client
>Affects Versions: 0.10.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
> Fix For: 0.11.0
>
>
> Add a WebSocket based Transport to the client 



--
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-7337) [Java Broker] Preference Store JDBC/Derby backend

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377258#comment-15377258
 ] 

ASF subversion and git services commented on QPID-7337:
---

Commit 1752692 from oru...@apache.org in branch 'java/trunk'
[ https://svn.apache.org/r1752692 ]

QPID-7337: [Java Broker] Implement PreferenceStoreProvider interface on Derby 
VHN

> [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] [Commented] (QPID-7331) [Java Broker] Preference Store JSON backend

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377176#comment-15377176
 ] 

ASF subversion and git services commented on QPID-7331:
---

Commit 1752683 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1752683 ]

QPID-7331: [Java Broker] fix JsonFilePreferenceStore state handling on 
concurrent open and close

> [Java Broker] Preference Store JSON backend
> ---
>
> Key: QPID-7331
> URL: https://issues.apache.org/jira/browse/QPID-7331
> Project: Qpid
>  Issue Type: New Feature
>  Components: Java Broker
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.1
>
>
> Implement a JSON 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] [Commented] (QPID-7337) [Java Broker] Preference Store JDBC/Derby backend

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377174#comment-15377174
 ] 

ASF subversion and git services commented on QPID-7337:
---

Commit 1752682 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1752682 ]

QPID-7337: [Java Broker] Implement Preference Store JDBC/Derby backend

> [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] [Commented] (QPID-7330) [Java Broker] Preference Strore Integration

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377178#comment-15377178
 ] 

ASF subversion and git services commented on QPID-7330:
---

Commit 1752684 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1752684 ]

QPID-7330: [Java Broker] delete PreferenceStore when VirtualHost is deleted

> [Java Broker] Preference Strore Integration
> ---
>
> Key: QPID-7330
> URL: https://issues.apache.org/jira/browse/QPID-7330
> Project: Qpid
>  Issue Type: New Feature
>  Components: Java Broker
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.1
>
>
> As part of the ongoing work on preference we need a new store for those 
> preferences [1].
> As part of this JIRA we should create the described interfaces and integrate 
> it into the existing code. This includes:
> * calls to openAndLoad from the SystemConfig/VHN
> * calls to create/update/delete from UserPreferences
> This does not include the following (covered by separate JIRAs):
> * useful backend implementation
> * implementation of a recoverer
> [1] https://cwiki.apache.org/confluence/display/qpid/Preference+Store



--
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-7332) [Java Broker] Preference Store BDB backend

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377171#comment-15377171
 ] 

ASF subversion and git services commented on QPID-7332:
---

Commit 1752681 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1752681 ]

QPID-7332: [Java Broker] Prevent BDB Preference Store downgrading and fix state 
handling on concurrent open and close

> [Java Broker] Preference Store BDB backend
> --
>
> Key: QPID-7332
> URL: https://issues.apache.org/jira/browse/QPID-7332
> Project: Qpid
>  Issue Type: New Feature
>  Components: Java Broker
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.1
>
>
> Implement BDB backend to the PreferenceStore
> see also QPID-7330
> This implies that the BDB store version needs to be bumped and the store 
> upgrader needs to create an empty preference database.



--
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-1256) Proton-c is very lax about allowing amqp and ssl protocol layers

[Andrew Stitcher (JIRA)]

Andrew Stitcher created PROTON-1256:
---

 Summary: Proton-c is very lax about allowing amqp and ssl protocol 
layers
 Key: PROTON-1256
 URL: https://issues.apache.org/jira/browse/PROTON-1256
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-c
Affects Versions: 0.13.1
Reporter: Andrew Stitcher
Assignee: Andrew Stitcher


The protocol auto detection code which is used when the proton-c transport is 
in server mode does not verify that the sequence of protocol layers it allows 
makes sense.

For instance it would recognise an AMQP_SASL header and process the layer and 
then allow any other layer to follow that even another AMQP_SASL layer.

As far as I know there are only a few legal sequences of protocol layers:

SSL; SASL; AMQP
SSL; AMQP
SASL; AMQP
SASL; AMQP_SSL; AMQP [Not sure if this is legal, seems to be]
AMQP_SSL; SASL; AMQP
AMQP_SSL; AMQP
AMQP

Any other sequence is non-sensical at best,




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Closed] (QPID-3003) By inspection looks like there is an error in qpid/python/messaging/message.py

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher closed QPID-3003.
-
Resolution: Cannot Reproduce

The mentioned file is no longer in the source tree

> By inspection looks like there is an error in qpid/python/messaging/message.py
> --
>
> Key: QPID-3003
> URL: https://issues.apache.org/jira/browse/QPID-3003
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Client
>Reporter: Andrew Stitcher
>Assignee: Rafael H. Schloming
>
> On trunk version r1059846:
> There appears to be an error in this map initialisation (line 40):
> TYPE_MAPPINGS={
>   dict: "amqp/map",
>   list: "amqp/list",
> HERE:
>   unicode: "text/plain; charset=utf8",
>   unicode: "text/plain",
> ^^^
> [Seems to be a duplicate entry for unicode]
>   buffer: None,
>   str: None,
>   None.__class__: None
>   }



--
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-1222) Some bugs spotted by coverity

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved PROTON-1222.
-
   Resolution: Fixed
Fix Version/s: 0.14.0

> Some bugs spotted by coverity
> -
>
> Key: PROTON-1222
> URL: https://issues.apache.org/jira/browse/PROTON-1222
> Project: Qpid Proton
>  Issue Type: Bug
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: 0.14.0
>
>
> Small fixes for coverity issues:
> CID 126953
> CID 126938



--
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-1215) Move codec::data class to internal namespace

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved PROTON-1215.
-
   Resolution: Fixed
Fix Version/s: 0.14.0

> Move codec::data class to internal namespace
> 
>
> Key: PROTON-1215
> URL: https://issues.apache.org/jira/browse/PROTON-1215
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: 0.14.0
>
>




--
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-1240) proton::connection::virtual_host not filled in on server side.

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved PROTON-1240.
-
   Resolution: Fixed
Fix Version/s: 0.14.0

> proton::connection::virtual_host not filled in on server side.
> --
>
> Key: PROTON-1240
> URL: https://issues.apache.org/jira/browse/PROTON-1240
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.13.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: 0.14.0
>
>
> The trivial server code:
> {noformat}
> #include 
> #include 
> #include 
> class ExampleHandler: public proton::messaging_handler {
> void on_container_start(proton::container& c) override {
> c.listen("localhost:5672");
> }
> void on_connection_open(proton::connection& c) override {
> std::cout << "New incoming connection to " << c.virtual_host() << 
> "\n";
> }
> };
> int main() {
> ExampleHandler h;
> proton::default_container(h).run();
> }
> {noformat}
> Produces output:
> {noformat}
> New incoming to 
> {noformat}
> When another trivial C++ client connects to it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1240) proton::connection::virtual_host not filled in on server side.

[Andrew Stitcher (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377015#comment-15377015
 ] 

Andrew Stitcher commented on PROTON-1240:
-

This seems to have missed the git-jira integration somehow:

SHA 391a09fc807cec0a03a51e729d41e8a563481d89


> proton::connection::virtual_host not filled in on server side.
> --
>
> Key: PROTON-1240
> URL: https://issues.apache.org/jira/browse/PROTON-1240
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.13.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>
> The trivial server code:
> {noformat}
> #include 
> #include 
> #include 
> class ExampleHandler: public proton::messaging_handler {
> void on_container_start(proton::container& c) override {
> c.listen("localhost:5672");
> }
> void on_connection_open(proton::connection& c) override {
> std::cout << "New incoming connection to " << c.virtual_host() << 
> "\n";
> }
> };
> int main() {
> ExampleHandler h;
> proton::default_container(h).run();
> }
> {noformat}
> Produces output:
> {noformat}
> New incoming to 
> {noformat}
> When another trivial C++ client connects to it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (PROTON-1252) Improve the error reporting for errors generated by Cyrus SASL

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved PROTON-1252.
-
   Resolution: Fixed
Fix Version/s: 0.14.0

> Improve the error reporting for errors generated by Cyrus SASL
> --
>
> Key: PROTON-1252
> URL: https://issues.apache.org/jira/browse/PROTON-1252
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: 0.13.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: 0.14.0
>
>




--
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-1232) Improve implementation of default_container

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved PROTON-1232.
-
Resolution: Fixed

> Improve implementation of default_container
> ---
>
> Key: PROTON-1232
> URL: https://issues.apache.org/jira/browse/PROTON-1232
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: 0.14.0
>
>
> It would be much better not to expose symbols for internal container classes, 
> but rather expose a factory for the container and use a header only proxy to 
> allow value like use.
> This allow adding new container types by simply exposing a new factory (a 
> single symbol/entry point) rather than exposing a whole new class.



--
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-1214) Implement a common machinery for caching property maps.

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved PROTON-1214.
-
Resolution: Fixed

> Implement a common machinery for caching property maps.
> ---
>
> Key: PROTON-1214
> URL: https://issues.apache.org/jira/browse/PROTON-1214
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: 0.14.0
>
>
> This is implemented by creating an internal cached_map template class that 
> implements the concrete property maps that are used in the API.



--
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-1228) Windows schannel needs default peer_hostname to match OpenSSL

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1228:

Fix Version/s: (was: 0.14.0)
   0.13.1

> Windows schannel needs default peer_hostname to match OpenSSL
> -
>
> Key: PROTON-1228
> URL: https://issues.apache.org/jira/browse/PROTON-1228
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: 0.13.0, 0.14.0
> Environment: Windows
>Reporter: Cliff Jansen
>Assignee: Cliff Jansen
> Fix For: 0.13.1
>
>
> The OpenSSL module sets a default peer_hostname from the bound connection.  
> schannel.c should do the same to behave the same.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (PROTON-1233) Windows schannel: match OpenSSL and require non-null hostname for PN_SSL_VERIFY_PEER_NAME

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross resolved PROTON-1233.
-
Resolution: Fixed

> Windows schannel: match OpenSSL and require non-null hostname for 
> PN_SSL_VERIFY_PEER_NAME
> -
>
> Key: PROTON-1233
> URL: https://issues.apache.org/jira/browse/PROTON-1233
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Reporter: Cliff Jansen
>Assignee: Cliff Jansen
> Fix For: 0.13.1
>
>
> A user should not be permitted to omit setting the peer hostname and use 
> verify peer name at the same time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Reopened] (PROTON-1233) Windows schannel: match OpenSSL and require non-null hostname for PN_SSL_VERIFY_PEER_NAME

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross reopened PROTON-1233:
-

> Windows schannel: match OpenSSL and require non-null hostname for 
> PN_SSL_VERIFY_PEER_NAME
> -
>
> Key: PROTON-1233
> URL: https://issues.apache.org/jira/browse/PROTON-1233
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Reporter: Cliff Jansen
>Assignee: Cliff Jansen
> Fix For: 0.13.1
>
>
> A user should not be permitted to omit setting the peer hostname and use 
> verify peer name at the same time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1233) Windows schannel: match OpenSSL and require non-null hostname for PN_SSL_VERIFY_PEER_NAME

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1233:

Fix Version/s: (was: 0.14.0)
   0.13.1

> Windows schannel: match OpenSSL and require non-null hostname for 
> PN_SSL_VERIFY_PEER_NAME
> -
>
> Key: PROTON-1233
> URL: https://issues.apache.org/jira/browse/PROTON-1233
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Reporter: Cliff Jansen
>Assignee: Cliff Jansen
> Fix For: 0.13.1
>
>
> A user should not be permitted to omit setting the peer hostname and use 
> verify peer name at the same time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1235) C Reactor: connection fails if hostname with no port is used for transport address

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1235:

Fix Version/s: (was: 0.14.0)

> C Reactor: connection fails if hostname with no port is used for transport 
> address
> --
>
> Key: PROTON-1235
> URL: https://issues.apache.org/jira/browse/PROTON-1235
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: 0.13.0
>Reporter: Ken Giusti
>Assignee: Ken Giusti
> Fix For: 0.13.1
>
>
> If the application uses the connection's hostname as the transport address 
> _and_ the port number is not present (ie no ":" suffix) the connection 
> attempt will fail with a "no address configured" error.
> The expected behavior is to adopt the default "5672" port if none is 
> specified.



--
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-1221) c++: new container interface lacks scheduled timer events

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1221:

Fix Version/s: (was: 0.13.1)
   0.14.0

> c++: new container interface lacks scheduled timer events
> -
>
> Key: PROTON-1221
> URL: https://issues.apache.org/jira/browse/PROTON-1221
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.14.0
>
>
> Scheduled timer events fell out of the new proton::container API and need to 
> be restored. Rather than adding timer functions to the messaging_handler 
> interface, container::schedule() will take a std::function (or C++03 functor 
> class) similar to event_loop::inject.



--
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-7349) [Java Tests] Test EndToEndTest.testHillClimbing failed to achieve target thresholds during one iteration and failed

[Lorenz Quack (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lorenz Quack resolved QPID-7349.

Resolution: Fixed

> [Java Tests] Test EndToEndTest.testHillClimbing failed to achieve target 
> thresholds during one iteration and failed
> ---
>
> Key: QPID-7349
> URL: https://issues.apache.org/jira/browse/QPID-7349
> Project: Qpid
>  Issue Type: Test
>  Components: Java Performance Tests, Java Tests
>Reporter: Alex Rudyy
>Assignee: Keith Wall
>
> Test EndToEndTest.testHillClimbing failed to achieve target thresholds during 
> one iteration and failed as below:
> {noformat}
> Unexpected number of lines in CSV expected:<6> but was:<1>
> Stacktrace
> junit.framework.AssertionFailedError: Unexpected number of lines in CSV 
> expected:<6> but was:<1>
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:234)
>   at junit.framework.TestCase.assertEquals(TestCase.java:401)
>   at 
> org.apache.qpid.systest.disttest.endtoend.EndToEndTest.testHillClimbing(EndToEndTest.java:182)
> {noformat}
> The results have not been written into CSV file because test thresholds have 
> not been achieved :
> {noformat}
> 2016-07-10 22:00:44,957 INFO  [main] o.a.q.d.c.HillClimbingTestRunner 
> Completed test unsuccessfully, run number 1/1, result 
> TestResult{_name='HillClimbing', _hasErrors=false, _producedMessageRate=1.0, 
> _consumedMessageRate=0.774593338497289}, target rate : 1.0, production to 
> target ratio : 100.0%, consumption to production ratio : 77.5%.
> 2016-07-10 22:00:44,957 INFO  [main] o.a.q.d.c.HillClimbingTestRunner 
> Target throughput (1.0) missed.
> 2016-07-10 22:00:44,957 WARN  [main] o.a.q.d.c.Controller Finished 
> test TestInstance[testName=HillClimbing, iterationNumber=0] without producing 
> a result.
> 2016-07-10 22:00:44,957 INFO  [main] o.a.q.d.r.ResultsCsvWriter Wrote 
> 0 test result(s) to output file 
> /tmp/EndToEndTest.testHillClimbing_1468188037533/hillclimbing.csv
> {noformat}



--
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