[jira] [Commented] (FLEX-34648) [BLAZEDS]Memory Leak occurred in AsyncMessage when sending alot of

["Woo Ju Shin (JIRA)" <ji...@apache.org>]

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

Woo Ju Shin commented on FLEX-34648:
------------------------------------

I'm not quite sure about anything at this moment but could this be related to httpd or Tomcat version?
Recently, our web application caused Tomcat to crash. And we believe that this issue was the problem.
I couldn't retrieve any heap-dump from our customer but I reproduced the problem in our test env. from Srinath's comment.

The only changes made to that server was upgrading versions of apache-httpd and apache-tomcat.
We were using apache-httpd 2.2.27 and upgraded it to 2.2.31, apache-tomcat was 7.0.55 and upgraded to 7.0.64.
Running O/S is mainly RHEL 4.7 and 6.2.
The funny thing is that we could easily reproduce the problem on httpd 2.2.31 and tomcat 7.0.64, but not on httpd 2.2.27 and tomcat 7.0.55.

The following are parts of the configurations that we think matters.
[httpd-default.conf]
Timeout 300
KeepAlive On
[web.xml]
<session-config>
    <session-timeout>5</session-timeout>
</session-config>
[messaging-config.xml]
<destination id="destinationname">
    <network>
         <session-timeout>0</session-timeout>
    </network>
</destination>

> [BLAZEDS]Memory Leak occurred in AsyncMessage when sending alot of 
> -------------------------------------------------------------------
>
>                 Key: FLEX-34648
>                 URL: https://issues.apache.org/jira/browse/FLEX-34648
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: BlazeDS
>    Affects Versions: BlazeDS 4.7
>            Reporter: ibrahem.shawky@gmail.com
>            Assignee: Christofer Dutz
>            Priority: Critical
>
> a memory leak occurred when sending alot of AsyncMessage through BLAZEDS in a real time systems which is heavilly using messaging however we are increasing the jvm heap size  to 4 GB 80% of the size is occupied by AsyncMessage objects this is very clear from the generated heap dump.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)