[
https://issues.apache.org/jira/browse/AXIS2-5049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036470#comment-13036470
]
Deepal Jayasinghe edited comment on AXIS2-5049 at 5/19/11 9:14 PM:
-------------------------------------------------------------------
Nope, you approach does not scale well. This will work if you have few
sessions, but if the system have many sessions (say 1000), this approach does
not work. The reason is Axis2 has to notify each and every SessionContext.
The better approach would be to invalidate SessionContext if the ServiceGroup
has been updated after creating the SessionContext. You can do this using a
handler.
Deepal
was (Author: deepal):
Nope, you approach does not scale well. This will work if your have few
session, but if the system have many sessions (say 1000), this approach does
not work. The reason is Axis2 has to notify each and every SessionContext.
The better approach would be to invalidate SessionContext if the ServiceGroup
has been updated after creating the SessionContext. You can do this using a
handler.
Deepal
> 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-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
