I think there's a JIRA raised for that already.
Fileinstall runs into a loop when it saves back the modified configuration.

On Tue, Nov 30, 2010 at 12:04, Felix Meschberger <[email protected]> wrote:
> Hi Carl,
>
> Are you using a SNAPSHOT build of FileInstall, which writes back any
> configurations when receiving an Configuration event ?
>
> Could it be that FileInstall too eagerly writes back and then notices a
> new configuration and writes back (due to configuration event) and then
> notices a new configuration and .... ?
>
> Regards
> Felix
>
> Am Montag, den 29.11.2010, 23:12 -0500 schrieb Carl Hall:
>> I have an assembly that puts together Felix and various needed bundles.
>>  Along with this, I include a load/ directory with a couple of
>> configurations I'd like to deploy.  Whenever I include these cfg files, I
>> get messages like below.  If I remove them the messages stop as expected.
>>  When a cfg file is returned to load/, the messages start again.  This
>> pattern is also seen if I introduce the cfg files after the start of the
>> server.  Is there something I should change?  These messages continue ad
>> nauseum.
>>
>> 29.11.2010 23:05:20.039 *INFO* [CM Event Dispatcher (Fire
>> ConfigurationEvent:
>> pid=cans.aa.datasource.mysql.DataSourceProvider.f35e3f24-bf9c-4000-bf25-eeca324c89ec)]
>> cans.aa.datasource.mysql Service [85] ServiceEvent REGISTERED
>> 29.11.2010 23:05:24.042 *INFO* [CM Event Dispatcher (Fire
>> ConfigurationEvent:
>> pid=cans.aa.datasource.mysql.DataSourceProvider.f35e3f24-bf9c-4000-bf25-eeca324c89ec)]
>> cans.aa.datasource.mysql Service [85] ServiceEvent UNREGISTERING
>> 29.11.2010 23:05:24.047 *INFO* [CM Event Dispatcher (Fire
>> ConfigurationEvent:
>> pid=cans.aa.datasource.mysql.DataSourceProvider.f35e3f24-bf9c-4000-bf25-eeca324c89ec)]
>> cans.aa.datasource.mysql Service [86] ServiceEvent REGISTERED
>> 29.11.2010 23:05:28.048 *INFO* [CM Event Dispatcher (Fire
>> ConfigurationEvent:
>> pid=cans.aa.datasource.mysql.DataSourceProvider.f35e3f24-bf9c-4000-bf25-eeca324c89ec)]
>> cans.aa.datasource.mysql Service [86] ServiceEvent UNREGISTERING
>> 29.11.2010 23:05:28.053 *INFO* [CM Event Dispatcher (Fire
>> ConfigurationEvent:
>> pid=cans.aa.datasource.mysql.DataSourceProvider.f35e3f24-bf9c-4000-bf25-eeca324c89ec)]
>> cans.aa.datasource.mysql Service [87] ServiceEvent REGISTERED
>> 29.11.2010 23:05:32.055 *INFO* [CM Event Dispatcher (Fire
>> ConfigurationEvent:
>> pid=cans.aa.datasource.mysql.DataSourceProvider.f35e3f24-bf9c-4000-bf25-eeca324c89ec)]
>> cans.aa.datasource.mysql Service [87] ServiceEvent UNREGISTERING
>> 29.11.2010 23:05:32.060 *INFO* [CM Event Dispatcher (Fire
>> ConfigurationEvent:
>> pid=cans.aa.datasource.mysql.DataSourceProvider.f35e3f24-bf9c-4000-bf25-eeca324c89ec)]
>> cans.aa.datasource.mysql Service [88] ServiceEvent REGISTERED
>> 29.11.2010 23:05:34.056 *INFO* [CM Event Dispatcher (Fire
>> ConfigurationEvent:
>> pid=cans.aa.datasource.mysql.DataSourceProvider.f35e3f24-bf9c-4000-bf25-eeca324c89ec)]
>> cans.aa.datasource.mysql Service [88] ServiceEvent UNREGISTERING
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to