[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] equinox standalone problem

Are you certain you are using the Thread.setDaemon(false) method? If you are not then the threads will inherit their daemon status from the invoking thread. If this happens to be one of the daemon framework threads then your bundle threads will be daemon also.

One quick way to find out is to run with a console and run the "threads" command. It will tell you the daemon status of your bundle threads.

Tom



Inactive hide details for "Karl Pauls" ---03/11/2008 05:14:20 PM---> Hi Karl,"Karl Pauls" ---03/11/2008 05:14:20 PM---> Hi Karl,


From:

"Karl Pauls" <karlpauls@xxxxxxxxx>

To:

"Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>

Date:

03/11/2008 05:14 PM

Subject:

Re: [equinox-dev] equinox standalone problem




> Hi Karl,
>
>  You are running into bug
>
https://bugs.eclipse.org/bugs/show_bug.cgi?id=215730

:-)

>  With 3.4 M5 you can set the configuration property
> osgi.framework.activeThreadType=normal to force a non-daemon thread be
> started so that the VM does not exit when the framework is running. The
> reason you see it stay up for 30 seconds is because there is a non-daemon
> thread spinning in the background waiting for a period of inactivity before
> persisting data. After it persists the data the thread exits and there is no
> other non-daemon thread alive to keep the VM running.

Well, that works but I don't really understand it. As I mentioned in
my previous mail, I actually have bundles installed that are creating
their own (non-daemon) threads so that should keep the jvm alive, no?

Thanks a lot for this workaround!

regards,

Karl

>  HTH
>
>  Tom
>
>
>
>  "Karl Pauls" ---03/11/2008 04:04:49 PM---Hi,
>
>
>
>
>  From:
>  "Karl Pauls" <karlpauls@xxxxxxxxx>
>
>  To:
>  equinox-dev@xxxxxxxxxxx
>
>  Date:
>  03/11/2008 04:04 PM
>
>  Subject:
>  [equinox-dev] equinox standalone problem ________________________________
>
>
>
>
>
> Hi,
>
>  I have a problem running equinox standalone. Basically, what I am
>  trying to do is to run equinox without a console. The set-up is as
>  follows:
>
>  equinox/
>   configuration/
>      config.ini
>   plugins/
>      <equinox jars>
>
>  > ../configuration/config.ini
>  osgi.bundles=<a set of bundles that use their own none daemon threads>
>  eclipse.ignoreApp=true
>  osgi.noShutdown=true
>
>  > java -jar org.eclipse.equinox.launcher_1.0.100.v20080303.jar -noExit
>
>  The above set-up does shutdown unexpectedly after a couple of seconds
>  (~ 30) on the first startup and immediately on subsequent ones.
>
>  I tried with all sorts of versions of equinox (including 3.3.2 3.4.M4
>  nightly, integration) and any combination of -Dosgi.noShutdown=true
>  config.ini/osgi.noShutdown=true and -noExit but to no avail. If I use
>  -console everything works fine.
>
>  Help would be much appreciated.
>
>  regards,
>
>  Karl
>
>  --
>  Karl Pauls
>  karlpauls@xxxxxxxxx
>  _______________________________________________
>  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
>
>



--
Karl Pauls
karlpauls@xxxxxxxxx
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

GIF image

GIF image