[
https://issues.apache.org/jira/browse/AXIS2C-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555244#action_12555244
]
Manjula Peiris commented on AXIS2C-858:
---------------------------------------
For the observations above my settings in the httpd.conf are the following.
LoadModule axis2_module /usr/local/apache2/modules/mod_axis2.so
Axis2RepoPath /home/manjula/axis2/c/deploy
Axis2LogFile /tmp/axis2.log
Axis2MaxLogFileSize 1
Axis2LogLevel 2
<Location /axis2>
SetHandler axis2_module
</Location>
But when I changed the settings to the following the observations changed.
Axis2MaxLogFileSize 10
Axis2LogLevel crit
Now the request processing happened at the same speed and memory total usage
remains between 85-90% when I ran mtom client with 4MB attachment in a loop
from 3 shells.
> Apache runs out of memory and crashes with a simple mtom service test run in
> a loop
> -----------------------------------------------------------------------------------
>
> Key: AXIS2C-858
> URL: https://issues.apache.org/jira/browse/AXIS2C-858
> Project: Axis2-C
> Issue Type: Bug
> Components: core/engine
> Affects Versions: 1.1.0
> Environment: Linux 2.6 kernel
> Reporter: Subra A Narayanan
> Assignee: Manjula Peiris
>
> I have a simple mtom service written in Axis2/C which receives requests from
> clients with attachments. I wrote a client to consume this service and ran a
> test in a loop with 4 mb attachments. I noticed that the apache server ran
> out of memory and became very unresponsive after about 45 mins and then core
> dumped. The server response seemed to improve after some of the
> threads/processes died due to lack of memory and new threads were created to
> process the request.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
