Proposal: https://github.com/ssorj/qpid-svn-reorg
Previous discussion:
http://qpid.2158936.n2.nabble.com/Qpid-Subversion-reorganization-proposal-td7639094.html
Hi, everyone.
Since my last update, I have been trying to get the revamped C++ tests to
function under Windows. I've had only mixed succ
Offhand, there would be two reasons I can see...
1. The original poster didn't reply to the request to test the patch - Ken said
he couldn't test it
2. There was no JIRA entered for it with the patch included
-Steve
> -Original Message-
> From: Adel Boutros [mailto:adelbout...@live.com]
>From my point of view for a solution it should have been enough for the
clients to connect with max-frame-size accordingly set to 16K without
modifying the broker. However, this is not working (the client hangs if
sending messages larger than 16K).
Meanwhile I got it working:
Solution was:
1.) N
Meanwhile I got it working:
Solution was:
1.) No need to modify the client c++ api
2.) Don't set max-frame-size in the client (i.e. in connection options)
3.) Modify the java broker to have a max-frame-size of 0x3FFF instead of
0X
in org/apache/qpid/server/protocol/v0_10/ServerConnectionDeleg
Hello Raphael,
I am experiencing the same issue. I would like to know if you were able to
provide a workaround or a patch other than just commenting out the
"__thread"?
Regards,
Adel Boutros
www.murex.com
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Building-qpid-0-34-on
Great!
And I can test it once it is ready to confirm it works.
Adel
> Date: Wed, 6 Apr 2016 15:46:49 +0100
> Subject: Re: Unroutable messages in Java Qpid Broker 6.0.0
> From: rob.j.godf...@gmail.com
> To: users@qpid.apache.org
>
> Thanks!
>
> I'll raise a JIRA to cover this later this afternoon
Thanks!
I'll raise a JIRA to cover this later this afternoon, as well as some for
the configuration options we discussed earlier.
-- Rob
On 6 April 2016 at 15:20, Adel Boutros wrote:
> Here it is:
> https://qpid.apache.org/releases/qpid-java-6.0.0/java-broker/book/Java-Broker-Concepts-Exchang
Here it is:
https://qpid.apache.org/releases/qpid-java-6.0.0/java-broker/book/Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-UnroutableMessage
When you read the last section "Unrouteable Messages", it is only talking about
message being discarded on the broker and not that the
Can you point me at the section in the document you are referencing? (Most
of the documentation was written with earlier versions of the protocol in
mind so there may be a few places where the AMQP 1.0 behaviour differs from
that of earlier versions).
-- Rob
On 6 April 2016 at 14:26, Adel Boutro
Hello,
While building Qpid C++ Broker on SunOS, I encountered an error which has to do
with NSS specific code.
After checking this link
(http://qpid.2158936.n2.nabble.com/NSS-lt-v3-14-and-qpidc-broker-build-td7622467.html)
and applying the proposed patch, the file compiled correctly.
Is there a
Hello Rob,
Thank you for explanation, it makes complete sense and the proposed
configuration would indeed be highly valued.
So if I understand correctly, today there is no way to configure it. In that
case, a workaround would consist in setting for the exchange in question an
alternate exchange
Alex's point is that the Java Broker change shouldn't really be necessary
as if the client wants 16K, the fact that the Broker offers up to 64K
shouldn't matter - the client should just use 16K, and the broker will use
16K... however maybe there is some issue in the client that makes this
necessary
Hi,
thanks for your feedback. This already helps me a lot. Appearantly I was
doing the changes at the wrong positions (ServerDelegate.java instead of
ServerConnectionDelegate.java of the 0-10 protocol).
I'll redo my experminents. If it's not working I'll generate the
corresponding client / broker
Hello All,
After being directed towards the Proton-J reactor (away from the messenger), I
have been experimenting with reactor. I modified the supplied reactor examples
to send/recv to/from a queue on HornetQ fairly quickly.
However, I appear to be having less success implementing a heartbeat/k
Hi Adel,
As you have discovered, currently when the Java Broker receives a message
over AMQP 1.0 where the message cannot be routed to a queue, it rejects the
message (on the basis that the broker has not actually accepted the
transfer of responsibility as it will be discarding it). This is proba
15 matches
Mail list logo
