[qpid java broker 6.1.x] enqueue/dequeue over HTTP?

I am going through the HTTP API documentation and I just want to confirm what I am seeing. Is there a portion of the API to enqueue and dequeue messages via HTTP? I was hoping for some REST api like Google's TaskQueues that inc

QPID C++ Broker MALLOC_ARENA_MAX

Hi, Been a while since I last posted anything to the QPID newsgroup, mainly due to the excellent reliability of the QPID C++ broker, keep up the good work. But I am seeing a strange issue at a clients site that i thought I would share with the community. A client is running a QPID C++ Bro

Re: [HEADS UP] qpid-cpp 1.37.0

- Original Message - > From: "Robbie Gemmell" > To: users@qpid.apache.org > Sent: Friday, March 17, 2017 11:08:20 AM > Subject: Re: [HEADS UP] qpid-cpp 1.37.0 > > I'm probably not going to get this started this week after all, > https://issues.apache.org/jira/browse/QPID-7713 was notice

Re: Corrupt artifacts on Qpid release web page

On Mon, Mar 20, 2017 at 6:59 AM, Adel Boutros wrote: > Could the issue be I am behind a proxy? > Yeah, that could definitely do it. The lua closer script uses a path that looks like just another file. If the proxy isn't forwarding the ultimate target's content type, it would guess wrong in the

Re: Corrupt artifacts on Qpid release 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 downloaded the correct package this > time. > > > > > >

Re: Corrupt artifacts on Qpid release web page

Could the issue be I am behind a proxy? However, I will not be able to test otherwise before tonight. Just to summarize with my Chrome or Firexfox: * corrupt: http://www.apache.org/dyn/closer.lua/qpid/java/6.1.1/qpid-java-6.1.1.tar.gz * works: http://www.apache.org/dyn/closer.cgi?filename=q

Re: Corrupt artifacts on Qpid release web page

nope - I went to http://www.apache.org/dyn/closer.lua/qpid/java/6.1.1/ qpid-java-6.1.1.tar.gz I get no auto download in either chrome or firefox -- Rob On 20 March 2017 at 14:31, Adel Boutros wrote: > It seems mails have a maximum length for a line after which the line is > split in two. You w

Re: Corrupt artifacts on Qpid release web page

On 20/03/17 13:31, Adel Boutros wrote: It seems mails have a maximum length for a line after which the line is split in two. You were able to see a download page, because you opened a part of the URL I sent due to that. You went to "http://www.apache.org/dyn/closer.lua/qpid/java/6.1.1/"; ins

Re: Corrupt artifacts on Qpid release web page

It seems mails have a maximum length for a line after which the line is split in two. You were able to see a download page, because you opened a part of the URL I sent due to that. You went to "http://www.apache.org/dyn/closer.lua/qpid/java/6.1.1/"; instead of "http://www.apache.org/dyn/close

Re: Corrupt artifacts on Qpid release web 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 artifacts proposed on the website.

Re: Corrupt artifacts on Qpid release web page

On 20 March 2017 at 14:20, Adel Boutros wrote: > Ok, so here is what I found: > > > The ".tar.gz" seems to be correct when downloaded by direct click on the > web page. However, when I extract it using B1 archiver, the ".tar" is > indeed a web page html. > > > ".tar.gz" (opened in notepad++) > >

Re: Corrupt artifacts on Qpid release web page

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 artifacts proposed on the website. So are you going to fix them all? Regards, Adel _

Re: Corrupt artifacts on Qpid release web page

Ok, so here is what I found: The ".tar.gz" seems to be correct when downloaded by direct click on the web page. However, when I extract it using B1 archiver, the ".tar" is indeed a web page html. ".tar.gz" (opened in notepad++) ‹ Í\{sÛ8’ÿÛúX¥&NfLÒo'Ž­)ÇÎõÇy67uu5‘ …„$ Ôc¯æ»_7

Re: Corrupt artifacts on Qpid release web page

So, after little bit of digging around [1], a URL of the form http://www.apache.org/dyn/closer.cgi?filename=&action=download will automatically download from the suggested mirror, so in Adel's example above: curl -O ' http://www.apache.org/dyn/closer.cgi?filename=qpid/java/6.1.1/qpid-java-6.1.1.ta

Re: Corrupt artifacts on Qpid release web page

Correcting myself: curl -L -o qpid-java-6.1.1.tar.gz 'http://www.apache.org/dyn/ > closer.cgi?filename=qpid/java/6.1.1/qpid-java-6.1.1.tar.gz&action=download > ' > -- Rob > On 20 March 2017 at 13:43, Lorenz Quack wrote: > >> Hello Adel, >> >> I have problems reproducing. On both windows (IE &

Re: Corrupt artifacts on Qpid release web page

Hello Adel, I have problems reproducing. On both windows (IE & Chrome) and Linux (Firefox) the download does not start automatically. In any 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 ed

Re: [Qpid Broker - 6.0.4] Junit testable?

On 20 March 2017 at 11:30, Adel Boutros wrote: > Hello Rob, > > > We have many types of testing. Some of them do not require testing > administration. So queues could be static at the start of the tests. > > In that case, loading JSON from memory would solve the issue for these > tests. > > Howev

Re: [DISCUSS] Drop 0-10 based JCA/RA artefacts from Qpid JMS 0-x Client.

+1. Thanks for raising this, Keith. On Sun, Mar 19, 2017 at 3:54 PM, Keith W wrote: > Hi all, > > I'd like to propose that we drop the AMQP 0-10 based JCA (J2EE > Connector Architecture) and RA (Resource Adaptor) artefacts from the > next major Qpid JMS 0-x Client release (6.3.0). > > The artef

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 downl

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?

Hello Rob, We have many types of testing. Some of them do not require testing administration. So queues could be static at the start of the tests. In that case, loading JSON from memory would solve the issue for these tests. However, we would need to wrap this in Java to allow the users writin

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 already provides a lot of helpers in testing. > > > The problem

Re: Corrupt artifacts 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

That isn't the URL for the archive... it's the URL for an HTML page which gives a list of suggested download locations. I'm not sure if there is a URL that will automatically redirect to the closest mirror... anyone know better? -- Rob On Mon, 20 Mar 2017 at 10:38, Adel Boutros wrote: > Hello

Re: Corrupt artifacts on Qpid release web page

Hello Lorenz, I tried on Windows and Linux Linux: curl -O http://www.apache.org/dyn/closer.lua/qpid/java/6.1.1/qpid-java-6.1.1.tar.gz tar xfz qpid-java-6.1.1.tar.gz gzip: stdin: not in gzip format

Re: [DISCUSS] Drop 0-10 based JCA/RA artefacts from Qpid JMS 0-x Client.

+1 to drop jca/ra artefacts for AMQP 0.10 Kind Regards, Alex - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org

Re: Corrupt artifacts on Qpid release web page

Hi, I just tried the source bundle of the "Qpid for Java 6.1.1," release without issues. I used the command $ tar xfz qpid-java-6.1.1.tar.gz to unpack the source bundle. With which artefacts do you experience problems specifically? What tools are you using to extract the files? Windows, Linux?

Re: [DISCUSS] Drop 0-10 based JCA/RA artefacts from Qpid JMS 0-x Client.

On 19/03/17 22:54, Keith W wrote: Hi all, I'd like to propose that we drop the AMQP 0-10 based JCA (J2EE Connector Architecture) and RA (Resource Adaptor) artefacts from the next major Qpid JMS 0-x Client release (6.3.0). The artefacts in question have the following Maven coordinates: https://

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: [DISCUSS] Drop 0-10 based JCA/RA artefacts from Qpid JMS 0-x Client.

Hi, I have never touched those components. I haven't even looked into them. Taking into account what Keith said about the code being pretty much dead already I am +1 for the removal in the next *minor* [1] release 6.3.0. Kind regards, Lorenz [1] http://semver.org/ On 19/03/17 22:54, Keith W

Re: [DISCUSS] Drop 0-10 based JCA/RA artefacts from Qpid JMS 0-x Client.

+1 Any future JCA/RA work would want to be around the AMQP 1.0 client (once we have distributed transactions defined for AMQP 1.0). The current components have no-one maintaining them, and no-one (to my knowledge) who is familiar with the codebase. On 19 March 2017 at 23:54, Keith W wrote: > Hi