[jira] [Commented] (DISPATCH-940) When running qdrouterd with -c and -d combined, configuration file is reporting as not found
[
https://issues.apache.org/jira/browse/DISPATCH-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392442#comment-16392442
]
ASF GitHub Bot commented on DISPATCH-940:
-
Github user fgiorgetti commented on the issue:
https://github.com/apache/qpid-dispatch/pull/266
Unit test has been created.
> When running qdrouterd with -c and -d combined, configuration file is
> reporting as not found
>
>
> Key: DISPATCH-940
> URL: https://issues.apache.org/jira/browse/DISPATCH-940
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 1.1.0
>Reporter: Fernando Giorgetti
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.1.0
>
>
> If you run qdrouterd as shown below, everything works just fine:
>
> {code:java}
> [fgiorget@fgiorget qpid-dispatch]$ qdrouterd -c qdrouterd.conf
> 2018-03-08 14:49:02.797039 -0300 SERVER (info) Container Name: Router.A
> 2018-03-08 14:49:02.797142 -0300 ROUTER (info) Router started in Standalone
> mode
> {code}
> But if you try to add -d (daemon) flag, then it does not find the
> configuration file.
> {code:java}
> [fgiorget@fgiorget qpid-dispatch]$ qdrouterd -d -c qdrouterd.conf
> qdrouterd: Not found: Configuration file could not be opened{code}
> It only works with fully qualified file name.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch issue #266: DISPATCH-940 - Allow configuration file to be used...
Github user fgiorgetti commented on the issue: https://github.com/apache/qpid-dispatch/pull/266 Unit test has been created. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-925) Doc: Update anchor name format
[ https://issues.apache.org/jira/browse/DISPATCH-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391895#comment-16391895 ] ASF GitHub Bot commented on DISPATCH-925: - Github user bhardesty commented on the issue: https://github.com/apache/qpid-dispatch/pull/264 @ganeshmurthy, this is ready to merge. > Doc: Update anchor name format > -- > > Key: DISPATCH-925 > URL: https://issues.apache.org/jira/browse/DISPATCH-925 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Documentation >Reporter: Ben Hardesty >Assignee: Ben Hardesty >Priority: Major > > In the QDR doc, the anchor names should use the [id='anchor-name'] format, > which is more versatile than the [[anchor-name]] format. This also involves > updating each "xref" and "link" that refers to an anchor name. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch issue #264: DISPATCH-925: Update anchor name format and links
Github user bhardesty commented on the issue: https://github.com/apache/qpid-dispatch/pull/264 @ganeshmurthy, this is ready to merge. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-940) When running qdrouterd with -c and -d combined, configuration file is reporting as not found
[
https://issues.apache.org/jira/browse/DISPATCH-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391872#comment-16391872
]
ASF GitHub Bot commented on DISPATCH-940:
-
Github user fgiorgetti commented on the issue:
https://github.com/apache/qpid-dispatch/pull/266
I will create a unit test for it. Thanks for the advise on the branch in
use.
> When running qdrouterd with -c and -d combined, configuration file is
> reporting as not found
>
>
> Key: DISPATCH-940
> URL: https://issues.apache.org/jira/browse/DISPATCH-940
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 1.1.0
>Reporter: Fernando Giorgetti
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.1.0
>
>
> If you run qdrouterd as shown below, everything works just fine:
>
> {code:java}
> [fgiorget@fgiorget qpid-dispatch]$ qdrouterd -c qdrouterd.conf
> 2018-03-08 14:49:02.797039 -0300 SERVER (info) Container Name: Router.A
> 2018-03-08 14:49:02.797142 -0300 ROUTER (info) Router started in Standalone
> mode
> {code}
> But if you try to add -d (daemon) flag, then it does not find the
> configuration file.
> {code:java}
> [fgiorget@fgiorget qpid-dispatch]$ qdrouterd -d -c qdrouterd.conf
> qdrouterd: Not found: Configuration file could not be opened{code}
> It only works with fully qualified file name.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch issue #266: DISPATCH-940 - Allow configuration file to be used...
Github user fgiorgetti commented on the issue: https://github.com/apache/qpid-dispatch/pull/266 I will create a unit test for it. Thanks for the advise on the branch in use. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8083) [REST] Refactor REST system test suite
[ https://issues.apache.org/jira/browse/QPID-8083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391747#comment-16391747 ] ASF subversion and git services commented on QPID-8083: --- Commit a3c59c14be2c66fb7dada29b45fcf87227e1e925 in qpid-broker-j's branch refs/heads/master from [~k-wall] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=a3c59c1 ] QPID-8083: [System Tests] [REST/HTTP] Refactor StatisticsReportingTest > [REST] Refactor REST system test suite > -- > > Key: QPID-8083 > URL: https://issues.apache.org/jira/browse/QPID-8083 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Keith Wall >Priority: Major > > REST is an orthogonal concern within the Broker. It should be possible for > developers of the Broker to easily exclude REST tests from test runs whilst > developing other parts of the Broker. To allow for this, the REST test suite > should be separate. > Also many of the current tests are very repetitious in nature. Currently > each model object is subjected to its own REST test merely testing that model > attributes are available over REST, pointlessly retesting the same piece of > common mechanism code over and over again. Such tests should be eliminated. > Tests that remain should focus on REST concerns such as: > * CRUD model access > * Model operations > * SASL and Preemptive Authentication > * Compression/Decompression > > -- 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-8121) [Broker-J] Virtualhost scoped statistics messages absent from virtualhost logs
[
https://issues.apache.org/jira/browse/QPID-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391746#comment-16391746
]
ASF subversion and git services commented on QPID-8121:
---
Commit 7ab64198e4af7bc01d90756c117d0139151adb4b in qpid-broker-j's branch
refs/heads/master from [~k-wall]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=7ab6419 ]
QPID-8121: [Broker-J] Include the VirtualHostPrincipal in the Subject used to
execute the StatisticsReportingTask for virtualhosts
> [Broker-J] Virtualhost scoped statistics messages absent from virtualhost logs
> --
>
> Key: QPID-8121
> URL: https://issues.apache.org/jira/browse/QPID-8121
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0
>Reporter: Keith Wall
>Priority: Minor
>
> The virtualhost scoped statistics messages is not being included in logs
> written by {{VirtualHostLoggers}}. It is being included in {{BrokerLoggers}}.
> The defect is simple that the {{StatisticsReportTask}} is running with a
> {{Subject}} that does not include the {{VirtualHostPrincipal}}.
--
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-8121) [Broker-J] Virtualhost scoped statistics messages absent from virtualhost logs
Keith Wall created QPID-8121:
Summary: [Broker-J] Virtualhost scoped statistics messages absent
from virtualhost logs
Key: QPID-8121
URL: https://issues.apache.org/jira/browse/QPID-8121
Project: Qpid
Issue Type: Bug
Components: Broker-J
Affects Versions: qpid-java-broker-7.0.0
Reporter: Keith Wall
The virtualhost scoped statistics messages is not being included in logs
written by {{VirtualHostLoggers}}. It is being included in {{BrokerLoggers}}.
The defect is simple that the {{StatisticsReportTask}} is running with a
{{Subject}} that does not include the {{VirtualHostPrincipal}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1788) Thread-safe schedule for 0.16 C++
[ https://issues.apache.org/jira/browse/PROTON-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen resolved PROTON-1788. -- Resolution: Won't Fix See comment regarding further work for generic platforms. This can be re-opened if there is demand for a 0.16.1 or later branch with this capability. > Thread-safe schedule for 0.16 C++ > - > > Key: PROTON-1788 > URL: https://issues.apache.org/jira/browse/PROTON-1788 > Project: Qpid Proton > Issue Type: Wish > Components: cpp-binding >Affects Versions: 0.16.0 >Reporter: Cliff Jansen >Assignee: Cliff Jansen >Priority: Minor > Attachments: p1788_0.patch > > > Thread-safe schedule for C++ is introduced in later versions of Proton using > the proactor. > This is a 0.16 based implementation suing the reactor that could be made part > of a 0.16.1 or later release if desired. -- 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-1788) Thread-safe schedule for 0.16 C++
[ https://issues.apache.org/jira/browse/PROTON-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391674#comment-16391674 ] Cliff Jansen commented on PROTON-1788: -- p17988_0.patch is a sample implementation that works with pthread. It could be enhanced to cover most platforms by using C++11 threading primitives and/or Windows primitives as used in qpid-cpp. It is unlikely to become part of a release without further user demand and work to make it more platform agnostic. > Thread-safe schedule for 0.16 C++ > - > > Key: PROTON-1788 > URL: https://issues.apache.org/jira/browse/PROTON-1788 > Project: Qpid Proton > Issue Type: Wish > Components: cpp-binding >Affects Versions: 0.16.0 >Reporter: Cliff Jansen >Assignee: Cliff Jansen >Priority: Minor > Attachments: p1788_0.patch > > > Thread-safe schedule for C++ is introduced in later versions of Proton using > the proactor. > This is a 0.16 based implementation suing the reactor that could be made part > of a 0.16.1 or later release if desired. -- 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] (PROTON-1788) Thread-safe schedule for 0.16 C++
[ https://issues.apache.org/jira/browse/PROTON-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen updated PROTON-1788: - Attachment: p1788_0.patch > Thread-safe schedule for 0.16 C++ > - > > Key: PROTON-1788 > URL: https://issues.apache.org/jira/browse/PROTON-1788 > Project: Qpid Proton > Issue Type: Wish > Components: cpp-binding >Affects Versions: 0.16.0 >Reporter: Cliff Jansen >Assignee: Cliff Jansen >Priority: Minor > Attachments: p1788_0.patch > > > Thread-safe schedule for C++ is introduced in later versions of Proton using > the proactor. > This is a 0.16 based implementation suing the reactor that could be made part > of a 0.16.1 or later release if desired. -- 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-1786) Multiframe transfer wire traffic patterns differ substantially
[
https://issues.apache.org/jira/browse/PROTON-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391664#comment-16391664
]
Chuck Rolke commented on PROTON-1786:
-
[Proton C] Dispatch will most likely have a different pattern than any other
client that uses Proton. One differentiator was added under
https://issues.apache.org/jira/browse/DISPATCH-807 where Dispatch stalls
incoming bytes and stops pumping data into Proton's outgoing byte buffer.
One aspect of Proton that hurt Dispatch was that a sending client could send
call pn_link_send with huge amounts of data and Proton just adds the bytes to
the outgoing byte buffer. When Dispatch sent a largish message to three links
there would be three copies of the message in the Proton outgoing bytes. WIth
fast producers and slow consumers Dispatch could have 10s of megabytes ready to
send.
Dispatch after DISPATCH-807 sets a threshold on the number of bytes that can be
in Proton outgoing bytes. On reaching that threshold Dispatch stops reading the
associated incoming link. After Proton sends some transfer data and reduces the
outgoing bytes buffer size then Dispatch will start reading the incoming links
and filling the outgoing bytes buffer(s) again.
Compare that with a simple sender does not care about Proton outgoing bytes. As
the sender sends it is pushing the bytes to be sent down to Proton.
When Proton gets to send data it behaves the same for Dispatch and for the
simple sender. It will send what it can in the largest frames and transfers
that it can. For simple senders Proton will likely send the whole message in
large frames. For Dispatch there is a real chance that Proton will empty its
outgoing byte buffers routinely while sending a large message stream. That
creates the opportunity for Proton to send a small frame in the middle of a
larger transfer because the outgoing bytes buffer went empty.
> Multiframe transfer wire traffic patterns differ substantially
> --
>
> Key: PROTON-1786
> URL: https://issues.apache.org/jira/browse/PROTON-1786
> Project: Qpid Proton
> Issue Type: Task
>Reporter: Kim van der Riet
>Priority: Major
> Attachments: dispatch.multiframe.07.pcapng
>
>
> This is not a bug (although it could become one), but rather an observation
> of large message transfer patterns observed using Wireshark while running
> Qpid Interop Test's amqp_large_content_test.
> The test sends large messages through a broker (in this case, dispatch
> router) of size 1MB and 10MB.
> I hope to add other observable patterns from other clients and/or brokers if
> they are significant. If there is consensus that this is a potential large
> message transfer efficiency issue, then this Jira can be a placeholder for
> this issue.
> See the attached file for an example. In this test, the receiver is using
> TCP port 59806 and the sender port 59808. The router is using the standard
> AMQP port.
> h2. C++ client:
> The client in this case uses the Proton C++ API and is based on the
> SimpleSender.cpp example. To isolate the traffic from this client, use the
> following filter in Wireshark:
> {noformat}
> amqp.performative == transfer && tcp.srcport == 59808{noformat}
> It can be seen that although there is a large message being sent, the sender
> appears to be restricted to a single transfer of 16kB or a 64kB frame
> containing 4 transfers (very occasionally, 2, 3 or 5 transfers) - for example:
> {noformat}
> 351.972620::1 ::1 AMQP16470 transfer
> 1177 2.032878::1 ::1 AMQP65550 transfer transfer
> transfer transfer
> {noformat}
> h2. Dispatch Router:
> This uses Proton through its native C interface. To isolate the traffic from
> the router to the receiver, use the following Wireshark filter:
> {noformat}
> amqp.performative == transfer && tcp.dstport == 59806{noformat}
> The traffic for this broker looks very different. Each frame contains only a
> single transfer, and the size of the transfers differ widely, from 196 bytes
> to the full 64kB max. I am assuming that the router is sending on message
> content it has received as soon as it becomes available no matter the size.
--
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] (PROTON-1788) Thread-safe schedule for 0.16 C++
Cliff Jansen created PROTON-1788: Summary: Thread-safe schedule for 0.16 C++ Key: PROTON-1788 URL: https://issues.apache.org/jira/browse/PROTON-1788 Project: Qpid Proton Issue Type: Wish Components: cpp-binding Affects Versions: 0.16.0 Reporter: Cliff Jansen Assignee: Cliff Jansen Thread-safe schedule for C++ is introduced in later versions of Proton using the proactor. This is a 0.16 based implementation suing the reactor that could be made part of a 0.16.1 or later release if desired. -- 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-940) When running qdrouterd with -c and -d combined, configuration file is reporting as not found
[
https://issues.apache.org/jira/browse/DISPATCH-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391635#comment-16391635
]
ASF GitHub Bot commented on DISPATCH-940:
-
GitHub user fgiorgetti opened a pull request:
https://github.com/apache/qpid-dispatch/pull/266
DISPATCH-940 - Allow configuration file to be used from relative path…
DISPATCH-940 - Allow configuration file to be used from relative path when
running as a daemon.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fgiorgetti/qpid-dispatch master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-dispatch/pull/266.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 #266
commit 710b6da05d8d8e2e4f0b8fbbed18c7947c4949e9
Author: Fernando Giorgetti
Date: 2018-03-08T17:51:52Z
DISPATCH-940 - Allow configuration file to be used from relative path when
running as a daemon
> When running qdrouterd with -c and -d combined, configuration file is
> reporting as not found
>
>
> Key: DISPATCH-940
> URL: https://issues.apache.org/jira/browse/DISPATCH-940
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 1.1.0
>Reporter: Fernando Giorgetti
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.1.0
>
>
> If you run qdrouterd as shown below, everything works just fine:
>
> {code:java}
> [fgiorget@fgiorget qpid-dispatch]$ qdrouterd -c qdrouterd.conf
> 2018-03-08 14:49:02.797039 -0300 SERVER (info) Container Name: Router.A
> 2018-03-08 14:49:02.797142 -0300 ROUTER (info) Router started in Standalone
> mode
> {code}
> But if you try to add -d (daemon) flag, then it does not find the
> configuration file.
> {code:java}
> [fgiorget@fgiorget qpid-dispatch]$ qdrouterd -d -c qdrouterd.conf
> qdrouterd: Not found: Configuration file could not be opened{code}
> It only works with fully qualified file name.
--
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 #266: DISPATCH-940 - Allow configuration file to ...
GitHub user fgiorgetti opened a pull request: https://github.com/apache/qpid-dispatch/pull/266 DISPATCH-940 - Allow configuration file to be used from relative path⦠DISPATCH-940 - Allow configuration file to be used from relative path when running as a daemon. You can merge this pull request into a Git repository by running: $ git pull https://github.com/fgiorgetti/qpid-dispatch master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/266.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 #266 commit 710b6da05d8d8e2e4f0b8fbbed18c7947c4949e9 Author: Fernando Giorgetti Date: 2018-03-08T17:51:52Z DISPATCH-940 - Allow configuration file to be used from relative path when running as a daemon --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-8120) [Broker-J] [BDB HA] Replica Broker entered error reporting loop after EnvironmentFailureException: Message op: Entry Body size [nnnn] is too large.
Keith Wall created QPID-8120:
Summary: [Broker-J] [BDB HA] Replica Broker entered error
reporting loop after EnvironmentFailureException: Message op: Entry Body size
[] is too large.
Key: QPID-8120
URL: https://issues.apache.org/jira/browse/QPID-8120
Project: Qpid
Issue Type: Bug
Components: Broker-J
Affects Versions: qpid-java-6.1.5
Reporter: Keith Wall
Attachments: log.txt
If a Broker in the replica role encounters a fatal exception, the Broker is
supposed to shutdown cleanly after reporting the exception. There is at least
one path through the code where this does not happen. As seen in the attached
log, following a {{com.sleepycat.je.EnvironmentFailureException: (JE 5.0.104)
Message op: Entry Body size: 14583287 is too large}} a error reporting loop
formed, repeating the same exception to the logs every 5ms or so.
This defect whilst not a root cause, may mask the true root cause or hamper an
attempt to return to business as usual.
--
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-940) When running qdrouterd with -c and -d combined, configuration file is reporting as not found
Fernando Giorgetti created DISPATCH-940:
---
Summary: When running qdrouterd with -c and -d combined,
configuration file is reporting as not found
Key: DISPATCH-940
URL: https://issues.apache.org/jira/browse/DISPATCH-940
Project: Qpid Dispatch
Issue Type: Bug
Components: Router Node
Affects Versions: 1.1.0
Reporter: Fernando Giorgetti
Fix For: 1.1.0
If you run qdrouterd as shown below, everything works just fine:
{code:java}
[fgiorget@fgiorget qpid-dispatch]$ qdrouterd -c qdrouterd.conf
2018-03-08 14:49:02.797039 -0300 SERVER (info) Container Name: Router.A
2018-03-08 14:49:02.797142 -0300 ROUTER (info) Router started in Standalone
mode
{code}
But if you try to add -d (daemon) flag, then it does not find the configuration
file.
{code:java}
[fgiorget@fgiorget qpid-dispatch]$ qdrouterd -d -c qdrouterd.conf
qdrouterd: Not found: Configuration file could not be opened{code}
It only works with fully qualified file name.
--
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-1638) Need to improve proton-c build tree layout
[ https://issues.apache.org/jira/browse/PROTON-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391527#comment-16391527 ] ASF GitHub Bot commented on PROTON-1638: GitHub user ssorj opened a pull request: https://github.com/apache/qpid-proton/pull/140 PROTON-1638, PROTON-1728: Reorganize the source tree I plan to squash this on merge. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ssorj/qpid-proton ssorj-reorganize-the-source-tree Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/140.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 #140 commit bb53a69334a88a0dbdb11550882b085660e765c7 Author: Justin Ross Date: 2017-12-21T14:32:50Z Remove old docs; some of this content will be restored to new locations commit 6a0801b08e47f888d5074def67eb65f237e8f884 Author: Justin Ross Date: 2017-12-21T17:39:06Z Rename version.txt to VERSION.txt commit 4dddef8019633f47f537645440c439d17102f349 Author: Justin Ross Date: 2017-12-21T18:00:14Z Add a .txt extension to LICENSE and NOTICE, for nicer behavior on Windows commit 654874b7ad62e3e850e4cc15fc7f6fb18d703690 Author: Justin Ross Date: 2017-12-21T18:21:29Z Fixups for file name conventions commit 7ce68cadcd25e718e87d8aa8241344f1f8ac81b7 Author: Justin Ross Date: 2017-12-21T18:29:48Z Rename tools/py to tools/python to match the other python dirs commit f36eba5aa4a988fe01432f19415c9878e6f5eec7 Author: Justin Ross Date: 2017-12-21T18:33:39Z Make a space for ancillary files commit 2beb5236ca6e0647c814a659db8d34bc4e3a1e94 Author: Justin Ross Date: 2017-12-21T18:46:30Z Move the docs dir to the top level commit 8a457c031132266014bc3b8f524c105d349495b6 Author: Justin Ross Date: 2017-12-21T19:06:23Z Move mllib to live with other python tools commit f0531db10070e9a37f049f4f629cbd8fbd906add Author: Justin Ross Date: 2017-12-21T20:03:51Z Move some includes and package configs to the top level commit 9bc93610f183e26e8c8a0ab9ba3678b15cf110f6 Author: Justin Ross Date: 2017-12-21T21:45:08Z Lift all of proton-c/* to the top level and adjust paths commit d1b359473f8e4ed899ed564a110866f8437ac68e Author: Justin Ross Date: 2017-12-21T22:29:34Z Adjust some reacharound paths commit 2d8f4b87e2a42dacdfe559a1b0530f7e21185398 Author: Justin Ross Date: 2017-12-21T22:33:49Z xproton.py is no longer used commit 6434aee3d7930555259deb498b1c3dadde16c526 Author: Justin Ross Date: 2017-12-21T22:44:03Z Move env.py with the other scripts in bin/ commit 4117280ca6b0d5eff0e3e6a8ca2818a6ac3c270c Author: Justin Ross Date: 2017-12-21T22:59:24Z Move tox.ini to misc/ commit 53facd9b7a676c1967983fd1c3ebf693cda46fb8 Author: Justin Ross Date: 2017-12-21T23:14:13Z Move the env config scripts to misc/; adjust the target for tox.ini.in commit 066afffcdd596613033fb44a14307106df07d0d5 Author: Justin Ross Date: 2017-12-21T23:17:51Z Move soak-check with the other scripts commit 781e3c9a586f6295ee1d84e363373eb7d22625c7 Author: Justin Ross Date: 2017-12-21T23:27:23Z Remove the C++ reactor app commit 2baa52785d683b6c4e68e99fd463e96d5d8bec0d Author: Justin Ross Date: 2017-12-21T23:42:29Z Move the legacy test apps to tools/test-apps/ commit 3864ff36be56c603f556d69918eb0cd17390 Author: Justin Ross Date: 2017-12-21T23:46:30Z Correct some paths I missed commit 7345c8c9e3174dea64580111e3f6a2cac189d9a9 Author: Justin Ross Date: 2017-12-21T23:49:37Z Rename appveyor.yml to .appveyor.yml commit b368b2a2b3adb351dfb3264b2a3c495d835d4e9d Author: Justin Ross Date: 2017-12-22T00:07:19Z Fix a broken path commit 82f3d53f93da9a53bf9c9b06e5e83fcadd1e056c Author: Justin Ross Date: 2017-12-22T00:26:41Z Move some of the less frequently used readme files to docs/ commit 4f87c3e5794b98ea0468593821070d2f433a3747 Author: Justin Ross Date: 2018-02-14T01:16:15Z Remove the perl, php, node, and javascript bindings commit a54afc17b38a4e4719afe286ffb55cc8e7c5e337 Author: Justin Ross Date: 2018-02-14T02:31:07Z Remove the messenger docs commit 4c7227bd906f4afb44ce61fff7c432df1fb1cd5d Author: Justin Ross Date: 2018-02-14T02:34:40Z Remove the python messenger API commit 00e3f95bb83756230a468d67a98ea32c64cd276b Author: Justin Ross Date: 2018-02-14T03:16:19Z Remove the ruby messenger API commit b931a410ba77bd49151cce52bbba69d15f1dd3d4 Author: Justin Ross Date: 2018-03-06T23:06:36Z Remove the reactor-based quick_perf commit 3a1f6c3b2af512f0c3ae01a6f526eb43ce2e45ef Author: Justin Ross Date: 2018-03-06T23:13:35Z Remove the python reactor-send impl commit af5ca6bfa90582d86d829697e28177bc
[GitHub] qpid-proton pull request #140: PROTON-1638, PROTON-1728: Reorganize the sour...
GitHub user ssorj opened a pull request: https://github.com/apache/qpid-proton/pull/140 PROTON-1638, PROTON-1728: Reorganize the source tree I plan to squash this on merge. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ssorj/qpid-proton ssorj-reorganize-the-source-tree Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/140.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 #140 commit bb53a69334a88a0dbdb11550882b085660e765c7 Author: Justin Ross Date: 2017-12-21T14:32:50Z Remove old docs; some of this content will be restored to new locations commit 6a0801b08e47f888d5074def67eb65f237e8f884 Author: Justin Ross Date: 2017-12-21T17:39:06Z Rename version.txt to VERSION.txt commit 4dddef8019633f47f537645440c439d17102f349 Author: Justin Ross Date: 2017-12-21T18:00:14Z Add a .txt extension to LICENSE and NOTICE, for nicer behavior on Windows commit 654874b7ad62e3e850e4cc15fc7f6fb18d703690 Author: Justin Ross Date: 2017-12-21T18:21:29Z Fixups for file name conventions commit 7ce68cadcd25e718e87d8aa8241344f1f8ac81b7 Author: Justin Ross Date: 2017-12-21T18:29:48Z Rename tools/py to tools/python to match the other python dirs commit f36eba5aa4a988fe01432f19415c9878e6f5eec7 Author: Justin Ross Date: 2017-12-21T18:33:39Z Make a space for ancillary files commit 2beb5236ca6e0647c814a659db8d34bc4e3a1e94 Author: Justin Ross Date: 2017-12-21T18:46:30Z Move the docs dir to the top level commit 8a457c031132266014bc3b8f524c105d349495b6 Author: Justin Ross Date: 2017-12-21T19:06:23Z Move mllib to live with other python tools commit f0531db10070e9a37f049f4f629cbd8fbd906add Author: Justin Ross Date: 2017-12-21T20:03:51Z Move some includes and package configs to the top level commit 9bc93610f183e26e8c8a0ab9ba3678b15cf110f6 Author: Justin Ross Date: 2017-12-21T21:45:08Z Lift all of proton-c/* to the top level and adjust paths commit d1b359473f8e4ed899ed564a110866f8437ac68e Author: Justin Ross Date: 2017-12-21T22:29:34Z Adjust some reacharound paths commit 2d8f4b87e2a42dacdfe559a1b0530f7e21185398 Author: Justin Ross Date: 2017-12-21T22:33:49Z xproton.py is no longer used commit 6434aee3d7930555259deb498b1c3dadde16c526 Author: Justin Ross Date: 2017-12-21T22:44:03Z Move env.py with the other scripts in bin/ commit 4117280ca6b0d5eff0e3e6a8ca2818a6ac3c270c Author: Justin Ross Date: 2017-12-21T22:59:24Z Move tox.ini to misc/ commit 53facd9b7a676c1967983fd1c3ebf693cda46fb8 Author: Justin Ross Date: 2017-12-21T23:14:13Z Move the env config scripts to misc/; adjust the target for tox.ini.in commit 066afffcdd596613033fb44a14307106df07d0d5 Author: Justin Ross Date: 2017-12-21T23:17:51Z Move soak-check with the other scripts commit 781e3c9a586f6295ee1d84e363373eb7d22625c7 Author: Justin Ross Date: 2017-12-21T23:27:23Z Remove the C++ reactor app commit 2baa52785d683b6c4e68e99fd463e96d5d8bec0d Author: Justin Ross Date: 2017-12-21T23:42:29Z Move the legacy test apps to tools/test-apps/ commit 3864ff36be56c603f556d69918eb0cd17390 Author: Justin Ross Date: 2017-12-21T23:46:30Z Correct some paths I missed commit 7345c8c9e3174dea64580111e3f6a2cac189d9a9 Author: Justin Ross Date: 2017-12-21T23:49:37Z Rename appveyor.yml to .appveyor.yml commit b368b2a2b3adb351dfb3264b2a3c495d835d4e9d Author: Justin Ross Date: 2017-12-22T00:07:19Z Fix a broken path commit 82f3d53f93da9a53bf9c9b06e5e83fcadd1e056c Author: Justin Ross Date: 2017-12-22T00:26:41Z Move some of the less frequently used readme files to docs/ commit 4f87c3e5794b98ea0468593821070d2f433a3747 Author: Justin Ross Date: 2018-02-14T01:16:15Z Remove the perl, php, node, and javascript bindings commit a54afc17b38a4e4719afe286ffb55cc8e7c5e337 Author: Justin Ross Date: 2018-02-14T02:31:07Z Remove the messenger docs commit 4c7227bd906f4afb44ce61fff7c432df1fb1cd5d Author: Justin Ross Date: 2018-02-14T02:34:40Z Remove the python messenger API commit 00e3f95bb83756230a468d67a98ea32c64cd276b Author: Justin Ross Date: 2018-02-14T03:16:19Z Remove the ruby messenger API commit b931a410ba77bd49151cce52bbba69d15f1dd3d4 Author: Justin Ross Date: 2018-03-06T23:06:36Z Remove the reactor-based quick_perf commit 3a1f6c3b2af512f0c3ae01a6f526eb43ce2e45ef Author: Justin Ross Date: 2018-03-06T23:13:35Z Remove the python reactor-send impl commit af5ca6bfa90582d86d829697e28177bce65a3617 Author: Justin Ross Date: 2018-03-07T01:18:19Z Correct a reach-around path in the ruby tests commit 892aad2f5e6db24ae65623fbf2a7d2d5f3b2ec71 Author: Justin Ross Date: 2018-03-07T13:31:11Z Move versions.cmake into src --- ---
Re: qpid-dispatch git commit: NO-JIRA - Modified code in server.c to reflect changes in proton API
I have reverted my earlier commit that changed the API functions that
dispatch used. I have made another commit to not fail the dispatch build if
there are warnings so dispatch will continue compiling when proton emits
warnings.As soon as the next version of proton is released we will change
dispatch master to use the new proton API functions and once again start to
fail the dispatch build on warnings.
Thanks.
On Thu, Mar 8, 2018 at 9:47 AM, Robbie Gemmell
wrote:
> I assume this is due to PROTON-1781, and means that Dispatch master
> requries use of Proton master now. Is that desired, and if so is there
> some version checking or documentation (e.g README) that maybe needs
> updated now to reflect that?
>
> Robbie
>
> On 7 March 2018 at 13:53, wrote:
> > Repository: qpid-dispatch
> > Updated Branches:
> > refs/heads/master 35b1c3f83 -> 11181b878
> >
> >
> > NO-JIRA - Modified code in server.c to reflect changes in proton API
> >
> >
> > Project: http://git-wip-us.apache.org/repos/asf/qpid-dispatch/repo
> > Commit: http://git-wip-us.apache.org/repos/asf/qpid-dispatch/
> commit/11181b87
> > Tree: http://git-wip-us.apache.org/repos/asf/qpid-dispatch/tree/11181b87
> > Diff: http://git-wip-us.apache.org/repos/asf/qpid-dispatch/diff/11181b87
> >
> > Branch: refs/heads/master
> > Commit: 11181b878265861308614dcb25c3021bf5887edc
> > Parents: 35b1c3f
> > Author: Ganesh Murthy
> > Authored: Wed Mar 7 08:52:47 2018 -0500
> > Committer: Ganesh Murthy
> > Committed: Wed Mar 7 08:52:47 2018 -0500
> >
> > --
> > src/server.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> > --
> >
> >
> > http://git-wip-us.apache.org/repos/asf/qpid-dispatch/blob/
> 11181b87/src/server.c
> > --
> > diff --git a/src/server.c b/src/server.c
> > index d27260d..8e65b07 100644
> > --- a/src/server.c
> > +++ b/src/server.c
> > @@ -579,8 +579,8 @@ void connect_fail(qd_connection_t *ctx, const char
> *name, const char *descriptio
> > /* Get the host IP address for the remote end */
> > static void set_rhost_port(qd_connection_t *ctx) {
> > pn_transport_t *tport = pn_connection_transport(ctx->pn_conn);
> > -const struct sockaddr* sa = pn_netaddr_sockaddr(pn_
> netaddr_remote(tport));
> > -size_t salen = pn_netaddr_socklen(pn_netaddr_remote(tport));
> > +const struct sockaddr* sa = pn_netaddr_sockaddr(pn_
> transport_remote_addr(tport));
> > +size_t salen = pn_netaddr_socklen(pn_transport_remote_addr(tport));
> > if (sa && salen) {
> > char rport[NI_MAXSERV] = "";
> > int err = getnameinfo(sa, salen,
> > @@ -707,7 +707,7 @@ static void handle_listener(pn_event_t *e,
> qd_server_t *qd_server) {
> > if (strcmp(port, "0") == 0) {
> > // If a 0 (zero) is specified for a port, get the actual
> listening port from the listener.
> > pn_listener_t *l = pn_event_listener(e);
> > -const pn_netaddr_t *na = pn_netaddr_listening(l);
> > +const pn_netaddr_t *na = pn_listener_addr(l);
> > char str[PN_MAX_ADDR] = "";
> > pn_netaddr_str(na, str, sizeof(str));
> > // "str" contains the host and port on which this listener
> is listening.
> >
> >
> > -
> > To unsubscribe, e-mail: commits-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: commits-h...@qpid.apache.org
> >
>
Re: qpid-dispatch git commit: NO-JIRA - Modified code in server.c to reflect changes in proton API
I assume this is due to PROTON-1781, and means that Dispatch master
requries use of Proton master now. Is that desired, and if so is there
some version checking or documentation (e.g README) that maybe needs
updated now to reflect that?
Robbie
On 7 March 2018 at 13:53, wrote:
> Repository: qpid-dispatch
> Updated Branches:
> refs/heads/master 35b1c3f83 -> 11181b878
>
>
> NO-JIRA - Modified code in server.c to reflect changes in proton API
>
>
> Project: http://git-wip-us.apache.org/repos/asf/qpid-dispatch/repo
> Commit: http://git-wip-us.apache.org/repos/asf/qpid-dispatch/commit/11181b87
> Tree: http://git-wip-us.apache.org/repos/asf/qpid-dispatch/tree/11181b87
> Diff: http://git-wip-us.apache.org/repos/asf/qpid-dispatch/diff/11181b87
>
> Branch: refs/heads/master
> Commit: 11181b878265861308614dcb25c3021bf5887edc
> Parents: 35b1c3f
> Author: Ganesh Murthy
> Authored: Wed Mar 7 08:52:47 2018 -0500
> Committer: Ganesh Murthy
> Committed: Wed Mar 7 08:52:47 2018 -0500
>
> --
> src/server.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/qpid-dispatch/blob/11181b87/src/server.c
> --
> diff --git a/src/server.c b/src/server.c
> index d27260d..8e65b07 100644
> --- a/src/server.c
> +++ b/src/server.c
> @@ -579,8 +579,8 @@ void connect_fail(qd_connection_t *ctx, const char *name,
> const char *descriptio
> /* Get the host IP address for the remote end */
> static void set_rhost_port(qd_connection_t *ctx) {
> pn_transport_t *tport = pn_connection_transport(ctx->pn_conn);
> -const struct sockaddr* sa =
> pn_netaddr_sockaddr(pn_netaddr_remote(tport));
> -size_t salen = pn_netaddr_socklen(pn_netaddr_remote(tport));
> +const struct sockaddr* sa =
> pn_netaddr_sockaddr(pn_transport_remote_addr(tport));
> +size_t salen = pn_netaddr_socklen(pn_transport_remote_addr(tport));
> if (sa && salen) {
> char rport[NI_MAXSERV] = "";
> int err = getnameinfo(sa, salen,
> @@ -707,7 +707,7 @@ static void handle_listener(pn_event_t *e, qd_server_t
> *qd_server) {
> if (strcmp(port, "0") == 0) {
> // If a 0 (zero) is specified for a port, get the actual
> listening port from the listener.
> pn_listener_t *l = pn_event_listener(e);
> -const pn_netaddr_t *na = pn_netaddr_listening(l);
> +const pn_netaddr_t *na = pn_listener_addr(l);
> char str[PN_MAX_ADDR] = "";
> pn_netaddr_str(na, str, sizeof(str));
> // "str" contains the host and port on which this listener is
> listening.
>
>
> -
> To unsubscribe, e-mail: commits-unsubscr...@qpid.apache.org
> For additional commands, e-mail: commits-h...@qpid.apache.org
>
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1786) Multiframe transfer wire traffic patterns differ substantially
[
https://issues.apache.org/jira/browse/PROTON-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391320#comment-16391320
]
Robbie Gemmell commented on PROTON-1786:
TCP and/or Proton transport buffer sizing, plus each peers independent max
frame sizes and perhaps even session window sizing, will all come into play if
shuffling through enough large frames bit by bit.
> Multiframe transfer wire traffic patterns differ substantially
> --
>
> Key: PROTON-1786
> URL: https://issues.apache.org/jira/browse/PROTON-1786
> Project: Qpid Proton
> Issue Type: Task
>Reporter: Kim van der Riet
>Priority: Major
> Attachments: dispatch.multiframe.07.pcapng
>
>
> This is not a bug (although it could become one), but rather an observation
> of large message transfer patterns observed using Wireshark while running
> Qpid Interop Test's amqp_large_content_test.
> The test sends large messages through a broker (in this case, dispatch
> router) of size 1MB and 10MB.
> I hope to add other observable patterns from other clients and/or brokers if
> they are significant. If there is consensus that this is a potential large
> message transfer efficiency issue, then this Jira can be a placeholder for
> this issue.
> See the attached file for an example. In this test, the receiver is using
> TCP port 59806 and the sender port 59808. The router is using the standard
> AMQP port.
> h2. C++ client:
> The client in this case uses the Proton C++ API and is based on the
> SimpleSender.cpp example. To isolate the traffic from this client, use the
> following filter in Wireshark:
> {noformat}
> amqp.performative == transfer && tcp.srcport == 59808{noformat}
> It can be seen that although there is a large message being sent, the sender
> appears to be restricted to a single transfer of 16kB or a 64kB frame
> containing 4 transfers (very occasionally, 2, 3 or 5 transfers) - for example:
> {noformat}
> 351.972620::1 ::1 AMQP16470 transfer
> 1177 2.032878::1 ::1 AMQP65550 transfer transfer
> transfer transfer
> {noformat}
> h2. Dispatch Router:
> This uses Proton through its native C interface. To isolate the traffic from
> the router to the receiver, use the following Wireshark filter:
> {noformat}
> amqp.performative == transfer && tcp.dstport == 59806{noformat}
> The traffic for this broker looks very different. Each frame contains only a
> single transfer, and the size of the transfers differ widely, from 196 bytes
> to the full 64kB max. I am assuming that the router is sending on message
> content it has received as soon as it becomes available no matter the size.
--
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-1786) Multiframe transfer wire traffic patterns differ substantially
[
https://issues.apache.org/jira/browse/PROTON-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391296#comment-16391296
]
Kim van der Riet commented on PROTON-1786:
--
I think the issue that seems strange to me with the C++ client is that there is
nothing to wait for. It has the complete large message, so it can carve it up
as it sees fit. But using 16kB frames? Maybe it is not as big a real
performance issue as I imagine it might be.
> Multiframe transfer wire traffic patterns differ substantially
> --
>
> Key: PROTON-1786
> URL: https://issues.apache.org/jira/browse/PROTON-1786
> Project: Qpid Proton
> Issue Type: Task
>Reporter: Kim van der Riet
>Priority: Major
> Attachments: dispatch.multiframe.07.pcapng
>
>
> This is not a bug (although it could become one), but rather an observation
> of large message transfer patterns observed using Wireshark while running
> Qpid Interop Test's amqp_large_content_test.
> The test sends large messages through a broker (in this case, dispatch
> router) of size 1MB and 10MB.
> I hope to add other observable patterns from other clients and/or brokers if
> they are significant. If there is consensus that this is a potential large
> message transfer efficiency issue, then this Jira can be a placeholder for
> this issue.
> See the attached file for an example. In this test, the receiver is using
> TCP port 59806 and the sender port 59808. The router is using the standard
> AMQP port.
> h2. C++ client:
> The client in this case uses the Proton C++ API and is based on the
> SimpleSender.cpp example. To isolate the traffic from this client, use the
> following filter in Wireshark:
> {noformat}
> amqp.performative == transfer && tcp.srcport == 59808{noformat}
> It can be seen that although there is a large message being sent, the sender
> appears to be restricted to a single transfer of 16kB or a 64kB frame
> containing 4 transfers (very occasionally, 2, 3 or 5 transfers) - for example:
> {noformat}
> 351.972620::1 ::1 AMQP16470 transfer
> 1177 2.032878::1 ::1 AMQP65550 transfer transfer
> transfer transfer
> {noformat}
> h2. Dispatch Router:
> This uses Proton through its native C interface. To isolate the traffic from
> the router to the receiver, use the following Wireshark filter:
> {noformat}
> amqp.performative == transfer && tcp.dstport == 59806{noformat}
> The traffic for this broker looks very different. Each frame contains only a
> single transfer, and the size of the transfers differ widely, from 196 bytes
> to the full 64kB max. I am assuming that the router is sending on message
> content it has received as soon as it becomes available no matter the size.
--
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-8119) Create a standalone web management console (WMC)
[ https://issues.apache.org/jira/browse/QPID-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391246#comment-16391246 ] Lorenz Quack commented on QPID-8119: A while ago I started a small proof of concept to demonstrate how we could implement a standalone WMC using angularJS 1. My attempt at using angularJS 2 failed quite miserably due to my inability to wrap my head around all the boilerplate, transpiling, and auxiliary tools and libs.I have not touched the code since I gave the demo at work in 2016. However, I thought that experiment might be useful in case someone ever wants to pursue something in this direction. So I just zipped it up and attached it here just as it was lying around on my disk without and cleanup (well, I did delete the "node_modules" and "bower_components" directories) or instructions. sorry. I had no prior experience with angularJS and the JS ecosystem so I am sure there are nicer and more idiomatic ways of doing things. It is what it is. I'll leave it at that. Do with the code as you will: Release, Relicense, Laugh at, Rip apart, Put back together again, Burn in a pyre, completely ignore, ... all are fair game and hereby explicitly permitted! > Create a standalone web management console (WMC) > > > Key: QPID-8119 > URL: https://issues.apache.org/jira/browse/QPID-8119 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Lorenz Quack >Priority: Minor > Attachments: qpid_wmc_ajs.tar.bz2 > > > For several reasons having a standalone web management console (WMC) might be > desirable: > * separation of concerns > * sepatate development and release cycles > * standalone WMC could connect to multiple brokers/virtualhosts (maybe even > non-qpid broker) > * standalone WMC available when broker is down (restarts) > * ... -- 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-8119) Create a standalone web management console (WMC)
[ https://issues.apache.org/jira/browse/QPID-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack updated QPID-8119: --- Attachment: qpid_wmc_ajs.tar.bz2 > Create a standalone web management console (WMC) > > > Key: QPID-8119 > URL: https://issues.apache.org/jira/browse/QPID-8119 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Lorenz Quack >Priority: Minor > Attachments: qpid_wmc_ajs.tar.bz2 > > > For several reasons having a standalone web management console (WMC) might be > desirable: > * separation of concerns > * sepatate development and release cycles > * standalone WMC could connect to multiple brokers/virtualhosts (maybe even > non-qpid broker) > * standalone WMC available when broker is down (restarts) > * ... -- 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-8119) Create a standalone web management console (WMC)
Lorenz Quack created QPID-8119: -- Summary: Create a standalone web management console (WMC) Key: QPID-8119 URL: https://issues.apache.org/jira/browse/QPID-8119 Project: Qpid Issue Type: Improvement Components: Broker-J Reporter: Lorenz Quack For several reasons having a standalone web management console (WMC) might be desirable: * separation of concerns * sepatate development and release cycles * standalone WMC could connect to multiple brokers/virtualhosts (maybe even non-qpid broker) * standalone WMC available when broker is down (restarts) * ... -- 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-8118) qpidd crashes at startup in certain conditions
[ https://issues.apache.org/jira/browse/QPID-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-8118: Assignee: Gordon Sim Fix Version/s: qpid-cpp-1.38.0 > qpidd crashes at startup in certain conditions > -- > > Key: QPID-8118 > URL: https://issues.apache.org/jira/browse/QPID-8118 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: qpid-cpp-1.37.0 >Reporter: Michael >Assignee: Gordon Sim >Priority: Major > Fix For: qpid-cpp-1.38.0 > > Attachments: qpidd-cpp-rdma.patch > > > On my debian/sid system qpidd crashed at startup. Quick investigation has > shown that the problem was in deviceCount() function from rdma_wrap.cpp > module. Patch with fix is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8118) qpidd crashes at startup in certain conditions
[ https://issues.apache.org/jira/browse/QPID-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-8118. -- Resolution: Fixed Thanks again Michael! > qpidd crashes at startup in certain conditions > -- > > Key: QPID-8118 > URL: https://issues.apache.org/jira/browse/QPID-8118 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: qpid-cpp-1.37.0 >Reporter: Michael >Priority: Major > Attachments: qpidd-cpp-rdma.patch > > > On my debian/sid system qpidd crashed at startup. Quick investigation has > shown that the problem was in deviceCount() function from rdma_wrap.cpp > module. Patch with fix is attached. -- 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-8118) qpidd crashes at startup in certain conditions
[ https://issues.apache.org/jira/browse/QPID-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391049#comment-16391049 ] ASF subversion and git services commented on QPID-8118: --- Commit 790d0fc849ba9e45c26c381557d7813967eaa325 in qpid-cpp's branch refs/heads/master from [~gsim] [ https://git-wip-us.apache.org/repos/asf?p=qpid-cpp.git;h=790d0fc ] QPID-8118: check device list before freeing Patch from Michael Ivanov > qpidd crashes at startup in certain conditions > -- > > Key: QPID-8118 > URL: https://issues.apache.org/jira/browse/QPID-8118 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: qpid-cpp-1.37.0 >Reporter: Michael >Priority: Major > Attachments: qpidd-cpp-rdma.patch > > > On my debian/sid system qpidd crashed at startup. Quick investigation has > shown that the problem was in deviceCount() function from rdma_wrap.cpp > module. Patch with fix is attached. -- 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-1786) Multiframe transfer wire traffic patterns differ substantially
[
https://issues.apache.org/jira/browse/PROTON-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390976#comment-16390976
]
Robbie Gemmell commented on PROTON-1786:
As you note, this will almost certainly be due to Dispatch handing over the
variable sizes of partial message content that you see and then processing the
proton transport, which then sends all it can of what it has been given. I
don't think you will see this behaviour from any other peers currently.
The only thing proton could do differently is deliberately not send what it has
been given and asked to send, which might seem odd to some, e.g imposing a
'minimum frame size' on outgoing frames with more=true. The router could more
simply choose not send the partial data while below a certain size.
> Multiframe transfer wire traffic patterns differ substantially
> --
>
> Key: PROTON-1786
> URL: https://issues.apache.org/jira/browse/PROTON-1786
> Project: Qpid Proton
> Issue Type: Task
>Reporter: Kim van der Riet
>Priority: Major
> Attachments: dispatch.multiframe.07.pcapng
>
>
> This is not a bug (although it could become one), but rather an observation
> of large message transfer patterns observed using Wireshark while running
> Qpid Interop Test's amqp_large_content_test.
> The test sends large messages through a broker (in this case, dispatch
> router) of size 1MB and 10MB.
> I hope to add other observable patterns from other clients and/or brokers if
> they are significant. If there is consensus that this is a potential large
> message transfer efficiency issue, then this Jira can be a placeholder for
> this issue.
> See the attached file for an example. In this test, the receiver is using
> TCP port 59806 and the sender port 59808. The router is using the standard
> AMQP port.
> h2. C++ client:
> The client in this case uses the Proton C++ API and is based on the
> SimpleSender.cpp example. To isolate the traffic from this client, use the
> following filter in Wireshark:
> {noformat}
> amqp.performative == transfer && tcp.srcport == 59808{noformat}
> It can be seen that although there is a large message being sent, the sender
> appears to be restricted to a single transfer of 16kB or a 64kB frame
> containing 4 transfers (very occasionally, 2, 3 or 5 transfers) - for example:
> {noformat}
> 351.972620::1 ::1 AMQP16470 transfer
> 1177 2.032878::1 ::1 AMQP65550 transfer transfer
> transfer transfer
> {noformat}
> h2. Dispatch Router:
> This uses Proton through its native C interface. To isolate the traffic from
> the router to the receiver, use the following Wireshark filter:
> {noformat}
> amqp.performative == transfer && tcp.dstport == 59806{noformat}
> The traffic for this broker looks very different. Each frame contains only a
> single transfer, and the size of the transfers differ widely, from 196 bytes
> to the full 64kB max. I am assuming that the router is sending on message
> content it has received as soon as it becomes available no matter the size.
--
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
