Re: [PROPOSAL] Completely remove Camel reference in the ActiveMQ broker

2022-08-05 Thread Jean-Baptiste Onofré
Hi, We have a consensus. So I will process creating a Jira and preparing a PR. Thanks all for your feedback. Regards JB On Thu, Aug 4, 2022 at 9:01 AM Jean-Baptiste Onofré wrote: > > Hi, > > We already removed the activemq-camel component from ActiveMQ distribution. > > However, we still have

Re: [PROPOSAL] Completely remove Camel reference in the ActiveMQ broker

2022-08-05 Thread Cesar Hernandez
+1 El jue, 4 ago 2022 a las 7:32, Matt Pavlovich () escribió: > +1 in favor of less dependencies in the bistro > > > On Aug 4, 2022, at 2:01 AM, Jean-Baptiste Onofré > wrote: > > > > Hi, > > > > We already removed the activemq-camel component from ActiveMQ > distribution. > > > > However, we sti

Re: A question about ClientMessage.setOutputStream()

2022-08-05 Thread Clebert Suconic
It’s been a while I wrote that. I remember there was a method for sabe that would block. saveSomethint I will check later. On Fri, Aug 5, 2022 at 12:04 PM Jan Šmucr wrote: > That’s an option, but given that it’s an AWS Lambda function, I’d prefer > to stream it, so that there’s no need to use

RE: A question about ClientMessage.setOutputStream()

2022-08-05 Thread Jan Šmucr
That’s an option, but given that it’s an AWS Lambda function, I’d prefer to stream it, so that there’s no need to use either the memory or the underlying ephemeral storage. However that’s not the point. I just wanted to know if the setOutputStream function is supposed to block, or if I’m doing

Re: A question about ClientMessage.setOutputStream()

2022-08-05 Thread Clebert Suconic
I would save the Message locally before you forward it anywhere else. On Fri, Aug 5, 2022 at 7:35 AM Jan Šmucr wrote: > > Hi Domenico, > thank you for your response. > Unfortunately, this does not work either. > > Tests which use this method pass fine, because the output stream happens to > be a

RE: A question about ClientMessage.setOutputStream()

2022-08-05 Thread Jan Šmucr
Hi Domenico, thank you for your response. Unfortunately, this does not work either. Tests which use this method pass fine, because the output stream happens to be a FileOutputStream instance which does not block (unless there’s some issue with the underlying file system). Jan From: Domenico Fr

Re: A question about ClientMessage.setOutputStream()

2022-08-05 Thread Domenico Francesco Bruscino
Hi Jan, calling checkCompletion() or getBodyBuffer() before calling setOutputStream(OutputStream) should fix your issue. Regards, Domenico On Fri, 5 Aug 2022 at 11:06, Jan Šmucr wrote: > Hello. > > The Large Messages documentation states that: > > setOutputStream(OutputStream): Set the OutputS

A question about ClientMessage.setOutputStream()

2022-08-05 Thread Jan Šmucr
Hello. The Large Messages documentation states that: > setOutputStream(OutputStream): Set the OutputStream that will receive the > body of a message. This method does not block. However if I write something like this: InputStream input = new PipedInputStream(1); OutputStream output = new PipedO