axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Afkham Azeez (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AXIS2-5049) Axis2 Services / ServiceGroups Not Updating Properly When doing Hot-Update with Transport Session
Date Sun, 22 May 2011 06:06:47 GMT

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

Afkham Azeez commented on AXIS2-5049:
-------------------------------------

Yes, this is a real production requirement. Our argument that hot update is not necessary,
many years ago, is not valid in today's context.

Anyway, Anjana. I agree with your approach but there is a slight flaw. If there are requests
in flight, you must server those requests using the old service, then put the service into
maintenance mode (where new requests are temporarily rejected or held back), then switch to
the new service & serve the requests.

> Axis2 Services / ServiceGroups Not Updating Properly When doing Hot-Update with Transport
Session
> -------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-5049
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5049
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.5.4
>            Reporter: Anjana Fernando
>             Fix For: nightly
>
>         Attachments: AXIS2-5049-Patch.txt
>
>
> The scenario is explained in the following points,
> * AxisService in Transport Session Scope.
> * Incoming request.
> * Create ServiceContext, ServiceGroupContext from AxisService and AxisServiceGroup and
store it in SessionContext.
> * SessionContext contains fixed ServiceContext and ServiceGroupContext throughout Transport
Session lifetime.
> * Changes to AxisConfiguratio wont be known by SessionContext, removing of services to
service group, removing service group.
> * Removing Service Group, removing Service from service group must be communicated to
SessionContext, so it can remove the necessory items from itself, and refresh the services
/ service groups in the next request.
> Because of the above problem, when doing hotupdate, a service which is in transport session
will not be updated to the newly deployed service. Also, same for service groups, if a service
group was removed and added again, the service group that is in the ServiceGroupContext will
be the old service group. 
> Cheers,
> Anjana.

--
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


Mime
View raw message