[ 
https://issues.apache.org/jira/browse/ARTEMIS-5483?focusedWorklogId=1005105&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1005105
 ]

ASF GitHub Bot logged work on ARTEMIS-5483:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 13/Feb/26 15:10
            Start Date: 13/Feb/26 15:10
    Worklog Time Spent: 10m 
      Work Description: AlexejTimonin commented on PR #5689:
URL: https://github.com/apache/artemis/pull/5689#issuecomment-3897727586

   Thanks for getting back to me. I will modify my PR according to your 
suggestions.
   
   




Issue Time Tracking
-------------------

    Worklog Id:     (was: 1005105)
    Time Spent: 0.5h  (was: 20m)

> Provide option to abort consumption of large javax.jms.TextMessage on client 
> side
> ---------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-5483
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5483
>             Project: Artemis
>          Issue Type: Improvement
>          Components: JMS
>            Reporter: Alexej Timonin
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> This improvement request comes from thread in [email protected]:
> Artemis JMS client: Can I stream body of ActiveMQTextMessage? 
> https://lists.apache.org/thread/t2bmc8g6tod1wlqz062g46gpwv52v2y5
> Provide an option for clients using JMS api through artemis-jakarta-client to 
> detect when a javax.jms.TextMessage is so large it would crash the client 
> because of out-of-memory errors.
> As it is now, a buggy producer can send a text message (type 3) so large that 
> it would crash the consumer because the current implementation of JMS 
> consumer reads whole text message into memory.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to