You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Prabath Abeysekara (JIRA)" <ji...@apache.org> on 2012/08/08 04:23:09 UTC
[jira] [Created] (SYNAPSE-903) Data sources used in DB mediators
are closed without considering the fact that the associated datasource is
configured globally, while hot-updating a proxy service.
Prabath Abeysekara created SYNAPSE-903:
------------------------------------------
Summary: Data sources used in DB mediators are closed without considering the fact that the associated datasource is configured globally, while hot-updating a proxy service.
Key: SYNAPSE-903
URL: https://issues.apache.org/jira/browse/SYNAPSE-903
Project: Synapse
Issue Type: Bug
Components: Core
Reporter: Prabath Abeysekara
Let's assume we have a proxy service that has DBLookup mediator configured to use a globally defined datasources in one of its sequences. There, if we hot update the service, like you mentioned, the existing service is stopped and all the mediator life cycles configured would also be destroyed. When the AbstractDBMediator's destroy method gets invoked, it closes the associated datasource without considering the fact that it is configured globally. Therefore the subsequent invocations fail as the datasource has already been closed
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] [Updated] (SYNAPSE-903) Data sources used in DB mediators
are closed without considering the fact that the associated datasource is
configured globally, while hot-updating a proxy service.
Posted by "Prabath Abeysekara (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prabath Abeysekara updated SYNAPSE-903:
---------------------------------------
Attachment: SYNAPSE-903.patch
Attaching the patch to fix the issue. Please review and apply.
Regards,
Prabath
> Data sources used in DB mediators are closed without considering the fact that the associated datasource is configured globally, while hot-updating a proxy service.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SYNAPSE-903
> URL: https://issues.apache.org/jira/browse/SYNAPSE-903
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Reporter: Prabath Abeysekara
> Attachments: SYNAPSE-903.patch
>
>
> Let's assume we have a proxy service that has DBLookup mediator configured to use a globally defined datasources in one of its sequences. There, if we hot update the service, like you mentioned, the existing service is stopped and all the mediator life cycles configured would also be destroyed. When the AbstractDBMediator's destroy method gets invoked, it closes the associated datasource without considering the fact that it is configured globally. Therefore the subsequent invocations fail as the datasource has already been closed
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org