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 Sat, 28 May 2011 12:36:48 GMT


Anjana Fernando commented on AXIS2-5049:

Hi Hiranya,

Thank you for pointing it out. As we discussed offline, that can be fixed by revering it to
the earlier list implementation and simply using another variable for the SessionContext observers
to track it's inclusions as AxisObservers. But I also came across another problem, since we
are putting the SessionContexts as AxisObservers, these will never be taken out, so these
will continue to grow as users make new sessions and they will never be garbage collected,
which is a significant problem. So please ignore the above patches, and we would have to figure
out a better approach to do this.

I did see a comment in AbstractContext class's "touch" method, which mentioned about a timer
task cleaning up the contexts, but I couldn't find the place it was actually doing that (the
timer task).


> 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-2.txt, 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