You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@sling.apache.org by "Roll, Kevin" <Ke...@idexx.com> on 2015/10/30 20:16:54 UTC
Upgrading an installation
We are having an issue that I don't see addressed in the pages on the Sling Launcher. We build our own launcher which takes the standard bundles plus a few of our own and run it in standalone mode. The problem comes when we upgrade to a new version and provide a newer standalone launcher. It appears that the existing bundles are not overwritten with the newer versions. Is this expected behavior, and is there a safe, approved way to force the bundles to be upgraded? The server will be shut down when this takes place. Thanks!
RE: Upgrading an installation
Posted by "Roll, Kevin" <Ke...@idexx.com>.
That appears to be exactly our issue.
-----Original Message-----
From: Robert Munteanu [mailto:rombert@apache.org]
Sent: Wednesday, November 04, 2015 8:43 AM
To: users@sling.apache.org
Subject: Re: Upgrading an installation
On Wed, Nov 4, 2015 at 2:15 PM, Roll, Kevin <Ke...@idexx.com> wrote:
> Hi, Bertrand. I've been trying to think of how I could provide an example. Our basic scenario is that we have an installed Sling, we overwrite the standalone jar with one that contains a *new* bundle, and when we start the bundle is not there. Adding the 'upgrade' flag seems to have solved the issue.
Without knowing the details of your launcher, the problem sounds a
little bit like
https://issues.apache.org/jira/browse/SLING-3307
Of course, depending on your specific scenario, it might be unrelated.
Robert
>
> -----Original Message-----
> From: Bertrand Delacretaz [mailto:bdelacretaz@apache.org]
> Sent: Monday, November 02, 2015 10:05 AM
> To: users
> Subject: Re: Upgrading an installation
>
> Hi,
>
> On Fri, Oct 30, 2015 at 8:16 PM, Roll, Kevin <Ke...@idexx.com> wrote:
>> ...The problem comes when we upgrade to a new version and provide a
>> newer standalone launcher....
>
> Could you provide a minimal example (source code) that demonstrates the problem?
>
> I'm not saying it does not happen, just want to make sure we test it
> with the exact same setup as you do.
>
> -Bertrand
Re: Upgrading an installation
Posted by Robert Munteanu <ro...@apache.org>.
On Wed, Nov 4, 2015 at 2:15 PM, Roll, Kevin <Ke...@idexx.com> wrote:
> Hi, Bertrand. I've been trying to think of how I could provide an example. Our basic scenario is that we have an installed Sling, we overwrite the standalone jar with one that contains a *new* bundle, and when we start the bundle is not there. Adding the 'upgrade' flag seems to have solved the issue.
Without knowing the details of your launcher, the problem sounds a
little bit like
https://issues.apache.org/jira/browse/SLING-3307
Of course, depending on your specific scenario, it might be unrelated.
Robert
>
> -----Original Message-----
> From: Bertrand Delacretaz [mailto:bdelacretaz@apache.org]
> Sent: Monday, November 02, 2015 10:05 AM
> To: users
> Subject: Re: Upgrading an installation
>
> Hi,
>
> On Fri, Oct 30, 2015 at 8:16 PM, Roll, Kevin <Ke...@idexx.com> wrote:
>> ...The problem comes when we upgrade to a new version and provide a
>> newer standalone launcher....
>
> Could you provide a minimal example (source code) that demonstrates the problem?
>
> I'm not saying it does not happen, just want to make sure we test it
> with the exact same setup as you do.
>
> -Bertrand
RE: Upgrading an installation
Posted by "Roll, Kevin" <Ke...@idexx.com>.
Hi, Bertrand. I've been trying to think of how I could provide an example. Our basic scenario is that we have an installed Sling, we overwrite the standalone jar with one that contains a *new* bundle, and when we start the bundle is not there. Adding the 'upgrade' flag seems to have solved the issue.
-----Original Message-----
From: Bertrand Delacretaz [mailto:bdelacretaz@apache.org]
Sent: Monday, November 02, 2015 10:05 AM
To: users
Subject: Re: Upgrading an installation
Hi,
On Fri, Oct 30, 2015 at 8:16 PM, Roll, Kevin <Ke...@idexx.com> wrote:
> ...The problem comes when we upgrade to a new version and provide a
> newer standalone launcher....
Could you provide a minimal example (source code) that demonstrates the problem?
I'm not saying it does not happen, just want to make sure we test it
with the exact same setup as you do.
-Bertrand
Re: Upgrading an installation
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
On Fri, Oct 30, 2015 at 8:16 PM, Roll, Kevin <Ke...@idexx.com> wrote:
> ...The problem comes when we upgrade to a new version and provide a
> newer standalone launcher....
Could you provide a minimal example (source code) that demonstrates the problem?
I'm not saying it does not happen, just want to make sure we test it
with the exact same setup as you do.
-Bertrand
RE: Upgrading an installation
Posted by "Roll, Kevin" <Ke...@idexx.com>.
Hi, Robert. We are using Sling/Jackrabbit as a back-end data store for an application which is distributed across a wide number of client sites. We are mainly using Jackrabbit to store images, plus some servlets and tasks in Sling as supporting pieces. Building a standalone jar seemed like the easiest way to distribute this system - we just install one jar, run it, and all of Sling unpacks and becomes available, along with our additional code. The alternative would be to attempt installation of various bundles, which would require Sling to be up and running. If there is another way to do this I am certainly open to suggestions.
-----Original Message-----
From: Robert Munteanu [mailto:rombert@apache.org]
Sent: Friday, October 30, 2015 5:16 PM
To: users@sling.apache.org
Subject: Re: Upgrading an installation
Hi Kevin,
I have a suggestion and a question :-)
On Fri, Oct 30, 2015 at 9:16 PM, Roll, Kevin <Ke...@idexx.com> wrote:
> We are having an issue that I don't see addressed in the pages on the Sling Launcher. We build our own launcher which takes the standard bundles plus a few of our own and run it in standalone mode.
Why do you have your own launcher? Is there something not provided
out-of-the-box by Sling?
> The problem comes when we upgrade to a new version and provide a newer standalone launcher. It appears that the existing bundles are not overwritten with the newer versions. Is this expected behavior, and is there a safe, approved way to force the bundles to be upgraded? The server will be shut down when this takes place. Thanks!
Have you tried setting
-Dorg.apache.sling.launchpad.startupmode=update on the command line ?
Thanks,
Robert
Re: Upgrading an installation
Posted by Robert Munteanu <ro...@apache.org>.
Hi Kevin,
I have a suggestion and a question :-)
On Fri, Oct 30, 2015 at 9:16 PM, Roll, Kevin <Ke...@idexx.com> wrote:
> We are having an issue that I don't see addressed in the pages on the Sling Launcher. We build our own launcher which takes the standard bundles plus a few of our own and run it in standalone mode.
Why do you have your own launcher? Is there something not provided
out-of-the-box by Sling?
> The problem comes when we upgrade to a new version and provide a newer standalone launcher. It appears that the existing bundles are not overwritten with the newer versions. Is this expected behavior, and is there a safe, approved way to force the bundles to be upgraded? The server will be shut down when this takes place. Thanks!
Have you tried setting
-Dorg.apache.sling.launchpad.startupmode=update on the command line ?
Thanks,
Robert