[prev in list] [next in list] [prev in thread] [next in thread] 

List:       rampart-dev
Subject:    [jira] [Issue Comment Edited] (AXIS2-5049) Axis2 Services /
From:       "Anjana Fernando (JIRA)" <jira () apache ! org>
Date:       2011-05-28 13:12:47
Message-ID: 397254173.50823.1306588367597.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


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

Anjana Fernando edited comment on AXIS2-5049 at 5/28/11 1:12 PM:
-----------------------------------------------------------------

Hi Hiranya,

Thank you for pointing it out. As we discussed offline, that can be fixed by \
reverting 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).

Cheers,
Anjana. 

      was (Author: anjana):
    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).

Cheers,
Anjana. 
  
> 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-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: 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


[prev in list] [next in list] [prev in thread] [next in thread]