You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/02/16 13:17:14 UTC

[jira] [Commented] (AMBARI-22754) STOMP message size limit should be configurable

    [ https://issues.apache.org/jira/browse/AMBARI-22754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367267#comment-16367267 ] 

Hudson commented on AMBARI-22754:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8744 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8744/])
AMBARI-22754. STOMP message size limit should be configurable. (mvp.202: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=f11859e3d27960c4106ae283733ac388488877e4])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/spring/AgentStompConfig.java


> STOMP message size limit should be configurable
> -----------------------------------------------
>
>                 Key: AMBARI-22754
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22754
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 3.0.0
>            Reporter: Myroslav Papirkovskyi
>            Assignee: Myroslav Papirkovskyi
>            Priority: Critical
>             Fix For: 3.0.0
>
>
> Default jetty and spring maximum size of message is 65536 bytes. This limitation causes intermittent exceptions during heavyweight messages transfering. Reproduced once for current alert definitions message and during HA enabling for command statuses. We should add ability to configure this limit.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)