[
https://issues.apache.org/jira/browse/SYNAPSE-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiranya Jayathilaka updated SYNAPSE-903:
----------------------------------------
Fix Version/s: (was: NIGHTLY)
3.0
> 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
> Assignee: Hiranya Jayathilaka
> Fix For: 3.0
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
