Thanks for the ideas, I'll try those out!
On Tue, Jan 25, 2022 at 1:23 PM Justin Bertram wrote:
> You can't get the content of the message in any form from the "data print"
> command. However, the _properties_ of the message are printed since those
> are stored with type information. Those could
You can't get the content of the message in any form from the "data print"
command. However, the _properties_ of the message are printed since those
are stored with type information. Those could potentially help you identify
the message.
If you really wanted to view the content of the message you
Hmm, that makes sense. Is there any way to view the content from a message
so that if we know the encoding, we could read what it says?
On Tue, Jan 25, 2022 at 12:53 PM Justin Bertram wrote:
> I know you got this work, but for posterity's sake I wanted to make one
> point clear...
>
> The "data
I know you got this work, but for posterity's sake I wanted to make one
point clear...
The "data print" command won't print the _content_ of the message. As far
as the broker is concerned the content of the message is an opaque byte
array. It could be binary data or text data, and even if it is te
My apologies, I just needed to try again, I got it working now. Thanks for
clearing everything up!
On Tue, Jan 25, 2022 at 12:39 PM Matthew Harris
wrote:
> That was definitely my point of confusion, thank you both for clearing it
> up.
>
> One quick follow up - what's the best way to analyze the
That was definitely my point of confusion, thank you both for clearing it
up.
One quick follow up - what's the best way to analyze the contents of a
"*.amq" journal file? I've tried various uses of the "artemis data ___"
command, but I've never gotten the messages I've sent during a broker's
sessi
In my opinion the documentation is not very clear on this point. It says:
> ActiveMQ Artemis will keep a copy of each generated journal file, up to
the configured retention period, at the unit chose. On the example above
the system would keep all the journal files up to 365 days.
As far as I can
It does not keep two copies of the data, is is more that journal files
that are candidates for deletion are archived or retained rather than
being deleted.
if the data is still in the journal, then it won't exist in the
retention folder.
send and consume more messages such that compaction would cl
Hi,
I'm trying to set up data persistence with an Artemis ActiveMQ broker,
version 2.20.0.
In broker.xml, I use a "journal-retention-directory" tag to create a
copy of the journals generated by running the broker in the
"data/retention" directory for 365 days, as described in the documentation
he
