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

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

                Author: ASF GitHub Bot
            Created on: 10/Mar/26 17:52
            Start Date: 10/Mar/26 17:52
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on PR #5689:
URL: https://github.com/apache/artemis/pull/5689#issuecomment-4033349202

   I am not sure if I set  HDR_LARGE_MESSAGE_SIZE with the original body size 
now (I don't remember). but if I do, we could change this method to play with 
that value:
   
   
https://github.com/apache/artemis/blob/a718bc5932fbb578ba48eecbd8d2a7f7a762701b/artemis-server/src/main/java/org/apache/activemq/artemis/core/persistence/impl/journal/LargeServerMessageImpl.java#L219-L227
   
   
   if not set, then we should set the original header size somehow. 
   
   
   We would need a test playing with an actual large message and do the proper 
filter to play with this.




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

    Worklog Id:     (was: 1008879)
    Time Spent: 1.5h  (was: 1h 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: 1.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