You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Richard Bergmann <RB...@colsa.com.INVALID> on 2022/06/27 15:06:59 UTC
Re: [External] - Re: JSON Message Body Not Display in Artemis Web Console
Here:
-----
from json import dumps
import stomp
import sys
conn = stomp.Connection12(heartbeats=(30000,0))
conn.connect("admin",
"admin",
wait=True,
headers = {"client-id": sys.argv[0]})
message = {"item": """This is a lot of text.
In fact, it's an incredible amount of text.
It's enough text so as to get the size of the message to 1867 bytes.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum."""}
conn.send("Some Queue",
dumps(message),
"application/json",
headers={"destination-type": "ANYCAST",
"persistent": "true",
"priority": 0})
conn.disconnect()
-----
Did the screenshot come through from my first post? If I try to "Show" the message it shows the message ID and an empty box underneath "Displaying body as bytes (turned off)"
________________________________
From: Domenico Francesco Bruscino <br...@gmail.com>
Sent: Monday, June 27, 2022 10:48 AM
To: users@activemq.apache.org <us...@activemq.apache.org>
Subject: [External] - Re: JSON Message Body Not Display in Artemis Web Console
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi Rich,
how are you sending your JSON message, can you share a simple reproducer?
Regards,
Domenico
On Mon, 27 Jun 2022 at 14:46, Richard Bergmann <RB...@colsa.com.invalid>
wrote:
> I have a queue with a 1867 byte JSON message, but the message body is not
> displayed when I "Show" message. Not sure what "Displaying body as byes
> (turned off)" means. I would find nothing in the documentation or config
> files and I come up short on Google searches as well.
>
> Can anyone provide me with any insight?
>
> Thank you!
>
> Regards,
>
> Rich Bergmann
>
>
> ------------------------------
> The information contained in this e-mail and any attachments from COLSA
> Corporation may contain company sensitive and/or proprietary information,
> and is intended only for the named recipient to whom it was originally
> addressed. If you are not the intended recipient, any disclosure,
> distribution, or copying of this e-mail or its attachments is strictly
> prohibited. If you have received this e-mail in error, please notify the
> sender immediately by return e-mail and permanently delete the e-mail and
> any attachments.
>
> COLSA Proprietary
>
________________________________
The information contained in this e-mail and any attachments from COLSA Corporation may contain company sensitive and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.
COLSA Proprietary
Antwort: [Ext] Re: [External] - Antwort: [Ext] Too Many Open Files error trying to start Artemis server from a SystemD service
Posted by He...@systema.com.
on RHEL LimitNOFILE is definitely a good idea.
I do not have a user in the systemd service, so it runs under system
defaults, maybe that helps me out.
Von: "Richard Bergmann" <RB...@colsa.com.INVALID>
An: "users@activemq.apache.org" <us...@activemq.apache.org>
Datum: 07.07.2022 16:52
Betreff: [Ext] Re: [External] - Antwort: [Ext] Too Many Open Files
error trying to start Artemis server from a SystemD service
Yes, ulimit -n reports 81920.
________________________________
From: Herbert.Helmstreit@systema.com <He...@systema.com>
Sent: Thursday, July 7, 2022 10:21 AM
To: users@activemq.apache.org <us...@activemq.apache.org>
Subject: [External] - Antwort: [Ext] Too Many Open Files error trying to
start Artemis server from a SystemD service
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.
Hello Richard
8k should be enough sockets. You must at least re-login or reboot to make
this active.
Did you verify with ulimit -n ? What did you get?
btw. After=network.target is sub-optimal.
After=network-online.target
is better.
Check this out
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/<
https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fwww.freedesktop.org%2Fwiki%2FSoftware%2Fsystemd%2FNetworkTarget%2F&data=05%7C01%7CRBERGMANN%40colsa.com%7Cc096e7f544e14cc74a2c08da60241118%7C9821086b78824b43a5edb1e979bee31f%7C1%7C0%7C637928006067698160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=JBD7f6FQvzRRxyk3p8dCJRJOwPTNdJHhcXThKtVH5V0%3D&reserved=0
>
Best Regards
Herbert
________________________________
Herbert Helmstreit
Dipl.-Phys.
Software Engineer
[SYSTEMA Logo]<
https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fwww.systema.com%2F&data=05%7C01%7CRBERGMANN%40colsa.com%7Cc096e7f544e14cc74a2c08da60241118%7C9821086b78824b43a5edb1e979bee31f%7C1%7C0%7C637928006067698160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=J8%2FypKJmI01tdDHelk4m1TEMIHDnV%2FMLMpja5K2nCqs%3D&reserved=0
>
Phone: +49 941 / 7 83 92 36
Fax: +49 351 / 88 24 772
Herbert.Helmstreit@systema.com<ma...@systema.com> |
www.systema.com<
https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fwww.systema.com%2F&data=05%7C01%7CRBERGMANN%40colsa.com%7Cc096e7f544e14cc74a2c08da60241118%7C9821086b78824b43a5edb1e979bee31f%7C1%7C0%7C637928006067698160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=J8%2FypKJmI01tdDHelk4m1TEMIHDnV%2FMLMpja5K2nCqs%3D&reserved=0
>
[LinkedIn]<
https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fsystema-gmbh%2F&data=05%7C01%7CRBERGMANN%40colsa.com%7Cc096e7f544e14cc74a2c08da60241118%7C9821086b78824b43a5edb1e979bee31f%7C1%7C0%7C637928006067698160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=e%2F%2BQlaPnLGBRHuugkY81AUdzNcQrytIdOt5wSOejmE4%3D&reserved=0
>[Facebook]<
https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fde-de.facebook.com%2FSYSTEMA.automation%2F&data=05%7C01%7CRBERGMANN%40colsa.com%7Cc096e7f544e14cc74a2c08da60241118%7C9821086b78824b43a5edb1e979bee31f%7C1%7C0%7C637928006067698160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=38bp0NDE45IrPTRuNUWoi7D3NNF2UaZb12Af1Vm4gAc%3D&reserved=0
>[XING]<
https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fwww.xing.com%2Fpages%2Fsystemagmbh&data=05%7C01%7CRBERGMANN%40colsa.com%7Cc096e7f544e14cc74a2c08da60241118%7C9821086b78824b43a5edb1e979bee31f%7C1%7C0%7C637928006067698160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=UDJfXXY9quG9lVsMWsGcrIKtWrTElaTe0SRiz%2Be0Jmg%3D&reserved=0
>
SYSTEMA Systementwicklung Dipl.-Inf. Manfred Austen GmbH
Schikanederstraße 2b - Posthof | 93053 Regensburg
HRB 11256 Amtsgericht Dresden | USt.-ID DE 159 607 786
Geschäftsführer: Manfred Austen, CEO und Dr. Ulf Martin, COO
Von: "Richard Bergmann" <RB...@colsa.com.INVALID>
An: "users@activemq.apache.org" <us...@activemq.apache.org>
Datum: 07.07.2022 16:10
Betreff: [Ext] Too Many Open Files error trying to start Artemis
server from a SystemD service
________________________________
I have been struggling with the Too Many Open Files issue running Artemis
as a service within a service (if that is not confusing enough). My
/etc/security/limits.conf files contains:
-----
.
.
.
# End of file
* soft nofile 81920
* hard nofile 81920
-----
Originally it was set to 8192 and I was able to start the service from the
command line: /opt/artemis/bin/artemis-service start
When I did so and ran: lsof -p <artemis pid> | wc -l
it reported some 5K files open by the process, hence the reason it
wouldn't run with the default limit of 1024.
I then tried to start the SystemD service: sudo systemctl start artemis
using this in /etc/systemd/system/artemis.service:
-----
[Unit]
Description=ActiveMQ Artemis Service
After=network.target
[Service]
ExecStart=/opt/artemis/bin/artemis-service start
ExecStop=/opt/artemis/bin/artemis-service stop
Type=forking
User=<my id>
Group=<my group>
[Install]
WantedBy=multi-user.target
-----
and it failed with the Too Many Open Files error. So I increased it to
the 81920 shown above, rebooted, and I STILL get the Too Many Open Files
error.
Is there something special about the way services are started such that it
doesn't use /etc/security/limits.conf to determine the number of open
files allowed for a process?
Regards,
Rich Bergmann
________________________________
The information contained in this e-mail and any attachments from COLSA
Corporation may contain company sensitive and/or proprietary information,
and is intended only for the named recipient to whom it was originally
addressed. If you are not the intended recipient, any disclosure,
distribution, or copying of this e-mail or its attachments is strictly
prohibited. If you have received this e-mail in error, please notify the
sender immediately by return e-mail and permanently delete the e-mail and
any attachments.
COLSA Proprietary
________________________________
The information contained in this e-mail and any attachments from COLSA
Corporation may contain company sensitive and/or proprietary information,
and is intended only for the named recipient to whom it was originally
addressed. If you are not the intended recipient, any disclosure,
distribution, or copying of this e-mail or its attachments is strictly
prohibited. If you have received this e-mail in error, please notify the
sender immediately by return e-mail and permanently delete the e-mail and
any attachments.
Re: [External] - Antwort: [Ext] Too Many Open Files error trying to start Artemis server from a SystemD service
Posted by Richard Bergmann <RB...@colsa.com.INVALID>.
Yes, ulimit -n reports 81920.
________________________________
From: Herbert.Helmstreit@systema.com <He...@systema.com>
Sent: Thursday, July 7, 2022 10:21 AM
To: users@activemq.apache.org <us...@activemq.apache.org>
Subject: [External] - Antwort: [Ext] Too Many Open Files error trying to start Artemis server from a SystemD service
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hello Richard
8k should be enough sockets. You must at least re-login or reboot to make this active.
Did you verify with ulimit -n ? What did you get?
btw. After=network.target is sub-optimal.
After=network-online.target
is better.
Check this out https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/<https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fwww.freedesktop.org%2Fwiki%2FSoftware%2Fsystemd%2FNetworkTarget%2F&data=05%7C01%7CRBERGMANN%40colsa.com%7Cc096e7f544e14cc74a2c08da60241118%7C9821086b78824b43a5edb1e979bee31f%7C1%7C0%7C637928006067698160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=JBD7f6FQvzRRxyk3p8dCJRJOwPTNdJHhcXThKtVH5V0%3D&reserved=0>
Best Regards
Herbert
________________________________
Herbert Helmstreit
Dipl.-Phys.
Software Engineer
[SYSTEMA Logo]<https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fwww.systema.com%2F&data=05%7C01%7CRBERGMANN%40colsa.com%7Cc096e7f544e14cc74a2c08da60241118%7C9821086b78824b43a5edb1e979bee31f%7C1%7C0%7C637928006067698160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=J8%2FypKJmI01tdDHelk4m1TEMIHDnV%2FMLMpja5K2nCqs%3D&reserved=0>
Phone: +49 941 / 7 83 92 36
Fax: +49 351 / 88 24 772
Herbert.Helmstreit@systema.com<ma...@systema.com> | www.systema.com<https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fwww.systema.com%2F&data=05%7C01%7CRBERGMANN%40colsa.com%7Cc096e7f544e14cc74a2c08da60241118%7C9821086b78824b43a5edb1e979bee31f%7C1%7C0%7C637928006067698160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=J8%2FypKJmI01tdDHelk4m1TEMIHDnV%2FMLMpja5K2nCqs%3D&reserved=0>
[LinkedIn]<https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fsystema-gmbh%2F&data=05%7C01%7CRBERGMANN%40colsa.com%7Cc096e7f544e14cc74a2c08da60241118%7C9821086b78824b43a5edb1e979bee31f%7C1%7C0%7C637928006067698160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=e%2F%2BQlaPnLGBRHuugkY81AUdzNcQrytIdOt5wSOejmE4%3D&reserved=0>[Facebook]<https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fde-de.facebook.com%2FSYSTEMA.automation%2F&data=05%7C01%7CRBERGMANN%40colsa.com%7Cc096e7f544e14cc74a2c08da60241118%7C9821086b78824b43a5edb1e979bee31f%7C1%7C0%7C637928006067698160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=38bp0NDE45IrPTRuNUWoi7D3NNF2UaZb12Af1Vm4gAc%3D&reserved=0>[XING]<https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fwww.xing.com%2Fpages%2Fsystemagmbh&data=05%7C01%7CRBERGMANN%40colsa.com%7Cc096e7f544e14cc74a2c08da60241118%7C9821086b78824b43a5edb1e979bee31f%7C1%7C0%7C637928006067698160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=UDJfXXY9quG9lVsMWsGcrIKtWrTElaTe0SRiz%2Be0Jmg%3D&reserved=0>
SYSTEMA Systementwicklung Dipl.-Inf. Manfred Austen GmbH
Schikanederstraße 2b - Posthof | 93053 Regensburg
HRB 11256 Amtsgericht Dresden | USt.-ID DE 159 607 786
Geschäftsführer: Manfred Austen, CEO und Dr. Ulf Martin, COO
Von: "Richard Bergmann" <RB...@colsa.com.INVALID>
An: "users@activemq.apache.org" <us...@activemq.apache.org>
Datum: 07.07.2022 16:10
Betreff: [Ext] Too Many Open Files error trying to start Artemis server from a SystemD service
________________________________
I have been struggling with the Too Many Open Files issue running Artemis as a service within a service (if that is not confusing enough). My /etc/security/limits.conf files contains:
-----
.
.
.
# End of file
* soft nofile 81920
* hard nofile 81920
-----
Originally it was set to 8192 and I was able to start the service from the command line: /opt/artemis/bin/artemis-service start
When I did so and ran: lsof -p <artemis pid> | wc -l
it reported some 5K files open by the process, hence the reason it wouldn't run with the default limit of 1024.
I then tried to start the SystemD service: sudo systemctl start artemis
using this in /etc/systemd/system/artemis.service:
-----
[Unit]
Description=ActiveMQ Artemis Service
After=network.target
[Service]
ExecStart=/opt/artemis/bin/artemis-service start
ExecStop=/opt/artemis/bin/artemis-service stop
Type=forking
User=<my id>
Group=<my group>
[Install]
WantedBy=multi-user.target
-----
and it failed with the Too Many Open Files error. So I increased it to the 81920 shown above, rebooted, and I STILL get the Too Many Open Files error.
Is there something special about the way services are started such that it doesn't use /etc/security/limits.conf to determine the number of open files allowed for a process?
Regards,
Rich Bergmann
________________________________
The information contained in this e-mail and any attachments from COLSA Corporation may contain company sensitive and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.
COLSA Proprietary
________________________________
The information contained in this e-mail and any attachments from COLSA Corporation may contain company sensitive and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.
Antwort: [Ext] Too Many Open Files error trying to start Artemis server from a SystemD service
Posted by He...@systema.com.
Hello Richard
8k should be enough sockets. You must at least re-login or reboot to make
this active.
Did you verify with ulimit -n ? What did you get?
btw. After=network.target is sub-optimal.
After=network-online.target
is better.
Check this out
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
Best Regards
Herbert
Von: "Richard Bergmann" <RB...@colsa.com.INVALID>
An: "users@activemq.apache.org" <us...@activemq.apache.org>
Datum: 07.07.2022 16:10
Betreff: [Ext] Too Many Open Files error trying to start Artemis
server from a SystemD service
I have been struggling with the Too Many Open Files issue running Artemis
as a service within a service (if that is not confusing enough). My
/etc/security/limits.conf files contains:
-----
.
.
.
# End of file
* soft nofile 81920
* hard nofile 81920
-----
Originally it was set to 8192 and I was able to start the service from the
command line: /opt/artemis/bin/artemis-service start
When I did so and ran: lsof -p <artemis pid> | wc -l
it reported some 5K files open by the process, hence the reason it
wouldn't run with the default limit of 1024.
I then tried to start the SystemD service: sudo systemctl start artemis
using this in /etc/systemd/system/artemis.service:
-----
[Unit]
Description=ActiveMQ Artemis Service
After=network.target
[Service]
ExecStart=/opt/artemis/bin/artemis-service start
ExecStop=/opt/artemis/bin/artemis-service stop
Type=forking
User=<my id>
Group=<my group>
[Install]
WantedBy=multi-user.target
-----
and it failed with the Too Many Open Files error. So I increased it to
the 81920 shown above, rebooted, and I STILL get the Too Many Open Files
error.
Is there something special about the way services are started such that it
doesn't use /etc/security/limits.conf to determine the number of open
files allowed for a process?
Regards,
Rich Bergmann
________________________________
The information contained in this e-mail and any attachments from COLSA
Corporation may contain company sensitive and/or proprietary information,
and is intended only for the named recipient to whom it was originally
addressed. If you are not the intended recipient, any disclosure,
distribution, or copying of this e-mail or its attachments is strictly
prohibited. If you have received this e-mail in error, please notify the
sender immediately by return e-mail and permanently delete the e-mail and
any attachments.
COLSA Proprietary
Re: [External] - Re: Too Many Open Files error trying to start Artemis server from a SystemD service
Posted by Richard Bergmann <RB...@colsa.com.INVALID>.
Thank you! I guess my Google chops are waning as I found this after your post: https://access.redhat.com/solutions/1257953
Regards,
Rich Bergmann
________________________________
From: SL <sl...@cecurity.com.INVALID>
Sent: Thursday, July 7, 2022 10:26 AM
To: users@activemq.apache.org <us...@activemq.apache.org>
Subject: [External] - Re: Too Many Open Files error trying to start Artemis server from a SystemD service
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
add
LimitNOFILE=81920
to the [Service] section of your systemd unit file
Regards,
Le 07/07/2022 à 16:09, Richard Bergmann a écrit :
> I have been struggling with the Too Many Open Files issue running Artemis as a service within a service (if that is not confusing enough). My /etc/security/limits.conf files contains:
>
> -----
> .
> .
> .
> # End of file
> * soft nofile 81920
> * hard nofile 81920
> -----
>
> Originally it was set to 8192 and I was able to start the service from the command line: /opt/artemis/bin/artemis-service start
>
> When I did so and ran: lsof -p <artemis pid> | wc -l
>
> it reported some 5K files open by the process, hence the reason it wouldn't run with the default limit of 1024.
>
> I then tried to start the SystemD service: sudo systemctl start artemis
>
> using this in /etc/systemd/system/artemis.service:
>
> -----
> [Unit]
> Description=ActiveMQ Artemis Service
> After=network.target
>
> [Service]
> ExecStart=/opt/artemis/bin/artemis-service start
> ExecStop=/opt/artemis/bin/artemis-service stop
> Type=forking
> User=<my id>
> Group=<my group>
>
> [Install]
> WantedBy=multi-user.target
> -----
>
> and it failed with the Too Many Open Files error. So I increased it to the 81920 shown above, rebooted, and I STILL get the Too Many Open Files error.
>
> Is there something special about the way services are started such that it doesn't use /etc/security/limits.conf to determine the number of open files allowed for a process?
>
> Regards,
>
> Rich Bergmann
> ________________________________
> The information contained in this e-mail and any attachments from COLSA Corporation may contain company sensitive and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.
>
>
> COLSA Proprietary
>
________________________________
The information contained in this e-mail and any attachments from COLSA Corporation may contain company sensitive and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.
Re: Too Many Open Files error trying to start Artemis server from a SystemD service
Posted by SL <sl...@cecurity.com.INVALID>.
add
LimitNOFILE=81920
to the [Service] section of your systemd unit file
Regards,
Le 07/07/2022 à 16:09, Richard Bergmann a écrit :
> I have been struggling with the Too Many Open Files issue running Artemis as a service within a service (if that is not confusing enough). My /etc/security/limits.conf files contains:
>
> -----
> .
> .
> .
> # End of file
> * soft nofile 81920
> * hard nofile 81920
> -----
>
> Originally it was set to 8192 and I was able to start the service from the command line: /opt/artemis/bin/artemis-service start
>
> When I did so and ran: lsof -p <artemis pid> | wc -l
>
> it reported some 5K files open by the process, hence the reason it wouldn't run with the default limit of 1024.
>
> I then tried to start the SystemD service: sudo systemctl start artemis
>
> using this in /etc/systemd/system/artemis.service:
>
> -----
> [Unit]
> Description=ActiveMQ Artemis Service
> After=network.target
>
> [Service]
> ExecStart=/opt/artemis/bin/artemis-service start
> ExecStop=/opt/artemis/bin/artemis-service stop
> Type=forking
> User=<my id>
> Group=<my group>
>
> [Install]
> WantedBy=multi-user.target
> -----
>
> and it failed with the Too Many Open Files error. So I increased it to the 81920 shown above, rebooted, and I STILL get the Too Many Open Files error.
>
> Is there something special about the way services are started such that it doesn't use /etc/security/limits.conf to determine the number of open files allowed for a process?
>
> Regards,
>
> Rich Bergmann
> ________________________________
> The information contained in this e-mail and any attachments from COLSA Corporation may contain company sensitive and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.
>
>
> COLSA Proprietary
>
Too Many Open Files error trying to start Artemis server from a SystemD service
Posted by Richard Bergmann <RB...@colsa.com.INVALID>.
I have been struggling with the Too Many Open Files issue running Artemis as a service within a service (if that is not confusing enough). My /etc/security/limits.conf files contains:
-----
.
.
.
# End of file
* soft nofile 81920
* hard nofile 81920
-----
Originally it was set to 8192 and I was able to start the service from the command line: /opt/artemis/bin/artemis-service start
When I did so and ran: lsof -p <artemis pid> | wc -l
it reported some 5K files open by the process, hence the reason it wouldn't run with the default limit of 1024.
I then tried to start the SystemD service: sudo systemctl start artemis
using this in /etc/systemd/system/artemis.service:
-----
[Unit]
Description=ActiveMQ Artemis Service
After=network.target
[Service]
ExecStart=/opt/artemis/bin/artemis-service start
ExecStop=/opt/artemis/bin/artemis-service stop
Type=forking
User=<my id>
Group=<my group>
[Install]
WantedBy=multi-user.target
-----
and it failed with the Too Many Open Files error. So I increased it to the 81920 shown above, rebooted, and I STILL get the Too Many Open Files error.
Is there something special about the way services are started such that it doesn't use /etc/security/limits.conf to determine the number of open files allowed for a process?
Regards,
Rich Bergmann
________________________________
The information contained in this e-mail and any attachments from COLSA Corporation may contain company sensitive and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.
COLSA Proprietary
Re: [External] - Re: JSON Message Body Not Display in Artemis Web Console
Posted by Richard Bergmann <RB...@colsa.com.INVALID>.
Thank you Robbie. I will pack that away in my memory banks for future posts.
Regards,
Rich Bergmann
________________________________
From: Robbie Gemmell <ro...@gmail.com>
Sent: Tuesday, June 28, 2022 6:37 AM
To: users@activemq.apache.org <us...@activemq.apache.org>
Subject: Re: [External] - Re: JSON Message Body Not Display in Artemis Web Console
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On Mon, 27 Jun 2022 at 16:07, Richard Bergmann
<RB...@colsa.com.invalid> wrote:
>
> Here:
>
> -----
> from json import dumps
> import stomp
> import sys
>
>
> conn = stomp.Connection12(heartbeats=(30000,0))
> conn.connect("admin",
> "admin",
> wait=True,
> headers = {"client-id": sys.argv[0]})
>
>
> message = {"item": """This is a lot of text.
> In fact, it's an incredible amount of text.
> It's enough text so as to get the size of the message to 1867 bytes.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum."""}
>
>
> conn.send("Some Queue",
> dumps(message),
> "application/json",
> headers={"destination-type": "ANYCAST",
> "persistent": "true",
> "priority": 0})
>
> conn.disconnect()
> -----
>
> Did the screenshot come through from my first post? If I try to "Show" the message it shows the message ID and an empty box underneath "Displaying body as bytes (turned off)"
>
Domenico seems to have answered, but to this bit...no, the mailing
lists are text based and strip essentially all attachments, so your
screenshot didnt make it.
> ________________________________
> From: Domenico Francesco Bruscino <br...@gmail.com>
> Sent: Monday, June 27, 2022 10:48 AM
> To: users@activemq.apache.org <us...@activemq.apache.org>
> Subject: [External] - Re: JSON Message Body Not Display in Artemis Web Console
>
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> Hi Rich,
>
> how are you sending your JSON message, can you share a simple reproducer?
>
> Regards,
> Domenico
>
> On Mon, 27 Jun 2022 at 14:46, Richard Bergmann <RB...@colsa.com.invalid>
> wrote:
>
> > I have a queue with a 1867 byte JSON message, but the message body is not
> > displayed when I "Show" message. Not sure what "Displaying body as byes
> > (turned off)" means. I would find nothing in the documentation or config
> > files and I come up short on Google searches as well.
> >
> > Can anyone provide me with any insight?
> >
> > Thank you!
> >
> > Regards,
> >
> > Rich Bergmann
> >
> >
> > ------------------------------
> > The information contained in this e-mail and any attachments from COLSA
> > Corporation may contain company sensitive and/or proprietary information,
> > and is intended only for the named recipient to whom it was originally
> > addressed. If you are not the intended recipient, any disclosure,
> > distribution, or copying of this e-mail or its attachments is strictly
> > prohibited. If you have received this e-mail in error, please notify the
> > sender immediately by return e-mail and permanently delete the e-mail and
> > any attachments.
> >
> > COLSA Proprietary
> >
> ________________________________
> The information contained in this e-mail and any attachments from COLSA Corporation may contain company sensitive and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.
>
>
> COLSA Proprietary
________________________________
The information contained in this e-mail and any attachments from COLSA Corporation may contain company sensitive and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.
COLSA Proprietary
Re: [External] - Re: JSON Message Body Not Display in Artemis Web Console
Posted by Robbie Gemmell <ro...@gmail.com>.
On Mon, 27 Jun 2022 at 16:07, Richard Bergmann
<RB...@colsa.com.invalid> wrote:
>
> Here:
>
> -----
> from json import dumps
> import stomp
> import sys
>
>
> conn = stomp.Connection12(heartbeats=(30000,0))
> conn.connect("admin",
> "admin",
> wait=True,
> headers = {"client-id": sys.argv[0]})
>
>
> message = {"item": """This is a lot of text.
> In fact, it's an incredible amount of text.
> It's enough text so as to get the size of the message to 1867 bytes.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum."""}
>
>
> conn.send("Some Queue",
> dumps(message),
> "application/json",
> headers={"destination-type": "ANYCAST",
> "persistent": "true",
> "priority": 0})
>
> conn.disconnect()
> -----
>
> Did the screenshot come through from my first post? If I try to "Show" the message it shows the message ID and an empty box underneath "Displaying body as bytes (turned off)"
>
Domenico seems to have answered, but to this bit...no, the mailing
lists are text based and strip essentially all attachments, so your
screenshot didnt make it.
> ________________________________
> From: Domenico Francesco Bruscino <br...@gmail.com>
> Sent: Monday, June 27, 2022 10:48 AM
> To: users@activemq.apache.org <us...@activemq.apache.org>
> Subject: [External] - Re: JSON Message Body Not Display in Artemis Web Console
>
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> Hi Rich,
>
> how are you sending your JSON message, can you share a simple reproducer?
>
> Regards,
> Domenico
>
> On Mon, 27 Jun 2022 at 14:46, Richard Bergmann <RB...@colsa.com.invalid>
> wrote:
>
> > I have a queue with a 1867 byte JSON message, but the message body is not
> > displayed when I "Show" message. Not sure what "Displaying body as byes
> > (turned off)" means. I would find nothing in the documentation or config
> > files and I come up short on Google searches as well.
> >
> > Can anyone provide me with any insight?
> >
> > Thank you!
> >
> > Regards,
> >
> > Rich Bergmann
> >
> >
> > ------------------------------
> > The information contained in this e-mail and any attachments from COLSA
> > Corporation may contain company sensitive and/or proprietary information,
> > and is intended only for the named recipient to whom it was originally
> > addressed. If you are not the intended recipient, any disclosure,
> > distribution, or copying of this e-mail or its attachments is strictly
> > prohibited. If you have received this e-mail in error, please notify the
> > sender immediately by return e-mail and permanently delete the e-mail and
> > any attachments.
> >
> > COLSA Proprietary
> >
> ________________________________
> The information contained in this e-mail and any attachments from COLSA Corporation may contain company sensitive and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.
>
>
> COLSA Proprietary
Re: [External] - Re: JSON Message Body Not Display in Artemis Web Console
Posted by Richard Bergmann <RB...@colsa.com.INVALID>.
Awesome. Thank you! I guess I lose my web interface explorer merit badge as I never did find the preferences mechanism (have to click on the user glyph). Anyway, between that and setting <management-message-attribute-size-limit>-1</management-message-attribute-size-limit> under the <address-setting> element I can now view the entire message in each of my queues. BTW, all my messages are ~2K, so I have no heartache with this setting.
Thank you again. It appears I am now finally fully up and running on Artemis.
Regards,
Rich Bergmann
________________________________
From: Domenico Francesco Bruscino <br...@gmail.com>
Sent: Tuesday, June 28, 2022 3:53 AM
To: users@activemq.apache.org <us...@activemq.apache.org>
Subject: Re: [External] - Re: JSON Message Body Not Display in Artemis Web Console
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi Rich,
ActiveMQ Artemis enqueues all STOMP messages with a `content-length` header
as binary messages, so you need to change your `Browse Bytes Messages`
setting in the artemis preference tab [1] to any value other than `Off` to
see the body of those messages.
[1] http://localhost:8161/console/preferences?tab=artemis
Regards,
Domenico
On Mon, 27 Jun 2022 at 17:07, Richard Bergmann <RB...@colsa.com.invalid>
wrote:
> Here:
>
> -----
> from json import dumps
> import stomp
> import sys
>
>
> conn = stomp.Connection12(heartbeats=(30000,0))
> conn.connect("admin",
> "admin",
> wait=True,
> headers = {"client-id": sys.argv[0]})
>
>
> message = {"item": """This is a lot of text.
> In fact, it's an incredible amount of text.
> It's enough text so as to get the size of the message to 1867 bytes.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
> tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim
> veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea
> commodo consequat. Duis aute irure dolor in reprehenderit in voluptate
> velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat
> cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id
> est laborum.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
> tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim
> veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea
> commodo consequat. Duis aute irure dolor in reprehenderit in voluptate
> velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat
> cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id
> est laborum.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
> tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim
> veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea
> commodo consequat. Duis aute irure dolor in reprehenderit in voluptate
> velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat
> cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id
> est laborum.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
> tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim
> veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea
> commodo consequat. Duis aute irure dolor in reprehenderit in voluptate
> velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat
> cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id
> est laborum."""}
>
>
> conn.send("Some Queue",
> dumps(message),
> "application/json",
> headers={"destination-type": "ANYCAST",
> "persistent": "true",
> "priority": 0})
>
> conn.disconnect()
> -----
>
> Did the screenshot come through from my first post? If I try to "Show"
> the message it shows the message ID and an empty box underneath "Displaying
> body as bytes (turned off)"
>
> ________________________________
> From: Domenico Francesco Bruscino <br...@gmail.com>
> Sent: Monday, June 27, 2022 10:48 AM
> To: users@activemq.apache.org <us...@activemq.apache.org>
> Subject: [External] - Re: JSON Message Body Not Display in Artemis Web
> Console
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> Hi Rich,
>
> how are you sending your JSON message, can you share a simple reproducer?
>
> Regards,
> Domenico
>
> On Mon, 27 Jun 2022 at 14:46, Richard Bergmann <RBERGMANN@colsa.com.invalid
> >
> wrote:
>
> > I have a queue with a 1867 byte JSON message, but the message body is not
> > displayed when I "Show" message. Not sure what "Displaying body as byes
> > (turned off)" means. I would find nothing in the documentation or config
> > files and I come up short on Google searches as well.
> >
> > Can anyone provide me with any insight?
> >
> > Thank you!
> >
> > Regards,
> >
> > Rich Bergmann
> >
> >
> > ------------------------------
> > The information contained in this e-mail and any attachments from COLSA
> > Corporation may contain company sensitive and/or proprietary information,
> > and is intended only for the named recipient to whom it was originally
> > addressed. If you are not the intended recipient, any disclosure,
> > distribution, or copying of this e-mail or its attachments is strictly
> > prohibited. If you have received this e-mail in error, please notify the
> > sender immediately by return e-mail and permanently delete the e-mail and
> > any attachments.
> >
> > COLSA Proprietary
> >
> ________________________________
> The information contained in this e-mail and any attachments from COLSA
> Corporation may contain company sensitive and/or proprietary information,
> and is intended only for the named recipient to whom it was originally
> addressed. If you are not the intended recipient, any disclosure,
> distribution, or copying of this e-mail or its attachments is strictly
> prohibited. If you have received this e-mail in error, please notify the
> sender immediately by return e-mail and permanently delete the e-mail and
> any attachments.
>
>
> COLSA Proprietary
>
________________________________
The information contained in this e-mail and any attachments from COLSA Corporation may contain company sensitive and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.
COLSA Proprietary
Re: [External] - Re: JSON Message Body Not Display in Artemis Web Console
Posted by Domenico Francesco Bruscino <br...@gmail.com>.
Hi Rich,
ActiveMQ Artemis enqueues all STOMP messages with a `content-length` header
as binary messages, so you need to change your `Browse Bytes Messages`
setting in the artemis preference tab [1] to any value other than `Off` to
see the body of those messages.
[1] http://localhost:8161/console/preferences?tab=artemis
Regards,
Domenico
On Mon, 27 Jun 2022 at 17:07, Richard Bergmann <RB...@colsa.com.invalid>
wrote:
> Here:
>
> -----
> from json import dumps
> import stomp
> import sys
>
>
> conn = stomp.Connection12(heartbeats=(30000,0))
> conn.connect("admin",
> "admin",
> wait=True,
> headers = {"client-id": sys.argv[0]})
>
>
> message = {"item": """This is a lot of text.
> In fact, it's an incredible amount of text.
> It's enough text so as to get the size of the message to 1867 bytes.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
> tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim
> veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea
> commodo consequat. Duis aute irure dolor in reprehenderit in voluptate
> velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat
> cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id
> est laborum.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
> tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim
> veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea
> commodo consequat. Duis aute irure dolor in reprehenderit in voluptate
> velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat
> cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id
> est laborum.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
> tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim
> veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea
> commodo consequat. Duis aute irure dolor in reprehenderit in voluptate
> velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat
> cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id
> est laborum.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
> tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim
> veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea
> commodo consequat. Duis aute irure dolor in reprehenderit in voluptate
> velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat
> cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id
> est laborum."""}
>
>
> conn.send("Some Queue",
> dumps(message),
> "application/json",
> headers={"destination-type": "ANYCAST",
> "persistent": "true",
> "priority": 0})
>
> conn.disconnect()
> -----
>
> Did the screenshot come through from my first post? If I try to "Show"
> the message it shows the message ID and an empty box underneath "Displaying
> body as bytes (turned off)"
>
> ________________________________
> From: Domenico Francesco Bruscino <br...@gmail.com>
> Sent: Monday, June 27, 2022 10:48 AM
> To: users@activemq.apache.org <us...@activemq.apache.org>
> Subject: [External] - Re: JSON Message Body Not Display in Artemis Web
> Console
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> Hi Rich,
>
> how are you sending your JSON message, can you share a simple reproducer?
>
> Regards,
> Domenico
>
> On Mon, 27 Jun 2022 at 14:46, Richard Bergmann <RBERGMANN@colsa.com.invalid
> >
> wrote:
>
> > I have a queue with a 1867 byte JSON message, but the message body is not
> > displayed when I "Show" message. Not sure what "Displaying body as byes
> > (turned off)" means. I would find nothing in the documentation or config
> > files and I come up short on Google searches as well.
> >
> > Can anyone provide me with any insight?
> >
> > Thank you!
> >
> > Regards,
> >
> > Rich Bergmann
> >
> >
> > ------------------------------
> > The information contained in this e-mail and any attachments from COLSA
> > Corporation may contain company sensitive and/or proprietary information,
> > and is intended only for the named recipient to whom it was originally
> > addressed. If you are not the intended recipient, any disclosure,
> > distribution, or copying of this e-mail or its attachments is strictly
> > prohibited. If you have received this e-mail in error, please notify the
> > sender immediately by return e-mail and permanently delete the e-mail and
> > any attachments.
> >
> > COLSA Proprietary
> >
> ________________________________
> The information contained in this e-mail and any attachments from COLSA
> Corporation may contain company sensitive and/or proprietary information,
> and is intended only for the named recipient to whom it was originally
> addressed. If you are not the intended recipient, any disclosure,
> distribution, or copying of this e-mail or its attachments is strictly
> prohibited. If you have received this e-mail in error, please notify the
> sender immediately by return e-mail and permanently delete the e-mail and
> any attachments.
>
>
> COLSA Proprietary
>