[jira] [Commented] (DISPATCH-56) Implement Create/Read/Update/Delete operations in the agent
[ https://issues.apache.org/jira/browse/DISPATCH-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127995#comment-14127995 ] ASF subversion and git services commented on DISPATCH-56: - Commit 1623899 from [~aconway] in branch 'dispatch/trunk' [ https://svn.apache.org/r1623899 ] DISPATCH-56: Make dispatch management client library public. The dispatch management client library is now installed as a normal python package qpid_dispatch.management - Added management.Entity with read, update, delete operations. - Added setup.py.in to install python packages to standard site-directory for CMAKE_INSTALL_PREFIX - Added VERSION.txt with project version, available in cmake as QPID_DISPATCH_VERSION - Separate proton.Messenger code from client.Node. - Add CRUD permissions to schema. Fix status return codes for CRUD ops. - Added DummyEntity to test CRUD, implements all 4 operations. > Implement Create/Read/Update/Delete operations in the agent > --- > > Key: DISPATCH-56 > URL: https://issues.apache.org/jira/browse/DISPATCH-56 > Project: Qpid Dispatch > Issue Type: Sub-task > Components: Management Agent >Reporter: Ted Ross >Assignee: Alan Conway > Fix For: 0.3 > > > Implement the CRUD-style commands in the management agent and use them to > access waypoints, address-prefixes, self, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6089) Qpidd doesn't correctly parse --known-hosts-url option
[ https://issues.apache.org/jira/browse/QPID-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127661#comment-14127661 ] Andrew Stitcher commented on QPID-6089: --- The cause of this problem is that there is currently no code in the broker to add protocols to the Url parser so that it recognises them. > Qpidd doesn't correctly parse --known-hosts-url option > -- > > Key: QPID-6089 > URL: https://issues.apache.org/jira/browse/QPID-6089 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.22 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > > The broker doesn't correctly parse fully specified connections urls for the > --known-hosts-url option, instead it will refuse to start. For example: > qpidd --no-module-dir --known-hosts-url amqp:tcp:localhost:5672 > Will fail to startup. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6089) Qpidd doesn't correctly parse --known-hosts-url option
[ https://issues.apache.org/jira/browse/QPID-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127660#comment-14127660 ] ASF subversion and git services commented on QPID-6089: --- Commit 1623882 from [~astitcher] in branch 'qpid/trunk' [ https://svn.apache.org/r1623882 ] QPID-6089: Need to register transports with the Url parser. > Qpidd doesn't correctly parse --known-hosts-url option > -- > > Key: QPID-6089 > URL: https://issues.apache.org/jira/browse/QPID-6089 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.22 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > > The broker doesn't correctly parse fully specified connections urls for the > --known-hosts-url option, instead it will refuse to start. For example: > qpidd --no-module-dir --known-hosts-url amqp:tcp:localhost:5672 > Will fail to startup. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-6089) Qpidd doesn't correctly parse --known-hosts-url option
Andrew Stitcher created QPID-6089: - Summary: Qpidd doesn't correctly parse --known-hosts-url option Key: QPID-6089 URL: https://issues.apache.org/jira/browse/QPID-6089 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.22 Reporter: Andrew Stitcher Assignee: Andrew Stitcher The broker doesn't correctly parse fully specified connections urls for the --known-hosts-url option, instead it will refuse to start. For example: qpidd --no-module-dir --known-hosts-url amqp:tcp:localhost:5672 Will fail to startup. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-6007) qpid-route uses machine hostname if host not given
[ https://issues.apache.org/jira/browse/QPID-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved QPID-6007. --- Resolution: Fixed Fix Version/s: 0.31 Assignee: Justin Ross > qpid-route uses machine hostname if host not given > -- > > Key: QPID-6007 > URL: https://issues.apache.org/jira/browse/QPID-6007 > Project: Qpid > Issue Type: Bug > Components: Python Tools >Affects Versions: 0.18, 0.22 >Reporter: Ernest Allen >Assignee: Justin Ross >Priority: Minor > Fix For: 0.31 > > Attachments: bz1121632.patch > > > When a broker address is not supplied to qpid-route, it attempts to use the > machines hostname as the broker address. This works well when the hostname is > translatable to an ip address. However, when the hostname has been set to a > non-translatable string, qpid-route fails. > For backwards compatability, qpid-route should continue to use hostname when > the broker address is not supplied, but if hostname is not a valid address, > qpid-route should default to "localhost". > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6007) qpid-route uses machine hostname if host not given
[ https://issues.apache.org/jira/browse/QPID-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127435#comment-14127435 ] ASF subversion and git services commented on QPID-6007: --- Commit 1623871 from [~justi9] in branch 'qpid/trunk' [ https://svn.apache.org/r1623871 ] QPID-6007: Test if hostname is valid; if not, default to trying localhost; this is a patch from Ernie Allen > qpid-route uses machine hostname if host not given > -- > > Key: QPID-6007 > URL: https://issues.apache.org/jira/browse/QPID-6007 > Project: Qpid > Issue Type: Bug > Components: Python Tools >Affects Versions: 0.18, 0.22 >Reporter: Ernest Allen >Priority: Minor > Attachments: bz1121632.patch > > > When a broker address is not supplied to qpid-route, it attempts to use the > machines hostname as the broker address. This works well when the hostname is > translatable to an ip address. However, when the hostname has been set to a > non-translatable string, qpid-route fails. > For backwards compatability, qpid-route should continue to use hostname when > the broker address is not supplied, but if hostname is not a valid address, > qpid-route should default to "localhost". > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6074) BDB HA VHN to use context variables rather than system property to control timeouts etc
[ https://issues.apache.org/jira/browse/QPID-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127351#comment-14127351 ] Keith Wall commented on QPID-6074: -- Hi Alex These defaults are a concern of ReplicatedEnvironmentFacade and not the BDBHAVHN model object. For me this is the same as the Bone CP defaults: these belong to BoneCPConnectionProvider and not the JDBCVHN (or JDBCVH).It is true the default values won't be available through the model and we will need to describe these in documentation We can do this is the same part of the documentation that talks of the ability to set je.* values on BDB VHN/VH to affect the behaviour of JE. I doubt most users have need to adjust these values. Does this sound reasonable? > BDB HA VHN to use context variables rather than system property to control > timeouts etc > --- > > Key: QPID-6074 > URL: https://issues.apache.org/jira/browse/QPID-6074 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Alex Rudyy > Fix For: 0.31 > > > The BDB HA VHN implementation currently uses system properties for a number > of timeout values, polling frequencies and retry intervals. These should be > converted to context variables. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5786) Memory leak in qpid-java-broker-0.26.tar.gz
[ https://issues.apache.org/jira/browse/QPID-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127115#comment-14127115 ] Rob Godfrey commented on QPID-5786: --- You can already add "limits" which cause logging when the size is breached (and you can set defaults at the virtual host level so they apply to new (temporary) queues as they are created). Similarly you can set flow control limits that enforce a size limit on the queue. The process for doing both these things has changed a bit in 0.30, but will be stable going forward. One feature yet to be added - though I think there is a JIRA for it, and if not we'll raise one - is to forcibly disconnect clients that ignore flow control requests - I'll be aiming to get that into the broker for 0.32. > Memory leak in qpid-java-broker-0.26.tar.gz > --- > > Key: QPID-5786 > URL: https://issues.apache.org/jira/browse/QPID-5786 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.26 > Environment: Linux Mint 15 (64 Bit) - any Linux version should do > Java // OpenJDK Runtime Environment (IcedTea 2.4.4) > also tested with Java(TM) SE Runtime Environment (build 1.6.0_26-b03) > Ruby 1.8.7 > Ruby Bunny Gem 1.2.2 >Reporter: Bobby Flitter > Attachments: amqp_bunny_qpid.pcap > > > When using the hello bunny example program from Ruby together with Apache > qpid server the memory consumption of qpid seems to grow continuously. > Steps to reproduce the problem in Linux: > wget > http://ftp-stud.hs-esslingen.de/pub/Mirrors/ftp.apache.org/dist/qpid/0.26/qpid-java-broker-0.26.tar.gz > tar xzvf qpid-java-broker-0.26.tar.gz > cd qpid-broker-0.26/bin/ > ./qpid-server > - in a new terminal > - meanwhile bunny 1.2.2. is available > - install ruby amqp bunny > sudo gem install bunny > - download hello bunny example > wget http://pastebin.com/raw.php?i=f6MesMCZ -O hello_bunny.rb > while true; do ruby hello_bunny.rb ; done > - in another terminal: > while true; do grep "^VmRSS" /proc/$(pgrep -f qpid)/status ; sleep 1;done > - memory consumption of java qpid is growing continuously until > OutOfMemoryError ends the server > Unhandled Exception java.lang.OutOfMemoryError: Java heap space in Thread > Thread-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5786) Memory leak in qpid-java-broker-0.26.tar.gz
[ https://issues.apache.org/jira/browse/QPID-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127094#comment-14127094 ] Bobby Flitter commented on QPID-5786: - Thank you again. Your query works with Eclipse Memory Analyzer. It seems that the memory growth of qpid with "normal" connections and the crash with too many messages in one queue are not related to each other. Therefore I only focus on the messages in the queue. I'm going to have a look at "bunny" qos and which of my processes writes so many log messages. If you introduce a limit for the number of messages in a queue in qpid with a self-speaking exception and a log message when the limit is reached, then you can close the issue. > Memory leak in qpid-java-broker-0.26.tar.gz > --- > > Key: QPID-5786 > URL: https://issues.apache.org/jira/browse/QPID-5786 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.26 > Environment: Linux Mint 15 (64 Bit) - any Linux version should do > Java // OpenJDK Runtime Environment (IcedTea 2.4.4) > also tested with Java(TM) SE Runtime Environment (build 1.6.0_26-b03) > Ruby 1.8.7 > Ruby Bunny Gem 1.2.2 >Reporter: Bobby Flitter > Attachments: amqp_bunny_qpid.pcap > > > When using the hello bunny example program from Ruby together with Apache > qpid server the memory consumption of qpid seems to grow continuously. > Steps to reproduce the problem in Linux: > wget > http://ftp-stud.hs-esslingen.de/pub/Mirrors/ftp.apache.org/dist/qpid/0.26/qpid-java-broker-0.26.tar.gz > tar xzvf qpid-java-broker-0.26.tar.gz > cd qpid-broker-0.26/bin/ > ./qpid-server > - in a new terminal > - meanwhile bunny 1.2.2. is available > - install ruby amqp bunny > sudo gem install bunny > - download hello bunny example > wget http://pastebin.com/raw.php?i=f6MesMCZ -O hello_bunny.rb > while true; do ruby hello_bunny.rb ; done > - in another terminal: > while true; do grep "^VmRSS" /proc/$(pgrep -f qpid)/status ; sleep 1;done > - memory consumption of java qpid is growing continuously until > OutOfMemoryError ends the server > Unhandled Exception java.lang.OutOfMemoryError: Java heap space in Thread > Thread-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5786) Memory leak in qpid-java-broker-0.26.tar.gz
[ https://issues.apache.org/jira/browse/QPID-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126970#comment-14126970 ] Rob Godfrey commented on QPID-5786: --- I also note that you are using a prefetch of 1... For a maximal throughput you might consider increasing this as otherwise you are going to suffer latency delays on receipt of messages. With a prefetch of 1, a new message is not send to the client until the previous message has been processed, and the acknowledgement has been received and processed by the broker. Where there is only one consumer on a given queue, one can increase the prefetch without fear of starving competing consumers - and increasing throughput by always having the next message on hand as soon as the previous message has finished processing. I'm not sure of the API which you are using for your client, but in AMQP 0-9-1 terms this is defined in terms of the Basic.QoS command in the "prefetch-count". > Memory leak in qpid-java-broker-0.26.tar.gz > --- > > Key: QPID-5786 > URL: https://issues.apache.org/jira/browse/QPID-5786 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.26 > Environment: Linux Mint 15 (64 Bit) - any Linux version should do > Java // OpenJDK Runtime Environment (IcedTea 2.4.4) > also tested with Java(TM) SE Runtime Environment (build 1.6.0_26-b03) > Ruby 1.8.7 > Ruby Bunny Gem 1.2.2 >Reporter: Bobby Flitter > Attachments: amqp_bunny_qpid.pcap > > > When using the hello bunny example program from Ruby together with Apache > qpid server the memory consumption of qpid seems to grow continuously. > Steps to reproduce the problem in Linux: > wget > http://ftp-stud.hs-esslingen.de/pub/Mirrors/ftp.apache.org/dist/qpid/0.26/qpid-java-broker-0.26.tar.gz > tar xzvf qpid-java-broker-0.26.tar.gz > cd qpid-broker-0.26/bin/ > ./qpid-server > - in a new terminal > - meanwhile bunny 1.2.2. is available > - install ruby amqp bunny > sudo gem install bunny > - download hello bunny example > wget http://pastebin.com/raw.php?i=f6MesMCZ -O hello_bunny.rb > while true; do ruby hello_bunny.rb ; done > - in another terminal: > while true; do grep "^VmRSS" /proc/$(pgrep -f qpid)/status ; sleep 1;done > - memory consumption of java qpid is growing continuously until > OutOfMemoryError ends the server > Unhandled Exception java.lang.OutOfMemoryError: Java heap space in Thread > Thread-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5786) Memory leak in qpid-java-broker-0.26.tar.gz
[
https://issues.apache.org/jira/browse/QPID-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126964#comment-14126964
]
Rob Godfrey commented on QPID-5786:
---
This query should help:
{noformat}
select "Exchange: '" + b._exchange._name.toString() + "', Queue: '" +
b._queue._name.toString() + "', Routing Key: '" + b._name.toString() + "',
Queue size: " + b._queue._atomicQueueCount.value
from org.apache.qpid.server.binding.BindingImpl b where
b._queue._atomicQueueCount.value > 0
{noformat}
from your heap dump I get:
{noformat}
Exchange: 'exchange.pte.log', Queue:
'tmp_58c26acf-f4be-40a8-b6a7-7b11a7cbd2f4', Routing Key: '', Queue size: 1398340
{noformat}
> Memory leak in qpid-java-broker-0.26.tar.gz
> ---
>
> Key: QPID-5786
> URL: https://issues.apache.org/jira/browse/QPID-5786
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.26
> Environment: Linux Mint 15 (64 Bit) - any Linux version should do
> Java // OpenJDK Runtime Environment (IcedTea 2.4.4)
> also tested with Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
> Ruby 1.8.7
> Ruby Bunny Gem 1.2.2
>Reporter: Bobby Flitter
> Attachments: amqp_bunny_qpid.pcap
>
>
> When using the hello bunny example program from Ruby together with Apache
> qpid server the memory consumption of qpid seems to grow continuously.
> Steps to reproduce the problem in Linux:
> wget
> http://ftp-stud.hs-esslingen.de/pub/Mirrors/ftp.apache.org/dist/qpid/0.26/qpid-java-broker-0.26.tar.gz
> tar xzvf qpid-java-broker-0.26.tar.gz
> cd qpid-broker-0.26/bin/
> ./qpid-server
> - in a new terminal
> - meanwhile bunny 1.2.2. is available
> - install ruby amqp bunny
> sudo gem install bunny
> - download hello bunny example
> wget http://pastebin.com/raw.php?i=f6MesMCZ -O hello_bunny.rb
> while true; do ruby hello_bunny.rb ; done
> - in another terminal:
> while true; do grep "^VmRSS" /proc/$(pgrep -f qpid)/status ; sleep 1;done
> - memory consumption of java qpid is growing continuously until
> OutOfMemoryError ends the server
> Unhandled Exception java.lang.OutOfMemoryError: Java heap space in Thread
> Thread-1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5033) [Windows C++ client] An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full
[ https://issues.apache.org/jira/browse/QPID-5033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen resolved QPID-5033. Resolution: Fixed Fix Version/s: 0.31 > [Windows C++ client] An operation on a socket could not be performed because > the system lacked sufficient buffer space or because a queue was full > -- > > Key: QPID-5033 > URL: https://issues.apache.org/jira/browse/QPID-5033 > Project: Qpid > Issue Type: Bug > Components: C++ Client > Environment: Windows, different versions >Reporter: JAkub Scholz >Assignee: Cliff Jansen > Fix For: 0.31 > > Attachments: client-trace.log, client.cpp > > > As discussed on the user mailing list > (http://qpid.2158936.n2.nabble.com/Qpid-throwed-WSAENOBUFS-while-receiving-data-from-a-broker-td7592938.html), > when receiving a large amounts of messages over SSL using a receiver > prefetch, the clients fails with an exception "An operation on a socket could > not be performed because the system lacked sufficient buffer space or because > a queue was full". This exception seems to originate from the SslAsynchIO > class, method sslDataIn. > Decreasing the capacity seems to improve the frequency with which the problem > appears. However with 1MB messages, even capacity 1 doesn't seem to work. The > problem seems to be quite easy to reproduce using following scenario: > 1) Create a large queue on a broker (C++ / Linux) > 2) Start feeding messages into the queue using C++/Linux program (in my case > I used approximately 1kB messages) > 3) Connect with a receiver (C++/Windows) using SSL and prefetch 1000 (no > client authentication, I used username & password) > 4) Wait few seconds to see the error in the receiver > The source code of the receiver as well as the full trace+ log are attached. > Please let me know should you need some additional information. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5786) Memory leak in qpid-java-broker-0.26.tar.gz
[ https://issues.apache.org/jira/browse/QPID-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126942#comment-14126942 ] Bobby Flitter commented on QPID-5786: - Thanks. I already thought this is the most problematic exchange / queue. There is one process in the test environment that collects all log messages of the other processes via AMQP and writes them to a log file on the disk. Could you be so kind to write the query statement how to find the exchange name from the queue ? Meanwhile I can see a situation at the web interface where the exchange.pte.log does not consume messages fast enough. Size: 220367 msgs (44.1 MB) Pre-fetched: 1 msgs (244 B) Inbound:1112 msg/s (228 KB/s) Outbound:691 msg/s (141 KB/s) > Memory leak in qpid-java-broker-0.26.tar.gz > --- > > Key: QPID-5786 > URL: https://issues.apache.org/jira/browse/QPID-5786 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.26 > Environment: Linux Mint 15 (64 Bit) - any Linux version should do > Java // OpenJDK Runtime Environment (IcedTea 2.4.4) > also tested with Java(TM) SE Runtime Environment (build 1.6.0_26-b03) > Ruby 1.8.7 > Ruby Bunny Gem 1.2.2 >Reporter: Bobby Flitter > Attachments: amqp_bunny_qpid.pcap > > > When using the hello bunny example program from Ruby together with Apache > qpid server the memory consumption of qpid seems to grow continuously. > Steps to reproduce the problem in Linux: > wget > http://ftp-stud.hs-esslingen.de/pub/Mirrors/ftp.apache.org/dist/qpid/0.26/qpid-java-broker-0.26.tar.gz > tar xzvf qpid-java-broker-0.26.tar.gz > cd qpid-broker-0.26/bin/ > ./qpid-server > - in a new terminal > - meanwhile bunny 1.2.2. is available > - install ruby amqp bunny > sudo gem install bunny > - download hello bunny example > wget http://pastebin.com/raw.php?i=f6MesMCZ -O hello_bunny.rb > while true; do ruby hello_bunny.rb ; done > - in another terminal: > while true; do grep "^VmRSS" /proc/$(pgrep -f qpid)/status ; sleep 1;done > - memory consumption of java qpid is growing continuously until > OutOfMemoryError ends the server > Unhandled Exception java.lang.OutOfMemoryError: Java heap space in Thread > Thread-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5786) Memory leak in qpid-java-broker-0.26.tar.gz
[ https://issues.apache.org/jira/browse/QPID-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126869#comment-14126869 ] Rob Godfrey commented on QPID-5786: --- From the queue I got the bindings and the binding log subject gives: [vh(/default)/ex(direct/exchange.pte.log)/qu(tmp_58c26acf-f4be-40a8-b6a7-7b11a7cbd2f4)/rk()] So the exchange is exchange.pte.log Hope this helps, Rob > Memory leak in qpid-java-broker-0.26.tar.gz > --- > > Key: QPID-5786 > URL: https://issues.apache.org/jira/browse/QPID-5786 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.26 > Environment: Linux Mint 15 (64 Bit) - any Linux version should do > Java // OpenJDK Runtime Environment (IcedTea 2.4.4) > also tested with Java(TM) SE Runtime Environment (build 1.6.0_26-b03) > Ruby 1.8.7 > Ruby Bunny Gem 1.2.2 >Reporter: Bobby Flitter > Attachments: amqp_bunny_qpid.pcap > > > When using the hello bunny example program from Ruby together with Apache > qpid server the memory consumption of qpid seems to grow continuously. > Steps to reproduce the problem in Linux: > wget > http://ftp-stud.hs-esslingen.de/pub/Mirrors/ftp.apache.org/dist/qpid/0.26/qpid-java-broker-0.26.tar.gz > tar xzvf qpid-java-broker-0.26.tar.gz > cd qpid-broker-0.26/bin/ > ./qpid-server > - in a new terminal > - meanwhile bunny 1.2.2. is available > - install ruby amqp bunny > sudo gem install bunny > - download hello bunny example > wget http://pastebin.com/raw.php?i=f6MesMCZ -O hello_bunny.rb > while true; do ruby hello_bunny.rb ; done > - in another terminal: > while true; do grep "^VmRSS" /proc/$(pgrep -f qpid)/status ; sleep 1;done > - memory consumption of java qpid is growing continuously until > OutOfMemoryError ends the server > Unhandled Exception java.lang.OutOfMemoryError: Java heap space in Thread > Thread-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5786) Memory leak in qpid-java-broker-0.26.tar.gz
[ https://issues.apache.org/jira/browse/QPID-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126838#comment-14126838 ] Bobby Flitter commented on QPID-5786: - Rob, thanks for your analysis so far. I tried jhat - but it crashes. Therefore I used the Eclipse Memory Analyser. It can also run some of your queries with OQL. But not the ones with the memory address that you have above. When I look at the web interface of the qpid server I can see the bindings and consumers of the queue. Do you have any chance to get the bindings and consumers of the identified queue from the hprof file ? The exchange binding has a name. It would help me if I knew the name of the problematic exchange. Meanwhile I checked all queues via the web interface: Broker - virtual hosts - default - queues - tmp... But I see that they all have size 0 while the memory consumption of the qpid server rises: Size:0 msgs (0.00 B) Pre-fetched: 0 msgs (0.00 B) Inbound: 0 msg/s (2.58 B/s) Outbound:0 msg/s (2.58 B/s) > Memory leak in qpid-java-broker-0.26.tar.gz > --- > > Key: QPID-5786 > URL: https://issues.apache.org/jira/browse/QPID-5786 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.26 > Environment: Linux Mint 15 (64 Bit) - any Linux version should do > Java // OpenJDK Runtime Environment (IcedTea 2.4.4) > also tested with Java(TM) SE Runtime Environment (build 1.6.0_26-b03) > Ruby 1.8.7 > Ruby Bunny Gem 1.2.2 >Reporter: Bobby Flitter > Attachments: amqp_bunny_qpid.pcap > > > When using the hello bunny example program from Ruby together with Apache > qpid server the memory consumption of qpid seems to grow continuously. > Steps to reproduce the problem in Linux: > wget > http://ftp-stud.hs-esslingen.de/pub/Mirrors/ftp.apache.org/dist/qpid/0.26/qpid-java-broker-0.26.tar.gz > tar xzvf qpid-java-broker-0.26.tar.gz > cd qpid-broker-0.26/bin/ > ./qpid-server > - in a new terminal > - meanwhile bunny 1.2.2. is available > - install ruby amqp bunny > sudo gem install bunny > - download hello bunny example > wget http://pastebin.com/raw.php?i=f6MesMCZ -O hello_bunny.rb > while true; do ruby hello_bunny.rb ; done > - in another terminal: > while true; do grep "^VmRSS" /proc/$(pgrep -f qpid)/status ; sleep 1;done > - memory consumption of java qpid is growing continuously until > OutOfMemoryError ends the server > Unhandled Exception java.lang.OutOfMemoryError: Java heap space in Thread > Thread-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5786) Memory leak in qpid-java-broker-0.26.tar.gz
[ https://issues.apache.org/jira/browse/QPID-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126792#comment-14126792 ] Rob Godfrey commented on QPID-5786: --- And doing some more querying of the heap... we can find the oldest and newest messages on the queue and their arrival times: oldest message Mon, 08 Sep 2014 11:42:02 GMT newest message Mon, 08 Sep 2014 11:54:42 GMT We can also navigate down to the connection and look at when the last write on the connection took place: last write time Mon, 08 Sep 2014 11:54:53 GMT and then looking at the statistics counters on the connection object you can see Messages Delivered By the Broker: last statistics Mon, 08 Sep 2014 11:54:52 GMT Peak message throughput : 1529 msg/s Current message throughput: 2 msg/s So... All the evidence is pointing to the broker just getting to the point where (because the consumer was slower than the producer) the queue grew too large, causing the broker to run out of heap, and then enter a GC loop slowing it down further (throughput of 2 msg/s) until eventually it died through heap exhaustion. As above, enabling flow control limits on queues would potentially be one solution (presuming the client respects the flow controlling requests), other than that, 0.30 will help a bit... Or you could introduce a TTL onto the messages if it is not vital that all messages get through... but ultimately any scenario where you have a producer that is outpacing the consumer will eventually cause a broker to die as they cannot provide infinite storage. > Memory leak in qpid-java-broker-0.26.tar.gz > --- > > Key: QPID-5786 > URL: https://issues.apache.org/jira/browse/QPID-5786 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.26 > Environment: Linux Mint 15 (64 Bit) - any Linux version should do > Java // OpenJDK Runtime Environment (IcedTea 2.4.4) > also tested with Java(TM) SE Runtime Environment (build 1.6.0_26-b03) > Ruby 1.8.7 > Ruby Bunny Gem 1.2.2 >Reporter: Bobby Flitter > Attachments: amqp_bunny_qpid.pcap > > > When using the hello bunny example program from Ruby together with Apache > qpid server the memory consumption of qpid seems to grow continuously. > Steps to reproduce the problem in Linux: > wget > http://ftp-stud.hs-esslingen.de/pub/Mirrors/ftp.apache.org/dist/qpid/0.26/qpid-java-broker-0.26.tar.gz > tar xzvf qpid-java-broker-0.26.tar.gz > cd qpid-broker-0.26/bin/ > ./qpid-server > - in a new terminal > - meanwhile bunny 1.2.2. is available > - install ruby amqp bunny > sudo gem install bunny > - download hello bunny example > wget http://pastebin.com/raw.php?i=f6MesMCZ -O hello_bunny.rb > while true; do ruby hello_bunny.rb ; done > - in another terminal: > while true; do grep "^VmRSS" /proc/$(pgrep -f qpid)/status ; sleep 1;done > - memory consumption of java qpid is growing continuously until > OutOfMemoryError ends the server > Unhandled Exception java.lang.OutOfMemoryError: Java heap space in Thread > Thread-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6074) BDB HA VHN to use context variables rather than system property to control timeouts etc
[
https://issues.apache.org/jira/browse/QPID-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126764#comment-14126764
]
Alex Rudyy commented on QPID-6074:
--
Keith,
I would like to clarify why BDB HA VHN context variables (
"qpid.bdb.ha.master_transfer_interval", "qpid.bdb.ha.db_ping_socket_timeout",
"qpid.bdb.ha.remote_node_monitor_interval",
"qpid.bdb.ha.environment_restart_retry_limit",
"qpid.bdb.ha.executor_shutdown_timeout") have not been declared on BDB HA VHN?
I would expect them do be defined on BDB HA VHN interface using annotations
similar to other context variables, for example
{code}
String MASTER_TRANSFER_INTERVAL = ""qpid.bdb.ha.master_transfer_interval";
@ManagedContextDefault(name =MASTER_TRANSFER_INTERVAL)
int DEFAULT_MASTER_TRANSFER_TIMEOUT = 1000 * 60;
{code}
The way you implemented context variable defaults seem inconsistent with other
code
> BDB HA VHN to use context variables rather than system property to control
> timeouts etc
> ---
>
> Key: QPID-6074
> URL: https://issues.apache.org/jira/browse/QPID-6074
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
>Reporter: Keith Wall
>Assignee: Alex Rudyy
> Fix For: 0.31
>
>
> The BDB HA VHN implementation currently uses system properties for a number
> of timeout values, polling frequencies and retry intervals. These should be
> converted to context variables.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-6071) Removing designated primary/electable group override from a node in a group without quorum should cause it to return to WAITING
[ https://issues.apache.org/jira/browse/QPID-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-6071. -- Resolution: Fixed The changes look good to me > Removing designated primary/electable group override from a node in a group > without quorum should cause it to return to WAITING > --- > > Key: QPID-6071 > URL: https://issues.apache.org/jira/browse/QPID-6071 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.31 >Reporter: Keith Wall >Assignee: Alex Rudyy > Fix For: 0.31 > > > I have a two node group with nodes A and B. > # Shutdown node B, > # Remaining node (A) correctly transitions into the WAITING role as it > automatically detects the loss of quorum. > # Designate Primary (A) > # Node A automatically transitions to MASTER. > # Remove Primary Designation from A > # Expected behaviour : node automatically transitions back to WAITING, actual > behaviour: node remains MASTER until next user transaction fails. > There is an equivalent defect in a multi node group when electable group > override is mutated back to Majority. > The defect will mean that the VH continues to accept connections and > non-persistent transactions until the first persistent transaction arrives. > At that point the node will transition correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
