[
https://issues.apache.org/jira/browse/SYNAPSE-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523837
]
Ruwan Linton commented on SYNAPSE-125:
--------------------------------------
Yes. I agree that this case is not dynamic.
That is because when we take the whole configuration from the registry, for it
to be dynamic we will have to rebuild the whole configuration at runtime which
introduces a downtime of nearly about 2 seconds (depends on the configuration)
for each and every cacheableDuration time period. This is not acceptable in
production envs. Thats why this was kept static.
I know that sample seems a little bit misleading. We will fix that sample
description.
If you want to keep a full registry based configuration you can put the
configuration in place and use registry based elements like sequences and
endpoints and refer to them in the configuration. But due to the above
described scenario proxy services are not dynamic (elements inside the proxy
like inSequence and outSequence can be dynamic though).
This sample demonstrates the fact that multiple synapse instances can share the
same configuration and if you put dynamic elements in there, by changing those
elements one can change the configuration of all the synapse instances.
> Synapse does not reload the configuration after "cachableDuration"
> ------------------------------------------------------------------
>
> Key: SYNAPSE-125
> URL: https://issues.apache.org/jira/browse/SYNAPSE-125
> Project: Synapse
> Issue Type: Bug
> Components: Deployment
> Affects Versions: 1.0
> Environment: Ubuntu, JDK 1.6
> Reporter: Eranga Jayasundera
> Attachments: repository.tar.gz
>
>
> I want to have a full registry based configuration as described in
> http://ws.apache.org/synapse/Synapse_Samples.html#Sample11. But I noticed
> that synapse does not reload the configuration after "cachableDuration". I
> have attached the configuration files used.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
