ely:
> https://github.com/apache/activemq-artemis/pull/3948
>
>
> On Wed, 23 Nov 2022 at 13:01, Jan Šmucr
> wrote:
> >
> > Hello.
> >
> > I’ve been using the Message.toPropertyMap() function and recently I’ve
> discovered that it does not preserve null valu
Hello.
I’ve been using the Message.toPropertyMap() function and recently I’ve
discovered that it does not preserve null values, as they get replaced by an
empty string in JsonUtil.truncate(). I understand that it’s not possible to put
null values into maps, but on the other hand, they are
Hello.
I’ve discovered that although I can add and remove diverts via the config file,
I cannot change filters associated to them.
Issue: https://issues.apache.org/jira/browse/ARTEMIS-4078
Tests:
https://github.com/apache/activemq-artemis/compare/main...jsmucr:activemq-artemis:ARTEMIS-4078
:zuzana.kacerek...@aimtecglobal.com>
Subject: Re: A question about ClientMessage.setOutputStream()
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 d
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 OutputStream that will receive
> the body of a message. This method does not
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
t soon whenever I get a full pass on my CI.
> >
> >
> > On Sat, Jul 16, 2022 at 1:07 PM Clebert Suconic
> > wrote:
> > >
> > > I closed your PR because I replaced it with another one. You should try
> > > that one.
> > >
> > > You can st
("globalMaxMessages")) {
configuration.globalMaxMessages = 10
} else {
configuration.globalMaxSize = 10 * 1024
}
Jan
From: Jan Šmucr<mailto:jan.sm...@aimtecglobal.com>
Sent: sobota 16. července 2022 18:00
To: dev@activemq.apache.org<mailto:dev@activemq.apache.org>
Subject:
t; 2_18 or <= 2_18
>
>
> I'm adding a test on 2.17 and 2.18 just to be sure... depending on
> failures I will change the < or <=
>
> On Fri, Jul 15, 2022 at 4:24 PM Jan Šmucr
> wrote:
> >
> > Thank you very much. I appreciate it. I'll post some feedbac
t; > > >
> > > > If it can be handled that way, I doubt there would be appetite for
> > > > releasing fixes across all the superceded intermediate versions rather
> > > > than just the latest. It doesnt appear to be widely hit so far in
> > > >
Dear devs,
I'd like to ask you for help with the communication incompatibility between
pre-2.18.0 servers and the newer ones. What I've learned so far is that in
2.18.0 there's been a change in the REPLICATION_START_FINISH_SYNC packet, yet
no new version of that packet has been introduced.
11 matches
Mail list logo
