You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Ian Boston <ie...@tfd.co.uk> on 2010/10/28 11:10:14 UTC
Bootloader not updating jars
Hi,
I might have missed a change in the launchpad/bootloader
When re rebuild the standalone jar with additional bundles or updatede bundles and restart and existing Sling instance, the new or updated bundles are not updated. The only way to update jars appears to be via one of the other methods (web console, file install, jcr installer).
Was there a change to the launchpad ?
I am sure this used to work.
Ian
Re: Bootloader not updating jars
Posted by Ian Boston <ie...@tfd.co.uk>.
Ok, thanks
We will have to find a work around, using one of the other techniques, I will talk to the production teams, they were building new jars as part of the deployment strategy and wondering why nothing was updating.
Ian
On 28 Oct 2010, at 10:57, Felix Meschberger wrote:
> Hi,
>
> IIRC we just discussed to remove this functionality from the launchpad
> and replace it with an extension to the OSGi Installer.
>
> But I do not exactly know where are standing here .... Maybe Carsten
> and/or Justin know more.
>
> Regards
> Felix
>
> Am Donnerstag, den 28.10.2010, 10:10 +0100 schrieb Ian Boston:
>> Hi,
>>
>> I might have missed a change in the launchpad/bootloader
>>
>> When re rebuild the standalone jar with additional bundles or updatede bundles and restart and existing Sling instance, the new or updated bundles are not updated. The only way to update jars appears to be via one of the other methods (web console, file install, jcr installer).
>>
>> Was there a change to the launchpad ?
>> I am sure this used to work.
>> Ian
>>
>
>
Re: Bootloader not updating jars
Posted by Ian Boston <ie...@tfd.co.uk>.
On 28 Oct 2010, at 21:07, Justin Edelson wrote:
>
> Better yet, set org.apache.sling.launchpad.force.package.bundle.loading to true, i.e.
>
> java -Dorg.apache.sling.launchpad.force.package.bundle.loading=true launchpad.jar -l INFO
>
> I forgot about that option.
>
> Justin
Hey, cool, thank you, I will pass that one on.
Ian
Re: Bootloader not updating jars
Posted by Justin Edelson <ju...@justinedelson.com>.
On Oct 28, 2010, at 7:43 AM, Ian Boston wrote:
>
> On 28 Oct 2010, at 12:29, Justin Edelson wrote:
>
>> I don't think that's happened yet. What might be happening is that the bundles aren't reloaded unless the timestamp of the launchpad base JAR has changed.
>
> Checked that,
> Recreated the jar, and the bundle jars inside with all the timestamps after everything in the sling folder. No update happens.
I'm almost 100% sure that's the problem. I just added some debug info, which you can see by running launchpad with -l INFO.
>
> Its not that much a problem we manage our servers with puppetd, and we can change the upgrade mechanism to loading over http or one of the felix mechanisms. (eg filesystem). The production team here don't like the idea of putting the jars in the JCR, so we probably wont use that one.
>
>>
>> Ian- try running a debugger and you should be able to see where in BootstapInstaller the decision is made to skip installation/upgrade.
>>
>> What I had to so is delete the bootstapinstaller.ser file manually. If this file is missing, bundles will always be installed/upgraded.
>
> Ok thats a good workaround and a safe switch, and upgrades just the new ones as before. If possible it would be really helpful to keep that "feature"
Better yet, set org.apache.sling.launchpad.force.package.bundle.loading to true, i.e.
java -Dorg.apache.sling.launchpad.force.package.bundle.loading=true launchpad.jar -l INFO
I forgot about that option.
Justin
> Thanks
> Ian
>
>>
>> Justin
>>
>> On Oct 28, 2010, at 5:57 AM, Felix Meschberger <fm...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> IIRC we just discussed to remove this functionality from the launchpad
>>> and replace it with an extension to the OSGi Installer.
>>>
>>> But I do not exactly know where are standing here .... Maybe Carsten
>>> and/or Justin know more.
>>>
>>> Regards
>>> Felix
>>>
>>> Am Donnerstag, den 28.10.2010, 10:10 +0100 schrieb Ian Boston:
>>>> Hi,
>>>>
>>>> I might have missed a change in the launchpad/bootloader
>>>>
>>>> When re rebuild the standalone jar with additional bundles or updatede bundles and restart and existing Sling instance, the new or updated bundles are not updated. The only way to update jars appears to be via one of the other methods (web console, file install, jcr installer).
>>>>
>>>> Was there a change to the launchpad ?
>>>> I am sure this used to work.
>>>> Ian
>>>>
>>>
>>>
>
Re: Bootloader not updating jars
Posted by Ian Boston <ie...@tfd.co.uk>.
On 28 Oct 2010, at 12:29, Justin Edelson wrote:
> I don't think that's happened yet. What might be happening is that the bundles aren't reloaded unless the timestamp of the launchpad base JAR has changed.
Checked that,
Recreated the jar, and the bundle jars inside with all the timestamps after everything in the sling folder. No update happens.
Its not that much a problem we manage our servers with puppetd, and we can change the upgrade mechanism to loading over http or one of the felix mechanisms. (eg filesystem). The production team here don't like the idea of putting the jars in the JCR, so we probably wont use that one.
>
> Ian- try running a debugger and you should be able to see where in BootstapInstaller the decision is made to skip installation/upgrade.
>
> What I had to so is delete the bootstapinstaller.ser file manually. If this file is missing, bundles will always be installed/upgraded.
Ok thats a good workaround and a safe switch, and upgrades just the new ones as before. If possible it would be really helpful to keep that "feature"
Thanks
Ian
>
> Justin
>
> On Oct 28, 2010, at 5:57 AM, Felix Meschberger <fm...@gmail.com> wrote:
>
>> Hi,
>>
>> IIRC we just discussed to remove this functionality from the launchpad
>> and replace it with an extension to the OSGi Installer.
>>
>> But I do not exactly know where are standing here .... Maybe Carsten
>> and/or Justin know more.
>>
>> Regards
>> Felix
>>
>> Am Donnerstag, den 28.10.2010, 10:10 +0100 schrieb Ian Boston:
>>> Hi,
>>>
>>> I might have missed a change in the launchpad/bootloader
>>>
>>> When re rebuild the standalone jar with additional bundles or updatede bundles and restart and existing Sling instance, the new or updated bundles are not updated. The only way to update jars appears to be via one of the other methods (web console, file install, jcr installer).
>>>
>>> Was there a change to the launchpad ?
>>> I am sure this used to work.
>>> Ian
>>>
>>
>>
Re: Bootloader not updating jars
Posted by Justin Edelson <ju...@gmail.com>.
I don't think that's happened yet. What might be happening is that the bundles aren't reloaded unless the timestamp of the launchpad base JAR has changed.
Ian- try running a debugger and you should be able to see where in BootstapInstaller the decision is made to skip installation/upgrade.
What I had to so is delete the bootstapinstaller.ser file manually. If this file is missing, bundles will always be installed/upgraded.
Justin
On Oct 28, 2010, at 5:57 AM, Felix Meschberger <fm...@gmail.com> wrote:
> Hi,
>
> IIRC we just discussed to remove this functionality from the launchpad
> and replace it with an extension to the OSGi Installer.
>
> But I do not exactly know where are standing here .... Maybe Carsten
> and/or Justin know more.
>
> Regards
> Felix
>
> Am Donnerstag, den 28.10.2010, 10:10 +0100 schrieb Ian Boston:
>> Hi,
>>
>> I might have missed a change in the launchpad/bootloader
>>
>> When re rebuild the standalone jar with additional bundles or updatede bundles and restart and existing Sling instance, the new or updated bundles are not updated. The only way to update jars appears to be via one of the other methods (web console, file install, jcr installer).
>>
>> Was there a change to the launchpad ?
>> I am sure this used to work.
>> Ian
>>
>
>
Re: Bootloader not updating jars
Posted by Felix Meschberger <fm...@gmail.com>.
Hi,
IIRC we just discussed to remove this functionality from the launchpad
and replace it with an extension to the OSGi Installer.
But I do not exactly know where are standing here .... Maybe Carsten
and/or Justin know more.
Regards
Felix
Am Donnerstag, den 28.10.2010, 10:10 +0100 schrieb Ian Boston:
> Hi,
>
> I might have missed a change in the launchpad/bootloader
>
> When re rebuild the standalone jar with additional bundles or updatede bundles and restart and existing Sling instance, the new or updated bundles are not updated. The only way to update jars appears to be via one of the other methods (web console, file install, jcr installer).
>
> Was there a change to the launchpad ?
> I am sure this used to work.
> Ian
>