This is essentially the same as batched transactions, and this does usually
increase performance a fair amount (where you have enough messages of a
small enough size that performance isnt governed by available of messages
of network bandiwdth) because you performing fewer synchronous round trips
to
One thing to try would be using an alternative SLF4J binding and logging
implementation for the client itself (and anything else using SLF4J), such
as the JDK logging binding, while retaining use of Log4J for your JMS
appender and actual application.
Robbie
On 9 April 2014 14:02, Miguel Madinavei
Just bumping this thread again - does anyone have any objections... I'd
plan on moving forward with switching the builds to 1.7 sometime next
week if we haven't heard any by then
-- Rob
On 8 April 2014 00:02, Robbie Gemmell wrote:
> On 7 April 2014 19:30, Fraser Adams wrote:
>
> > I think tha
The recently-discovered "Heartbleed" security vulnerability
in OpenSSL may affect some users of qpid.
What is *not* affected:
* The qpid c++ broker does not use OpenSSL internally.
It uses NSS.
What may be affected:
* The native python qpid.messaging client.
It uses OpenSSL "
Den 09. april 2014 19:41, skrev Gordon Sim:
On 04/09/2014 03:28 PM, Chris Richardson wrote:
I've set this scenario up on my test system (I had to add "--argument
domain=BrokerB" to the "qpid-config add incoming|outgoing ..."
commands...)
Sorry!
and it looks promising, except if I understand
Hey smartdog it is *definitely* the cxx-devel that is needed. When I was
wondering why my system wasn't building this stuff I ended up tearing my
hair out for ages - which is why I modded the CMake to provide some
slightly better messages, but I still thought I was going mad 'cause I
was seeing
On 04/09/2014 03:28 PM, Chris Richardson wrote:
I've set this scenario up on my test system (I had to add "--argument
domain=BrokerB" to the "qpid-config add incoming|outgoing ..." commands...)
Sorry!
and it looks promising, except if I understand correctly there is no
queuing on the relaying
Hi Justin, currently a heads up rather than formal request for inclusion...
I have noticed a few packaging issues with the beta which need resolved,
and also some trivial inconsistencies in the Ant build as compared with the
upcoming maven build (as it exists on the 0.28 branch) that I would quite
On Thu, 2014-04-03 at 11:47 -0400, Kim van der Riet wrote:
> A recent update (r.1578899) introduced a bug into the store in which
> initializing a non-existent queue caused a segfualt. The fix is both
> obvious and trivial.
>
> JIRA: https://issues.apache.org/jira/browse/QPID-5651
I incorrectly u
Gordon,
Thanks. I'm trying to get trace logging enabled and/or a tcpdump. The
latter is probably problematic since the system is carrying sensitive data.
Bill
On Wed, Apr 9, 2014 at 11:27 AM, Gordon Sim wrote:
> On 04/09/2014 04:12 PM, Bill Freeman wrote:
>
>> Let me wool gather a bit furth
On 04/09/2014 04:12 PM, Bill Freeman wrote:
Let me wool gather a bit further.
Though logged by the broker, it sounds as though this must be a result of a
client action. Is it safe to assume that an error would have been reported
to the client? Or might there not have been a path to do so?
Ye
Let me wool gather a bit further.
Though logged by the broker, it sounds as though this must be a result of a
client action. Is it safe to assume that an error would have been reported
to the client? Or might there not have been a path to do so?
Bill
On Wed, Apr 9, 2014 at 10:29 AM, Bill Free
Gordon,
Thanks. We'll go about gathering more information as you suggest. (I
haven't been directly involved. I'm just the stuckee for all matter Qpid,
or so it seems.)
Bill
On Wed, Apr 9, 2014 at 10:28 AM, Gordon Sim wrote:
> On 04/09/2014 03:13 PM, Bill Freeman wrote:
>
>> We run a three
On 8 April 2014 15:41, Gordon Sim wrote:
>
>
>> We are particularly interested in your comment "...qpidd (which supports
>> establishing basic AMQP 1.0 links to/from other processes)..."; Chris've
>> tried things like adding a link from a broker to a router with
>> "qpid-route link add..." but t
On 04/09/2014 03:13 PM, Bill Freeman wrote:
We run a three node cluster, fed by federation links from non-clustered
brokers on what we call workflow servers. All C++ brokers (0.18,
probably). As near to simultaneously as we can tell (log has 1 second
resolution) we are seeing the following erro
We run a three node cluster, fed by federation links from non-clustered
brokers on what we call workflow servers. All C++ brokers (0.18,
probably). As near to simultaneously as we can tell (log has 1 second
resolution) we are seeing the following error on three (probably all of
the) workflow serv
+1 for releasing this. It has useful additions to 0.1 and getting it out
to those interested is valuable.
On 04/04/2014 08:24 PM, Ted Ross wrote:
The 0.2beta1 cut of Dispatch Router has been out for over a month and
has been tested by several people with no issues discovered. I'm
starting a vot
On Tue, 2014-04-08 at 14:49 -0700, smartdog wrote:
> Thanks for the reply.
>
> This is what I have.
> cmake ..
> -- Qpid proton found, amqp 1.0 support enabled
> -- Legacystore requires BerkeleyDB for C++ which is absent.
> -- Legacystore is excluded from build.
> -- Linearstore requires Berkeley
For the client we also use log4j.
how do you solved the problem? to prevent the same client generates problems
when writing to the log?
--
View this message in context:
http://qpid.2158936.n2.nabble.com/The-AMQConnection-class-fail-to-connect-when-use-in-log4j-appender-tp7606582p7606586.html
S
Hi Hari,
Thanks for the very detailed report! It looks like you are doing the
right things so I'm not sure why it is not working.
Try adding:
log-enable=debug+:HA
in your qpidd.conf. That may give a clue, or send me the log files &
I'll take a look.
I see you're using qpid 0.18, can you try i
Hi,
I noticed high consumer speedup (>10x) when I do not acknowledge individual
messages but bunch of them at once. I use client acknowledge mode as in the
case of failure to correctly process the message I may lose it. Seeing message
more than once is not a (big) problem. Currently I consume w
What SLF4J logging implementation are you using for the client itself?
We typically use log4j also, which could cause initialisation problems in
this situation due to the client attempting to log during the connection
creation, which will need log4j to have initialised your appender that
requires
Hello everyone.
I have a problem when trying to connect to Qpid server, the class
AMQConnection fails giving a timeout error, this only happens if I include
this code in a log4j appender, if I put the same code outside the appender
the connection works well.
the goal is to write all the log4j me
23 matches
Mail list logo
