[prev in list] [next in list] [prev in thread] [next in thread]
List: axis-dev
Subject: [jira] [Created] (AXIS2-5100) AbstractHTTPSender.initializeTimeouts
From: "Igor Kamyshnikov (JIRA)" <jira () apache ! org>
Date: 2011-07-26 8:07:09
Message-ID: 1219712052.6849.1311667629678.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]
AbstractHTTPSender.initializeTimeouts changes timeouts for shared HttpClient which is \
not thread safe
-----------------------------------------------------------------------------------------------------
Key: AXIS2-5100
URL: https://issues.apache.org/jira/browse/AXIS2-5100
Project: Axis2
Issue Type: Bug
Components: transports
Reporter: Igor Kamyshnikov
Priority: Minor
I have tried to set default timeouts for shared HttpClient in shared \
ConfigurationContext but it appears it is not possible to make it work because each \
call of AxisEngine.send(msgContext) (e.g. from OutInAxisOperation) overrides timeouts \
of HttpClient from MessageContext (where this timeout might not be even defined \
causing to use default 30 seconds timeout).
More over it appears it a threading issue because HttpClient could be shared by a \
number of threads. That's why I don't understand why configuration of HttpClient is \
changed by each call of AxisEngine.send.
This makes me not to use shared ConfigurationContext with shared HttpClient with \
MultithreadedHttpConnectionManager. It is required to create ConfigurationContext \
(and HttpClient, and HttpConnectionManager) for each stub instance.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic