[jira] Created: (AXIS2-3160) Changing the timeout has no effect when reusing the same stub, and with HTTPConstants.REUSE_HTTP_CLIENT set to "true"

Changing the timeout has no effect when reusing the same stub, and with HTTPConstants.REUSE_HTTP_CLIENT set to "true"
---------------------------------------------------------------------------------------------------------------------

                 Key: AXIS2-3160
                 URL: https://issues.apache.org/jira/browse/AXIS2-3160
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: kernel, transports
    Affects Versions: 1.3
         Environment: Win XP SP2, Java 6 update 2
            Reporter: Chris Gibbs


In the constructor of a stub, I use the following code:

_getServiceClient().getOptions().setProperty(HTTPConstants.SO_TIMEOUT, timeout);
_getServiceClient().getOptions().setProperty(HTTPConstants.CONNECTION_TIMEOUT, timeout);
_getServiceClient().getOptions().setTimeOutInMilliSeconds(timeout);
_getServiceClient().getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT, "true");

This works fine - the timeout is set correctly, and the HTTP connections are being re-used correctly.

However, if I then reuse the same stub but change the timeout value, then the timeout of the underlying HTTP connection stays at the old value the next time a request is made. Setting REUSE_HTTP_CLIENT to "false" cause the timeout to be updated correctly.





--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@...
For additional commands, e-mail: axis-dev-help@...

     [ https://issues.apache.org/jira/browse/AXIS2-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davanum Srinivas resolved AXIS2-3160.
-------------------------------------

    Resolution: Won't Fix

> Changing the timeout has no effect when reusing the same stub, and with HTTPConstants.REUSE_HTTP_CLIENT set to "true"
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-3160
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3160
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel, transports
>    Affects Versions: 1.3
>         Environment: Win XP SP2, Java 6 update 2
>            Reporter: Chris Gibbs
>
> In the constructor of a stub, I use the following code:
> _getServiceClient().getOptions().setProperty(HTTPConstants.SO_TIMEOUT, timeout);
> _getServiceClient().getOptions().setProperty(HTTPConstants.CONNECTION_TIMEOUT, timeout);
> _getServiceClient().getOptions().setTimeOutInMilliSeconds(timeout);
> _getServiceClient().getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT, "true");
> This works fine - the timeout is set correctly, and the HTTP connections are being re-used correctly.
> However, if I then reuse the same stub but change the timeout value, then the timeout of the underlying HTTP connection stays at the old value the next time a request is made. Setting REUSE_HTTP_CLIENT to "false" cause the timeout to be updated correctly.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@...
For additional commands, e-mail: axis-dev-help@...

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

Davanum Srinivas commented on AXIS2-3160:
-----------------------------------------

this is by design. we populate the information to the shared http client only the first time.

-- dims

> Changing the timeout has no effect when reusing the same stub, and with HTTPConstants.REUSE_HTTP_CLIENT set to "true"
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-3160
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3160
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel, transports
>    Affects Versions: 1.3
>         Environment: Win XP SP2, Java 6 update 2
>            Reporter: Chris Gibbs
>
> In the constructor of a stub, I use the following code:
> _getServiceClient().getOptions().setProperty(HTTPConstants.SO_TIMEOUT, timeout);
> _getServiceClient().getOptions().setProperty(HTTPConstants.CONNECTION_TIMEOUT, timeout);
> _getServiceClient().getOptions().setTimeOutInMilliSeconds(timeout);
> _getServiceClient().getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT, "true");
> This works fine - the timeout is set correctly, and the HTTP connections are being re-used correctly.
> However, if I then reuse the same stub but change the timeout value, then the timeout of the underlying HTTP connection stays at the old value the next time a request is made. Setting REUSE_HTTP_CLIENT to "false" cause the timeout to be updated correctly.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@...
For additional commands, e-mail: axis-dev-help@...

     [ https://issues.apache.org/jira/browse/AXIS2-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Gibbs reopened AXIS2-3160:
--------------------------------


Although it probably wouldn't take much code to modify this? It would be very handy if the timeouts of the shared client can be modified after it has been created.

> Changing the timeout has no effect when reusing the same stub, and with HTTPConstants.REUSE_HTTP_CLIENT set to "true"
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-3160
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3160
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel, transports
>    Affects Versions: 1.3
>         Environment: Win XP SP2, Java 6 update 2
>            Reporter: Chris Gibbs
>
> In the constructor of a stub, I use the following code:
> _getServiceClient().getOptions().setProperty(HTTPConstants.SO_TIMEOUT, timeout);
> _getServiceClient().getOptions().setProperty(HTTPConstants.CONNECTION_TIMEOUT, timeout);
> _getServiceClient().getOptions().setTimeOutInMilliSeconds(timeout);
> _getServiceClient().getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT, "true");
> This works fine - the timeout is set correctly, and the HTTP connections are being re-used correctly.
> However, if I then reuse the same stub but change the timeout value, then the timeout of the underlying HTTP connection stays at the old value the next time a request is made. Setting REUSE_HTTP_CLIENT to "false" cause the timeout to be updated correctly.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@...
For additional commands, e-mail: axis-dev-help@...

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

Davanum Srinivas commented on AXIS2-3160:
-----------------------------------------

yes, it should be easy...would you mind taking a shot at submitting a patch? just grep for REUSE_HTTP_CLIENT thru the sources and you will see the spot.

thanks,
dims

> Changing the timeout has no effect when reusing the same stub, and with HTTPConstants.REUSE_HTTP_CLIENT set to "true"
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-3160
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3160
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel, transports
>    Affects Versions: 1.3
>         Environment: Win XP SP2, Java 6 update 2
>            Reporter: Chris Gibbs
>
> In the constructor of a stub, I use the following code:
> _getServiceClient().getOptions().setProperty(HTTPConstants.SO_TIMEOUT, timeout);
> _getServiceClient().getOptions().setProperty(HTTPConstants.CONNECTION_TIMEOUT, timeout);
> _getServiceClient().getOptions().setTimeOutInMilliSeconds(timeout);
> _getServiceClient().getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT, "true");
> This works fine - the timeout is set correctly, and the HTTP connections are being re-used correctly.
> However, if I then reuse the same stub but change the timeout value, then the timeout of the underlying HTTP connection stays at the old value the next time a request is made. Setting REUSE_HTTP_CLIENT to "false" cause the timeout to be updated correctly.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@...
For additional commands, e-mail: axis-dev-help@...