[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435392#comment-17435392
]
arne anka edited comment on ARTEMIS-3535 at 10/28/21, 1:11 PM:
---------------------------------------------------------------
In case it matters: the `producer` command sends `text`, not `bytes` as Artemis
supposes my messages to be; sending one of my XML or a plain text messages with
`–data` fails with an error.
Next, I send my messages via REST, once I add the artemis-rest.war the issue
appears – no matter whether I send XML or plain text.
So, obviously the communication between the REST webapp and the server is
somehow causing trouble.
Since the created WAR is about 29M I won't attach it, but here's the additional
files:
[^web.xml]
[^rest.messaging.config.file.xml]
and the `push-topic-registration` (lives in
$ARTEMIS_HOME/push-registrations/topics/)
[^test.xml]
In `broker.xml` add
{code:xml}
<addresses>
...
<address name="FOO.topic">
<multicast/>
</address>
</addresses>
{code}
was (Author: 2020-11-12):
In case it matters: the `producer` command sends `text`, not `bytes` as Artemis
supposes my messages to be; sending one of my XML or a plain text messages with
`–data` fails with an error.
Next, I send my messages via REST, once I add the artemis-rest.war the issue
appears – no matter whether I send XML or plain text.
So, obviously the communication between the REST webapp and the server is
somehow causing trouble.
Since the created WAR is about 29M I won't attach it, but here's the additional
files:
[^web.xml]
[^rest.messaging.config.file.xml]
and the `push-topic-registration` (lives in
$ARTEMIS_HOME/push-registrations/topics/)
[^test.xml]
In `broker.xml` add
```
<addresses>
...
<address name="FOO.topic">
<multicast/>
</address>
</addresses>
```
> management-message-attribute-size-limit = -1 does not unlimit
> -------------------------------------------------------------
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Environment: A' Artems 2.19.0
> Reporter: arne anka
> Priority: Major
> Attachments: broker.xml, limited.jpg, rest.messaging.config.file.xml,
> test.xml, unlimited.jpg, web.xml
>
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
> <address-setting match="#">
> ...
>
> <management-message-attribute-size-limit>-1</management-message-attribute-size-limit>
> </address-setting>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
