You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org> on 2010/06/09 11:02:27 UTC
[jira] Created: (SYNAPSE-660) Synchronization Issue in Synapse Hot
Deployment Implementation
Synchronization Issue in Synapse Hot Deployment Implementation
--------------------------------------------------------------
Key: SYNAPSE-660
URL: https://issues.apache.org/jira/browse/SYNAPSE-660
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-660) Synchronization Issue in Synapse Hot
Deployment Implementation
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka resolved SYNAPSE-660.
-----------------------------------------
Resolution: Fixed
Fixed in the trunk
> Synchronization Issue in Synapse Hot Deployment Implementation
> --------------------------------------------------------------
>
> Key: SYNAPSE-660
> URL: https://issues.apache.org/jira/browse/SYNAPSE-660
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org