synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiranya Jayathilaka (JIRA)" <>
Subject [jira] Resolved: (SYNAPSE-660) Synchronization Issue in Synapse Hot Deployment Implementation
Date Wed, 09 Jun 2010 10:06:13 GMT


Hiranya Jayathilaka resolved SYNAPSE-660.

    Resolution: Fixed

Fixed in the trunk

> Synchronization Issue in Synapse Hot Deployment Implementation
> --------------------------------------------------------------
>                 Key: SYNAPSE-660
>                 URL:
>             Project: Synapse
>          Issue Type: Bug
>    Affects Versions: NIGHTLY
>            Reporter: Hiranya Jayathilaka
>            Assignee: Hiranya Jayathilaka
>             Fix For: 2.0
> The Axis2SynapseController calls the following method to load any custom mediator extensions
(.xar files) deployed to the server:
>         configurationContext.getAxisConfiguration().getConfigurator().loadServices();
> When hot deployment is enabled, the above call will start a timer task to handle hot
update events for the custom extensions. This task is in addition to the task initiated by
the Axis2 engine when the configuration context is created. Both these tasks will share a
single RepositoryListener instance thus running into all kinds of race conditions. As a result
the server encounters many issues related to hot deployment and hot update at runtime. Some
artifacts will be undeployed and deployed for no reason. Sometimes artifacts will be deployed
without first undeploying them.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message