You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Rory Douglas <ro...@oracle.com> on 2009/01/16 20:19:11 UTC
SlingServerRepository configuration change - expected behavior?
If I select the SlingServerRepository configuration in the webconsole (
the .2423424etc configuration, not the factory configuration), change a
property (in this case, max idle sessions) and click "Save", I see a
second configuration gets created ( .44534534etc), and I start seeing
workspace lock errors from the RepositoryPinger.
I can fix this by just deleting the old configuration, but is this
expected behavior or a bug? I would expect this kind of behavior when
clicking "Create" on a factory config only.
Regards,
Rory
Re: SlingServerRepository configuration change - expected behavior?
Posted by Pontus Amberg <po...@milso.se>.
I've encountered the same problem and using the 1.2.3 web console from
Felix seems to have fixed the problem for me.
/Pontus
Felix Meschberger wrote:
> Hi Rory,
>
> I have tracked this down a bug in the web console, which actually
> creates a new factory configuration instance on each call to store the
> updated configuration. I created FELIX-885 [1] for this.
>
> I have committed a fix and deployed a SNAPSHOT version
> (1.2.3-20090118.131353-3) of the web console. Could you try with that
> version, whether your issue is fixed ? Many thanks.
>
> Regards
> Felix
>
> [1] https://issues.apache.org/jira/browse/FELIX-885
>
> Rory Douglas schrieb:
>
>> Looks like I'm running 1.2.2 of the console. I can reproduce this on
>> FireFox 3, Google Chrome and IE 6 (all on WinXP).
>>
>> Regards,
>> Rory
>>
>> Felix Meschberger wrote:
>>
>>> Hi Rory,
>>>
>>> Rory Douglas schrieb:
>>>
>>>
>>>> If I select the SlingServerRepository configuration in the webconsole (
>>>> the .2423424etc configuration, not the factory configuration), change a
>>>> property (in this case, max idle sessions) and click "Save", I see a
>>>> second configuration gets created ( .44534534etc), and I start seeing
>>>> workspace lock errors from the RepositoryPinger.
>>>>
>>>> I can fix this by just deleting the old configuration, but is this
>>>> expected behavior or a bug? I would expect this kind of behavior when
>>>> clicking "Create" on a factory config only.
>>>>
>>>>
>>> This really sounds like a bug. Clicking save should really just store
>>> the configuration.
>>>
>>> Are you using the SNAPSHOT version of the console or the latest 1.2.2
>>> release ? What browser are you using (I have a problem report with IE7).
>>>
>>> Regards
>>> Felix
>>>
>>>
>
>
Re: SlingServerRepository configuration change - expected behavior?
Posted by Felix Meschberger <fm...@gmail.com>.
Hi Rory,
Thanks for the feedback.
Regards
Felix
Rory Douglas schrieb:
> I grabbed the latest trunk of the webconsole & updated. This fixed the
> issue.
>
> Thanks Felix
> Regards,
> Rory
>
> Felix Meschberger wrote:
>> Hi Rory,
>>
>> I have tracked this down a bug in the web console, which actually
>> creates a new factory configuration instance on each call to store the
>> updated configuration. I created FELIX-885 [1] for this.
>>
>> I have committed a fix and deployed a SNAPSHOT version
>> (1.2.3-20090118.131353-3) of the web console. Could you try with that
>> version, whether your issue is fixed ? Many thanks.
>>
>> Regards
>> Felix
>>
>> [1] https://issues.apache.org/jira/browse/FELIX-885
>>
>> Rory Douglas schrieb:
>>
>>> Looks like I'm running 1.2.2 of the console. I can reproduce this on
>>> FireFox 3, Google Chrome and IE 6 (all on WinXP).
>>>
>>> Regards,
>>> Rory
>>>
>>> Felix Meschberger wrote:
>>>
>>>> Hi Rory,
>>>>
>>>> Rory Douglas schrieb:
>>>>
>>>>
>>>>> If I select the SlingServerRepository configuration in the
>>>>> webconsole (
>>>>> the .2423424etc configuration, not the factory configuration),
>>>>> change a
>>>>> property (in this case, max idle sessions) and click "Save", I see a
>>>>> second configuration gets created ( .44534534etc), and I start seeing
>>>>> workspace lock errors from the RepositoryPinger.
>>>>>
>>>>> I can fix this by just deleting the old configuration, but is this
>>>>> expected behavior or a bug? I would expect this kind of behavior when
>>>>> clicking "Create" on a factory config only.
>>>>>
>>>> This really sounds like a bug. Clicking save should really just store
>>>> the configuration.
>>>>
>>>> Are you using the SNAPSHOT version of the console or the latest 1.2.2
>>>> release ? What browser are you using (I have a problem report with
>>>> IE7).
>>>>
>>>> Regards
>>>> Felix
>>>>
>
Re: SlingServerRepository configuration change - expected behavior?
Posted by Rory Douglas <ro...@oracle.com>.
I grabbed the latest trunk of the webconsole & updated. This fixed the
issue.
Thanks Felix
Regards,
Rory
Felix Meschberger wrote:
> Hi Rory,
>
> I have tracked this down a bug in the web console, which actually
> creates a new factory configuration instance on each call to store the
> updated configuration. I created FELIX-885 [1] for this.
>
> I have committed a fix and deployed a SNAPSHOT version
> (1.2.3-20090118.131353-3) of the web console. Could you try with that
> version, whether your issue is fixed ? Many thanks.
>
> Regards
> Felix
>
> [1] https://issues.apache.org/jira/browse/FELIX-885
>
> Rory Douglas schrieb:
>
>> Looks like I'm running 1.2.2 of the console. I can reproduce this on
>> FireFox 3, Google Chrome and IE 6 (all on WinXP).
>>
>> Regards,
>> Rory
>>
>> Felix Meschberger wrote:
>>
>>> Hi Rory,
>>>
>>> Rory Douglas schrieb:
>>>
>>>
>>>> If I select the SlingServerRepository configuration in the webconsole (
>>>> the .2423424etc configuration, not the factory configuration), change a
>>>> property (in this case, max idle sessions) and click "Save", I see a
>>>> second configuration gets created ( .44534534etc), and I start seeing
>>>> workspace lock errors from the RepositoryPinger.
>>>>
>>>> I can fix this by just deleting the old configuration, but is this
>>>> expected behavior or a bug? I would expect this kind of behavior when
>>>> clicking "Create" on a factory config only.
>>>>
>>>>
>>> This really sounds like a bug. Clicking save should really just store
>>> the configuration.
>>>
>>> Are you using the SNAPSHOT version of the console or the latest 1.2.2
>>> release ? What browser are you using (I have a problem report with IE7).
>>>
>>> Regards
>>> Felix
>>>
>>>
--
Rory Douglas | Senior Principal Consultant
Fax: +1-201-604-6428 | Mobile: +1-917-498-5344
Oracle North America Consulting
ORACLE United States | | San Diego, CA
"Please consider your environmental responsibility before printing this
e-mail"
Re: SlingServerRepository configuration change - expected behavior?
Posted by Felix Meschberger <fm...@gmail.com>.
Hi Rory,
I have tracked this down a bug in the web console, which actually
creates a new factory configuration instance on each call to store the
updated configuration. I created FELIX-885 [1] for this.
I have committed a fix and deployed a SNAPSHOT version
(1.2.3-20090118.131353-3) of the web console. Could you try with that
version, whether your issue is fixed ? Many thanks.
Regards
Felix
[1] https://issues.apache.org/jira/browse/FELIX-885
Rory Douglas schrieb:
> Looks like I'm running 1.2.2 of the console. I can reproduce this on
> FireFox 3, Google Chrome and IE 6 (all on WinXP).
>
> Regards,
> Rory
>
> Felix Meschberger wrote:
>> Hi Rory,
>>
>> Rory Douglas schrieb:
>>
>>> If I select the SlingServerRepository configuration in the webconsole (
>>> the .2423424etc configuration, not the factory configuration), change a
>>> property (in this case, max idle sessions) and click "Save", I see a
>>> second configuration gets created ( .44534534etc), and I start seeing
>>> workspace lock errors from the RepositoryPinger.
>>>
>>> I can fix this by just deleting the old configuration, but is this
>>> expected behavior or a bug? I would expect this kind of behavior when
>>> clicking "Create" on a factory config only.
>>>
>>
>> This really sounds like a bug. Clicking save should really just store
>> the configuration.
>>
>> Are you using the SNAPSHOT version of the console or the latest 1.2.2
>> release ? What browser are you using (I have a problem report with IE7).
>>
>> Regards
>> Felix
>>
>
Re: SlingServerRepository configuration change - expected behavior?
Posted by Rory Douglas <ro...@oracle.com>.
Looks like I'm running 1.2.2 of the console. I can reproduce this on
FireFox 3, Google Chrome and IE 6 (all on WinXP).
Regards,
Rory
Felix Meschberger wrote:
> Hi Rory,
>
> Rory Douglas schrieb:
>
>> If I select the SlingServerRepository configuration in the webconsole (
>> the .2423424etc configuration, not the factory configuration), change a
>> property (in this case, max idle sessions) and click "Save", I see a
>> second configuration gets created ( .44534534etc), and I start seeing
>> workspace lock errors from the RepositoryPinger.
>>
>> I can fix this by just deleting the old configuration, but is this
>> expected behavior or a bug? I would expect this kind of behavior when
>> clicking "Create" on a factory config only.
>>
>
> This really sounds like a bug. Clicking save should really just store
> the configuration.
>
> Are you using the SNAPSHOT version of the console or the latest 1.2.2
> release ? What browser are you using (I have a problem report with IE7).
>
> Regards
> Felix
>
--
Rory Douglas | Senior Principal Consultant
Fax: +1-201-604-6428 | Mobile: +1-917-498-5344
Oracle North America Consulting
ORACLE United States | | San Diego, CA
"Please consider your environmental responsibility before printing this
e-mail"
Re: SlingServerRepository configuration change - expected behavior?
Posted by Felix Meschberger <fm...@gmail.com>.
Hi Rory,
Rory Douglas schrieb:
> If I select the SlingServerRepository configuration in the webconsole (
> the .2423424etc configuration, not the factory configuration), change a
> property (in this case, max idle sessions) and click "Save", I see a
> second configuration gets created ( .44534534etc), and I start seeing
> workspace lock errors from the RepositoryPinger.
>
> I can fix this by just deleting the old configuration, but is this
> expected behavior or a bug? I would expect this kind of behavior when
> clicking "Create" on a factory config only.
This really sounds like a bug. Clicking save should really just store
the configuration.
Are you using the SNAPSHOT version of the console or the latest 1.2.2
release ? What browser are you using (I have a problem report with IE7).
Regards
Felix