[
https://issues.apache.org/jira/browse/AXIS2-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397468#comment-17397468
]
Robert Lazarski commented on AXIS2-6009:
----------------------------------------
Look for your log4j.properties and set org.apache.axis2 to TRACE. Note: we
switched to log4j2 in 1.8.0.
I would try something like this in 1.7.9 ... I dug this out of
OperationContextSaveTest.java, like I said I never attempted this. Might be
easier to upgrade.
OperationContext operationContext =
stub._getServiceClient().getLastOperationContext();
MessageContext outMessageContext =
operationContext.getMessageContext(WSDL2Constants.MESSAGE_LABEL_OUT);
TransportOutDescription transportOut = new TransportOutDescription("null");
transportOut.setSender(new HTTPClient4TransportSender());
outMessageContext.setTransportOut(transportOut);
> 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: [email protected]
For additional commands, e-mail: [email protected]
