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

Eoghan O'Hare commented on AXIS2-6009:
--------------------------------------

Ok I got rid of axis2.xml and set the transportOut manually from the code - I 
had to call the init method explicitly;
{quote}TransportOutDescription transportOut = new 
TransportOutDescription("https");

HTTPClient4TransportSender sender = new HTTPClient4TransportSender(); 
{color:#de350b}sender.init(stub._getServiceClient().getServiceContext().getConfigurationContext(),
 transportOut);{color} transportOut.setSender(sender);

options.setTransportOut(transportOut);
{quote}
This seemed to now at least get me past the null pointer exception in axis2 
that I pointed out above.

For the SSL connection I had to use some deprecated classes to create the 
cached client;
{quote}SSLSocketFactory sf = new 
SSLSocketFactory(sslSocketFactory.getSSLContext());SSLSocketFactory sf = new 
SSLSocketFactory(sslSocketFactory.getSSLContext());    
sf.setHostnameVerifier(SSLSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER);    Scheme 
httpsScheme = new Scheme("https", 443, sf);    SchemeRegistry schemeRegistry = 
new SchemeRegistry();        schemeRegistry.register(httpsScheme); 
ClientConnectionManager conmgr = new 
PoolingClientConnectionManager(schemeRegistry); DefaultHttpClient client = new 
DefaultHttpClient(conmgr);
{quote}
Previously I tried to use the HttpClientBuilder, however the 
CloseableHttpClient that was returned was not compatible with the property 
HTTPConstants.CACHED_HTTP_CLIENT. Threw a class cast exception in axis2.

Using these deprecated classes is not great but I could not find another way 
around it, unfortunately.

At this point, the web service request is now being sent using HttpClient4.

However when the web service response is received the callback methods that 
have been registered in the auto generated stubs are not being called.

To even get to this stage it has taken a lot of my time to be honest. Can you 
help with this callback issue? Any idea please would be great. 

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

Reply via email to