[
https://issues.apache.org/jira/browse/AXIS2-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397406#comment-17397406
]
Eoghan O'Hare commented on AXIS2-6009:
--------------------------------------
I can possibly try to move to 1.8 however it is unlikely that would be a
solution for us since we are between releases. Likely we would not be able to
change the axis2 version until the next release.
When you say "upgrade your axis2.xml so it uses org.apache.http", what exactly
do you mean?
For the client side of the web services we are actually not using axis2.xml for
configuration.
Is there any additional logging that I can enable in axis2 to help identify the
issue in 1.7.9?
The problem is easily reproducible.
Really I am hoping for a workaround with the current axis2 version if at all
possible.
Thanks for the quick response.
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, axis2client.7z
>
>
> 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
