[
https://issues.apache.org/jira/browse/AXIS2-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404632#comment-17404632
]
Eoghan O'Hare commented on AXIS2-6009:
--------------------------------------
Hi,
I increased the number of open files limit in /etc/security/limits.conf;
* soft nofile 10000
I rebooted the server afterwards.
The ulimit displays the updated value.
[root@pmdpriepm52 ~]# ulimit -H -n
262144
[root@pmdpriepm52 ~]# ulimit -S -n
10000
I re-ran the load test, same issue though, only 5 http connections created and
delays.
Not sure if you have access to this link, its a RHEL document regarding ulimits
and the fact that JAVA does not honour them by default of the hard and soft
limits are different.
[https://access.redhat.com/solutions/1339423]
Rough details;
{quote}Java process ignores the soft limit of "open files" (file descriptor)
setting for the user and it increases to the hard limit. So, its "max file
descriptor" is different from the result of "ulimit -n" of the user. For
example, "file descriptor (open files)" for the user of Java process is set to
{{1024}}
h2. Resolution
* It's expected behavior if *soft limit* and *hard limit* of "file descriptor"
for the user are different.
* Java option *{{-XX:+MaxFDLimit}}* is enabled by default. And, when this
option is enabled, {{setrlimit}} is called, and "file descriptor" is increased
to the hard limit internally inside Java VM.
* If you do not like this behavior, you can set Java option
*{{-XX:-MaxFDLimit}}* to disable it.
{quote}
{{}}
The hard and soft limits for root would be different as seen from above
outputs. The client test application is running under root.
Regards,
Eoghan
> ServiceClient::createClient intermittently under load blocks for 5 seconds
> --------------------------------------------------------------------------
>
> Key: AXIS2-6009
> URL: https://issues.apache.org/jira/browse/AXIS2-6009
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.7.9
> Reporter: Eoghan O'Hare
> Priority: Major
> Attachments: ExceptionStackTrace.txt, axis2.xml, axis2client.7z,
> axis2client_httpclient4.log
>
>
> Using the axis2-kernel-1.7.9.jar.
> Our application is using automatically generated WS stubs for asynchronous
> SOAP web services over https.
> ServiceClient::createClient is called for every asynchronous web service
> request.
> Callbacks are registered using OperationClient::setCallback().
> The non blocking web service request is sent by the API
> OperationClient::execute(false).
> The option isUseSeparateListener is set to false.
> The default number of http connections are created, this is two from looking
> at pcap traces.
> Under low load rates, 20 requests per second, 1000 total requests,
> intermittently the call to ServiceClient::createClient blocks the calling
> thread for 5 seconds. Seems to be just over 5 seconds every time it occurs
> (between 5000ms and 5030ms), so it sounds like some timeout.
> The blocking seems to occur when a response to a previous web service is
> received at a similar time.
> After the 5 second blocking, an Exception is thrown from axis2 to our
> applications error callback. Exception stack trace is attached.
> I have tried to enable axis2 logging on the client side however there was
> nothing obvious in it from my point of view. Attaching the log. In the log
> the 5 second delay is between;
> 06:47:50:574
> 06:47:55:579
> If you require additional logging to be enabled to debug please let me know.
> Or if you need any further information, please let me know.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
