Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Equinox OSGI - multiple instances

Anyone has other ideas as to why this might not work?

 

Thanks,
Deepa.

 

From: Desai, Deepalakshmi [Tech]
Sent: Wednesday, October 13, 2010 10:08 AM
To: Equinox development mailing list
Subject: RE: [equinox-dev] Equinox OSGI - multiple instances

 

I tried this option – didn’t work.

 

 

From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Thomas Watson
Sent: Wednesday, October 13, 2010 9:05 AM
To: Equinox development mailing list
Subject: Re: [equinox-dev] Equinox OSGI - multiple instances

 

I suspect the issue where the framework is stopping immediately after launch is because there are no non-daemon threads running. You can work around this issue by using -Dosgi.framework.activeThreadType=normal to force the framework to create a non-daemon thread as long as the framework is active. This prevents the VM from terminating the process. Also see https://bugs.eclipse.org/bugs/show_bug.cgi?id=310426. The osgi.framework.activeThreadType=normal is the default in 3.7 now.

With this setting you should not have to specify the console or port to keep the framework (VM) alive.

Tom



Inactive hide details for "Desai, Deepalakshmi [Tech]" ---10/12/2010 12:09:55 PM---We are using keepalive to start this as a da"Desai, Deepalakshmi [Tech]" ---10/12/2010 12:09:55 PM---We are using keepalive to start this as a daemon process.


From:


"Desai, Deepalakshmi [Tech]" <Deepalakshmi.Desai@xxxxxx>


To:


Equinox development mailing list <equinox-dev@xxxxxxxxxxx>


Date:


10/12/2010 12:09 PM


Subject:


Re: [equinox-dev] Equinox OSGI - multiple instances





We are using keepalive to start this as a daemon process.
And if I don’t specify the port it never starts the process - it keeps retrying.

As far as the bootdelegation=*? was concerned, it had trouble looking for jdk libraries when I didn't specify it earlier on.

For now I tried removing the bootdelegation=* option and also tried starting the second instance on a different port. I am still facing the same issue.

Thanks,
Deepa



-----Original Message-----
From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Neil Bartlett
Sent: Tuesday, October 12, 2010 12:44 PM
To: Equinox development mailing list
Subject: Re: [equinox-dev] Equinox OSGI - multiple instances

Hmm... the options seem to be out of order but it looks like you may
be specifying the same console port (9999) each time. The second
instance will fail to bind to the socket and therefore immediately
exit.

A couple of questions... what is the 9999 supposed to be for, and why
are you doing bootdelegation=*?

Regards,
Neil

On Tue, Oct 12, 2010 at 5:40 PM, Desai, Deepalakshmi [Tech]
<Deepalakshmi.Desai@xxxxxx> wrote:
>
> I have deployed a set of OSGI bundles on Linux java
> -Dorg.osgi.framework.bootdelegation=* -jar
> org.eclipse.osgi_3.5.2.R35x_v20100126.jar -console –clean 9999
> And these bundles have been configured within the config.ini
>
> I try and start another instance , and the process just gets killed.
>
> Am wondering if its ins’t possible to start multiple instances of the same
> bundles (may be with a different or even with the same configuration)?
> Is yes, can someone point me as to how I can do it.
>
> Any help will be appreciated.
>
> Thanks,
> Deepa.
>
>
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
>
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


Back to the top