Re: [Dispatch 1.2.0] Wrong download link in the web page ?

Hello, It could also be a proxy issue 😉 I had it before when I was in my previous company and we were behind a proxy. Regards, Adel From: Ken Giusti Sent: Thursday, July 5, 2018 3:50 PM To: users Subject: Re: [Dispatch 1.2.0] Wrong download link in the web page

Re: Welcome Chris Richardson as an Apache Qpid committer

Welcome Chris!! From: Chris Richardson Sent: Wednesday, November 15, 2017 3:20:43 PM To: users Subject: Re: Welcome Chris Richardson as an Apache Qpid committer Thanks all! I do promise to execute this office to the best of my ability etc etc so help me Qpid. On

Re: Proposed update to minimum tool requirements for proton-c

+1 for the propositions. How about a 1.0 release? Is proton mature enough for a major release? Adel From: Robbie Gemmell Sent: Friday, October 20, 2017 11:22:41 PM To: users@qpid.apache.org Subject: Re: Proposed update to minimum tool requirements for proton-c O

Re: [VOTE] Release Apache Qpid Proton 0.18.0

particularly once other issues > and fixes have inevitably appeared. > > Robbie > > On 19 October 2017 at 18:36, Adel Boutros wrote: >> If the fix is quick, I prefer to have it natively in 0.18.0. Otherwise, I >> will have to have a local patch to disable it and thu

Re: [VOTE] Release Apache Qpid Proton 0.18.0

I've seen so far, but there may be others. Most "normal" network failures (bad address, nobody listening on port, no route etc.) are not detected immediately and are handled correctly. On Fri, Oct 20, 2017 at 8:35 AM, Adel Boutros wrote: > Hello, > > I am wondering if a

Re: [Qpid Java Broker 6.1.4] JDBC fixes

Thanks Keith! Regards, Adel From: Keith W Sent: Friday, October 20, 2017 9:57:56 AM To: users@qpid.apache.org Subject: Re: [Qpid Java Broker 6.1.4] JDBC fixes Hi Adel On 18 October 2017 at 11:39, Adel Boutros wrote: > Hello guys, > > > While

Re: [VOTE] Release Apache Qpid Proton 0.18.0

Hello, I am wondering if all those who casted the votes or will do so have tested the different proactor implementations? >From the voting replies this is not clear. In my case, I am being defaulted to the epoll as I haven't installed libuv yet. Regards, Adel Fr

Re: [VOTE] Release Apache Qpid Proton 0.18.0

@qpid.apache.org Subject: Re: [VOTE] Release Apache Qpid Proton 0.18.0 I can confirm the ipv6 problem, I've opened https://issues.apache.org/jira/browse/PROTON-1639 and I'm working on fixing it in case of respin. On Thu, Oct 19, 2017 at 5:19 PM, Adel Boutros wrote: > I have a patch for the

Re: [VOTE] Release Apache Qpid Proton 0.18.0

pt. Regards, Adel From: Andrew Stitcher Sent: Thursday, October 19, 2017 6:50:27 PM To: users@qpid.apache.org Subject: Re: [VOTE] Release Apache Qpid Proton 0.18.0 On Thu, 2017-10-19 at 16:40 +, Adel Boutros wrote: > Re-attaching the log as it seems the mailing server rejected the >

Re: [VOTE] Release Apache Qpid Proton 0.18.0

Re-attaching the log as it seems the mailing server rejected the first one. Adel From: Adel Boutros Sent: Thursday, October 19, 2017 6:38:58 PM To: users@qpid.apache.org Subject: Re: [VOTE] Release Apache Qpid Proton 0.18.0 Hello Andrew, Yes, we are using a

Re: [VOTE] Release Apache Qpid Proton 0.18.0

+, Adel Boutros wrote: > Hello Robbie, > > > It is GCC 4.9.2 on Red Hat Enterprise Linux Server release 6.4 Are you using a custom compiler? As far as I know RHEL6 has gcc 4.4.7. Andrew - To unsubscribe, e-mail: us

Re: [VOTE] Release Apache Qpid Proton 0.18.0

detail around e.g OS, compiler, etc, so that folks can better assess the issue, any fix needed, and whether it is sufficient reason to respin as opposed to say, a reason to do a 0.18.1. On 19 October 2017 at 16:53, Adel Boutros wrote: > Hello again, > > > I will have to vote -1 here.

Re: [VOTE] Release Apache Qpid Proton 0.18.0

: test_ssl(&t) 21: TEST: test_proactor_addr(&t) 21: TEST: test_parse_addr(&t) 21: TEST: test_netaddr(&t) 21: TEST: test_disconnect(&t) 21: TEST: test_abort(&t) 21: TEST: test_refuse(&t) 21: TEST: test_message_stream(&t) 21/25 Test #21: c-proactor-tests ..

Re: [VOTE] Release Apache Qpid Proton 0.18.0

/data/jenkins-slave/home/workspace/proton-acceptance/proton-workspace/qpid-proton-0.18.0-rc1/proton-c/src/ssl/openssl.c:1505: undefined reference to `pthread_once' collect2: error: ld returned 1 exit status Regards, Adel ____ From: Adel Boutros Sent: Thursday,

Re: [VOTE] Release Apache Qpid Proton 0.18.0

Hello, I am trying to build proton 0.18.0 but I am facing errors with ruby-gem. Do you know how I can deactivate this target? [ 5%] Generating qpid_proton-0.18.0.gem /usr/bin/gem:8:in `require': no such file to load -- rubygems (LoadError) from /usr/bin/gem:8 make[2]: *** [proton-c/bindings/r

Re: [Qpid Java Broker 6.1.4] Some expections are hidden

. On 16 October 2017 at 12:34, Keith W wrote: > Hi Adel > > Please raise a JIRA. Include a patch or pull request if you like. > I'll try to include in v7.0. > > cheers Keith > > On 16 October 2017 at 12:06, Adel Boutros wrote: >> No, this was the o

[Qpid Java Broker 6.1.4] JDBC fixes

Hello guys, While testing the tableNamePrefix, we noticed a bug and a very slow performance on Oracle Database. I have submitted 2 jiras one for each and a pull request on the master of qpid-broker-j. So I was wondering if they are accepted if it is possible to backport them to 6.1 branch a

Re: [Qpid Java Broker 6.1.4] Broker is ready even if an error is occuring on startup and failStartupWithErroredChild set to true

Subject: Re: [Qpid Java Broker 6.1.4] Broker is ready even if an error is occuring on startup and failStartupWithErroredChild set to true On 16 October 2017 at 13:08, Adel Boutros wrote: > Hello Rob, > > If a virtual host is not available, then all queues and persisted messages > a

Re: [Qpid Java Broker 6.1.4] Broker is ready even if an error is occuring on startup and failStartupWithErroredChild set to true

set to true Hi Adel, I think broker.failStartupWithErroredChild=true will only cause the broker to fail if a *direct* child of the broker fails to start, the vhost is a child of the vhostnode, so if the vhost node starts up, the broker doesn't fail. -- Rob On 16 October 2017 at 11:16,

Re: [Qpid Java Broker 6.1.4] Some expections are hidden

deliberate, it's a bug :-) It looks like this particular case has been this way since at least 2014... Have you found any other cases? -- Rob On 16 October 2017 at 11:22, Adel Boutros wrote: > Hello, > > > While using the Qpid Java Broker, I have noticed that sometimes th

[Qpid Java Broker 6.1.4] Some expections are hidden

Hello, While using the Qpid Java Broker, I have noticed that sometimes the causes of the exceptions are silenced and thus I don't know why my broker failed. I had to remote debug it to find out. I wanted to know if this was on purpose or not? You can check for example: GenericJDBCMessageStor

[Qpid Java Broker 6.1.4] Broker is ready even if an error is occuring on startup and failStartupWithErroredChild set to true

Hello, Using the Qpid Java Broker 6.1.4, I have noticed that even if i specify "set QPID_OPTS=-Dbroker.failStartupWithErroredChild=true" and my JDBC virtual host cannot start, then the broker is set to ready. Is this expected? 2017-10-16 11:11:02,520 ERROR [VirtualHostNode-default-Config]

Re: Consumer affinity (JMSXGroupID), AMQP 1.0

ues.apache.org/jira/browse/QPID-7937 > > On 29 September 2017 at 11:47, Rob Godfrey wrote: >> On 29 September 2017 at 10:35, Adel Boutros wrote: >> >>> Hello Rob, >>> >>> >>> I would like to give my opinion on this. >>> >>>

Re: Consumer affinity (JMSXGroupID), AMQP 1.0

Hello Rob, I would like to give my opinion on this. In our current use cases, we are configuring the brokers dynamically using the REST API. We would like to have this possibility in the use case of Olivier. Also, having to restart the virtual host is damaging the High Availability of the me

Re: Plans for Qpid Broker J v7.0

Hello Keith, Normally, with a major release, I could expect some broken APIs when developing code for an older version of the Qpid Broker such as REST API for communicating with the broker or any configuration related disruptive changes. Does the 7.0 version include any disruptive change? Or

Re: [Qpid Java Broker 6.0.4] [Linux] Stop script keeps trying to kill a dead broker

at 11:22, Adel Boutros wrote: > Hello Rudyy, > > > +1 for the enhancements 😊 > > > Regards, > > Adel > > > From: Oleksandr Rudyy > Sent: Tuesday, September 19, 2017 11:17:15 AM > To: users@qpid.apache.org > Subject: Re:

Re: Plans for the Qpid Dispatch Router 1.0.0

Hello Ted, A nice early Christmas gift for me would be https://issues.apache.org/jira/browse/DISPATCH-773 (You don't have to be that generous though if it is not possible). Regards, Adel From: Ted Ross Sent: Monday, September 18, 2017 10:08:18 PM To: users@

Re: [Qpid Java Broker 6.0.4] [Linux] Stop script keeps trying to kill a dead broker

Is this feature officially supported? > And one more question, why is the broker's qpid.stop script not using the > same graceful mechanism? > > Thanks, > Olivier > > -Original Message- > From: Adel Boutros [mailto:adelbout...@live.com] > Sent: jeudi 14 septe

Re: Does qpid-client-6.0.4 support AMQP 1.0 ?

Oops, I spoke too soon :( From: Adel Boutros Sent: Friday, September 15, 2017 12:25:49 PM To: users@qpid.apache.org Subject: Re: Does qpid-client-6.0.4 support AMQP 1.0 ? Hello, I agree the website page you reference to seems confusing especially that the

Re: Does qpid-client-6.0.4 support AMQP 1.0 ?

Hello, I agree the website page you reference to seems confusing especially that the client mentions Qpid JMS. From my experience, I confirm the Qpid clients (at least JMS) supports AMQP 1.0. We use it exclusively in 1.0 mode along with the Qpid Java Broker 6.0.4 (also only in AMQP 1.0) and i

Re: [Qpid Java Broker 6.0.4] [Linux] Stop script keeps trying to kill a dead broker

start). Kind Regards, Alex On 6 September 2017 at 17:21, Adel Boutros wrote: > Hello, > > > In one of our tests, we were having a random failure. It seems we cannot > stop a broker correctly. > > We have a started broker and we call "bin/qpid.stop $BROKER_PID" to stop &

[Qpid Java Broker 6.0.4] [Linux] Stop script keeps trying to kill a dead broker

Hello, In one of our tests, we were having a random failure. It seems we cannot stop a broker correctly. We have a started broker and we call "bin/qpid.stop $BROKER_PID" to stop it. It seems to work from the first time but maybe not fast enough because the script keeps trying to kill the brok

Re: Welcome Adel Boutros as an Apache Qpid committer

Thank you all! It has been a fun and exciting journey so far :) From: Ganesh Murthy Sent: Wednesday, August 9, 2017 3:13:31 PM To: users@qpid.apache.org Subject: Re: Welcome Adel Boutros as an Apache Qpid committer Adel, congrats and welcome. Looking forward to

Re: [Proton 0.16.0] [Dispatch Router 0.7.0] [Java Broker 6.0.4] [JMS 0.11.1] JMS sender's connection is being closed by the dispatch router

, 2017 10:32:25 PM To: users@qpid.apache.org Subject: Re: [Proton 0.16.0] [Dispatch Router 0.7.0] [Java Broker 6.0.4] [JMS 0.11.1] JMS sender's connection is being closed by the dispatch router On Wed, Aug 2, 2017 at 12:42 PM, Adel Boutros wrote: > Hello, > > > As stated in a s

[Proton-c C++ 0.16.0] [Solaris Sparc] [GCC 4.9.2] Assuming threads will propage exceptions

Hello, I hope you missed my mails about Solaris 😉 We are currently testing whether we can compile on Solaris using GCC 4.9.2. We were successful in doing so for Solaris x86 but we have hit a problem in Sparc. It seems related to certain assumptions made around how threads propagates excepti

Re: Reactor receiver stuck when transport is broken

Hello, I imagine you are talking about Qpid Proton's reactor? If that is the case, have you implemented the "onError" as well? Some errors go there. Also, the reactor will always be running until you close the connection in one of the callbacks; are you doing so? void on_transport_error(prot

Re: Dispatch Router throughput

Hello, I think it depends on how you are using the Dispatch Router. From Gordon's and Chuck's reply, they assumed you were talking about peer-to-peer communication using the Dispatch Router which is a very useful use case. However, if like us, you have an actual broker connected via the dispa

Re: Qpid High Availability

eady configured could you please send me the screen shot. [Inline image 1] On Tue, Jul 11, 2017 at 3:03 PM, Adel Boutros mailto:adelbout...@live.com>> wrote: Hello, You can find it on Oracle's website: http://www.oracle.com/technetwork/database/database-technologies/berkeleydb/d

Re: Qpid High Availability

Hello, You can find it on Oracle's website: http://www.oracle.com/technetwork/database/database-technologies/berkeleydb/downloads/index-098622.html Regards, Adel From: girish lc Sent: Tuesday, July 11, 2017 11:04:31 AM To: users@qpid.apache.org Subject: Re:

Re: [Dispatch Router] List of connected producers

Thank you both, I will try what you suggested. I was wondering why the phases are actually named "0" and "1" as this a bit confusing. Wouldn't a more meaningful string representation be better especially for the users? Adel From: Gordon Sim Sent: Wednesday

[Dispatch Router] List of connected producers

Hello, I was wondering if there was a way to get the list of producers (or clients in general) connected to a queue on the dispatch router? Context: We would like to block the deletion of a waypoint as long as someone might be using it. Regards, Adel Get Outlook for Android

Re: help building proton for windows

Hello Greg, Could you show an example of the errors? We were able to compile Proton-c and C++ bindings 0.17.0 on Windows Server 2012 but we might not all have the same configuration. Regards, Adel From: Greg Oliver Sent: Friday, June 23, 2017 1:12:47 AM To

Re: [DISCUSSION] Queue Reject Policy Behaviour

on a live queue should be very rare. Kind regards, Lorenz On Tue, 2017-06-13 at 10:15 +, Adel Boutros wrote: > Hello Lorenz, > > > In my opinion, it depends on the context and there is no general rule for > this. > > For example, if your queue has some sensitive data and

Re: [DISCUSSION] Queue Reject Policy Behaviour

Hello Lorenz, In my opinion, it depends on the context and there is no general rule for this. For example, if your queue has some sensitive data and your producers considers the messages available. So they will never send them back. If you delete the messages which overflow the queue, you will

Re: Dispatch router 2-phase start

ately thereafter and before the router could run thru the rest of the static configuration. Thanks. - Original Message - > From: "Jiri Danek" > To: "users" > Sent: Monday, May 15, 2017 6:21:01 AM > Subject: Re: Dispatch router 2-phase start > > On

Re: Dispatch router 2-phase start

start On Mon, May 15, 2017 at 12:00 PM, Adel Boutros wrote: > Hello Gordon, > > > With what you are proposing, the order of the configuration becomes > critical because if the public listener is configured before the connectors > and autolinks, I would have the same issue with the

Re: Dispatch router 2-phase start

router 2-phase start On 13/05/17 10:29, Adel Boutros wrote: > Hello, > > We have noticed a race conditon with the dispatch router's behavior. > If you have a producer and a consumer exchanging messages on a queue > configured on a broker and accessible via the router. The consumer

Dispatch router 2-phase start

Hello, We have noticed a race conditon with the dispatch router's behavior. If you have a producer and a consumer exchanging messages on a queue configured on a broker and accessible via the router. The consumer and producers are JMS clients configured with Failover options for retry. If the rou

Public CI

Hello, We are currently compiling internally Qpid components using Jenkins on Windows, Linux and Solaris. In order to ease the process, I was experimenting with public CIs and have noticed you are using Travis (For Linux) and Appveyor (For Windows). So I was wondering if you could share your

Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

. This PR passes on Travis as well as seen here - https://travis-ci.org/apache/qpid-dispatch/builds/218223226 Thanks. - Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Monday, April 3, 2017 12:57:37 PM > Subject: Re: Qpid Dispatch Router 0.8

Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

? As for the Solaris test failures, there seem to be a whole bunch of them. I have created a JIRA - https://issues.apache.org/jira/browse/DISPATCH-738 I am not sure we can get to them before the 0.8.0 release. Thanks. - Original Message - > From: "Adel Boutros" > To: users

Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

Small correction: We are using Proton 0.16.0 with only C++ and Python bindings activated. From: Adel Boutros Sent: Friday, March 31, 2017 9:55:32 AM To: users@qpid.apache.org Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 Hello Ganesh, Please

Re: [Proton C++ 0.16.0] Reconnect and reconnect timer

users@qpid.apache.org On Thu, 2017-03-30 at 07:51 +, Adel Boutros wrote: > Thank you Rob, > > > I actually got this exception while a proton client was trying to > connect to a broker shutting down. > > > From your answer, I conclude that if the below error is thrown, th

Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

problem. -Ted On 03/30/2017 11:30 AM, Adel Boutros wrote: > Hello Ted, > > > I thought the 0.8.0 release included the fixes to ignore IPv6 tests but it > doens't seem to be the case. Ganesh was working on fixing those. > > Do you confirm they are not included? &

Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

Hello Ted, I thought the 0.8.0 release included the fixes to ignore IPv6 tests but it doens't seem to be the case. Ganesh was working on fixing those. Do you confirm they are not included? (http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-s

Re: [Java Broker - 6.0.4] Dojo toolkit dependency

30, 2017 10:22:28 AM To: users@qpid.apache.org Subject: Re: [Java Broker - 6.0.4] Dojo toolkit dependency On 30 March 2017 at 08:49, Adel Boutros wrote: > Thank you Rob, > > > Actually, we were wondering about the "dojo-1.10.3-distribution.zip" > available under

Re: [Proton C++ 0.16.0] Reconnect and reconnect timer

tarted independently of the port listener, the fact that the port is up doesn't actually mean the virtual host has finished started. -- Rob On Wed, 29 Mar 2017 at 21:23, Adel Boutros wrote: > Thank you Alan, > > > As discussed with Andrew offline, we will develop our own reconnect >

Re: [Java Broker - 6.0.4] Dojo toolkit dependency

s for SHA-1 / SHA-256 if I remember correctly. (See https://tools.ietf.org/html/rfc5802 and https://tools.ietf.org/html/rfc7677 for details of the SCRAM-SHA* SASL mechanisms). Hope this helps, Rob On 29 March 2017 at 21:17, Adel Boutros wrote: > Hello, > > > While our legal team was r

Re: [Proton C++ 0.16.0] Reconnect and reconnect timer

Thank you Alan, As discussed with Andrew offline, we will develop our own reconnect strategy as we need it to handle all possible scenarios, examples: * Failure while establishing connection * Failure while sending a message * Failure while receiving a message and by failure we mean any fail

[Java Broker - 6.0.4] Dojo toolkit dependency

Hello, While our legal team was reviewing the Broker's packaged dependencies and their licenses, they had some questions regarding Dojo toolkit materials which I hope you can help me with: * Could you please list all cryptographic means contained in the dojo materials used? * Could you ple

Re: Qpid Dispatch Release Plans

Hello Ted, What about: * DISPATCH-627 * DISPATCH-624 +1 for release model. Regards, Adel From: Ted Ross Sent: Wednesday, March 22, 2017 2:43:42 PM To: users@qpid.apache.org Subject: Qpid Dispatch Release Plans A couple of topics for discussion: Qpid Dispatch

Re: Corrupt artifacts on Qpid release web page

web page On Mon, Mar 20, 2017 at 6:26 AM, Rob Godfrey wrote: > On 20 March 2017 at 14:23, Adel Boutros wrote: > > > Hello Rob, > > > > > > I just saw your mail and I confirm what you propose works correctly. I > > opened your link via chrome and it do

Re: Corrupt artifacts on Qpid release web page

eb page On 20 March 2017 at 14:23, Adel Boutros wrote: > Hello Rob, > > > I just saw your mail and I confirm what you propose works correctly. I > opened your link via chrome and it downloaded the correct package this time. > > > Please note this is the case for all the art

Re: Corrupt artifacts on Qpid release web page

downloaded > to see whether it is a html page or a binary (probably gz)? > For example opening it in a text editor. > > In case it is as I suspect the html page you could try using > cURL's -L switch to make it follow redirects. > > Kind regards, > Lorenz > > >

Re: Corrupt artifacts on Qpid release web page

case, did you check the content of the thing you downloaded to see whether it is a html page or a binary (probably gz)? For example opening it in a text editor. In case it is as I suspect the html page you could try using cURL's -L switch to make it follow redirects. Kind regards, Lorenz On

Re: Corrupt artifacts on Qpid release web page

tifacts on Qpid release web page Hello Adel, That is not the link to the actual file. There is one more level of indirection. You are downloading a html page. Kind regards, Lorenz On 20/03/17 09:37, Adel Boutros wrote: > Hello Lorenz, > > > I tried on Windows and > Linux&

Re: Corrupt artifacts on Qpid release web page

Hello Rob, Lorenz, When you hover on any of the links under "download" section on https://qpid.apache.org/releases/qpid-java-6.1.1/index.html, you got the below link which I am trying to download. On windows, I click on the link and it is automatically downloaded. So I am not explicitly downloadin

Re: [Qpid Broker - 6.0.4] Junit testable?

bject: Re: [Qpid Broker - 6.0.4] Junit testable? On Fri, 17 Mar 2017 at 16:10, Adel Boutros wrote: > Indeed, most users will most probably inject a JMS connection using Spring > annotations. So testing it against an easy to embedd broker would be highly > appreciated because Spring alre

Re: Corrupt artifacts on Qpid release web page

he source bundle. With which artefacts do you experience problems specifically? What tools are you using to extract the files? Windows, Linux? Kind regards, Lorenz On 20/03/17 09:05, Adel Boutros wrote: > Hello, > > > It seems all ".tar" artifacts are corrupt when ac

Corrupt artifacts on Qpid release web page

Hello, It seems all ".tar" artifacts are corrupt when accessed from https://qpid.apache.org/releases. I can download all ".tar.gz" and unzip them. However, I cannot extract the ".tar". Are you aware of such issue? Regards, Adel

Re: [Qpid Broker - 6.0.4] Junit testable?

agement. This will allow you to fully manage the Broker from an > AMQP messaging connection. You will be able to use this to fully > configure the Broker from say, a JMS connection. I expect this will > become our recommendation. > > Hope this helps. > > > &

Re: [Qpid Broker - 6.0.4] Junit testable?

Hello Robbie, Can you please provide a simple example? Regards, Adel From: Robbie Gemmell Sent: Friday, March 17, 2017 12:57:59 PM To: users@qpid.apache.org Subject: Re: [Qpid Broker - 6.0.4] Junit testable? On 16 March 2017 at 18:01, Adel Boutros wrote

[Qpid Broker - 6.0.4] Junit testable?

Hello, As we are currently deploying a messaging solution based on the Java Broker, we have tried to start a broker from a Junit test and it is not very straightforward as the configuration part is a bit difficult. Of course here we are talking about Component Based Testing and Integration Tes

Re: [Java Broker] Port 0 range

Thanks Rob for the answer! From: Rob Godfrey Sent: Wednesday, March 15, 2017 2:39:46 PM To: users@qpid.apache.org Subject: Re: [Java Broker] Port 0 range On 14 March 2017 at 17:47, Adel Boutros wrote: > Hello Rob, > > > I think I wasn't clear

Re: [qpid-proton-cpp] default_container does not implement thread safety at all?

Hello, As Alan said, we have for example "abused" the schedule in C++. Today we run the container on another thread and we have a shared queue between the container threads and the other threads. We call schedule very frequently with a delay of 0. Whenever the container thread wakes, it checks

Re: [Java Broker] Port 0 range

est_anon_port tcp_largest_anon_port On 14 March 2017 at 16:56, Adel Boutros wrote: > Hello, > > > We are asked to deploy broker on random ports. So we thought about using > Port 0 and let the Broker find available ports. > > This works as expected however we have a concern

[Java Broker] Port 0 range

Hello, We are asked to deploy broker on random ports. So we thought about using Port 0 and let the Broker find available ports. This works as expected however we have a concern with the port range. It seems by default Java will take any port outside the well known ports and assign it. Howeve

Re: [Qpid Dispatch - 0.7.0] Random failure on unit test "system_tests_link_routes" on Linux

system_test.py which will default workerThreads to 4. Thanks for bringing this to our attention. Thanks. - Original Message ----- > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Thursday, March 2, 2017 10:48:04 AM > Subject: Re: [Qpid Dispatch - 0.7.0] Random fa

Re: [Qpid Dispatch - 0.7.0] Random failure on unit test "system_tests_link_routes" on Linux

reproduce your problem locally. I will keep you posted on my findings. Thanks. - Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Wednesday, March 1, 2017 3:11:59 PM > Subject: Re: [Qpid Dispatch - 0.7.0] Random failure on unit test

Re: [Qpid Dispatch - 0.7.0] Random failure on unit test "system_tests_link_routes" on Linux

Hello Ganesh, It seems that "zip" files are not allowed and thus my mail is never getting delivered. You can get it from here: http://www.filedropper.com/test_210 Regards, Adel ____ From: Adel Boutros Sent: Wednesday, March 1, 2017 9:09:29 PM

Re: [Qpid Dispatch - 0.7.0] Random failure on unit test "system_tests_link_routes" on Linux

Hello Ganesh, Did you have any luck with what I sent you? Regards, Adel From: Adel Boutros Sent: Wednesday, March 1, 2017 9:56:44 AM To: users@qpid.apache.org Subject: Re: [Qpid Dispatch - 0.7.0] Random failure on unit test "system_tests_link_route

Re: [Qpid Dispatch - 0.7.0] Random failure on unit test "system_tests_link_routes" on Linux

kRouteTest.test_www_drain_support_all_messages" Thanks. - Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Tuesday, February 28, 2017 10:20:42 AM > Subject: Re: [Qpid Dispatch - 0.7.0] Random failure on unit test > "system_tests_lin

Re: [Qpid Dispatch - 0.7.0] Random failure on unit test "system_tests_link_routes" on Linux

till fails randomly? Thanks. - Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Tuesday, February 28, 2017 9:00:36 AM > Subject: Re: [Qpid Dispatch - 0.7.0] Random failure on unit test > "system_tests_link_routes" on Linux

Re: Patch + jira vs pull request

ply looks like Travis was running at full capacity for Apache. It should come thru as soon as the backlog is cleared. Thanks. - Original Message ----- > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Tuesday, February 28, 2017 9:10:26 AM > Subject: Re: Patch + jira

Re: Patch + jira vs pull request

gt;> Also the GitHub mirror is treated as read-only. And it is quite possible >>>> that pull request might go unnoticed. >>>> So, for the Qpid broker for Java component I would recommend for the time >>>> being to use JIRA/patches/email. >>>> >&g

Re: [Qpid Dispatch - 0.7.0] Random failure on unit test "system_tests_link_routes" on Linux

ures=1) 1/1 Test #13: system_tests_link_routes .***Failed 110.16 sec Regards, Adel ________ From: Adel Boutros Sent: Tuesday, February 28, 2017 2:47:16 PM To: users@qpid.apache.org Subject: [Qpid Dispatch - 0.7.0] Random failure on unit test "system_tests_link_routes"

[Qpid Dispatch - 0.7.0] Random failure on unit test "system_tests_link_routes" on Linux

Hello, I noticed a random issue with the Dispatch Router 0.7.0 which has a random failure in the test "system_tests_link_routes". I launch the same test 10 times, it fails randomly (Failure occurs at the 4th or 5th run) but always with a similar error. It seems the timeout of 5 milliseconds i

Re: [Qpid Dispatch] Message States on Web Management Console of Qpid Java Broker

of its in-flight deliveries will be released to the broker and held there until another consumer appears. -Ted On 02/24/2017 10:58 AM, Adel Boutros wrote: > That's perfectly clear! In our use cases, the default behavior will be enough > for now. &

Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms

mer = managementSession.createConsumer(temporaryQueue); On 22 February 2017 at 11:33, Adel Boutros wrote: > Hello guys, > > > My basic JMS API is almost ready. I will share it with you soon to have your > feedback. > > > However, I tried one last thing by get

Re: [Qpid Dispatch] Message States on Web Management Console of Qpid Java Broker

wever. It would only be useful if there were consumers on the broker that access the broker directly and not through the router network. If all the consumers access the broker through the routers, the current behavior is more efficient. -Ted On 02/24/2017 09:01 AM, Adel Boutros wrote: > Than

Re: [Qpid Dispatch] Message States on Web Management Console of Qpid Java Broker

t;? Regards, Adel From: Ted Ross Sent: Thursday, February 23, 2017 9:48:32 PM To: users@qpid.apache.org Subject: Re: [Qpid Dispatch] Message States on Web Management Console of Qpid Java Broker On 02/23/2017 05:52 PM, Adel Boutros wrote: > Hello Ted, > > > What we tested

Re: [Qpid Dispatch] Message States on Web Management Console of Qpid Java Broker

Hello Ted, What we tested shows that once credit has been made available to the dispatch router, it remains even if no more consumers are connected to it. So as Anouchka said any new message sent to the broker is being taken by the dispatch router which has no consumer. So no other valid consu

Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms

- Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Wednesday, February 22, 2017 10:58:42 AM > Subject: Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms > > Hello, > > > One more issue: I am trying to replicate a "

Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms

resultObject = (Map) replyMessage.getObject(); for (Map.Entry entry : resultObject.entrySet()) { System.out.println(entry.getKey() + ": " + entry.getValue()); } managementConnection.close(); Regards, Adel From: Adel Boutros Sent: Wednesday, February 22, 2017 12:33:32 PM

Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms

4:46:59 PM To: users@qpid.apache.org Subject: Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms On 15 February 2017 at 16:07, Robbie Gemmell wrote: > On 15 February 2017 at 14:15, Adel Boutros wrote: > > Hello guys, > > > > > > Based on the discussion, we are

Re: [Dispatch Router] Unexpected behavior when starting the same dispatch router twice

router twice On Tue, 2017-02-14 at 20:35 +, Adel Boutros wrote: > Hello, > > > Was anyone able to take a look at the submitted patches? I am just about to. Have been working on the proton side and on other stuff lately but am going back to dispatch now. I will try to ensure that your

Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms

urrent failure and having it throw an > >>> aexception from createTemporaryQueue is simple enough. > >>> > >>> Hacking the client to use a dynamic recieving link instead, an address > >>> was returned by Dispatch in the attach response as ex

Re: [Dispatch Router] Unexpected behavior when starting the same dispatch router twice

Hello, Was anyone able to take a look at the submitted patches? Regards, Adel From: Adel Boutros Sent: Thursday, February 2, 2017 4:24:30 PM To: users@qpid.apache.org Subject: Re: [Dispatch Router] Unexpected behavior when starting the same dispatch router

Re: [VOTE] Release Qpid Proton 0.17.0

Symbolic +1 Compiled Proton + unit tests on Linux (GCC 4.9.1) Compiled Proton + unit tests on Windows (Visual Studio 2013) Compiled Proton + unit tests on Solaris x86 (SunStudio 12.1) Compiled Proton + unit tests on Solaris Sparc (SunStudio 12.1) Compiled Qpid Dispatch 0.7.0 + unit tests (Wit

Re: [Qpid Proton] How mandatory is Cyrus for SASL

ndatory is Cyrus for SASL On Thu, 2017-02-02 at 19:41 +0000, Adel Boutros wrote: > Hello, > > > I was wondering if SASL would be completely disabled in Proton if > Cyrus was not found during compilation or is there an alternative > implementation? > > > Regards, > > A

  1   2   3   4   5   >