[
https://issues.apache.org/jira/browse/AXIS2-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294625#comment-13294625
]
Kishanthan Thangarajah commented on AXIS2-3818:
-----------------------------------------------
This issue is there in current trunk as-well. Even-though these two parameter
are getting initialized in the init method, but they are not used afterwords,
rather these two values again taken from transportOut parameters and then set
to messageContext. Looks like the same work is being done again in the invoke
method of CommonsHTTPTransportSender (line-176).
// set the timeout properties
Parameter soTimeoutParam =
transportOut.getParameter(HTTPConstants.SO_TIMEOUT);
Parameter connTimeoutParam =
transportOut.getParameter(HTTPConstants.CONNECTION_TIMEOUT);
// set the property values only if they are not set by the user
explicitly
if ((soTimeoutParam != null) &&
(msgContext.getProperty(HTTPConstants.SO_TIMEOUT) == null))
{
msgContext.setProperty(HTTPConstants.SO_TIMEOUT,
new Integer((String) soTimeoutParam.getValue()));
}
if ((connTimeoutParam != null) &&
(msgContext.getProperty(HTTPConstants.CONNECTION_TIMEOUT)
== null)) {
msgContext.setProperty(HTTPConstants.CONNECTION_TIMEOUT,
new Integer((String) connTimeoutParam.getValue()));
}
So i think the correct way here should be to use the values of those two
attributes which are already initialized, if they are not set by the user. I
can provide a fix for this.
Thanks,
Kishanthan.
> CommonsHTTPTransportSender - static timeout parameter are not handled properly
> ------------------------------------------------------------------------------
>
> Key: AXIS2-3818
> URL: https://issues.apache.org/jira/browse/AXIS2-3818
> Project: Axis2
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.4
> Reporter: Oliver Waeldrich
>
> The static timeout parameter of the axis2.xml configuration file are not
> handled properly in CommonsHTTPTransportSender. They are initialized properly
> in the init() method, but are not used at all when sending a message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]