axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anjana Fernando (JIRA)" <>
Subject [jira] [Commented] (AXIS2-5049) Axis2 Services / ServiceGroups Not Updating Properly When doing Hot-Update with Transport Session
Date Thu, 19 May 2011 21:51:47 GMT


Anjana Fernando commented on AXIS2-5049:

Hi Deepal,

Well, if I understood it correctly, your approach will also have problems, where this will
incur a performance overhead on the actual service invocations, where as, what I suggested
just happens at deployment time. 

Because, lets say 1000 unique sessions / 1000 users, will be sending requests, for each request
from each of the user, the handler will check if the SessionContext has valid service group
context's and service contexts inside that group, so there's some logic that needs to be executed
to check whether those contexts are valid and up to date against the ServiceGroups and Services.

So compared to that, what I suggested will only happen when a change to a service group /
service has occurred and then notified to the SessionContexts, so 1 time 1000 notifications
at once. But in what you suggested, there will always be 1000 sessions (provided they are
sending requests often), sending 1000 requests always to check up on a state that most probably
have not changed for a while.


> Axis2 Services / ServiceGroups Not Updating Properly When doing Hot-Update with Transport
> -------------------------------------------------------------------------------------------------
>                 Key: AXIS2-5049
>                 URL:
>             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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message