You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/04/24 23:57:00 UTC

[jira] [Work logged] (AMQ-7467) A new XStream serializer is created on every message that flows through the broker causing high CPU utilization under load

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

ASF GitHub Bot logged work on AMQ-7467:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 24/Apr/20 23:56
            Start Date: 24/Apr/20 23:56
    Worklog Time Spent: 10m 
      Work Description: thodimi1 opened a new pull request #523:
URL: https://github.com/apache/activemq/pull/523


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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

            Worklog Id:     (was: 427131)
    Remaining Estimate: 0h
            Time Spent: 10m

> A new XStream  serializer is created on every message that flows through the broker causing high CPU utilization under load
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-7467
>                 URL: https://issues.apache.org/jira/browse/AMQ-7467
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: STOMP
>    Affects Versions: 5.13.5
>            Reporter: Murali Mogalayapalli
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> A new serailizer object is created to handle on each conversion from Openwire to STOMP. The serializer uses heavy reflection resulting a lot of GC and CPU utilization. This is un necessary and not scalable. One serilaizer could be created for each subscription and reutilize that for the subscription.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)