On 22 Sep 2015, at 1:15 AM, Graham Leggett wrote:
> In the example code for the async sending of messages below, the example is
> somewhat contrived in that it cleans up the pn_message structure after the
> whole messenger event loop has been shut down.
>
> Obviously in a real
Hi all,
I am trying to create a queue larger than will fit in available RAM (1TB in my
case). The messages on the queue will be modest in size (1MB each or so), the
key thing is that I need to be able to enqueue large quantities of data.
I am using qpid-cpp-server as supplied by EPEL, along wit
On 28 Mar 2016, at 4:59 PM, Andrew Stitcher wrote:
> On Sun, 2016-03-27 at 02:50 +0200, Graham Leggett wrote:
>> ... (A bunch of questions about proton's internal io routines.)
>
> The real question is what you are doing that you need to use
> pn_selectable at all?
Q
Hi,
According to the API at
https://qpid.apache.org/releases/qpid-proton-0.12.0/proton/c/api/group__selectable.html#ga18868416a68de0a8c51cfb664510edac
the pn_selectable_terminate() call is described as "Terminate a selectable”.
I am looking for a more specific description - would it be true to
On 07 Oct 2015, at 1:14 PM, Robbie Gemmell wrote:
> You didn't elaborate much on the setup being used or how it was
> configured. One question would be whether this was or without AMQP
> heartbeating/idle-timeout handling enabled on the connections? Clients
> and servers can for example each use
On Fri, 2015-10-02 at 10:51 -0400, Ted Ross wrote:
>> https://netprototalk.wordpress.com/2015/10/01/amqp-as-a-network-proto
>> col
>>
>> This is the first of a planned series of articles about AMQP, message
>> routing, and distributed-system use cases.
We tried to use AMQP v1.0 as a network prot
Hi all,
In the example code for the async sending of messages below, the example is
somewhat contrived in that it cleans up the pn_message structure after the
whole messenger event loop has been shut down.
Obviously in a real application you want to send many messages, and you need to
free tho
Hi all,
I am currently trying to integrate proton into an external event loop, and am
trying to work out the correct way to shut the event loop down gracefully. In
other words, you tell the event loop “time to stop”, and the event loop
finishes any upload it might be in the middle of until pn_m
On 15 Sep 2015, at 11:07 AM, Gordon Sim wrote:
> There is no standard way of doing this with AMQP 1.0 that will work for
> different brokers as yet.
>
> Though there is no simple API call, most brokers support management via
> messages sent/received to a specific address and.or via HTTP, so it
Hi all,
Before generating an expensive message and placing it on the queue, I would
like to know whether this message will fit onto that queue before going to the
trouble.
Is there an API call in proton with amqp 1.0 where you can check whether a
message of a given size will be accepted on a
Hi all,
I have a need to configure a very large queue that is able to store about 1
million messages of around 10kb each. The queue will be too big to fit into
RAM, and will need to spool to disk.
I have been struggling to configure the queue, as the queue seems to become
full after a few thou
Hi all,
I have been looking for an RPM of qpid v0.28 for RHEL6 and I have been
struggling, I can either get latest qpid on bleeding edge Fedora, or very old
qpid on RHEL6 (via MRG).
Does anyone have a link either to either a spec file or an SRPM for this?
Regards,
Graham
—
--
Hi all,
We are trying to use jms selectors, but hit the following message in the client:
09:32:49.559 [http-bio-8080-exec-6] DEBUG o.a.q.c.AMQConnectionDelegate_0_10 -
Server support for feature 'qpid.jms-selector' : false
Is there a way to turn this feature on in the c++ qpid broker?
Regards,
On 11 Oct 2013, at 9:38 AM, Robbie Gemmell wrote:
> You can control creation of queues through options in your destination
> strings, e.g instructing your producers/consumers/both to ensure the queue
> is created when they start up.
>
> The documentation for the address strings is at:
> http://q
On 10 Oct 2013, at 6:36 PM, Gordon Sim wrote:
> Yes it does, but the configuration is entirely different between these two
> clients. In particular I don't believe the 0.8/0-9-1/0-10 client uses 'amqps'
> to indicate ssl is to be used:
>
> http://qpid.apache.org/releases/qpid-0.24/programming/
On 10 Oct 2013, at 6:08 PM, Graham Leggett wrote:
> javax.jms.JMSException: Failed to parse entry: Not an AMQP URL
> amqps://amqp.sandbox.xxx.net:5671?jms.prefetchPolicy.queuePrefetch=1 due to :
> Not an AMQP URL:
> amqps://amqp.sandbox.xxx.net:5671?jms.prefetchPolicy.queuePrefetc
On 10 Oct 2013, at 4:57 PM, Gordon Sim wrote:
>> I have tried qpid-java-client (expecting it to work) and
>> qpid-java-amqp-1-0-client-jms (expecting it to give me a clear "protocol not
>> supported" error) v0.24 and v0.18, and all 4 fail with the same
>> "java.net.SocketException: Broken pipe
On 10 Oct 2013, at 4:08 PM, Gordon Sim wrote:
> Do you have the AMQP 1.0 plugin for the broker? It would be in the
> module-dir, the default for which should be indicated by /usr/sbin/qpidd
> --help
>
> My guess is that it is not there or is not being loaded. Without it qpidd
> only speaks 0-
On 10 Oct 2013, at 2:56 PM, Graham Leggett wrote:
> When the client tries the connect, the qpid-client v0.24 reports a
> "java.net.SocketException: Broken pipe" and then hangs solid, the hang solid
> most probably due to bug https://issues.apache.org/jira/browse/QPID-5113.
Hi all,
I am currently trying to swap in qpid-cpp v0.18 to replace an unreliable
activemq server installation. The connection is protected with client
certificates.
When the client tries the connect, the qpid-client v0.24 reports a
"java.net.SocketException: Broken pipe" and then hangs solid,
On 09 Oct 2013, at 3:27 PM, Graham Leggett wrote:
> Oct 9 13:15:29 localhost qpidd[17764]: 2013-10-09 13:15:29 error Failed to
> initialise SSL plugin: Failed to load certificate 'Server-Cert'
> (qpid/sys/ssl/SslSocket.cpp:184)
> "Server-Cert"
Hi all,
I am trying to configure an SSL enabled version of the qpid-cpp broker, and I
am struggling to get it to work. The broker starts and runs as follows:
qpidd17764 0.3 2.3 239728 11692 ?Ssl 13:15 0:00
/usr/sbin/qpidd --data-dir /var/lib/qpidd --daemon --ssl-cert-db
sql:/e
Hi all,
I have a client that makes once off connections to an activemq server over aqmp
to poll for messages from time to time (no long lived connections are used).
This works great for a period of time, until we suddenly get the unexpected
exception below printed to the console. At this point
Hi all,
I have just discovered I am affected by
https://issues.apache.org/jira/browse/QPID-5113# which is marked as fixed, is
there a plan for a release any time soon for qpid?
Regards,
Graham
--
-
To unsubscribe, e-mail: use
24 matches
Mail list logo
