[jira] [Commented] (PROTON-1935) [cpp] Read a config file to get default connection parameters
[
https://issues.apache.org/jira/browse/PROTON-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619933#comment-16619933
]
ASF subversion and git services commented on PROTON-1935:
-
Commit 32b9708c6a1a59e5fce2c64930fdc16f02aa9cd4 in qpid-proton's branch
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=32b9708 ]
PROTON-1935: [cpp] fix minor c++03 compatibility issues.
> [cpp] Read a config file to get default connection parameters
> --
>
> Key: PROTON-1935
> URL: https://issues.apache.org/jira/browse/PROTON-1935
> Project: Qpid Proton
> Issue Type: Improvement
> Components: cpp-binding
>Affects Versions: proton-c-0.25.0
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Major
> Fix For: proton-c-0.26.0
>
>
> Implement no-argument C++ connect() to connect using information loaded from
> a config file located and formatted as follows:
>
> {code:java}
> # Connection Configuration {#connect_config}
> Proton clients can read default connection information from a
> configuration file.
> If the environment variable `MESSAGING_CONNECT_FILE` is set, it is the
> path to the file. Otherwise the client looks for a file named
> `connect.json` in the following locations, using the first one found:
> * Current working directory of client process.
> * `$HOME/.config/messaging/` - $HOME is user's home directory.
> * `/etc/messaging/`
> The configuration file is in JSON object format. Comments are allowed,
> as defined by the [JavaScript
> Minifier](https://www.crockford.com/javascript/jsmin.html)
> The file format is as follows. Properties are shown with their default
> values, all properties are optional.
> {
> "scheme": "amqp", // [string] URL scheme for connection. Use
> "amqps" for a TLS connection.
> "host": "localhost", // [string] DNS or IP address for connection.
> "port": "amqp", // [string] Defaults to be the same as the
> scheme.
> "user": null, // [string] Authentication user name
> "password": null, // [string] Authentication password
> "sasl": {
> "enable": true, // [boolean] Enable/disable SASL
> authentication
> "mechanisms": null, // [list] List of SASL mechanism names.
> If null the library determines the default list.
> "allow_insecure": false // [boolean] Allow mechanisms that send
> clear-text passwords, even on an unencrypted connection.
> }
> "tls": {
> // NOTE: This section is not final and will change.
> "enable": true, // boolean (true)
> "pem_cert_store": null, // string [file or dir or ?]
> (null)
> "pem_ca_cert_store": null, // string [file or dir or ?]
> (null)
> "pem_key_file": null, // string file path (null)
> "pkcs12_key_store": null, // string (null)
> "pkcs12_trust_store": null, // string (null)
> "key_password": null, // string (null)
> "verify_hostname": true // boolean (true)
> },
> }{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8242) [Broker-J] JDBC store should remove message content/metadata asynchronously
[ https://issues.apache.org/jira/browse/QPID-8242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8242: -- Attachment: QPID-8242.patch > [Broker-J] JDBC store should remove message content/metadata asynchronously > --- > > Key: QPID-8242 > URL: https://issues.apache.org/jira/browse/QPID-8242 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Rob Godfrey >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > Attachments: QPID-8242.patch > > > Currently in the JDBC store the message content is deleted synchronously > after the last reference is removed. There is no need to make this operation > synchronous and the message deletes could be batched. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8242) [Broker-J] JDBC store should remove message content/metadata asynchronously
[ https://issues.apache.org/jira/browse/QPID-8242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8242: -- Summary: [Broker-J] JDBC store should remove message content/metadata asynchronously (was: [Broker-J] JDBC store should remove message content/metadata asynchronousle) > [Broker-J] JDBC store should remove message content/metadata asynchronously > --- > > Key: QPID-8242 > URL: https://issues.apache.org/jira/browse/QPID-8242 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Rob Godfrey >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > Currently in the JDBC store the message content is deleted synchronously > after the last reference is removed. There is no need to make this operation > synchronous and the message deletes could be batched. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-8242) [Broker-J] JDBC store should remove message content/metadata asynchronousle
Rob Godfrey created QPID-8242: - Summary: [Broker-J] JDBC store should remove message content/metadata asynchronousle Key: QPID-8242 URL: https://issues.apache.org/jira/browse/QPID-8242 Project: Qpid Issue Type: Improvement Components: Broker-J Reporter: Rob Godfrey Fix For: qpid-java-broker-7.1.0 Currently in the JDBC store the message content is deleted synchronously after the last reference is removed. There is no need to make this operation synchronous and the message deletes could be batched. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1124) Assert(buf) in qd_message_send; message copied locally and routed onward
[
https://issues.apache.org/jira/browse/DISPATCH-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619603#comment-16619603
]
Chuck Rolke commented on DISPATCH-1124:
---
If only a single receiver is attached to the green router then it will receive
indefinitely. As soon as a second receiver is attached then the green router
fails.
If the standard qpid-proton cpp simple-send example is the sender then it will
receive indefinitely with one or two receivers. When simple-send is modified to
send a 1443-byte text string then the green router fails.
The longer message wakes up the "message streaming" feature of dispatch
qd_message_send. The multiple receivers wakes up the message fanout and shared
message content features. This test exercises streaming, fanout, and shared
content.
> Assert(buf) in qd_message_send; message copied locally and routed onward
>
>
> Key: DISPATCH-1124
> URL: https://issues.apache.org/jira/browse/DISPATCH-1124
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Routing Engine
>Affects Versions: 1.3.0
> Environment: Fedora 27/28.
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>Priority: Major
> Attachments: BLU.conf, COLLECTD.conf, GRN.conf
>
>
> {{Three routers connected in linear chain.}}
> {{Two systems connected with wireless lan.}}
> {{This does not fail as frequently with all routers on localhost.}}
> {{+-+ ++}}
> {{| System A | | System B |}}
> {{| +---+ | | +--+ |}}
> {{| | green +>| blue +-> rcvr2}}
> {{| | | | | +--+ |}}
> {{| | | | | |}}
> {{| | | | | +--+ |}}
> {{| | |<+ collectd |<- sndr}}
> {{| +---+---+ | | +--+ |}}
> {{+-|---+ ++}}
> {{ V}}
> {{ rcvr1}}
> {{System A:}}
> {{ green router}}
> {{ 5672 - normal listener}}
> {{ 20001 - inter-router listener}}
> {{System B:}}
> {{ blue router}}
> {{ 5672 - normal listener}}
> {{ connector to green}}
> {{ collectd router}}
> {{ 15672 - normal listener}}
> {{ connector to green}}
> {{Failing test:}}
> {{ Start receiver 1 on A:5672 (green)}}
> {{ Start receiver 2 on B:5672 (blue)}}
> {{ Start sender on B:15672 (collectd)}}
> {{ Receivers have credit of 1000}}
> {{ Senders send 500-byte payloads. And plenty of 'em.}}
> {{Data path:}}
> {{ messages received on collectd forwarded to green}}
> {{ green receives interrouter; sends to local receiver, forwards to blue}}
> {{ blue receives interrouter; sends to local receiver}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1935) [cpp] Read a config file to get default connection parameters
[
https://issues.apache.org/jira/browse/PROTON-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619570#comment-16619570
]
ASF subversion and git services commented on PROTON-1935:
-
Commit 23a4b4f8993fb3814e7be4b2c851034339febfc1 in qpid-proton's branch
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=23a4b4f ]
PROTON-1935: minor correction to docs/connect_config.md
> [cpp] Read a config file to get default connection parameters
> --
>
> Key: PROTON-1935
> URL: https://issues.apache.org/jira/browse/PROTON-1935
> Project: Qpid Proton
> Issue Type: Improvement
> Components: cpp-binding
>Affects Versions: proton-c-0.25.0
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Major
> Fix For: proton-c-0.26.0
>
>
> Implement no-argument C++ connect() to connect using information loaded from
> a config file located and formatted as follows:
>
> {code:java}
> # Connection Configuration {#connect_config}
> Proton clients can read default connection information from a
> configuration file.
> If the environment variable `MESSAGING_CONNECT_FILE` is set, it is the
> path to the file. Otherwise the client looks for a file named
> `connect.json` in the following locations, using the first one found:
> * Current working directory of client process.
> * `$HOME/.config/messaging/` - $HOME is user's home directory.
> * `/etc/messaging/`
> The configuration file is in JSON object format. Comments are allowed,
> as defined by the [JavaScript
> Minifier](https://www.crockford.com/javascript/jsmin.html)
> The file format is as follows. Properties are shown with their default
> values, all properties are optional.
> {
> "scheme": "amqp", // [string] URL scheme for connection. Use
> "amqps" for a TLS connection.
> "host": "localhost", // [string] DNS or IP address for connection.
> "port": "amqp", // [string] Defaults to be the same as the
> scheme.
> "user": null, // [string] Authentication user name
> "password": null, // [string] Authentication password
> "sasl": {
> "enable": true, // [boolean] Enable/disable SASL
> authentication
> "mechanisms": null, // [list] List of SASL mechanism names.
> If null the library determines the default list.
> "allow_insecure": false // [boolean] Allow mechanisms that send
> clear-text passwords, even on an unencrypted connection.
> }
> "tls": {
> // NOTE: This section is not final and will change.
> "enable": true, // boolean (true)
> "pem_cert_store": null, // string [file or dir or ?]
> (null)
> "pem_ca_cert_store": null, // string [file or dir or ?]
> (null)
> "pem_key_file": null, // string file path (null)
> "pkcs12_key_store": null, // string (null)
> "pkcs12_trust_store": null, // string (null)
> "key_password": null, // string (null)
> "verify_hostname": true // boolean (true)
> },
> }{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1935) [cpp] Read a config file to get default connection parameters
[
https://issues.apache.org/jira/browse/PROTON-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619557#comment-16619557
]
Alan Conway commented on PROTON-1935:
-
The testing is insufficient: need to provide private access to
connection_option::impl for internal tests and verify a wide range of config
file settings testing default values, invalid values etc. are handled correctly.
> [cpp] Read a config file to get default connection parameters
> --
>
> Key: PROTON-1935
> URL: https://issues.apache.org/jira/browse/PROTON-1935
> Project: Qpid Proton
> Issue Type: Improvement
> Components: cpp-binding
>Affects Versions: proton-c-0.25.0
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Major
> Fix For: proton-c-0.26.0
>
>
> Implement no-argument C++ connect() to connect using information loaded from
> a config file located and formatted as follows:
>
> {code:java}
> # Connection Configuration {#connect_config}
> Proton clients can read default connection information from a
> configuration file.
> If the environment variable `MESSAGING_CONNECT_FILE` is set, it is the
> path to the file. Otherwise the client looks for a file named
> `connect.json` in the following locations, using the first one found:
> * Current working directory of client process.
> * `$HOME/.config/messaging/` - $HOME is user's home directory.
> * `/etc/messaging/`
> The configuration file is in JSON object format. Comments are allowed,
> as defined by the [JavaScript
> Minifier](https://www.crockford.com/javascript/jsmin.html)
> The file format is as follows. Properties are shown with their default
> values, all properties are optional.
> {
> "scheme": "amqp", // [string] URL scheme for connection. Use
> "amqps" for a TLS connection.
> "host": "localhost", // [string] DNS or IP address for connection.
> "port": "amqp", // [string] Defaults to be the same as the
> scheme.
> "user": null, // [string] Authentication user name
> "password": null, // [string] Authentication password
> "sasl": {
> "enable": true, // [boolean] Enable/disable SASL
> authentication
> "mechanisms": null, // [list] List of SASL mechanism names.
> If null the library determines the default list.
> "allow_insecure": false // [boolean] Allow mechanisms that send
> clear-text passwords, even on an unencrypted connection.
> }
> "tls": {
> // NOTE: This section is not final and will change.
> "enable": true, // boolean (true)
> "pem_cert_store": null, // string [file or dir or ?]
> (null)
> "pem_ca_cert_store": null, // string [file or dir or ?]
> (null)
> "pem_key_file": null, // string file path (null)
> "pkcs12_key_store": null, // string (null)
> "pkcs12_trust_store": null, // string (null)
> "key_password": null, // string (null)
> "verify_hostname": true // boolean (true)
> },
> }{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8240) [Broker-J] Detect idle connections
[ https://issues.apache.org/jira/browse/QPID-8240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619514#comment-16619514 ] ASF subversion and git services commented on QPID-8240: --- Commit 339a57f6faf0edad685e9d72be105ca76d8ac9bb in qpid-broker-j's branch refs/heads/master from Robert Godfrey [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=339a57f ] QPID-8240 : Detect idle connections > [Broker-J] Detect idle connections > -- > > Key: QPID-8240 > URL: https://issues.apache.org/jira/browse/QPID-8240 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.7 >Reporter: Tomas Vavricka >Priority: Minor > Labels: connection, message > > There is JSON key 'lastIoTime' in connection statistics, but value of key > 'lastIoTime' is also changing when no messages was sent/received over > connection (probably heartbeat). > It would be helpful to detect when was last message sent/received over > connection to detect idle connections. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1123) Add a link-endpoint API for in-core modules that need to terminate links
[ https://issues.apache.org/jira/browse/DISPATCH-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619420#comment-16619420 ] ASF subversion and git services commented on DISPATCH-1123: --- Commit 290292eeec33da784ed6e8d45f18b8c8299d297c in qpid-dispatch's branch refs/heads/master from [~tr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=290292e ] DISPATCH-1123 - Added shell for link-endpoint implementation. Header now compiles. > Add a link-endpoint API for in-core modules that need to terminate links > > > Key: DISPATCH-1123 > URL: https://issues.apache.org/jira/browse/DISPATCH-1123 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Major > Fix For: 1.4.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1100) Allow link routes to auto delete when the corresponding container is removed
[ https://issues.apache.org/jira/browse/DISPATCH-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619410#comment-16619410 ] ASF subversion and git services commented on DISPATCH-1100: --- Commit 46549fa9edbb110ac3b0515ebfc5b34034f0513e in qpid-dispatch's branch refs/heads/master from Kenneth Giusti [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=46549fa ] DISPATCH-1100: fix typo in schema documentation > Allow link routes to auto delete when the corresponding container is removed > > > Key: DISPATCH-1100 > URL: https://issues.apache.org/jira/browse/DISPATCH-1100 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Management Agent, Router Node >Affects Versions: 1.2.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Minor > Fix For: 1.4.0 > > > This would allow a server to create its own link route which is removed when > the server is no longer attached to the router. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1124) Assert(buf) in qd_message_send; message copied locally and routed onward
Chuck Rolke created DISPATCH-1124:
-
Summary: Assert(buf) in qd_message_send; message copied locally
and routed onward
Key: DISPATCH-1124
URL: https://issues.apache.org/jira/browse/DISPATCH-1124
Project: Qpid Dispatch
Issue Type: Bug
Components: Routing Engine
Affects Versions: 1.3.0
Environment: Fedora 27/28.
Reporter: Chuck Rolke
Assignee: Chuck Rolke
Attachments: BLU.conf, COLLECTD.conf, GRN.conf
{{Three routers connected in linear chain.}}
{{Two systems connected with wireless lan.}}
{{This does not fail as frequently with all routers on localhost.}}
{{+-+ ++}}
{{| System A | | System B |}}
{{| +---+ | | +--+ |}}
{{| | green +>| blue +-> rcvr2}}
{{| | | | | +--+ |}}
{{| | | | | |}}
{{| | | | | +--+ |}}
{{| | |<+ collectd |<- sndr}}
{{| +---+---+ | | +--+ |}}
{{+-|---+ ++}}
{{ V}}
{{ rcvr1}}
{{System A:}}
{{ green router}}
{{ 5672 - normal listener}}
{{ 20001 - inter-router listener}}
{{System B:}}
{{ blue router}}
{{ 5672 - normal listener}}
{{ connector to green}}
{{ collectd router}}
{{ 15672 - normal listener}}
{{ connector to green}}
{{Failing test:}}
{{ Start receiver 1 on A:5672 (green)}}
{{ Start receiver 2 on B:5672 (blue)}}
{{ Start sender on B:15672 (collectd)}}
{{ Receivers have credit of 1000}}
{{ Senders send 500-byte payloads. And plenty of 'em.}}
{{Data path:}}
{{ messages received on collectd forwarded to green}}
{{ green receives interrouter; sends to local receiver, forwards to blue}}
{{ blue receives interrouter; sends to local receiver}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1086) Dispatch Router sporadically goes into a state where TLS connections to the auth service fail
[
https://issues.apache.org/jira/browse/DISPATCH-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619367#comment-16619367
]
Gordon Sim commented on DISPATCH-1086:
--
[~calohmn] you don't have a core dump by any chance?
> Dispatch Router sporadically goes into a state where TLS connections to the
> auth service fail
> -
>
> Key: DISPATCH-1086
> URL: https://issues.apache.org/jira/browse/DISPATCH-1086
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Keith Wall
>Priority: Major
>
> Whilst running performance tests against Enmasse, we periodically see a
> problem where Dispatch Router (1.1.0) goes into a state where fails to form
> TLS connections to the authservice. When this occurs, the router needs to be
> restarted to restore service. There does not seem to be a pattern to when the
> issue occurs, but in all cases where it has been seen, the test case included
> tens or hundreds of concurrently formed connections.
> The following message is written to the log:
>
> {noformat}
> 2018-07-06 10:38:45.543519 + AUTHSERVICE (warning) Cannot initialise
> SSL{noformat}
> Unfortunately turning up the router logging (using the following command)
> reveal no more useful information. This Proton improvement JIRA was raised to
> include the diagnostics from OpenSSL.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1123) Add a link-endpoint API for in-core modules that need to terminate links
[ https://issues.apache.org/jira/browse/DISPATCH-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619312#comment-16619312 ] ASF subversion and git services commented on DISPATCH-1123: --- Commit 6a56c1efa2be71836b137e5d494b3a284de9b01a in qpid-dispatch's branch refs/heads/master from [~tr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=6a56c1e ] DISPATCH-1123 - Added first draft of the API header for in-core link endpoints. > Add a link-endpoint API for in-core modules that need to terminate links > > > Key: DISPATCH-1123 > URL: https://issues.apache.org/jira/browse/DISPATCH-1123 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Major > Fix For: 1.4.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1123) Add a link-endpoint API for in-core modules that need to terminate links
Ted Ross created DISPATCH-1123: -- Summary: Add a link-endpoint API for in-core modules that need to terminate links Key: DISPATCH-1123 URL: https://issues.apache.org/jira/browse/DISPATCH-1123 Project: Qpid Dispatch Issue Type: Improvement Components: Router Node Reporter: Ted Ross Assignee: Ted Ross Fix For: 1.4.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1935) [cpp] Read a config file to get default connection parameters
[
https://issues.apache.org/jira/browse/PROTON-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619262#comment-16619262
]
ASF subversion and git services commented on PROTON-1935:
-
Commit b164d99c80129a2a24ae7203846579569c9cf3b5 in qpid-proton's branch
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=b164d99 ]
PROTON-1935: [cpp] connection configuration and default connect()
docs/connect-config.md: describes connection configuration JSON format.
container::connect() connects using the default configuration file
Additional API in proton::connect_config allows the user to parse configuration
and apply to a connection_options object for more flexible use.
> [cpp] Read a config file to get default connection parameters
> --
>
> Key: PROTON-1935
> URL: https://issues.apache.org/jira/browse/PROTON-1935
> Project: Qpid Proton
> Issue Type: Improvement
> Components: cpp-binding
>Affects Versions: proton-c-0.25.0
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Major
> Fix For: proton-c-0.26.0
>
>
> Implement no-argument C++ connect() to connect using information loaded from
> a config file located and formatted as follows:
>
> {code:java}
> # Connection Configuration {#connect_config}
> Proton clients can read default connection information from a
> configuration file.
> If the environment variable `MESSAGING_CONNECT_FILE` is set, it is the
> path to the file. Otherwise the client looks for a file named
> `connect.json` in the following locations, using the first one found:
> * Current working directory of client process.
> * `$HOME/.config/messaging/` - $HOME is user's home directory.
> * `/etc/messaging/`
> The configuration file is in JSON object format. Comments are allowed,
> as defined by the [JavaScript
> Minifier](https://www.crockford.com/javascript/jsmin.html)
> The file format is as follows. Properties are shown with their default
> values, all properties are optional.
> {
> "scheme": "amqp", // [string] URL scheme for connection. Use
> "amqps" for a TLS connection.
> "host": "localhost", // [string] DNS or IP address for connection.
> "port": "amqp", // [string] Defaults to be the same as the
> scheme.
> "user": null, // [string] Authentication user name
> "password": null, // [string] Authentication password
> "sasl": {
> "enable": true, // [boolean] Enable/disable SASL
> authentication
> "mechanisms": null, // [list] List of SASL mechanism names.
> If null the library determines the default list.
> "allow_insecure": false // [boolean] Allow mechanisms that send
> clear-text passwords, even on an unencrypted connection.
> }
> "tls": {
> // NOTE: This section is not final and will change.
> "enable": true, // boolean (true)
> "pem_cert_store": null, // string [file or dir or ?]
> (null)
> "pem_ca_cert_store": null, // string [file or dir or ?]
> (null)
> "pem_key_file": null, // string file path (null)
> "pkcs12_key_store": null, // string (null)
> "pkcs12_trust_store": null, // string (null)
> "key_password": null, // string (null)
> "verify_hostname": true // boolean (true)
> },
> }{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8241) [Broker-J] Remove use of javax.xml.bind.DatatypeConverter
[ https://issues.apache.org/jira/browse/QPID-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8241: -- Status: Reviewable (was: In Progress) > [Broker-J] Remove use of javax.xml.bind.DatatypeConverter > - > > Key: QPID-8241 > URL: https://issues.apache.org/jira/browse/QPID-8241 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Rob Godfrey >Assignee: Rob Godfrey >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > As per [this > comment|https://issues.apache.org/jira/browse/QPID-7885?focusedCommentId=16613383&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16613383] > on QPID-7885, javax.xml.bind.DatatypeConverter is no longer contained in the > default classpath in Java 9. As such we should reimplement all places in the > broker code using this. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-8241) [Broker-J] Remove use of javax.xml.bind.DatatypeConverter
[ https://issues.apache.org/jira/browse/QPID-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned QPID-8241: - Assignee: Rob Godfrey > [Broker-J] Remove use of javax.xml.bind.DatatypeConverter > - > > Key: QPID-8241 > URL: https://issues.apache.org/jira/browse/QPID-8241 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Rob Godfrey >Assignee: Rob Godfrey >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > As per [this > comment|https://issues.apache.org/jira/browse/QPID-7885?focusedCommentId=16613383&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16613383] > on QPID-7885, javax.xml.bind.DatatypeConverter is no longer contained in the > default classpath in Java 9. As such we should reimplement all places in the > broker code using this. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8241) [Broker-J] Remove use of javax.xml.bind.DatatypeConverter
[ https://issues.apache.org/jira/browse/QPID-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619170#comment-16619170 ] ASF subversion and git services commented on QPID-8241: --- Commit c8c82033021fb8b0ebfea5bd6367832780a3a8c4 in qpid-broker-j's branch refs/heads/master from Robert Godfrey [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=c8c8203 ] QPID-8241 : Remove use of javax.xml.bind.DatatypeConverter > [Broker-J] Remove use of javax.xml.bind.DatatypeConverter > - > > Key: QPID-8241 > URL: https://issues.apache.org/jira/browse/QPID-8241 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Rob Godfrey >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > As per [this > comment|https://issues.apache.org/jira/browse/QPID-7885?focusedCommentId=16613383&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16613383] > on QPID-7885, javax.xml.bind.DatatypeConverter is no longer contained in the > default classpath in Java 9. As such we should reimplement all places in the > broker code using this. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8241) [Broker-J] Remove use of javax.xml.bind.DatatypeConverter
[
https://issues.apache.org/jira/browse/QPID-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619166#comment-16619166
]
Rob Godfrey commented on QPID-8241:
---
Note there are a couple of tests that verify a Date/Time of the form
{{1970-01-02Z}}. As far as I can tell this is neither a valid date nor a valid
datetime ({{1970-01-02}} would be a valid date, {{1970-01-02T00:00:00Z}} would
be a valid datetime).
As the form seems invalid I suggest changing the tests as part of this change.
> [Broker-J] Remove use of javax.xml.bind.DatatypeConverter
> -
>
> Key: QPID-8241
> URL: https://issues.apache.org/jira/browse/QPID-8241
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Reporter: Rob Godfrey
>Priority: Major
> Fix For: qpid-java-broker-7.1.0
>
>
> As per [this
> comment|https://issues.apache.org/jira/browse/QPID-7885?focusedCommentId=16613383&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16613383]
> on QPID-7885, javax.xml.bind.DatatypeConverter is no longer contained in the
> default classpath in Java 9. As such we should reimplement all places in the
> broker code using this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8241) [Broker-J] Remove use of javax.xml.bind.DatatypeConverter
[ https://issues.apache.org/jira/browse/QPID-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8241: -- Issue Type: Improvement (was: Bug) > [Broker-J] Remove use of javax.xml.bind.DatatypeConverter > - > > Key: QPID-8241 > URL: https://issues.apache.org/jira/browse/QPID-8241 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Rob Godfrey >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > As per [this > comment|https://issues.apache.org/jira/browse/QPID-7885?focusedCommentId=16613383&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16613383] > on QPID-7885, javax.xml.bind.DatatypeConverter is no longer contained in the > default classpath in Java 9. As such we should reimplement all places in the > broker code using this. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8241) [Broker-J] Remove use of javax.xml.bind.DatatypeConverter
[ https://issues.apache.org/jira/browse/QPID-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-8241: -- Description: As per [this comment|https://issues.apache.org/jira/browse/QPID-7885?focusedCommentId=16613383&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16613383] on QPID-7885, javax.xml.bind.DatatypeConverter is no longer contained in the default classpath in Java 9. As such we should reimplement all places in the broker code using this. (was: As per this comment on QPID-7885, javax.xml.bind.DatatypeConverter is no longer contained in the default classpath in Java 9. As such we should reimplement all places in the broker code using this.) > [Broker-J] Remove use of javax.xml.bind.DatatypeConverter > - > > Key: QPID-8241 > URL: https://issues.apache.org/jira/browse/QPID-8241 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Reporter: Rob Godfrey >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > As per [this > comment|https://issues.apache.org/jira/browse/QPID-7885?focusedCommentId=16613383&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16613383] > on QPID-7885, javax.xml.bind.DatatypeConverter is no longer contained in the > default classpath in Java 9. As such we should reimplement all places in the > broker code using this. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-8241) [Broker-J] Remove use of javax.xml.bind.DatatypeConverter
Rob Godfrey created QPID-8241: - Summary: [Broker-J] Remove use of javax.xml.bind.DatatypeConverter Key: QPID-8241 URL: https://issues.apache.org/jira/browse/QPID-8241 Project: Qpid Issue Type: Bug Components: Broker-J Reporter: Rob Godfrey Fix For: qpid-java-broker-7.1.0 As per this comment on QPID-7885, javax.xml.bind.DatatypeConverter is no longer contained in the default classpath in Java 9. As such we should reimplement all places in the broker code using this. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1096) support AMQP prioritized messages
[ https://issues.apache.org/jira/browse/DISPATCH-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619067#comment-16619067 ] ASF subversion and git services commented on DISPATCH-1096: --- Commit 92f00baf66533d884cbeba186405cfee480f6992 in qpid-dispatch's branch refs/heads/master from [~tr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=92f00ba ] DISPATCH-1096 - Added a new link-list-class for local (on-stack) lists. Tightened up some critical sections. This closes #375 > support AMQP prioritized messages > - > > Key: DISPATCH-1096 > URL: https://issues.apache.org/jira/browse/DISPATCH-1096 > Project: Qpid Dispatch > Issue Type: New Feature >Reporter: michael goulish >Assignee: michael goulish >Priority: Major > Fix For: 1.4.0 > > > Detect priority info from message header in the router code. > Create separate inter-router links for the various priorities. > Per connection (i.e. not globally across the router) service high-priority > inter-router links before low priority links. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #375: DISPATCH 1096 - store priority in links
Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/375 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1122) Authenticated username not printed
[
https://issues.apache.org/jira/browse/DISPATCH-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved DISPATCH-1122.
--
Resolution: Fixed
> Authenticated username not printed
> --
>
> Key: DISPATCH-1122
> URL: https://issues.apache.org/jira/browse/DISPATCH-1122
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ulf Lilleengen
>Priority: Major
>
> When using the remote authentication service, the username that was
> authenticated is not printed due to a incorrect format string.
>
> Currently the output is:
>
> {{2018-09-17 00:08:32.899183 + AUTHSERVICE (info) authenticated as }}
>
> without the username added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1122) Authenticated username not printed
[
https://issues.apache.org/jira/browse/DISPATCH-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618698#comment-16618698
]
ASF GitHub Bot commented on DISPATCH-1122:
--
Github user asfgit closed the pull request at:
https://github.com/apache/qpid-dispatch/pull/379
> Authenticated username not printed
> --
>
> Key: DISPATCH-1122
> URL: https://issues.apache.org/jira/browse/DISPATCH-1122
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ulf Lilleengen
>Priority: Major
>
> When using the remote authentication service, the username that was
> authenticated is not printed due to a incorrect format string.
>
> Currently the output is:
>
> {{2018-09-17 00:08:32.899183 + AUTHSERVICE (info) authenticated as }}
>
> without the username added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #379: DISPATCH-1122: Use correct format specifier
Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/379 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1122) Authenticated username not printed
[
https://issues.apache.org/jira/browse/DISPATCH-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618696#comment-16618696
]
ASF subversion and git services commented on DISPATCH-1122:
---
Commit 94bef705d11a3ece802094aa8b603192344967a2 in qpid-dispatch's branch
refs/heads/master from [~lulf]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=94bef70 ]
DISPATCH-1122: Use correct format specifier
> Authenticated username not printed
> --
>
> Key: DISPATCH-1122
> URL: https://issues.apache.org/jira/browse/DISPATCH-1122
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ulf Lilleengen
>Priority: Major
>
> When using the remote authentication service, the username that was
> authenticated is not printed due to a incorrect format string.
>
> Currently the output is:
>
> {{2018-09-17 00:08:32.899183 + AUTHSERVICE (info) authenticated as }}
>
> without the username added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1122) Authenticated username not printed
[
https://issues.apache.org/jira/browse/DISPATCH-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulf Lilleengen updated DISPATCH-1122:
-
Flags: Patch
PR https://github.com/apache/qpid-dispatch/pull/379
> Authenticated username not printed
> --
>
> Key: DISPATCH-1122
> URL: https://issues.apache.org/jira/browse/DISPATCH-1122
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ulf Lilleengen
>Priority: Major
>
> When using the remote authentication service, the username that was
> authenticated is not printed due to a incorrect format string.
>
> Currently the output is:
>
> {{2018-09-17 00:08:32.899183 + AUTHSERVICE (info) authenticated as }}
>
> without the username added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1122) Authenticated username not printed
[
https://issues.apache.org/jira/browse/DISPATCH-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618624#comment-16618624
]
ASF GitHub Bot commented on DISPATCH-1122:
--
GitHub user lulf opened a pull request:
https://github.com/apache/qpid-dispatch/pull/379
DISPATCH-1122: Use correct format specifier
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lulf/qpid-dispatch DISPATCH-1122
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-dispatch/pull/379.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #379
commit 94bef705d11a3ece802094aa8b603192344967a2
Author: Ulf Lilleengen
Date: 2018-09-18T07:48:54Z
DISPATCH-1122: Use correct format specifier
> Authenticated username not printed
> --
>
> Key: DISPATCH-1122
> URL: https://issues.apache.org/jira/browse/DISPATCH-1122
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ulf Lilleengen
>Priority: Major
>
> When using the remote authentication service, the username that was
> authenticated is not printed due to a incorrect format string.
>
> Currently the output is:
>
> {{2018-09-17 00:08:32.899183 + AUTHSERVICE (info) authenticated as }}
>
> without the username added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #379: DISPATCH-1122: Use correct format specifier
GitHub user lulf opened a pull request: https://github.com/apache/qpid-dispatch/pull/379 DISPATCH-1122: Use correct format specifier You can merge this pull request into a Git repository by running: $ git pull https://github.com/lulf/qpid-dispatch DISPATCH-1122 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/379.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #379 commit 94bef705d11a3ece802094aa8b603192344967a2 Author: Ulf Lilleengen Date: 2018-09-18T07:48:54Z DISPATCH-1122: Use correct format specifier --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1122) Authenticated username not printed
Ulf Lilleengen created DISPATCH-1122:
Summary: Authenticated username not printed
Key: DISPATCH-1122
URL: https://issues.apache.org/jira/browse/DISPATCH-1122
Project: Qpid Dispatch
Issue Type: Bug
Reporter: Ulf Lilleengen
When using the remote authentication service, the username that was
authenticated is not printed due to a incorrect format string.
Currently the output is:
{{2018-09-17 00:08:32.899183 + AUTHSERVICE (info) authenticated as }}
without the username added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
