[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435489#comment-17435489
]
arne anka edited comment on ARTEMIS-3535 at 10/28/21, 3:20 PM:
---------------------------------------------------------------
Are you familiar with the artemis-rest portion of the Artemis project? They may
be able to tell you whether these steps can be shortened.
Anyway, that's what I am using.
Create a WAR of it (change POM's {{packaging}} from {{jar}} to {{war}}), make
sure to include the provided {{web.xml}} (in {{src/main/webapp/WEB-INF/}}) and
{{rest.message...xml}} ({{src/main/resources/}}) before building.
Edit: seems Jira accepted my WAR, so you can just use that.
Add the WAR to {{$ARTEMIS_HOME/web/}} and to {{bootstrap.xml}} and (re)start
the broker.
As far as I can tell, the {{test.xml}} topic registration is required by
artemis-rest to create the REST endpoint and mapping to a queue
({{FOO.topic/test}}) – at least, if omitted, the file will not appear.
Send a file via curl
{code:java}
curl -vvv -4 http://localhost:8161/rest/topics/FOO.topic/create -d
@/tmp/test.txt
{code}
Due to the non-existant link target {{[http://localhost:50001/]}} messages
will end up in {{DLQ}}.
Alternatively, pause queue {{FOO.topic/test}} to see messages there.
# open console
# expand 0.0.0.0 -> addresses -> FOO.topic -> queues -> multicast -> test
# switch to *Browse Queue*
# *Show* message
# as you can see, the message is not shown, neither bytes nor text, despite
being ~20k of size:
!broken_message.png!
was (Author: 2020-11-12):
Are you familiar with the artemis-rest portion of the Artemis project? They may
be able to tell you whether these steps can be shortened.
Anyway, that's what I am using.
Create a WAR of it (change POM's {{packaging}} from {{jar}} to {{war}}), make
sure to include the provided {{web.xml}} (in {{src/main/webapp/WEB-INF/}}) and
{{rest.message...xml}} ({{src/main/resources/}}) before building.
Add the WAR to {{$ARTEMIS_HOME/web/}} and to {{bootstrap.xml}} and (re)start
the broker.
As far as I can tell, the {{test.xml}} topic registration is required by
artemis-rest to create the REST endpoint and mapping to a queue
({{FOO.topic/test}}) – at least, if omitted, the file will not appear.
Send a file via curl
{code:java}
curl -vvv -4 http://localhost:8161/rest/topics/FOO.topic/create -d
@/tmp/test.txt
{code}
Due to the non-existant link target {{[http://localhost:50001/]}} messages
will end up in {{DLQ}}.
Alternatively, pause queue {{FOO.topic/test}} to see messages there.
# open console
# expand 0.0.0.0 -> addresses -> FOO.topic -> queues -> multicast -> test
# switch to *Browse Queue*
# *Show* message
# as you can see, the message is not shown, neither bytes nor text, despite
being ~20k of size:
!broken_message.png!
> 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: artemis-rest-2.19.0.war, broken_message.png, 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)
